Building engineering teams that ship in the AI era

Surface the problem whose solution compounds, not the ten that look urgent.

Every yes is an allocation. Saying no well is what separates leaders from order-takers.

The most consequential call an EM makes each quarter.

Picking what gets nothing this quarter. Explicit starvation beats implicit neglect.

Inference spend treated as a quarterly allocation by engineering.

A version leadership will remember and peers won't undermine.

Trust survives only if the re-narration is honest about what changed and why.

Great engineers are not on job boards. Sourcing is a leadership activity.

Rituals that keep the bar where it started, against quarterly pressure.

Offer-to-ramp is where most hires are won or lost.

A new developmental arc, and the trap of rewarding volume over judgment.

When separation is the right call, make it humane, fast, and final.

Tolerating them longer than six months is almost always a mistake.

Too many seniors: gridlock. Too many juniors: low ceiling.

The specific practices that make distributed teams work.

Planning cadence lags delivery cadence when work shrinks to hours.

Design the path explicitly. Don't let engineers improvise it.

What review is for now (taste, architecture, intent), and what to stop reviewing.

Agents fail silently, plausibly, at scale. Monitoring catches them.

Agentic systems built to live within their token, latency, and reliability budgets.

Documentation as the infrastructure the team runs on.

Each new hire should improve onboarding for the next.

The team's running log of what was chosen and why.

Async as a coordination contract with its own discipline.

What humans still coordinate on when agents run overnight.

Humane rotation design. Burnout makes incidents worse.

Imagining failure before it happens is cheaper than recovering from it.

Detection, containment, and rollback of agent-driven damage at scale.

Complexity wins by default. Make simplicity a team norm.

Stake ground and still update when the evidence arrives.

The last line of defence against shipping slop.

Voice the concern others are avoiding, without becoming the blocker.

Conventional pyramids underfit non-deterministic systems.

The small set the team will not compromise regardless of pressure.

A learning ritual rather than a gatekeeping one.

Say hard things in a way the receiver can act on.

Leaders who can't take critique don't get honest teams.

LOC, PR count, keystroke telemetry. Refusing to measure is a leadership act.

Who reads it, what decision it drives, what happens when the number moves.

Observable behaviour, not survey score. What you do on Monday.

DORA as baseline, plus what it misses.

When refusing to compare is the leadership move.

A new vocabulary for the work that still requires humans.

Run long-horizon work inside a short-horizon org without losing the team's confidence.

Most major problems were visible six months before they exploded.

The quiet senior, the slipping review latency, the unasked question.

Leaders make worse decisions when tired, anxious, or triggered, and almost never notice.

Intervening too fast and too late are both common.

If you can't write it clearly, you haven't thought it clearly.

A leader's habit of leaving every decision with something written.

The first thing that dies under pressure. And the thing most necessary under it.

External presence compounds across years. A core asset built slowly.

Built in small choices over a decade, in uncelebrated moments.

The disagreement on record, the commitment real.

The personal list, written down before the pressure arrives.

Use power with awareness; push back on peers who misuse theirs.

What's disclosed, what's expected, what's off-limits, before someone crosses a line no one named.