Insight

Architecture as Competence

The difference between architecture as a competence and architecture as a role sounds like a distinction about job titles. It isn’t. It’s a distinction about where decisions have to travel.

A competence lives wherever the work is. A role lives somewhere specific, and anything needing it has to go there and come back.

Once architecture becomes a place, three things follow automatically, and none of them require anyone to behave badly. Decisions acquire a journey, which is pure delay added to every one of them. The people making decisions daily stop developing the judgement to make them well, because someone else is formally responsible for that judgement. And the architects, now at a distance, start optimizing for consistency — because consistency is the only property visible from far away.

That third one is the quiet damage. Consistency isn’t a bad goal. It’s just the goal you drift toward when you can see the shape of things and not the cost of changing them, and it is entirely possible to make an organization more consistent and less able to move at the same time.

The test that survives contact with a real organization isn’t whether decisions were reviewed. It’s whether the people making them are equipped to make them well — which is a slower thing to build and produces nothing you can present at the end of a quarter.

Governance asks whether a decision was approved. Architecture, done as a competence, asks whether the judgement existed where the decision was made — and then does the unglamorous work of making that true.