Skip to main content

Relating Capabilities to Strategy and Business Model

Relating Capabilities to Strategy and Business Model

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
relating capabilities to strategy and business model

In our ongoing blog series on Capabilities and Capability-based Planning, we’ve mainly concentrated on the capability concept itself. We’ve discussed why capabilities are useful as a concept, how to define them, and how to structure Capability Maps. We’ve also looked at how you can use Capability Maps to support business challenges such as investment decision-making, to name a few. 

In this blog, we want to cast a wider net and look at the relationships between capabilities, and share best practices for your business and strategic planning.

Relating Business Strategy and Capabilities

The relationship between business strategy and capabilities is a two-way street. On the one hand, the strategy of an enterprise is a way of configuring its capabilities and resources to achieve certain goals. This may entail improving some capabilities, developing or acquiring completely new ones, or even divesting some non-core, non-strategic capabilities. 

Summary

Relating capabilities to strategy and business models enables organizations to move from abstract planning to actionable insights. By aligning capabilities with resources, value streams, and investment priorities, enterprises can ensure that strategy translates into measurable outcomes. This integrated perspective allows business architects to better guide transformation initiatives, support decision-making, and create long-term business value.

FAQs

Business strategy configures capabilities and resources to achieve goals, while existing capabilities can open opportunities for new ventures.

The Business Model Canvas highlights key capabilities needed for value creation, making strategy and investment planning more concrete.

Capabilities represent potential, while value streams represent value creation in motion. Cross-mapping them shows how capabilities support each stage of value delivery.

 

Using ArchiMate® to Visualize the TOGAF® Enterprise Continuum

Using ArchiMate® to Visualize the TOGAF® Enterprise Continuum

Sep 24, 2025 - Bernd Ihnen - Enterprise Architecture
using archimate to visualize the togaf enterprise continuum

The TOGAF® Enterprise Continuum is a cornerstone of enterprise architecture, providing a structured way to classify and organize architectural descriptions across different levels of abstraction. When combined with the ArchiMate® modeling language, organizations gain a clear and standardized notation to visualize Architecture Building Blocks (ABBs), Solution Building Blocks (SBBs), and deployed solutions. 

Understanding the TOGAF Enterprise Continuum

Previously, I have written about the use of a modeling language and the practical usage of the TOGAF Enterprise Continuum to classify architectural descriptions along different levels of abstraction.

Summary

Visualizing the TOGAF Enterprise Continuum with ArchiMate helps enterprise architects bridge the gap between conceptual architecture and real-world solutions. By applying ArchiMate’s flexible notation to ABBs, SBBs, and deployed solutions, organizations can ensure traceability, consistency, and clarity across different levels of abstraction. Whether developing new architectures, adding application services, or creating separate models, the key is to choose the approach that best fits the scope of your project while avoiding unnecessary modeling complexity. This synergy between TOGAF and ArchiMate provides a strong foundation for strategic planning and architecture governance.

FAQs

It is a classification system that organizes architectural artifacts across different abstraction levels, including Architecture Building Blocks (ABBs), Solution Building Blocks (SBBs), and deployed solutions.

ArchiMate provides a standardized modeling language that allows ABBs, SBBs, and their relationships to be visualized consistently, making enterprise architectures easier to understand and communicate.

The choice depends on context: the first approach works well for new architectures, the second adds an additional layer with artifacts, and the third allows separate logical and physical models.

 

The Business Architect's Toolbox: Value Stream Mapping

The Business Architect's Toolbox: Value Stream Mapping

Sep 26, 2025 - Marc Lankhorst - Enterprise Architecture
The Business Architect's toolbox: Value Stream Mapping

Value Stream Mapping (VSM) is one of the most powerful tools in a business architect’s arsenal. By visualizing how value flows across processes, teams, and systems, VSM helps organizations identify inefficiencies, align capabilities, and drive strategic improvements. In this article, we explore how value stream mapping fits into the broader business architecture landscape and why it’s essential for delivering enterprise-wide transformation.

What is Value Stream Mapping?

Business architecture is a comprehensive approach to understanding and designing an organization’s structure, processes, and capabilities. It encompasses several key domains as defined by the Guide to the Business Architecture Body of Knowledge (BIZBOK Guide®), which form the foundation of business architecture and are interconnected components that provide different perspectives on an organization’s operations and structure. The four core domains are Value Streams, Capabilities, Organization, and Information. 

 

Business Architecture Redefined: Mapping BIZBOK® to ArchiMate®

Business Architecture Redefined: Mapping BIZBOK® to ArchiMate®

Sep 24, 2025 - Marc Lankhorst - Bernd Ihnen - Enterprise Architecture
map BIZBOK® to the ArchiMate® modeling language

The Business Architecture Body of Knowledge (BIZBOK®) has become a widely used reference for business architects worldwide. ArchiMate®, in parallel, provides an open standard to represent enterprise architecture with a clear, consistent notation.

Mapping BIZBOK to ArchiMate bridges these two approaches, enabling architects to connect business architecture concepts to the broader scope of enterprise architecture. This mapping helps teams align definitions, avoid concept drift, and keep business architecture directly connected to planning, change, and investment decisions.

In this article, we explain how BIZBOK® can be expressed in ArchiMate®, highlight key mapping examples, and show why this integration strengthens both strategic and operational modeling.

What is BIZBOK®?

Since the foundation of the Business Architecture Guild and publishing version 1 of Business Architecture Body of Knowledge (BIZBOK®) in 2011, the best practices have become a popular set of guidelines and techniques for practicing business architects.

FAQs

BIZBOK® provides a core set of concepts, guidelines, and techniques for expressing business architecture as defined by the Business Architecture Guild. Its metamodel outlines key elements such as capabilities, value streams, stakeholders, value propositions, and organizational structures, offering a structured way for business architects to describe how the business creates and delivers value. 

ArchiMate® supports BIZBOK® concepts by offering a standardized modeling language and notation that can express those same business architecture elements within a broader enterprise architecture context. It includes motivation, strategy, business, implementation, and migration elements that correspond to many of the BIZBOK® metamodel concepts. It also allows for hierarchical modeling, making it possible to represent different levels of detail—such as capabilities, value streams, and organizational units—in a consistent way. 

Mapping BIZBOK® to ArchiMate® makes business architecture easier to connect to the rest of enterprise architecture. It ensures that abstract concepts like capabilities and value streams can be linked to more concrete elements such as processes, applications, and roles. This helps architects avoid business architecture becoming a stand-alone discipline, improves understanding for non-architects, and provides a clearer line of sight from strategic intent to operational models and implementation. 

 

Use Our Business Process Maturity Model to Measure Progress

Use Our Business Process Maturity Model to Measure Progress

Sep 27, 2025 - Bizzdesign - Enterprise Architecture
use our business process maturity model to measure progress

Business process maturity model provides a structured framework to measure the current state, identify strengths and weaknesses, and define a roadmap for improvement.

With more than 23 years of experience in enterprise architecture and BPM, Bizzdesign has developed an easy-to-use business process maturity model. This model helps organizations assess their BPM practices, prioritize improvement initiatives, and build a scalable foundation for continuous process optimization. 

What is a Business Process Maturity Model?

Business Process Management focuses on how the enterprise operates and delivers the results, i.e., products and services to external and internal customers. 

A business process maturity model is a structured framework to assess your organization’s level of maturity in managing and optimizing business processes. 

Summary

Whether you are just starting with BPM or looking to optimize advanced processes, using this model ensures your improvement efforts are targeted, structured, and aligned with business goals. With the right insights and tools, you can transform BPM from isolated initiatives into a driver of sustainable enterprise-wide performance.

 

Expressing the BIAN Reference Model for the Banking Industry in the ArchiMate Modeling Language

Expressing the BIAN Reference Model for the Banking Industry in the ArchiMate Modeling Language

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
expressing the bian reference model

Reference models play a crucial role in enterprise architecture, providing standardized blueprints that align technology and business strategy. For the financial sector, the Banking Industry Architecture Network (BIAN) offers a comprehensive framework of business capabilities, service domains, and business objects. Expressed in the ArchiMate® modeling language, this reference model helps financial institutions improve interoperability, streamline processes, and strengthen governance. In this article, we explore how the BIAN model is represented in ArchiMate and present a case study that illustrates its practical application.

Break-down of the BIAN reference model

It stands to reason that such a standard reference model should be expressed in a standard notation, to foster its adoption, and BIAN recognized this need. BIAN version 13.0 has therefore been expressed in the ArchiMate 3 modeling language. The core of the BIAN reference model is its Service Landscape. 

Summary

The BIAN® reference model expressed in the ArchiMate® modeling language demonstrates how industry standards can accelerate digital transformation in financial services. By combining BIAN’s structured service domains with ArchiMate’s modeling capabilities, financial institutions gain a common language to improve interoperability, streamline processes, and strengthen governance. This alignment not only supports compliance and efficiency but also provides a solid foundation for innovation in the evolving financial landscape.

 

Planning and Roadmapping Modeling in ArchiMate

Planning and Roadmapping Modeling in ArchiMate

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
planning and roadmapping modeling in archimate

In our previous blog post on planning and roadmapping, we introduced the concept in the context of enterprise architecture and capability-based planning. We explored different levels of roadmaps, from short-term sprints lasting just a few weeks to long-term, multi-year strategic roadmaps, and shared initial insights into how ArchiMate® conceptscan be used for roadmap modeling.

 

In this article, we take a closer look at the different ways to model the evolution of your architecture, providing more practical guidance for creating effective roadmaps that support transformation initiatives.

Modeling roadmaps with plateaus

The most prominent feature of the ArchiMate language is the Plateau concept. In the standard, this is defined as: “a relatively stable state of the architecture that exists during a limited period of time.” 

This concept intends to model fairly major changes to your architecture, hence the ‘relatively stable’; small-scale changes are too frequent to lend themselves easily for collecting them in plateaus. 

 

Linking Capabilities to the Operating Model Business Functions and Organizational Structure

Linking Capabilities to the Operating Model Business Functions and Organizational Structure

Sep 26, 2025 - Marc Lankhorst - Enterprise Architecture
 Name linking capabilities to the operating model business functions

Editor's Note: Business Capabilities are fundamental to Business Architecture, making it essential to understand how to implement them effectively. To help you navigate Capability-Based Planning, we've created the ultimate eBook, packed with insights, strategies, and practical guidance to set you on the right path. This blog post is an excerpt from the eBook, providing a glimpse into the valuable content you'll find inside.

How they relate: Capabilities, Business Functions, the Organization

In this blog, we want specifically to answer the question: How does the enterprise’s operating model deliver capabilities? Let’s start by clearing up an important misunderstanding: a Capability Map is not a functional decomposition of the enterprise!

Summary

Linking business capabilities to the operating model provides a clear line of sight from strategic intent to operational execution. By distinguishing between capabilities and business functions, and relating them to organizational units, processes, and technology, business architects can build models that are both strategic and actionable. This capability-driven perspective ensures that enterprises stay focused on what they can do, while functions and resources define how they achieve it—creating flexibility, traceability, and long-term business value.

FAQs

Business capabilities describe what an enterprise can do, while business functions describe how these capabilities are performed in practice.

It ensures alignment between strategic goals and day-to-day operations, providing clarity and traceability across people, processes, and technology.

While they are often confused, it is best to use capability maps for high-level abilities and business function maps for operational detail to avoid redundancy.

 

How to Combine ArchiMate® With Industry Standards for Better EA

How to Combine ArchiMate® With Industry Standards for Better EA

Sep 27, 2025 - Marc Lankhorst - Enterprise Architecture
combining archimate with other standards

The ArchiMate® modeling language becomes even more powerful when combined with other enterprise architecture and business standards. 

By integrating ArchiMate with frameworks such as TOGAF®, BPMN, or UML, organizations can achieve richer models, improved consistency, and stronger alignment between strategy, processes, applications, and technology. 

This synergy enables enterprise architects to create more comprehensive views, support collaboration across disciplines, and deliver greater value to transformation initiatives.

What is the ArchiMate modeling language?

ArchiMate is an open, standardized modeling language for enterprise architecture. It provides a unified framework for describing, analyzing, and visualizing connections across business domains. It offers a clear, consistent way to capture and communicate complex organizational relationships. 

The ArchiMate language is not intended to replace other standards and modeling approaches. For many domains, languages, and techniques are available that provide more detailed descriptions. 

Summary

First of all, let’s repeat what we started with: ArchiMate is not intended to replace other standards and techniques but rather to complement them. For many domains, there are languages and techniques available with a narrower scope but a greater level of detail. ArchiMate provides a broader description that helps to see the dependencies between different aspects and areas and gives a general overview of your enterprise. 

It can connect to those other techniques because their concepts overlap. Since ArchiMate is only a modeling language, it does not provide its way of working, but it will, of course, be used in the context of such a process. Much has been written about using ArchiMate with TOGAF—both Open Group standards and easily complementary—and we did not want to repeat that in this blog. 

In addition to this typical use in enterprise architecture, we discussed the relevance of architecture and ArchiMate in agile development. Although the role of models in an agile approach differs from the traditional ‘big design up front’ development style, they are important in ensuring coherence across different timescales, iterations, and domains. 

You need to make sure that agile teams work with and not against each other and avoid creating silos, and you want to align everyone from strategy to operations with the same purpose. 

Creating, evolving, and sharing just-in-time models that capture the information necessary to make the right decisions at all levels of the organization at the right moment is the best way to become a truly adaptive enterprise. If you have any further questions about linking ArchiMate to other standards, please contact us.

 

The Future of Enterprise Architecture and AI Integration

The Future of Enterprise Architecture and AI Integration

Oct 27, 2023 - Bizzdesign - Enterprise Architecture
the future of enterprise architecture and ai integration

‘The future of enterprise architecture’ is increasingly intertwined with Generative AI, which isn't merely a fleeting trend. Generative AI is a transformative tool that can diagnose medical conditions by predicting machinery failure or directing traffic and goods flow. Moreover, its symbiotic relationship with machine learning (ML) reshapes IT structures and enterprise architecture.

Future of enterprise architecture in the Generative AI era. 

Having a legacy spanning over three decades, enterprise architecture now faces the formidable task of navigating the burgeoning field of AI. The rapid technological advancements require enterprise architects to be nimble in recognizing potential trends, implementing transformative processes swiftly, and handling vast data volumes with finesse.