Skip to the main content.
YouDesign Logo Horizontal on light
Accessing your ServiceNow data has never been more straightforward.
You can effortlessly translate complex interdependencies into dynamic diagrams, intricate models, compelling visualizations, or organized tables.

Extension packs
The ins-pi professional services are tailored to make our customers self-sufficient. Contact the Sales team to learn more.
Explore, sign up, and gain valuable knowledge from the most recent events hosted by ins-pi.

2 min read

Getting Started as an Enterprise Architect

Getting Started as an Enterprise Architect

You have assembled your Enterprise Architecture team. So now what? How do you start with Enterprise Architecture? We have compiled these three important things you should focus on in the beginning.



What do your stakeholders expect from you? What are their targets? What are their pain points? Is it clear what they want from you, and can you deliver that?

Before doing anything else, you should brainstorm with key stakeholders and take as long as you need to until you reach a mutual agreement and understanding. Do not leave the meeting until expectations are set, so that the results you deliver later will meet their needs. Do not start architecting just for the sake of architecting.

The quality of your data should be your highest priority.



When you start to collect data for your portfolio, the most important thing you need to figure out is where your stakeholders' key focus is. Only after understanding that will you know what information you need to bring in and where to put your architectural focus.

(Looking for a single source of truth for your data? Try Designer.)

As for the data itself, collect only enough data to help answer the stakeholder's question at hand. That should be your primary focus and target. If the data you have is not directly linked to the key value that you are bringing to your stakeholder, do NOT put it in. You can learn more about collecting the right data here.

When putting data into your portfolio, if you're not sure whether it is relevant or not, asking the following will help you decide:
  • What question do I need to answer?
  • What kind of information do I need to answer that question?
  • How will this data be kept current and accurate?



Your EA Portfolio is not a data dump. Enterprise Architecture is a journey on which you slowly mature on the way. Make sure to only add relevant data.

The data you have in your portfolio should be able to meet the following 2 criteria:
  1. The data is complete.
  2. The data is current.

Expanding your portfolio should have natural progress over time and be populated with new data as you answer more and more questions for the business stakeholders. Enterprise Architecture is not a sprint.



Want to learn more on the topic? Watch our webinar on Enterprise Architecture 101 now:

enterprise architecture 101



Using ServiceNow as Your Enterprise Architecture Management Platform

What are the benefits of having your Enterprise Architecture Management (EAM) tool on ServiceNow? Let’s have a chat, so we can understand your Enterprise Architecture needs and use-cases better. Only then will we give you a demo of the tool that we think will fit your EA needs best. 


How to Win Data Stewards and Influence Senior Management

5 min read

How to Win Data Stewards and Influence Senior Management

Data stewards play a crucial role in ensuring the quality and usability of an organization's data, and effective data management can provide...

Read More
3 Ways to be a Happy Enterprise Architect

3 min read

3 Ways to be a Happy Enterprise Architect

When doing Enterprise Architecture, you should always have a specific business value in mind to provide to stakeholders and business management. If...

Read More
Future State Planning on ServiceNow

3 min read

Future State Planning on ServiceNow

Enterprises need to keep up with the constantly evolving digital world. Adding an ongoing pandemic to that – future state planning is becoming more...

Read More