Successfully Navigating Standards and Frameworks for Your Organization
Hundreds of EA standards prescribe overlapping metamodels — and no single one fits every organisation. Here is a practical guide to tailoring frameworks so they actually work for yours.
A Guide to Effectively Tailoring Standards
Walk into any enterprise architecture team and you will quickly encounter a familiar problem: the debate about terminology. What is a “capability”? Is a “function” different from a “service”? Does your metamodel need ArchiMate relationships, TOGAF phases, or both?
As EA researcher Graham Berrisford has documented extensively, hundreds of standards prescribe overlapping metamodels for enterprise architecture — each with its own vocabulary, notation, and structural assumptions. The result is not clarity; it is decision paralysis. Teams spend weeks debating definitions while the architecture work stalls.
100s
EA standards with overlapping metamodels
1–2
Standards most organisations actually tailor and use
2
Core tailoring approaches used by leading EA teams
Accept That There Is No Silver Bullet
The most important insight in EA framework selection is also the most counterintuitive: there is no universally correct answer. What works for a global bank operating under DORA will not work for a mid-market logistics company undergoing a cloud migration. What suits a heavily regulated public-sector body will frustrate a product-led tech firm.
The goal is not to find the “best” framework. The goal is to find the framework — or combination of frameworks — that fits your organisation's context, maturity, and strategic intent, and then tailor it accordingly.
How Organisations Tailor Standards
In practice, most organisations settle on one or two standards as a foundation and then tailor them to match their specific needs. There are two predominant approaches:
Turn off what you don't need
The simplest tailoring strategy is subtraction. Start with a comprehensive standard — TOGAF, ArchiMate, or a government reference architecture — and systematically disable the viewpoints, object types, and metadata fields that your organisation will never use.
This approach reduces cognitive load for architects, accelerates onboarding for new team members, and prevents the sprawl of half-populated models. The risk is under-tailoring: leaving enough of the standard intact that architects still spend time navigating irrelevant constructs. The discipline is to be ruthless — if your team will not use it in the next six months, remove it.
Merge standards to get the best of each
More sophisticated EA teams combine elements from multiple standards into a single, coherent metamodel. A common example: pair TOGAF's Architecture Development Method (ADM) — which provides a powerful governance and phase structure — with ArchiMate's rich relationship model, which enables precise, notation-based diagramming.
The benefit is a metamodel precisely tuned to your organisation's needs. The challenge is the upfront investment: merging standards requires careful debate about which elements to retain, how to resolve naming conflicts, and how to document the resulting bespoke model so future team members understand it. Done well, it becomes a durable competitive advantage. Done poorly, it produces a confusing hybrid that architects quietly abandon.
Define Your Standard Before You Choose Your Tool
One of the most common — and costly — mistakes in EA programme setup is selecting tooling before the metamodel is defined. Most legacy EA platforms encode their own assumptions about structure, relationships, and notation. Once you are inside a tool, those assumptions become constraints.
The right sequence is always: define your standard first, then find a tool that can support it — not the other way around.
“You can't do that” — escaping legacy EA tool limitations
“What works for one organisation won't work for another.”
Legacy EA tools were built when the field had fewer standards and less diversity in organisational approaches. As a result, they typically support one or two fixed metamodels and offer limited ability to deviate from them. When an architect tries to implement a bespoke standard, the answer is often: “The tool doesn't support that.”
This forces a damaging compromise: organisations bend their carefully considered standards to fit the tool, rather than having the tool support their standard. The downstream cost — in misaligned models, workarounds, and eventual platform replacement — is substantial.
Tooling That Follows Your Standard — Not the Other Way Around
Enterprise Insight was built specifically to address this constraint. Rather than encoding a single fixed metamodel, the platform enables architects to implement virtually any metamodel setup, with popular standards available as pre-configured starting points that can be modified, extended, or merged without restriction.
Whether your organisation runs TOGAF, ArchiMate, a national reference architecture, or a proprietary bespoke model, Enterprise Insight adapts to your standard — not the reverse. The result is faster programme setup, better adoption from architects, and models that remain accurate and useful as your standard evolves over time.
TL;DR
There is no single correct EA framework. Successful organisations select one or two standards, tailor them aggressively to remove irrelevant constructs or merge the best of each, and define their metamodel before choosing tooling. Legacy tools that force organisations to reverse this sequence are a hidden source of programme failure. The right tool follows your standard — it does not constrain it.
Implement your standard, not ours
Enterprise Insight supports virtually any metamodel out of the box. Book a demo and configure your framework in a single session.
Ready to transform your
architecture practice?
Join leading EA teams using Enterprise Insight to move faster, communicate better, and deliver real business value.
No commitment · Personalised walkthrough · Live Q&A included