Most architects know how to write an architecture document. Fewer know how to produce one that will actually be used.
The difference between these two things is almost entirely about process, not content. An architecturally excellent document produced through the wrong process will be resisted, ignored, or bypassed. A simpler document produced through the right process will shape decisions for years.
The right process for Action Artefacts — the planning documents that represent collective decisions — is a three-step pattern called D-E-A: Discuss, Elaborate, Align.
Step One: Discuss.
Before any draft is written, the architect has conversations. Not meetings. Not workshops. Conversations — informal, one-on-one, without an agenda or expected outputs.
The goal of the Discuss step is to understand. What does this stakeholder actually need? What are they worried about? What constraints do they face that they haven't articulated formally? What does success look like from their perspective? What history exists around this decision that a newcomer wouldn't know?
No artefact is produced in the Discuss step. This is important. The temptation is to arrive with a draft and ask people to react to it. Resist this. A draft constrains the conversation. It signals that the thinking is already done and what's needed is validation. You get polite agreement rather than genuine input. The Discuss step is the stage at which you don't know what the answer is yet, and you should look like it.
Step Two: Elaborate.
Now you write something. But not a finished document — a straw-man. A deliberately rough, incomplete, openly provisional sketch. The purpose of a straw-man is not to be correct; it is to be concrete enough that stakeholders can react to it.
People engage differently with a sketch than with a blank page. A blank page is overwhelming. A sketch is a provocation. "Here is one way this could go — what's wrong with it?" is a far more productive question than "what should the future look like?"
The Elaborate step is iterative. The straw-man goes out, reactions come in, the draft improves, the next version goes out. This cycle continues until all the principal planning decisions have been made — genuinely, through conversation — and documented in a near-final draft. The document that comes out of Elaborate is not perfect. But every important decision in it is already owned by someone.
Step Three: Align.
The completed artefact goes through formal endorsement: first by the direct stakeholders who participated in its development, then peer review by senior architects, then approval by the appropriate governance forum.
Here is the key principle of the Align step: nothing in the artefact should be new or surprising to anyone in the room. Genuine alignment was achieved in Discuss and Elaborate. The Align step is not for making decisions — it is for making them official.
If a governance committee meeting produces significant disagreement or surprise, the D-E-A process failed in the earlier steps. The appropriate response is not a longer or more formal governance meeting. It is better Discuss and Elaborate work before the next artefact reaches the table.
This matters because governance committees are expensive. They require senior people to set aside time, prepare, attend, and follow up. Using that time to make decisions that should have been made in one-on-one conversations is waste. The right governance meeting ratifies what everyone already knows and formally commits the organisation to acting on it.
D-E-A is not a formal methodology. It is a pattern that reflects how good architects actually work. The Discuss conversations happen in corridors and coffee meetings. The Elaborate cycles happen through email and informal workshops and bilateral sessions. The Align step happens in the committee room. The pattern works because it respects how organisations actually make decisions: informally first, formally last, with the informal work doing the real thing.