Engineering leadership

Delegation is a control system

Delegation is not throwing work over a wall. It is choosing the right amount of context, authority, and feedback for the risk.

~5 minLeadership
scroll
01 · the shape

Too little context creates rework

Bad delegation sounds efficient in the moment: "can you handle this?" Then the person guesses the goal, the constraints, the stakeholders, and what good looks like.

manager · task handoff

The useful signal is usually already there.

team has a map

Leadership bugs are system bugs too. Pull context out and the team graph starts wobbling.

02 · the move

Delegate the decision, not just the task

Name the outcome, boundaries, owner, check-in rhythm, and decision rights. People grow when they own judgment, not just typing.

delegation-brief.md

A brief beats a hallway memory.

03 · the check

Tune the feedback loop

High-risk work needs tighter checkpoints. Familiar work can run looser. Delegation fails when the loop is either absent or suffocating.

team clarity switchboard
muddy
clear0
muddy: people can move, but they are guessing while they do it

Flip the switches and watch the story turn into a tiny operating model.

0clear owner for the outcome
0checkpoints before launch for risky work
0mystery decision rights
04 · the takeaway

Control is not the same as doing it yourself

A good delegation system increases trust because everyone knows where autonomy starts and where support appears.

source trail