Technical Leadership

The transition that defines the role: from making good decisions to enabling good decisions at scale. An architect who personally designs everything is a bottleneck whose effectiveness is capped by their own hours.

What the work consists of in practice: setting direction clearly enough that others can make consistent decisions without asking; making the right thing easy through paved roads, templates and working examples, which is more durable than persuasion; raising capability, since twenty engineers designing better is a larger effect than one architect designing everything; removing obstacles, which is what earns the credibility everything else depends on; and taking responsibility for outcomes rather than for having been right.

The behaviours that distinguish it from seniority: admitting error quickly and publicly, which is read as evidence that the reasoning is honest; giving credit away; disagreeing with more senior people when the evidence supports it, which is the behaviour that most determines whether junior people will raise concerns; and staying close enough to delivery to remain useful, since distance from the work is what erodes technical credibility fastest.

The measure that matters: do decisions get better when you are not in the room? If they do not, the direction was not set clearly enough, and the role has become a dependency rather than a multiplier.