Capability mapping: what is it and main examples

Capability mapping is the practice of identifying and visually organizing the capabilities an organization needs to execute its strategy and create value.

As a methodology combining business architecture, strategic planning, and organizational design, which helps—by defining a company’s key capabilities—to align them with business objectives and identify gaps between the current state and the desired state.

In this article, we’ll explore what capability mapping is, what it’s used for, and how it’s structured, with practical examples and guidelines so you can create your own capability map.

What is capability mapping (or business capability mapping)?

Capability mapping is a visual representation, organized hierarchically, of the capabilities an organization possesses or needs to acquire to achieve strategic objectives; as such, it also serves to analyze gaps. By comparing the current state with the desired state, it highlights the capabilities the company lacks or those that need to be strengthened, based on solid evidence that serves as a rationale for advocating improvement actions.

When the model covers the entire company, it is called business capability mapping.

The difference from other diagrams, such as the HR business model canvas, is that this model focuses on what the business does, but does not address how, where, or by whom a task or project is performed. In other words, it does not describe the sequence of a task, the system that executes it, or the team responsible for it.

Each capability is referred to as a skill rather than an action; for example, “customer management” or “claims processing” is noted, rather than “managing customers” or “processing claims.”

Where does business capability mapping come from?

This technique has its origins in a method developed in the fields of defense and public administration to plan actions based on what forces needed to be capable of doing, rather than on the equipment they had available.

The same logic (separating the “what” from the “how”) proved useful for businesses, and throughout the 2000s, business capability took center stage in transformation planning.

Two organizations then contributed significantly to formalizing and disseminating this practice:

• The Business Architecture Guild codified capability mapping in its Business Architecture Body of Knowledge (the BIZBOK guide). It made it one of the fundamental artifacts of enterprise architecture, alongside value streams and information maps.
• The Open Group: incorporated capability-based planning and enterprise capability mapping into TOGAF, its widely used enterprise architecture framework. Its work primarily consisted of transforming a maturing practice into a documented standard.

Thanks to these important contributions, capability mapping is now a common approach in both the business and information technology fields.

What is a capability map used for? 6 key points

Capability mapping focuses exclusively on what the business does, rather than how, where, or who does it. According to the sources consulted, we can identify the following essential applications:

1. Aligning the business with information technology: it translates corporate objectives into clear technological requirements. This eliminates the communication gap between executives and technical staff, ensuring that every infrastructure investment addresses a real need within the organization.
2. Gap analysis: it helps realistically compare the company’s current capabilities with the competencies needed to achieve new goals or improve the customer experience. Through this process, you can develop a structured roadmap while minimizing uncertainty and risk.
3. Identifying and reducing internal bottlenecks: capability mapping, from a flow engineering perspective, helps diagnose operational friction such as cognitive overload, leadership gaps, or miscommunication. By acting on this information, you can unlock the full potential of your teams’ talent.
4. Optimizing investments and talent: this tool provides valuable insights into which underdeveloped skills you should allocate more resources to in order to strengthen your overall strategy. It helps you determine whether you need to create specific training programs to foster professional development, hire specialists, outsource services, or commit to a transformation toward inspirational leadership.
5. Visual diagnosis using heat maps: the presentation of information transforms complex operational data into heat maps that help reflect the health of the business. For example, using colors helps you see at a glance the critical areas requiring priority intervention (in red) or the optimized areas (in green) that become competitive advantages.
6. Operational efficiency and autonomy: this increases profitability by identifying and consolidating identical or overlapping processes carried out in different departments. It can also help assess which valuable external services can be brought in-house to reduce reliance on third parties.

The levels of a capability map

A capability map is a hierarchical structure that is read from top to bottom, with increasing levels of detail. Typically, the structure consists of three levels, although, depending on the specific case, the maps can go into much greater depth.

To give you an idea of what this business tool entails, we’ll break down what the first levels consist of in the following sections.

Level 1 of capability mapping: domains and what your organization does

At this first level, you should include high-level groupings. Compile the domains (usually between 10 and 15) that summarize what the organization does. This structure allows, for example, an executive committee to gain an accurate picture of the business without getting lost in the details.

Among these more overarching capabilities, we can find talent management, customer management, financial management, and operations management. Depending on the sector, the terminology may vary. For example, a hospital might use the term “patient” while a government agency might use “citizen”, but the underlying capability remains the same.

Level 2: capabilities – the operational core of strategic decisions

At Level 2, each domain is broken down into its constituent capabilities, detailing the specific business functions in greater depth than the previous level.

For example, if we focus on talent management, at this level we would find:

• Candidate attraction: the ability to identify the profiles needed for the project, publicize job openings, and build a talent pool of applicants.
• Competency assessment: the capability to measure a candidate’s knowledge and competencies.
• Test administration: the capability to make these assessments available to candidates under controlled and reliable conditions.
• Candidate onboarding: the capability to integrate the selected individual into the organization once they have successfully completed the selection process.

It’s important to note that at this level, you should not concern yourself with the execution; in other words, you should not go into detail about how these processes are carried out. This limitation on information helps keep this layer stable, even as the protocols, vendors, or tools that make up the “how” of level 3 change.

Most professionals recognize level 2 as the true core of capability mapping: it is detailed enough to support strategic discussions with solid arguments, and stable enough to remain valid for years.

Levels 3-4: sub-capabilities and execution

Starting at this level, the map moves beyond describing broad areas of the business and begins to delve into the details of how each capability is executed through the skills required to develop them.

The idea is that each level adds a more specific version of the previous one, breaking down each Level 2 capability into smaller capabilities as levels are added.

Remember that, as we mentioned earlier, this is a hierarchical structure that progresses from levels with more general information to more detailed ones, forming a sort of chain where each link is an internal component of the previous one.

If we focus on the competency assessment capability, the chain can be broken down into test administration, exam supervision, candidate authentication, etc. Each of these components remains a capability in its own right: no matter how specific it becomes, it still describes “what is done,” never “how it is done.”

Then, below the top-level competency, as we move down through the levels, the structure can extend to specific actions that implement competencies, such as recording an attempt, logging an incident, or validating a result.

To what level is it necessary to break down the map? Depth based on objective

The number of levels of depth will depend on the objective. For example, in areas such as strategic planning and high-level analysis, maps typically do not go beyond level 3, because the capabilities at that level already provide sufficient specificity to inform initial investment and technology decisions.

In this context, levels 4 through 6 are usually reserved for greater precision: aligning specific capabilities across business units or linking each capability to systems and services.

In any case, a key premise for creating effective capability mapping is selective decomposition, delving deeper only where additional detail supports an actual decision. Keep in mind that a map where every branch reaches level 5 would be impossible to maintain.

What are the 3 types of capabilities?

Business capability mapping typically classifies capabilities into three categories, each of which answers a different question about how a function contributes to the organization:

1. Core capabilities or operating capabilities: These define what the company sells or offers and to whom. They underpin an organization’s value proposition to the market, including products, services, marketing to potential customers, and the maintenance of ongoing customer relationships. They answer the question: “What do we offer?”
2. Support capabilities or proprietary assets and capabilities: these are the capabilities that keep the business running, such as finance, human resources management, information technology infrastructure, and facilities management. Without them, a company cannot function; however, they are not differentiating capabilities, that is, two companies can have the same ones without either gaining a competitive advantage. Nevertheless, they are what enable standardization, shared services, or outsourcing. They answer the question: “What allows us to keep operating?”
3. Strategic capabilities or leadership capabilities: these are the capabilities that chart the organization’s course, such as interpreting changes in the market and the environment, defining objectives, or financing strategic initiatives. Here you’ll find capabilities such as managing the product innovation process or integrating mergers and acquisitions. They answer the question: “Where are we headed?”

It’s important to clarify that the typology of capabilities is not the same as the hierarchical level discussed in the previous section. Capability mapping divides capabilities into levels (L1, L2, L3, Ln), and each level may contain basic, supporting, and strategic elements, since these are dimensions that function differently.

It is also important to note that a capability is not the same as an asset. A patent or a trademark is something the company owns; a capability is something the company does in the broadest sense of the term.

Along these same lines, some frameworks may use different terms than those we’ve just seen, such as “enabling, operational, or differentiating capabilities.” However, the logic remains the same: to distinguish between what makes the company succeed, what keeps it running, and what sets its long-term course.

Capability mapping examples

Before going into detail on how you can design a capability map, we’d like to share some visual examples with you so you can begin to consolidate what we’ve discussed so far.

To start, here’s a basic Level 1 table that outlines the main domains of a distance learning company:

At this same level, it is also possible to organize the content around the three types of skills. In our example, it would look like this: 

Building on this foundation, levels 2, 3, and beyond will break down the organization’s capabilities in greater detail.

How to create a business capability map step by step

The most important thing when designing a business capability map is to follow a structure aligned with business objectives. Depending on the scope and urgency of the project, organizations opt for comprehensive strategic methodologies or agile tactical approaches.

Approach 1: the step-by-step strategic process

This approach is designed to build the capability map hierarchically and at the corporate level, following three phases:

• Phase A – preparation and definition of level 1: this phase focuses on creating a basic template and refining it based on the company’s current situation, validating the domains with senior leaders. In this phase, it is recommended to share the first draft to gather informed feedback and improve the version. You must ensure that these domains are aligned with the organization’s actual objectives.
• Phase B – breakdown and prioritization: next, you must detail Levels 2 and 3, prioritizing the capabilities that add direct value to the business before involving the technical experts for each one.
• Phase C – validation and final publication: Finally, organize a formal meeting with the executive team to reach a final consensus and publish the map in a space accessible to the entire company.

Approach 2: tactical flow engineering

A capability map can also be used to resolve bottlenecks. In this case, you’ll need an agile process that can be completed in four steps:

1. Initial identification of critical friction points in the current value stream.
2. List capabilities vertically, evaluating them based on these criteria: ownership, backup, skill level, and resources.
3. Address the identified gaps and work through them using internal training plans or by hiring talent.
4. Use the map to justify investments in specific actions, such as purchasing productivity tools or proposing the in-house development of services.

Core design principles

Regardless of the approach you choose, adhering to certain basic principles is necessary for the capability map to maintain its stability and long-term usefulness:

• “What” versus “how”: to ensure the map doesn’t lose its purpose, focus on what your business does, not how it does it.
• Nouns, not verbs: Use terms like “customer management” instead of “serving the customer,” because you should focus on the static capability, not on a dynamic process.
• No redundancies: Each capability should appear only once on the map. It is a single asset, even if it is used by multiple departments or business units.
• A single corporate map: so you can break down fragmentation between departments and enable an aggregated view of the organization.

There’s another universal principle for creating this type of map: devote the necessary time to it and solicit feedback from those involved. A map that doesn’t truly reflect your company will be useless.

Tools for designing a capability map

For U.S. organizations, some of the leading tools for effectively designing capability maps are:

• Enterprise architecture platforms: SAP LeanIX and Ardoq are the industry standards in the U.S. They allow you to maintain dynamic, hierarchical maps linked to applications and objectives. Large corporations focused on investment portfolios often use tools such as Planview Portfolios or MEGA Hopex because they offer high-quality centralized repositories, or Jibility, which stands out for its heat mapping that facilitates gap analysis.
• Diagramming and presentation: one option is Lucidchart, a cloud-native tool that allows you to quickly model drafts and integrates with Ardoq and LeanIX, for example. Although it may seem surprising, for senior management, Microsoft PowerPoint remains one of the most widely used formats for exporting and presenting the map as a single-page executive poster.

Here again, remember: the value of capability mapping lies not in the software or application you use to create it, but in its ability to connect capabilities with your technological infrastructure and business structure.

Capability mapping: benefits and limitations

Capability mapping provides benefits such as:

• Organizational clarity: it visually organizes what the company does, what sustains it, and where it is headed.
• Centralized decision-making: it facilitates strategic decision-making that, without this analysis, might remain isolated or scattered across the organization’s various departments.
• Common language: it connects marketing, IT, and management through a shared business language, eliminating communication silos and departmental jargon.
• Operational efficiency: it facilitates the identification and elimination of duplicated functions or efforts among different work teams.
• Investment prioritization: serves as a guide to precisely direct the budget toward the most urgent technology investments.
• Project justification: serves as a solid basis for justifying transformation projects to senior management.

Despite these benefits, the critical limitation of capability mapping is a lack of alignment. If it is not connected to the company’s IT infrastructure and operational reality, it can become a mere decorative chart rather than a key asset for decision-making.

Practical application: from the capability map to operational reality

If we return to the example we’ve been using throughout this article (in distance learning institutions), this logic applies directly to central issues such as academic integrity.

In a standard business capabilities map for online education, “student management” serves as a Level 1 domain; at Level 2, “learning assessment” emerges as a core capability; at Level 3, “academic integrity and identity verification” is identified as the critical, non-negotiable sub-capability for protecting the value of the certifications issued by the institution.

If your gap analysis reveals that the organization lacks the technology necessary to ensure the security of remote exams, management must face a strategic decision: invest significant resources in developing in-house software or partner with a specialized provider to address that need.

This is where Smowltech can successfully step in. It may be time to review proctoring plans to determine which one best fits the volume of exams and the project’s risk level.

At Smowltech, we offer our clients four customizable plans built precisely on this logic, which integrate with most LMS platforms on the market. All plans include detailed reports that reinforce the objectivity and integrity of the exams.

Additionally, we comply with both FERPA (Family Educational Rights and Privacy Act) and the CCPA (California Consumer Privacy Act), ensuring that institutions and organizations operating in the U.S. can implement SMOWL solutions without compromising the legal framework for their students or employees.

To help you better understand the solutions we can offer and address any questions you may have, we invite you to request a free demo.

Resources and tools to continue learning about capability mapping

If you’d like to delve deeper into the practical application of capability mapping, we recommend consulting the following sources:

• TOGAF standard (The Open Group): the world’s most widely used enterprise architecture framework. It offers business capabilities guides that explain how to connect business capabilities with the technology infrastructure and the phases of the Architecture Development Method (ADM) cycle.
• Resources from LeanIX and Ardoq: These leading platforms offer numerous free downloadable guides and real-world case studies on the application of this type of enterprise mapping in their resource and knowledge centers.
• Enterprise Architecture as Strategy, Creating a Foundation for Business Execution (Jeanne W. Ross, Peter Weill, David C. Robertson): a book that has become an essential classic, explaining how the capabilities map defines the company’s operating system and determines its level of digitization.