How architecture groups make decisions that stick

Rolling hills of dry golden grass dotted with dark green scrub, with a faint trail running along a ridge under a clear blue sky

I have sat in a lot of architecture meetings. Councils, review boards, guilds, working groups. Some made decisions still in force years later, some argued about again within a month. I assumed the difference was the people in the room. I now think it is a handful of habits, and most of them are boring.

Decisions nobody can find are not decisions

The most common way an architecture decision dies is not that someone overturns it. It is that nobody can find it. It lived in a meeting, a thread, or a slide deck, and a new team asks the question fresh.

The first habit is dull. Write the decision down in one place everyone knows about, short enough that people will read it. What was decided, what the alternatives were, and why this one.

I think the reason matters more than the decision. With it, the decision can be retired the day the reason stops being true. Without it, nobody can tell.

The people who decide should be the people who live with it

An architecture group of people who no longer write code will make decisions the people who do quietly route around, because the decision does not fit the work as it is.

I have come to believe the group has to include people who will feel the consequences, working engineers from the teams the decision touches, and it has to be small enough to decide. A room of twenty can discuss. A room of six can decide.

Decide the question, not the technology

The decisions that last tend to be about boundaries and contracts, how services talk to each other, who owns what, what a team may depend on and what it may not. The decisions that age fastest name a specific library or version.

A technology choice is the current best answer and should carry a review date, so that when it is replaced nobody feels a rule was broken.

Give every decision a date

Strangely, the decisions I have seen hold longest were explicitly temporary. A decision with a review date gets revisited on purpose, by the group. One with no date gets revisited by accident, by whoever is most frustrated, usually in a pull request comment.

The review date also lets people accept a decision they disagree with, because there is a time and a place to make the case again.

Where this stops being true

A small team does not need an architecture group. Three engineers who talk every day are the group. Writing decisions down is still worth doing. The rest is ceremony.

Some decisions are not the group's to make. When a direction comes from above, from a merger, a compliance requirement, or a company-wide platform choice, the group's job is to work out what it means for its systems and write it down. I think a group that is honest about which questions it owns keeps the authority to decide the ones it does.

Photo source: https://photos.robertstowe.com/utah