How to run effective 1:1 meetings

An effective 1:1 is a recurring, protected conversation owned by the person being managed, held often enough that nothing has to wait for it. It is not a status update: status can be read. The purpose is to surface the things that do not appear in a project tool: blockers someone is embarrassed by, ambitions they have not voiced, and problems that are still small enough to fix cheaply.

How often should you hold 1:1s?

Weekly for most people, fortnightly at the absolute longest. The interval matters more than the length.

The reason is arithmetic. If you meet monthly, a problem that starts the day after your last 1:1 gets four weeks to compound before you hear about it, and by then the person has usually made a decision about it, including, sometimes, the decision to leave. Thirty minutes weekly beats an hour monthly for exactly this reason.

The exception is very senior people who genuinely operate independently and will raise things unprompted. Even then, the cost of a cancelled weekly is lower than the cost of a missed month.

Who should own the 1:1 agenda?

The person being managed. It is their meeting; you are a standing guest with an agenda item at the end.

When the manager owns the agenda, the meeting drifts toward status, because status is what managers most easily generate questions about. When the report owns it, you find out what is actually on their mind, which is the entire point and the only thing this meeting is uniquely able to do.

This does not mean you arrive with nothing. It means your items go last, and get dropped when theirs run long.

What should you talk about in a 1:1?

Whatever they brought, then anything unresolved from last time, then your items. In practice the useful territory is blockers, working relationships, growth, and feedback in both directions.

A question that reliably outperforms "how is it going?" is a specific one that references something real: "last time you said the handover was eating your week: is that still true?" Specificity signals that you were listening and gives them permission to say no, it got worse.

  • What is in your way that I have not heard about?
  • What is taking more time than it should?
  • Is there anything you have been sitting on?
  • What do you want to be doing more of in six months?
  • What should I be doing differently?

What makes 1:1s feel like a waste of time?

Four things, in rough order of frequency: they get cancelled, they become status meetings, nothing raised in them ever changes, and the manager clearly does not remember the last one.

The last is the most damaging and the least noticed. Re-asking a question someone answered in detail three weeks ago tells them their answer went nowhere. After that happens twice, most people stop giving detailed answers, and the meeting becomes the status update you were trying to avoid.

Cancelling is the second-most damaging, because it is a ranking. Cancelling occasionally is unavoidable; cancelling on the same person repeatedly communicates their position in your priorities more clearly than anything you say in the meeting.

How do you keep 1:1s connected over time?

Write down two things after each one: what mattered, and what you committed to, and read them before the next one. That single habit is the difference between twelve disconnected conversations a quarter and one continuous thread.

The mechanism matters less than the consistency. A document per person works. A notebook works. What tends not to work is relying on memory across eight people and a twelve-week quarter, which is the default most managers fall back to.

This is the problem LetEmily was built for. Emily keeps the thread per person and assembles it into a brief before the next conversation, so building on the last one does not depend on you having filed anything, or on having had a spare ten minutes that morning.

Common questions

How long should a 1:1 be?

Thirty minutes weekly suits most reporting relationships. Sixty minutes tends to fill with status; fifteen is too short for anything someone is reluctant to raise.

Should 1:1s have a written agenda?

A shared running document that the person being managed adds to during the week works well. It removes the cold start and creates a record you can both look back at.

What if my report has nothing to talk about?

That is usually a signal, not an absence. Try a specific question about something they raised previously, or use the time for a growth conversation rather than filling it with status.

Stop leading from memory

Emily keeps the context of your team connected, and brings it back before your next conversation. Free to start, no credit card required.

Last reviewed