G2

rohi v.

Senior ServiceNow Developer

Enterprise (> 1000 emp.)

9/15/2026

Business partner of the seller or seller's competitor, not included in G2 scores.

"Connected Architecture Data and CMDB Integration for Clearer Impact Visibility"

4.5/5

What do you like best about ServiceNow Enterprise Architecture?

As a ServiceNow developer, I find the centralized application and technology portfolio particularly useful. I use Enterprise Architecture to work with application information, business capabilities, technology models, relationships, ownership, and lifecycle information in the ServiceNow platform.

The ability to relate architecture data with CMDB and other ServiceNow data is valuable when reviewing application dependencies and understanding the potential impact of changes. Application portfolio and technology lifecycle information also helps identify applications or technologies that require review, rationalization, or modernization.

I also find the dashboards and portfolio views useful for presenting architecture information to different stakeholders. From a development perspective, the platform's configurable data model, relationships, views, and governance capabilities provide flexibility to align the solution with organizational architecture processes. Review collected by and hosted on G2.com.

What do you dislike about ServiceNow Enterprise Architecture?

The main challenge I have experienced is the learning curve. Enterprise Architecture has several related data objects, relationships, portfolio concepts, and configuration options, so understanding how everything fits together takes some time, particularly for developers who are new to the product.

I also find that some implementations require significant configuration and data preparation before the platform provides meaningful portfolio insights. When working with a large application portfolio, maintaining relationships and keeping the underlying data accurate can require ongoing effort.

The UI provides useful portfolio and relationship views, but navigating between related architecture records can sometimes feel complex. More guided configuration and simpler bulk data maintenance would make the experience easier. Review collected by and hosted on G2.com.

What problems is ServiceNow Enterprise Architecture solving and how is that benefiting you?

ServiceNow Enterprise Architecture helps solve the problem of fragmented architecture information by bringing applications, business capabilities, technologies, ownership, lifecycle data, and relationships into a common platform. This gives technical and business teams a clearer view of the overall technology landscape and helps with application rationalization, modernization, and lifecycle decisions.

The integration with CMDB and other ServiceNow capabilities is one of the biggest benefits because architecture information can be connected with operational and configuration data. This makes it easier to understand dependencies and assess the potential impact of changes.

From a UI/UX perspective, the dashboards, portfolio views, and visual representation of relationships make large amounts of architecture data easier to analyze, although some areas can take time to learn. Performance has generally been suitable for working with architecture data and reporting, though the experience can depend on the amount of data and customization involved.

The platform's flexibility provides good ROI when an organization is already using ServiceNow, as it reduces the need for separate architecture repositories and duplicate data maintenance. However, the initial implementation, configuration, and licensing investment should be considered based on the size and maturity of the organization.

For onboarding, the breadth of the product means there is a learning curve, so good documentation, training, and implementation guidance are important. The platform's automation and AI capabilities also have potential to improve how architecture data is analyzed and used for recommendations, risk identification, and decision-making as these capabilities mature.

Overall, the biggest benefit is having architecture and operational information connected in the same ecosystem, which helps teams make better-informed technology and modernization decisions. Review collected by and hosted on G2.com.