Capability Engineering
How do you build a capability that lasts?
Capability Engineering is the emerging discipline we use to answer that question: principles and practices for turning a business initiative into something the organization can do, keep and develop. We are writing it together with anyone who wants to contribute.
Building is faster. Making what you build last is still hard.
AI writes code, models change often, tools multiply and teams become mixed, made of people and agents. All of this speeds up the work, and it also makes it easier for knowledge to get scattered.
We call this phase the Era of Make: it is our way of reading it. The question it raises is less about how to build, and more about how to keep, over time, the ability to use, oversee and improve what has been built.
From delivering a project to building a capability
Software remains essential, and software engineering continues to cover its full lifecycle. Capability Engineering widens the view: beyond what is built, it looks at who uses it, with which data and procedures, and how the organization will keep developing it.
- Requirements set at the start
- A vendor who builds
- A handover at the end
- Further development handled separately
- A business initiative with goals you can check
- In-house team, partners, AI and platform together
- Shared, accessible knowledge
- A capability the company keeps and develops
The guiding question: what will the organization be able to do at the end of the program, and in the years that follow?
The capability, and what makes it work
A capability is an organization’s ability to achieve a result consistently: answering customers, running a process, launching a service. To work, it needs concrete elements, which we call Enterprise Assets: software, data, models, workflows, automations, agents, knowledge bases, APIs, procedures. The assets can change; the capability endures as long as people and knowledge support it.
“If Software Engineering designs software, Capability Engineering designs Enterprise Assets. […] It does not replace existing disciplines. It integrates them, coordinates them and orients them toward a common goal: building organizations capable of evolving.” — The Capability Engineering Manifesto, FP-001, chapters IV and IX (translated from Italian)
- 01
Business Initiative
The starting intention: what the company wants to become able to do.
- 02 →
Capability
The ability to achieve a result repeatedly, with clear accountability and room to improve. It can outlast changes in technology, vendors or people, as long as the knowledge is shared.
- 03 →
Enterprise Asset
The durable elements through which the capability becomes operational, is retained, transferred and updated.
An example of continuity: if a company changes the AI model that supports its customer service, the procedures, data and responsibilities stay in place. One component is replaced, and the capability keeps working.
Six principles to start with
- 01
Organizations compete through their Capabilities, not through software.
- 02
A Business Capability is a strategic asset of the enterprise.
- 03
Every Capability must be made operational through governable Enterprise Assets.
- 04
Enterprise Assets must be designed to evolve, not merely to be delivered.
- 05
Artificial Intelligence amplifies the ability to build Enterprise Assets, but does not replace the design of Capabilities.
- 06
Capability Engineering integrates business, organization, technology and AI into a single governance model.
This discipline is still being written.
The Manifesto is a discussion draft, openly incomplete. These are the areas where we are looking for contributions from people working in companies, research and the professions.
Measurement
Metrics and maturity models to assess the value of a capability over time.
Governance
Governance models for the continuous evolution of Enterprise Assets.
Education
Academic and professional paths for people who design capabilities.
Tools
Architectures and tooling for the Capability Factory in the AI era.
Economics
Recognizing capabilities as company assets in economic and investment models.
We invite companies, software houses, system integrators, technology providers, practitioners, researchers, universities, designers, innovation ecosystems, and institutions.
Contribute to the Manifesto
A critique, a case, a better definition, an open question: every well-grounded contribution becomes part of the discussion. A new discipline is built through practice, debate and different points of view.
The current text: The Capability Engineering Manifesto, Foundational Paper FP-001, Discussion Draft 0.1.