Posted on
Article 2 of 7 in the Architecture as Strategy series. Previously: The Gap Between Strategy and Execution Isn't a Culture Problem. It's an Architecture Problem.
A large infrastructure organisation we worked with had been through four restructures in six years. Each was designed to better align the business to its strategy. None held.
When we mapped their capabilities, the problem became immediately visible. Three separate business units were managing variants of the same customer fulfilment capability, different systems, different definitions, different performance standards. Governance sat in a fourth team with no line of sight to any of them.
The restructures hadn't failed because the thinking was wrong. They had failed because the underlying capability duplication was never resolved. You can redraw the org chart over a broken capability model. The model does not change.
Once a shared capability map was in place, stable, owned, and anchored to strategic intent, investment decisions changed. The next capital allocation cycle was structured around capability health rather than competing project business cases. Three programmes were consolidated into one. The governance function had a clear mandate for the first time in its history.
That outcome is not unusual. It is what Business Architecture is supposed to produce.
Business Architecture: A Discipline That Stops Your Strategy Dying in PowerPoint
The restructure is almost never the answer.
It is what happens when the answer isn't known.
When a strategy isn't landing, the instinct is to move the boxes. Align the structure to the intent. Draw clearer ownership. Create a new function with a mandate that feels bigger than the last one's. Six months of disruption later, the structure is different and the problems are largely the same, because the underlying issues were never about who reports to whom.
They were about what the organisation actually needs to be able to do, and whether it can do those things well enough, at the right level of investment, in a way that compounds rather than fragments.
That is a Business Architecture problem. And it's one of the most consistently misdiagnosed issues in complex organisations.
What Business Architecture Actually Does
The discipline separates two things that most organisations treat as interchangeable: what an organisation does, and how it's currently organised.
Departments, reporting lines, and job titles describe the structure at this point in time. They shift when a CFO leaves, when a division is merged for the third time in four years, or when a new executive decides the team needs reshaping to fit their model. They are inherently unstable.
Capabilities describe the work. They are stable, outcome-focused descriptions of what the organisation must perform to deliver its strategy, regardless of who currently does it or how.
Customer Onboarding. Risk Assessment. Product Fulfilment. Market Intelligence. These don't change when a General Manager leaves or a division is renamed. They persist across restructures. And they become the stable reference point that every downstream decision, i.e. investment, initiative design, governance, platform selection and more can anchor to.
When Business Architecture Works
When Business Architecture is working, three things become possible that otherwise aren't.
- Capital allocation starts with capability health. Which capabilities are genuine strategic differentiators? Which are fragmented across three teams doing largely the same thing with different systems? Which are over-invested relative to what they actually deliver? These are the questions that should drive budget decisions. They rarely do, because there is no shared map to answer them from.
- Strategic conversations stay grounded in what the business needs to do better — rather than in what projects are currently in flight, or whose initiative is being championed with the most conviction.
- Initiatives stop duplicating capability and start consolidating it, because the map exists to show where the duplication is. Without it, the duplication is invisible until the post-implementation review.
The practical impact on people inside the organisation is significant. One of the most exhausting features of repeated change cycles is that every initiative starts from scratch. Definitions get reinvented. Scope gets relitigated. Decisions that should have been settled two years ago resurface in every workshop. A well-maintained capability model removes that friction. It gives teams shared language and a clear view of where investment is needed and where it isn't.
What the Research Says
The evidence is consistent across sources, and the Australian numbers are particularly pointed.
ADAPT's 2025 research across 450+ Australian CIOs and CDAOs found that AI investment averages $28 million annually across local enterprises, yet 72% report failing to achieve measurable ROI. The picture is stark: while 78% of boards treat AI as strategic, only 24% of organisations possess AI-ready data architectures. ADAPT (ADAPT, 2025)
The diagnosis matters. This is not an AI problem. Organisations are funding capability aspirations on foundations that were never designed to support them. The AI use cases that generate real returns are anchored to clear, defined capabilities with known owners, quality inputs, and measurable outcomes. Without a capability model, there is no reliable basis to distinguish those use cases from the ones that look compelling in a business case and underdeliver at scale.
Forrester's Q4 2025 analysis of the enterprise architecture market found that only 15% of organisations have matured to the point where architecture genuinely connects strategy to execution, shaping customer journeys, value streams, and cross-functional work patterns rather than producing documentation that lives in a repository. The same analysis noted that the organisations reaching this level want architecture to live where decisions are made, not where assets are stored. (Forrester, January 2026)
Forrester's Business Architecture research is direct on mandate: most BA practitioners today focus on helping their firms adopt business capability investment planning, but the discipline's value is only realised when that work actively shapes how capital is allocated, not just how capabilities are described. (Forrester, 2025)
Gartner's 2025 analysis notes that CEOs are spending 5% of revenue on digital initiatives, with around half of C-suite leaders believing a significant source of digital value loss stems from poor estimation of expected benefits, and that unanticipated technical dependencies are a primary factor in lowering returns. Gartner identifies Business Architecture specifically as the discipline that addresses the why and the what before the how, the starting point for linking technology investment to business direction. (Gartner, 2025)
McKinsey's 2025 research across 2,000 executives found that organisations typically lose 20 to 30% of their potential returns on capital due to poor operating model alignment, with the gap between strategic intent and delivered performance widening in volatile conditions. (McKinsey, June 2025)
The consistent pattern: the return gap is not a technology gap. It is an architecture gap. Specifically, a capability clarity gap.
What a Capability Model Actually Looks Like
The F2A IAF is an extensive framework to manage this, and our Business Capability Model(BCM) is a tool to help map between business intent and business capabilities.
A well-built capability model organises across three levels, with enough structure to be useful, without becoming an org chart in disguise.
Strategic capabilities: what differentiates you in the market:
- Customer Experience: how you attract, serve, and retain customers
- Product and Service Innovation: how you develop and bring offerings to market with speed and relevance
- Market and Competitive Intelligence: how you sense and respond to shifts before they force a crisis
Operational capabilities: what keeps the business running reliably at scale:
- Risk and Compliance Management: managing obligation and exposure without paralysing the business
- Service Delivery and Fulfilment: the core work your customers and stakeholders depend on every day
- Workforce and Performance Management: the capability that shapes how the organisation actually functions
Enabling capabilities: the foundations that support everything else:
- Finance and Reporting: turning numbers into decisions, not just records
- Technology and Data Management: the infrastructure that everything else runs on
- Governance and Architecture: the discipline that keeps the whole system coherent over time
The model is not the deliverable. The model is the tool. Its value lies in the conversations it structures, the investment decisions it informs, and the shared language it creates across business and technology functions.
A well-run organisation can look at that map and say, with real confidence: this is where we over-invest, this is where we have dangerous gaps, and this is where our next dollar should go. Without it, those conversations happen anyway, just on the basis of opinion, relationship, and whoever assembled the most persuasive slide deck.
Where Business Architecture Breaks Down
Two failure modes account for most of the wasted effort.
The first is the documentation trap. The capability model gets built, carefully, accurately, with significant effort and then it doesn't influence any decision of consequence. It sits in a repository. Gets cited in strategy decks. Has no bearing on what gets funded or how initiatives get scoped. This is not a model quality problem. It's a mandate problem. The work was done; the authority to act on it was never established.
The second is the BA-EA disconnect. Business Architecture teams build capability models that describe the business in strategic terms. Enterprise Architecture teams build technical reference architectures. But the operational bridge between "we need stronger customer intelligence capability" and "here's how we're going to build it without creating three new data silos" doesn't exist. Both disciplines produce good work. Neither compounds into organisational capability.
McKinsey's research found that of organisations that announce cost-reduction or transformation initiatives, only one in four sustains savings for more than four years. McKinsey & Company That figure holds partly because the capability duplication and architectural debt that created the need for the programme in the first place are never addressed. The next initiative starts from the same place.
The Question Worth Sitting With
Most organisations have some version of a capability model. The useful question is not whether one exists.
It is whether the last significant capital allocation decision was structured around it.
If the budget went to the most urgent-sounding project, or the most tenacious executive sponsor, the model is not doing any work. And the strategy however well-reasoned is being executed against assumptions rather than evidence.
The Connection to What Comes Next
Business Architecture answers a deceptively simple question: what does this organisation need to be able to do?
Everything downstream depends on the clarity of that answer. How capabilities are connected (Enterprise Architecture). How specific problems are solved (Solution Architecture). How data is governed (Data Architecture). How risk is managed by design (Security Architecture). How intent survives delivery (Integration, Cloud and Application Architecture).
Without that clarity, each discipline makes its own assumptions about what matters strategically. Those assumptions, multiplied across dozens of initiatives over years, are where architectural debt accumulates and the gap between strategy and execution quietly becomes structural.
As we wrote in Article 1: the architecture you have in place today determines whether your next strategic priority becomes a capability or just another programme.
Business Architecture is where that determination begins.
Next in the series: Enterprise Architecture (coming soon)
