Capability First Architecture: Aligning Business and IT
It’s surprisingly common to lose track of the things you already have. Homeowners forget about tools sitting in the garage. Maintenance teams procure spare parts that are already stocked in a warehouse. And Organizations buy or build digital solutions that already exist somewhere in their own digital landscape.
This isn’t about bad intentions — it’s about visibility. It’s human nature to take the path of least resistance. When finding what already exists requires digging through documentation, tracking down the right stakeholders, or navigating a complex digital landscape, buying or building something new often feels like the easier option. At its core, this is a data problem — and one that has real business consequences.
Isn’t the Application Inventory the solution?
Application inventories — or more formally, the Configuration Management Database (CMDB) — are IT-centric repositories that track the applications in an environment. They cover things like lifecycle stage, business criticality, information classification, and support ownership. Useful for IT, but not particularly meaningful to the business. A stakeholder asking “what do we have that supports this business process?” won’t get a clear answer from a CMDB.
What’s striking is that this gap persists even with major vendors heavily promoting their CMDB platforms. The tools exist — the business-facing view largely doesn’t.
Adding the secret ingredient
The secret ingredient — the thing that brings business context into the picture — is something Enterprise Architecture has promoted for a long time: Business Capabilities.
Most referenced definitions come from TOGAF and the BIZBOK Guide, both of these refer to business capabilities as an important artifact to understand and describe the Business Architecture:
A business capability represents the ability for a business to do something. *TOGAF v10 - Business Capability Planning
“A business capability is a particular ability or capacity that a business may possess or exchange to achieve a specific purpose or outcome.” — Ulrich Homann, Microsoft / cited in Business Architecture Guild
“A business capability is what the business does.” — BIZBOK® Guide, Business Architecture Guild
Both point to the same idea: business capabilities describe abilities an organization needs to delive value and operate. Independent of how it’s done, what processes it follows, or what technology it uses. That last part is key — it’s what makes capabilities the right bridge between business and IT.
My organization already has business process, is that enough?
Business processes are important — they’re also a core part of Business Architecture. But processes describe how things are done, and that detail varies. The same business capability can be executed differently across business units, regions, or legal entities due to local regulations or operational differences. Capabilities sit one level above that variation, which is exactly what makes them more stable and more useful as a shared reference point between business and IT.
What is the value of business capabilities?
For an IT organization, the real value of business capabilities comes when you connect them to other elements of the IT landscape. A few examples:
- Applications — Which applications support each capability? Are multiple applications doing the same thing for the same capability? Are there gaps with no automation at all? How many application instances we have for a given capability?
- Application Cost — How much is the organization spending per capability? Is that investment proportional to how critical the capability is to the business?
- IT Initiatives — Which projects are building, enhancing, or transforming each capability? Are the most critical capabilities getting the right level of attention?
- Technical Debt — What is the tech debt per capability? Are there capabilities with tech debt that is not being remediated? Are the critical capabilities at risk due to tech debt?
These are just a few starting points. Capabilities can be linked to many other dimensions — risks, vendors, data, people — and each connection adds more context for better decisions.
How this helps aligning Business with IT and IT with Business?
Business capabilities give IT a business lens, and give the business a technology lens. Think of it as a Rosetta Stone — a shared language that helps both sides understand each other, collaborate more effectively, and ultimately make better decisions together.
- IT can see which areas of the business need automation or improvement, and align investments accordingly. IT can also proactively research and propose technology strategy to improve these areas.
- Business can see what applications are already available, which initiatives are in flight, and where there is overlap before committing to something new.
We tried this but didn’t worked for us.
This isn’t a one-off project you complete and move on from. It’s an ongoing practice — one that Enterprise Architecture can drive, but only works with active participation from the business side. That means leadership support from both IT and business is essential: not just to sponsor the effort, but to surface the right stakeholders and keep the right people engaged.