Running a Useful One-to-One

Most recurring one-to-ones are a verbal version of a report the manager could have read. They get cancelled first when things are busy, which tells you what everyone thinks they are worth.

The version that works is structurally different, and the difference is mostly about who owns it.

The reframing

It is their meeting, not yours. They set the agenda. You have items and they come second. A manager who arrives with a list and works through it has created a status meeting with a friendly name.

Status belongs elsewhere. Written updates, a board, a channel. Using synchronous time to transmit information that could have been read is the most common failure and the easiest to fix.

What remains is what needs a conversation: blockers requiring a decision, uncertainty about priorities, friction with someone, career direction, feedback in both directions, and anything they would not put in writing.

The mechanics

Weekly for direct reports, thirty minutes. Fortnightly for people who need less. Weekly beats monthly-for-an-hour because problems surface sooner and small things get raised before they compound.

Never cancel. Reschedule if you must. Cancelling communicates the priority accurately, and once it becomes cancellable it stops being useful.

A shared running document. Both add items during the week. Notes and actions in the same place. This solves the "what were we going to discuss" problem and creates a record you can look back over.

Do not fill the silence. The most useful thing said in these meetings frequently comes after a pause the manager was tempted to fill.

Questions that produce something

Not all in one session. One good question is enough.

"What is slowing you down?" The highest-value question available, and the one managers are best placed to act on.

"What are you unsure I want?" Surfaces misalignment before it becomes wasted work.

"What are you working on that you think is not worth doing?"

"What do you want to be doing in a year that you are not doing now?" Career direction, asked before someone has already decided to leave.

"What would you change about how the team works?"

"What feedback do you have for me?" Ask it, expect nothing for months, and keep asking. When it eventually comes, the response determines whether it ever comes again.

"Is there anything you have been meaning to raise?"

Feedback in these meetings

Specific, prompt, and about behaviour rather than character. "In Tuesday's review, the way that was phrased landed badly with the client" is actionable. "You need to work on communication" is not.

Praise specifically too. Vague praise reads as filler and devalues the specific kind.

Never deliver serious negative feedback for the first time in a performance review. If it is a surprise then, the one-to-ones failed.

Do not save things up. A month-old observation is much harder to act on and it signals you were keeping score.

The failure modes

It becomes a status meeting. Fix by moving status to writing.

It becomes therapy with no action. Listening is valuable and it needs to produce something. End with what happens next.

Only the manager talks. If you are speaking most of the time, the meeting is not doing its job.

Nothing is written down, so the same issue is raised three months running with no one noticing.

It gets cancelled.

Skip-levels and reverse

Skip-level meetings — with your reports' reports — surface things that do not travel up. They need care: the purpose is understanding the organisation, not evaluating the manager in between, and it should be explicit which it is.

For the person being managed: you can run this too. Bring an agenda, raise the blockers, ask for the feedback, ask what your manager is worried about. A meeting where you arrive with three items is materially more useful than one where you wait to be asked.

The first one with a new report

The opening meeting sets what the series becomes, and there is a version that works better than a status update.

Say what the meeting is for. Their agenda, not yours; not status; nothing is off limits.

Ask how they like to work. How they prefer feedback, how they want to be told when something is wrong, what a bad week looks like for them.

Ask what they need from a manager, and be honest about what you are good and bad at.

Agree the mechanics. Frequency, the shared document, who adds what.

Ask what they are worried about. Early, before anything has gone wrong.

Do not use it to set objectives. That is a different conversation and mixing them makes this one feel like assessment.

Twenty minutes of this makes the following year of meetings substantially more useful, and almost nobody does it.