When a company talks about transforming itself, it usually starts with technology: which tool to adopt, which process to automate. A more useful question is different: what does it need to be able to do better, differently or for the first time?
A working definition
A business capability is something an organization can do consistently to achieve a result: serving customers, identifying commercial opportunities, managing risks, coordinating operations or developing products, for example.
Three traits set it apart. It is oriented to a result that matters to the business. It is repeatable: it does not depend on one person making an extraordinary effort every time. And it is observable: you can describe how it works and measure what it produces.
A capability is not the same as a process, a department or a tool. The process describes a sequence of steps; the department, a way of organizing people; the tool, a technical means. The capability is what all of them, combined, make possible.
What a capability is made of
Every capability combines five components. When one of them lags behind, the whole performs below its potential:
- People: knowledge, judgment and clear responsibilities.
- Processes: the way work is organized and coordinated.
- Information: what is known, where it lives and how it flows between areas.
- Technology: systems, applications, automations and AI agents.
- Decisions: who decides what, with which rules and which information.
This view explains why excellent technology may fail to improve results: if information is still scattered or nobody changed the decision rules, the capability remains limited by those components.
Why thinking in capabilities helps
Thinking in capabilities brings together several conversations that usually happen separately:
- It connects strategy and operations. A strategic priority translates into the capabilities that need strengthening to reach it.
- It avoids isolated investments. Before buying a tool, you ask which capability it improves and what other components must change.
- It makes transformation measurable. Each capability has a result and therefore indicators that show whether it is improving.
- It improves the dialogue between business and technology. Both teams talk about the same thing: what the company needs to be able to do.
Three questions for each capability
Take a specific capability, such as serving customers, and ask it three questions:
What could we do better? Shorten response times, avoid rework, resolve more cases on first contact.
What could we do differently? Reorganize who handles what, integrate information that today sits in several systems, decide which tasks AI agents can carry out and which require human judgment.
What could we do that is not yet possible today? Anticipate needs before customers express them, offer a new service or serve a segment that is costly to serve today.
The first question improves what exists. The other two open space for new ways of operating and new sources of value.
How to start
A practical path can be short:
- Choose a capability that is critical for the business.
- Describe how it works today through its five components.
- Define the result you want to improve and how it will be measured.
- Identify the component that limits performance the most.
- Design the change, implement it within a limited scope and measure.
At SF/CIA this path corresponds to the four moves of our method: understand, redesign, implement and evolve. The goal of every engagement is a new or improved capability that can be used, measured and evolved.
Smarter capabilities. Greater value.
Understand. Redesign. Implement. Evolve.