A group of people representing everyone

Everyone’s Essential

If Everyone’s Essential, EA Must Meet People Where They Are

One of the most interesting shifts happening in enterprise architecture right now is being driven by AI. Not long ago, a big part of the challenge was extracting insights from EA data; building dashboards, creating visuals, or stitching together reports that actually told a story. That part is quickly becoming easier. AI can now generate insights, summaries, and even conversational responses from complex datasets with minimal effort.

So, if insight generation is getting easier, where’s the real challenge moving?

We believe it’s shifting upstream to knowledge acquisition.

Enterprise architecture knowledge doesn’t live in one neat, tidy system. It’s scattered everywhere. Some of it sits in spreadsheets. Some of it lives in slide decks or documents. You’ll find more in diagrams created in tools like Visio or draw.io. Then there are collaboration platforms like Confluence or SharePoint, project and portfolio management tools, CMDBs, and business systems like finance or HR platforms.

And of course, a significant chunk of it lives in people’s heads.

“Everyone’s Essential”

We started to use the term “Everyone’s Essential” around 4 years ago as a reminder that EA knowledge is owned, maintained and consumed by stakeholders across business and IT.

That’s the reality. EA knowledge is distributed, fragmented, and often informal.

The obvious goal, then, is to bring all of this together to create a single source of truth with a clear, well-defined ontology that connects everything in a meaningful way. A common instinct is to standardise everything. Create a single form, a master spreadsheet, or a survey, and tell everyone: “This is how you capture EA data now.” In theory, that gives you consistency. In practice, it rarely works.

This is primarily because people already have ways of working that suit them. Project managers are comfortable in their PPM tools. Operations teams rely on their CMDBs. Architects think in diagrams. Data teams model things in their own specialised tools. These approaches aren’t arbitrary, they’re deeply embedded in how these roles operate day to day.

Trying to force everyone into a single method often creates resistance. At best, you get partial adoption. At worst, you get workarounds, outdated data, or outright disengagement. So instead of forcing change, a more effective approach is to meet people where they are.

Let project managers keep using their project tools; let operations teams manage infrastructure in their CMDBs; let solution architects design in diagrams; let data architects build their models in the tools they know best.

The key isn’t to standardise the input mechanism, it’s to standardise the meaning.

As long as there’s a consistent ontology underpinning everything, the format in which the data is created becomes far less important. What matters is that the information can be understood, connected, and integrated into the broader EA landscape.

Consistency

This is where the focus should be: making it easy for people to contribute knowledge without disrupting their day jobs.

If capturing EA data feels like extra work, it won’t happen consistently. If it fits naturally into what people are already doing, adoption becomes much easier. The less friction there is, the more complete and accurate your EA knowledge base will be.

In other words, the goal isn’t to force everyone into the same tool, it’s to create an ecosystem where different tools and approaches can coexist, while still feeding into a unified, structured understanding of the enterprise.

And that’s how you make “Everyone’s Essential” more than just a slogan.

In reality, everyone is already essential. The challenge is making it easy for their knowledge to be captured, connected, and used without asking them to change how they work. Get that right, and everything else – insights, dashboards, AI-driven analysis – falls into place much more easily.

Contact Us