No Right Answers, Only Defensible Trade-offs

The question that gives a junior architect away is “what’s the right architecture for this?” — asked in the tone of someone expecting a right answer to exist. It doesn’t. Not because the field is vague, but because every architectural choice buys something and pays for it somewhere else. Consistency costs availability. Speed now costs speed later. Buying costs control; building costs time. There is no option on the table that only wins.

Which means architecture cannot be judged the way we instinctively want to judge it — on whether the choice turned out best. You almost never know that at decision time, and by the time you do, the conditions have moved. Judging an architect on outcomes alone rewards luck and punishes sound reasoning that met bad fortune.

The real standard is whether the decision was defensible. Did you name the alternatives you rejected, and why? Did you state the trade-off you were accepting — out loud, not buried? Did you surface the assumptions the choice depends on, and the conditions under which you would reverse it? A defensible decision can still turn out wrong, and remain a good decision. An indefensible one can happen to work, and remain bad architecture — you simply haven’t been caught yet.

This is what a design review is actually testing, though few of them say so. It is not checking whether the design is correct, as if correctness could be certified in a room. It is pressure-testing whether the reasoning holds when someone pushes: the CFO asking what it costs at ten times the volume, the security lead asking what happens when this component is breached, the operations lead asking who gets paged at 3am. The design that passes is not the clever one. It is the one whose logic is still standing after the questions.

This is why “it depends” is not the dodge people take it for — provided you can finish the sentence. “It depends” followed by silence is an architect who hasn’t done the work. “It depends — on your consistency requirements, your failure budget, and how much you trust this vendor in three years, and here is how I’d weigh each” is an architect doing the entire job in one breath.

Learning to think in defensible trade-offs, rather than hunting for answers that were never there, is one of the core moves the manifesto and the books set out to teach.