We performed a comparison between LeanIX and ServiceNow based on real PeerSpot user reviews.
Find out what your peers are saying about LeanIX, Sparx Systems, erwin by Quest and others in Enterprise Architecture Management."The most valuable feature would be application portfolio management, which is where they came from, but over time, they have got artificial intelligence. They built up a very good repository. If I identify a system by name, from historical information, oftentimes, they can tell me that this is deployed with this number of CPUs and they can give me a really good profile of the application for me to put it into a change management database with very little effort."
"We've been able to develop some nice looking reports, and the dashboard's capability to map is very easy compared to Enterprise Architect."
"The ability to import data and generate reports from it. That's where its power lies."
"The solution has a very useful assessment tool that automatically populates from input data to produce a detailed analysis of customer's environments."
"The solution provides a single window view of business, application, data, and technology views of the IT ecosystem."
"The most valuable features are that it's user-friendly and the user experience. It's easy to map the fact sheets."
"Ease of use is the most valuable feature. From an enterprise architecture perspective, it's not too cumbersome with too many functionalities, yet it has a lot of attributes for the content it covers."
"One of the product's most valuable features is its ability to configure hardware devices."
"ServiceNow is very easy to set up."
"Being able to have the required information for project management is valuable. I've got multiple people accessing it, and I'm tracking tasks with percentages done. It allows me to have detailed notes and provides the ability to attach documents. I have used a lot of project management solutions, and there were gaps in terms of what was available. ServiceNow has got all the features and functionalities. It is a solid solution. It is also easy to get into and use. It is certainly highly scalable."
"The biggest feature is that it is cloud-based, so it's always updated, it's always current. We don't have to worry about patches, revisions. We're always working with the latest version."
"I don't have to look through a whole bunch of other incidents that aren't relevant to me. It's very useful in that sense."
"I like the reporting aspect of it. It helps us know where we stand regarding the types of issues we're receiving... It also shows us trends. That enables us to possibly predict an issue that might come up in the future as well as what is happening right now. We will like that feature. With it, we can either avoid certain issues or know where we need to focus more regarding the service we provide."
"The analytics - we like to keep track of how much work everyone is doing."
"Creating a ticket is much simpler in this tool. That is one big advantage. Also, the simplicity and ease of use are much better. I've used HPSM and it is very complex in comparison to ServiceNow."
"ServiceNow has been implemented to streamline team workflows across different departments in our company. Users, including traveling leaders, were able to approve requests and authorize additional rights through the mobile platform."
"Does a poor job of being able to allocate detailed costings to components within the network."
"Another area for improvement is that when you're starting to look into more advanced information, using the solution's APIs and its customizations, documentation for that specific aspect is not very good. There is not too much support built into the offering for that aspect, for a developer."
"The solution uses Gartner's time-based framework for application rationalization. One more thing that you can consider is having some add-on frameworks for the same, not just Gartner."
"What would make LeanIX better is more variety in terms of reporting, and more flexibility with its data importing feature."
"Not a ten because you always have that gap between complexity and easy to use. And the more complex the tool becomes, the more difficult it is to get the usability."
"The solution’s API integration needs to improve. I would like to see a digital screen watch feature also in the solution."
"They're probably positioned pretty well. I hope that they would not focus that much on the business architecture, and they would focus more on the overall cloud strategy and how we can leverage multi-cloud and transition back and forth from other cloud providers. With a lot of current vendors, you get locked in with one cloud, and then you try to migrate to someone else, and it becomes very problematic. What they need to do is to look at the overall data strategy, and they probably need to amplify their data strategy, especially around multi-cloud."
"Report generation could be more detailed. There are some shortcomings when creating reports. We can't create tag-based reports or go beyond basic technical reports."
"The user interface for accessing assistance sometimes disconnects."
"They need to be providing vendors and implementation partners with materials and guidance on implementation."
"Performance could be improved."
"The user interface could be much improved, and the developer tools and sets can be improved greatly, they are lacking."
"They could improve license management, particularly when integrating different applications or toolsets."
"The technical support SLA can be improved because sometimes they take a long time to answer our queries."
"I would like the reporting aspect to be better, including the graphs. It could have some way for us to easily to export to a csv or spreadsheet so that if a graph cannot be provided by ServiceNow itself, we would be able to use other applications to create them. Also, if there was a feature that enabled us to interact with end users directly from ServiceNow, like an instant-messaging type of feature, that would be great."
"The installation and deployment of ServiceNow can be a bit challenging. One major issue I've encountered is that ServiceNow doesn't provide the same mobile responsiveness or features that we used to enjoy with other tools. For example, with Splunk, our response times were about five minutes, and we could manage alerts and incidents directly from our mobile devices."
LeanIX is ranked 1st in Enterprise Architecture Management with 18 reviews while ServiceNow is ranked 1st in IT Service Management (ITSM) with 212 reviews. LeanIX is rated 8.6, while ServiceNow is rated 8.4. The top reviewer of LeanIX writes "Streamlines the process of identifying apps nearing end-of-life or requiring retirement and facilitates informed decisions about app retention". On the other hand, the top reviewer of ServiceNow writes "A stable and scalable solution that has excellent features and is useful for collecting data and building KPIs". LeanIX is most compared with Sparx Systems Enterprise Architect, MEGA HOPEX, ADOIT, iServer and Avolution ABACUS, whereas ServiceNow is most compared with BMC Helix ITSM, Microsoft Power Apps, Pega BPM, Appian and JIRA Service Management.
We monitor all Enterprise Architecture Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
LeanIX has a ServiceNow connector for easy integration, that comes as add-on to the price of product.
Yes, there are number of use cases that such integration can be valuable. One example is identifying “crown jewels” asserts for the Risk Management. LeanIX can have application and data making plus application criticality, while SN can have an Application-to Asset mapping. Those together will provide critical assets that can be managed in a specific way in SN.
ServiceNow is an ITSM tool but does not enable development and operationalization of business/enterprise (process, capability, strategy) and IT architectures (it does handle physical structures but does not integrate with the models that describe the business as a whole which ideally should be the driver for IT decision making).
Architectures should be developed and managed in an architecture tool (i.e. QualiWare) that spans your organization which then feeds your IT operations area information as to application lifecycle, system valid to/from dates, etc. Your operational systems (i.e. Cherwell/Ivanti, ServiceNow) should feed performance and issues stats back to the architecture tool to provide a more comprehensive picture of the organization enabling management to make better strategic, business and technology investment decisions.
That is why a bidirectional link is required...
IMHO, ServiceNow is a complete ITSM tool, designed to support tradictional/waterfall and digital/agile "business" and is completely adherent with ITIL (and others frameworks). LeanIX offers a more limited setup of inventary, correlation and others tools (for example, offers only few ITIL domains), such as showed here https://docs.leanix.net/docs.
For market-time, features and maturity i'll choice ServiceNow but the price may be a problem.