Organising the first PDX conference, I made hundreds of decisions personally — which vendor, which stage layout, which speaker slot. By PDX2026, my job had changed almost entirely. I was no longer making most of those decisions. I was designing the system that let other people make them well, without calling me first.
Decision-Maker vs System Architect
A decision-maker is the person everyone waits on. A system architect is the person whose absence doesn’t stop anything, because the structure already tells people how to decide. Most leaders I meet are still operating as the first, even as their organisation has grown far past the size where that scales.
What a decision-maker optimises for
Being right, quickly, on the specific thing in front of them. It feels responsive. It also means every important choice funnels through one person’s calendar.
What a system architect optimises for
Designing the conditions — the information flow, the escalation rules, the shared context — so that a good decision is the default outcome even when the architect isn’t in the room. It feels slower to set up. It scales without you.
The PDX Test
The clearest sign PDX had become a system rather than a one-man decision engine: during the 2026 event itself, I was mostly moving between stages, not fielding operational questions. The team had the structure to handle what came up. That wasn’t luck. It was eighteen months of deliberately building the structure instead of just making faster decisions.
FAQ
Does this mean leaders shouldn’t make decisions anymore?
No — it means reserving your personal decision-making for the handful of choices that genuinely need it, and designing everything else so your team doesn’t need to ask.
Where should a leader start?
Pick the single decision your team asks you for most often. Instead of answering it again, write down the rule you used to answer it, and hand the rule to the team. That's the first brick of the system.