Composable Thinking Is Trending. But What Are You Actually Composing?
“Composable thinking” is having its moment in the enterprise architecture world.
CIOs are being told to think in building blocks. Analysts are urging organisations to modularise everything. Vendors are retrofitting the word composable into every product suite imaginable.
But here’s the uncomfortable truth:
You can’t compose what you haven’t defined.
Most organisations still lack a clear, shared, and stable view of their business. Not just their systems. Not their structure. But the actual capabilities the business needs to perform, regardless of who or what delivers them.
Without that, “composable” becomes yet another buzzword dressed up as a solution.
What’s really going on?
Let’s look at the landscape:
- CIOs are under pressure to deliver agility, speed, and reusability
- Business leaders want solutions that can shift with market and policy changes
- Everyone’s talking about modular design, but very few can pinpoint what they’re modularising
So what happens?
Projects get restructured, teams get reshuffled, platforms get replaced, but all on top of assumptions about how the business works, rather than a clearly articulated model of what the business actually does.
We end up “recomposing” in the dark.
Why capability models matter more than ever
A business capability model doesn’t solve all your problems, but it gives you the map.
It answers the foundational questions:
- What are the stable functions this organisation performs?
- Which of them differentiate us, and which just need to be done well?
- Who owns the data and decisions in each area?
- What are we changing, and what impact will that have?
It acts as the backbonefor:
- Change initiatives
- Technology investments
- AI and automation strategies
- Risk and compliance decisions
- Operating model design
And it stays relevant even as systems, processes, and people shift, because capabilities reflect the what, not the who or how.
The illusion of composability
Most organisations aren’t “composable”, they’re just constantly recomposing.
We see this all the time:
- A vendor sells a modular solution that doesn’t match the actual business structure
- Teams re-architect without alignment to strategy or capability ownership
- Leadership asks for flexibility, but lacks a common model to assess impact or opportunity
You can’t reuse what isn’t understood. You can’t align what hasn’t been mapped. And you can’t orchestrate agility if your business logic lives inside spreadsheets and PowerPoint decks.
What composable thinking really needs
Not another framework.
Clarity.
Clarity about:
- What your organisation is designed to do
- What it should be investing in
- Where agility is actually needed, and where it’s just noise
That’s where a capability model comes in. It’s not a silver bullet, it’s a shared foundation.
From fragile to agile isn’t about tooling. It’s about structure.
You can buy all the composable tools you like. But without a capability-led foundation, all you’re doing is rearranging the furniture, while the house is still on fire.
The organisations that truly become agile? They start by getting clear on what they are, and build from there.