About / Philosophy
Whether it has been described or not.
There is always a model of how the business creates value, what it depends on, how decisions get made and where work happens.
The question is whether that model is explicit, shared and usable, or whether it lives in someone's head, degrades when they leave and creates friction every time the business tries to move.
The discipline
It became anchored in IT for forty years because that is where complexity was most visible.
But the real problem was always at the business layer: in the strategy that could not be tested, the transformation that could not describe what it was transforming, and the investment that could not explain what it needed to connect to.
It accumulated frameworks, jargon and methodology until it became inaccessible to the people who needed it most: the people running the business.
It also stayed anchored to IT, which is only one vantage point of a business, not the whole picture.
They do not change by industry or size.
A 10-person company and a 10,000-person enterprise are both trying to understand what outcomes matter, what they need to know, what they can rely on, who can act and where work happens.
The complexity differs. The architecture does not.
Value
Everything else is in service of outcomes.
If you do not know what you are trying to create, where you are heading and what needs protection, every other architectural decision is guesswork.
Structure
A building architect builds the frame, the walls and the usability before trying to move anyone in.
Business architecture should work the same way. Describe the business first. Then fit the people, the systems and the capabilities into a structure that already makes sense.
Slowly in stable markets. Quickly in volatile ones.
The businesses that know what they are, precisely, explicitly and in a way that is shared across leadership, are the ones that act with precision.
Others rely on judgement and memory. Sometimes that works, until conditions change.
Intelligent systems can only navigate what has been described.
The businesses deploying AI well are the ones that did the architectural work first.
The ones deploying it poorly are finding out, expensively, that AI cannot fix what the business has not defined.
Architecture should make a business composable and collapsible: able to assemble new capabilities quickly and exit old ones cleanly, without structural damage.
See the approach