Engineering leadership

The one-on-one is not a status meeting

If your one-on-one is just a Jira tour with feelings at the end, you are wasting the only meeting designed for the person instead of the project.

~5 minLeadership
scroll
01 · the mistake

Status has better homes

Status belongs in the board, the standup, the project doc, or the pull request. The one-on-one is for signal that does not fit there: motivation, confusion, ambition, burnout, friction, trust, and the weird little blocker someone is embarrassed to name in a group.

calendar · 1:1

Same slot, better agenda.

team has a map

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

02 · the owner

The report should shape the agenda

A manager can bring questions, but the meeting should not become manager theater. Ask the person to keep a running note. What should we talk about? What decision do you need? What feedback would help? That turns the meeting from inspection into leverage.

The best one-on-one agenda is alive before the meeting starts.stdout manager note
03 · the pattern

Listen for changes in slope

A single rough week might be noise. A month of flat energy is signal. The value of regular one-on-ones is not one brilliant question. It is noticing the slope early enough to do something humane and useful.

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.

0shared note beats memory
0commitments max, or nothing moves
0minutes is enough when the agenda is real
04 · the follow-through

Trust is built after the meeting

The real one-on-one test happens later. Did the manager unblock the thing? Did they give the feedback they promised? Did they remember the career thread? The meeting creates the promise. Follow-through makes it believable.

source trail