How does an architect develop architectural judgement in others rather than just answering their questions?
Show the full answer Hide the answer
The shift
Answering questions transfers conclusions; developing judgement transfers reasoning. An engineer who receives answers can apply them to the cases the architect foresaw and is stuck on the rest — which is every case that matters.
What develops judgement
1. Ask what they would do, first. Before offering an answer, hear their reasoning. It reveals where the gap actually is, which is frequently not where it appeared to be.
2. Explain the reasoning, not just the conclusion — including the constraints they did not know about and the options you rejected. Without those, the design looks arbitrary and cannot be extended to new cases.
3. Give them decisions to own, with a safety net. Judgement develops by making calls and observing outcomes; it does not develop by watching someone else make calls.
4. Let them be wrong where it is cheap. A reversible decision made badly is an excellent lesson. Preventing every mistake prevents the learning and produces engineers who cannot decide without you.
5. Make the trade-offs visible. "We are giving this up to get that" is the core habit, and modelling it consistently is more effective than teaching it abstractly.
6. Review reasoning, not just designs. In a design review, ask "what did you consider and reject, and why?" — which develops the habit of considering alternatives rather than the habit of defending a proposal.
The specific things worth teaching explicitly
- Classify by reversibility before deciding how much analysis to do.
- Ask what happens when each dependency is slow rather than down.
- Do the arithmetic — requests, bytes, round trips, what one node does — before the design.
- Name the assumption and its shelf life, because architectures decay from expired premises rather than from bad decisions.
- Write the decision down with the rejected options.
The measure
What the team decides well without you. An architect whose absence blocks decisions has been answering questions; one whose absence is barely noticed has been developing judgement — which is the harder and more valuable thing.