Successfully Navigating Standards and Frameworks for your Organization

A guide to effectively tailoring standards

Countless meetings are spent answering questions about Enterprise Architecture (EA) terminology, like: ‘What is a capability’, or ‘How do we define an application’. These conversations are a frequent time-sink as many reading this will know. 

A recent article presents an eloquent solution. Conceptualizing an enterprise as a system by Graham Berrisford addresses how hundreds of standards prescribe overlapping metamodels for EA, and the challenges this presents. His easily digestible EA concept graph provides a powerful starting point for an EA repository schema (below).

Conceptualizing an enterprise as a system. Enterprise Architecture repository schema

It’s rare to find organizations adopting a single metamodel and for good reason: this approach is prone to failure and sleepless nights. A more typical, and dynamic approach is to take a standard or two and tailor them to meet the specific needs of the organization.

But what is the best approach and what are the downstream impacts?

Accept that there is no silver bullet

What works for one organization, won’t work for another. Often the right answer is to find something everyone can agree on. 

Any approach can work well for a single architect or a small team. But for larger organizations, it’s best to use well-defined standards and adjust them to ensure a good fit. What would this approach entail? 

 

How organizations tailor standards

Commonly, tailoring standards come in two forms:

1. Turn off what you don’t need 

Most organizations don’t need every viewpoint, object, relationship, and piece of metadata a standard prescribes. So they turn off what they don’t need, and reintroduce them as necessary. 

2. Merge Standards

Each standard has its strengths – for example,  TOGAF’s ADM, and ArchiMate’s relationships. Sure, you benefit from the strengths of each standard when you merge them, but this comes at a high price: it’s a complex procedure, often leading to time-consuming debates. 

The more standards being merged the bigger the headache.

 

You can’t do that! – Escaping the constraints of legacy EA tools

To avoid being constrained by downstream technicalities (like EA software), decisions and discussions about standards should come before deciding where to put them.

Legacy EA tools are a bottleneck for the best decisions tailored to a business’s ever-changing needs since implementing bespoke standards isn’t possible without a great deal of labor. Unfortunately, they end up limiting the potential of tailored standards. 

Tools like Enterprise Insight were born out of a need to meet these challenges, allowing architects to implement virtually any metamodel setup with pre-configured standards out of the box and metamodels can easily be used together.

Enjoyed this content?

more blog posts...

Blog

Why Can’t Financial Institutions Ignore TOGAF Anymore?

Banks and insurance companies operate in increasingly complex technological and regulatory environments. Gabor Sulok, CEO of Bdat Solutions with 20+ years in the Enterprise Architecture (EA) industry explains how TOGAF helps align EA with business goals and compliance. 1: Architecture is becoming mandatory In several countries, financial regulators now explicitly require or strongly encourage the use of TOGAF or TOGAF-based frameworks, especially in sectors classified as critical infrastructure.  Failing to demonstrate architectural maturity in such environments can delay licensing, increase regulatory scrutiny, or result in operational penalties. Which regions have most recently been affected? Hungary: The Hungarian National Bank (MNB) refers to TOGAF-based enterprise architecture as a foundational element in its regulatory expectations. The MNB’s published methodological guide to IT system integrity specifically emphasizes the need for structured architectural documentation and planning, citing TOGAF as an accepted model for enterprise alignment. Saudi Arabia: The Digital Government Authority (DGA) mandates the use of TOGAF-aligned principles through the National Overall Reference Architecture (NORA), which is binding for public and financial sector organizations operating in the Kingdom. Nigeria: The National Information Technology Development Agency (NITDA) has introduced the National Enterprise Architecture Framework (NEAF) based on TOGAF, with the aim of modernizing digital governance across key sectors including banking. Finland: Public sector IT procurements must be grounded in enterprise architecture. While not limited to TOGAF, the national guidance strongly reflects TOGAF principles and methodologies. European Union (DORA regulation): While the Digital Operational Resilience Act (DORA), effective from January 2025, does not name TOGAF explicitly, its enterprise-wide ICT risk management requirements align closely with TOGAF’s structured approach to architecture and governance. 2. Cross-border operations require consistent architecture Multinational banks and insurers often operate in multiple jurisdictions, each with unique compliance requirements. TOGAF provides a standard, adaptable architecture language that ensures internal consistency while allowing for localized extensions. Whether expanding into the Gulf region, complying with EU legislation, or integrating systems post-merger, TOGAF enables organizations to scale without fragmenting.  3. Strategic alignment of IT and business capabilities One of TOGAF’s strongest values is aligning technology initiatives with business strategy. In financial services, this means ensuring systems contribute directly to priorities like credit risk modelling, ESG reporting, or customer onboarding optimization. The TOGAF Architecture Development Method (ADM) guides this process from high-level goals to detailed execution steps.  4. Modernizing legacy systems with minimal disruption Legacy systems are common in the financial sector, but replacing them is risky. TOGAF helps organizations define a Baseline Architecture, design Transition Architectures, and work toward a clearly articulated Target Architecture. This staged approach reduces risk and helps manage cost, change resistance, and data migration challenges during core banking or insurance platform modernization.  5. Faster adoption of national and sectoral architecture mandates Organizations that already use TOGAF internally are better positioned to align with national frameworks and sector-specific mandates. They can map their internal architecture models to external requirements more quickly and reduce the time and cost of compliance. To summarize, current examples where TOGAF or TOGAF-based frameworks are institutionalized or expected include: Hungary – MNB regulatory architecture guidance Saudi Arabia – DGA’s NORA framework Nigeria – NEAF framework under NITDA Finland – National enterprise architecture standards European Union – DORA ICT architecture expectations United Arab Emirates – Digital Government Architecture Framework, a TOGAF-based model required for public and quasi-public entities, including financial services South Africa, Egypt, Estonia – National architecture efforts strongly inspired by TOGAF principles Of course, every business is different. This is why, even with TOGAF’s explicit guidelines, you can still modify it for your needs, which we always recommend.  In conclusion: For financial institutions, TOGAF is no longer just a best practice; it is becoming a compliance tool, a strategic alignment framework, and a competitive necessity. In a world where regulators expect full architectural transparency and digital change at scale, TOGAF delivers the structure to evolve confidently and consistently.  🚀 Get TOGAF-qualified: Gabor offers TOGAF courses as an accredited instructor. Get in contact here. 🚀 Have TOGAF loaded in your EA software in just two clicks. Book a demo with Enterprise Insight to see how. Load TOGAF into your architecture in a couple of clicks.  Reliable and always updated so you can spend time on what really matters. Book a demo

Read More »

Sign Up today for a Demo

Please fill in the below form and we will get back to you with your demo with 24 hours