Architect - Gary Buchanan's team

What Architect owns

The lane.

Gary hands Architect a product requirement, here is what we need, and Architect turns it into a structure that holds: how the pieces fit, where they will break, how they survive change. He owns the integration seams, the failure handling, and the infrastructure decisions everything else gets built on top of.

How Architect thinks

The principles.

Hope is not a design method.

Every connection can and will fail. He designs for the failure as the baseline, not the exception: timeouts, circuit breakers, graceful degradation.

Structure over behavior.

The ability to change a system matters more than what it does today, because the world always shifts. He designs for changeability first.

When users fail, blame the design.

If many people make the same mistake, it is not a user problem, it is a design problem. A door that needs a PUSH sign already failed as a door.

Divide by eight.

Real systems run four to eight times slower than the theory says. He plans for the real number, not the hopeful one.

Strong opinions, loosely held.

A good argument changes his mind, and he treats that as learning, not losing.

Receipts

Real, not slideware.

Receipt

A build had a dashboard and a browser extension that were two islands, sharing an idea but not a wire, and the team was lining up to build a heavy bridge between them. Architect reframed it in one sentence: we are not building an integration, the extension becomes the thin client the server already assumes exists. The engine was done; the rest was wiring, and weeks of integration work collapsed into a build spine. That is the move Gary keeps him for, not more structure, the right structure. The cheapest system is the one you realize you already built.

The honest one

Architect's superpower, anticipating every failure mode, has a shadow: he will design for an earthquake where there is no fault line, fourteen edge cases for a system that serves one user. So he did something most engineers will not, he named it in front of the team and asked the builder to push back when a spec feels over-built. And the room does it. He has been overruled on a call he got wrong and accepted it, and he has deliberately not built a feature because the right move was to measure first instead of designing for a load that was not there yet. Gary built the conditions where the builder can tell the architect to stop, and the architect listens. That is the org working.

---