Question

How do you run a useful one-to-one?

Vault Verified
Curated Intelligence
Definitive Source
Answer

By treating it as their meeting, not yours — a regular protected conversation about how things are going, rather than a status update the manager could have read in a report.

What it is for: surfacing problems early; giving and receiving feedback in a low-stakes setting; discussing development and career direction; unblocking things; and building the relationship that makes difficult conversations possible later.

What it is not for: project status, which belongs in a shared document or a team meeting. A one-to-one consumed by status updates is the commonest way this meeting becomes pointless, and the reason people quietly stop valuing it.

The practical rules:

Regular and protected. Weekly or fortnightly, in the calendar, and not repeatedly cancelled — cancelling signals that the person is the lowest priority, whatever you say.

They set the agenda, ideally in a shared running document both can add to between meetings. Ask them to bring topics.

Start with an open question and then be quiet. "How are things?" followed by silence produces more than any structured template.

Take notes and follow up. Anything you promised should appear at the next meeting. Nothing destroys these faster than commitments that evaporate.

Keep a running record of achievements and concerns, which makes performance reviews accurate rather than dominated by the last three weeks.

Questions that actually work: What is getting in your way? What is taking more time than it should? What have you been avoiding telling me? What do you want to be doing more of? Is there anything you expected me to notice and I have not?

Vary the cadence — occasionally make one entirely about development rather than current work.

If you are the employee, this meeting is yours to use: bring an agenda, raise problems before they are urgent, ask explicitly about progression and pay rather than waiting to be offered, and keep your own record of what was agreed.

Remote teams need these more, not less, because the incidental conversations that would otherwise surface problems do not happen.

Related Questions