run-one-on-one

name	run-one-on-one
description	Use when preparing for or improving weekly one-on-one meetings between a manager and a direct report
source	Ben Horowitz "The Hard Thing About Hard Things" (2014); Manager Tools Podcast (Horstman & Auzenne)
tags	["one-on-one","leadership","management","coaching","feedback","retention"]
verified	true

Run One-on-One

Make every 1:1 a high-signal conversation that builds trust, surfaces problems early, and develops the direct report.

Why This Is Best Practice

Adopted by: Manager Tools methodology used by 5M+ managers; Andy Grove formalized 1:1s at Intel as a core management tool Impact: Gallup research shows that managers who hold regular 1:1s reduce voluntary turnover by up to 25% and improve engagement scores by 3× compared to ad-hoc check-ins

Why best: The 1:1 is the primary tool for a manager to learn what is actually happening on the ground. It belongs to the direct report, not the manager — inverting the usual power dynamic creates psychological safety and honest reporting.

Steps

1. Schedule at a fixed time — Same day, same time, weekly. Treat cancellation as a last resort. Consistency signals that the person matters.
2. Prepare a shared agenda doc — Both parties add items before the meeting. The direct report's items go first. Use a running doc so nothing is lost between weeks.
3. Open with the direct report's topics — Ask "What's on your mind?" and let them lead for the first half. Do not fill silence with your own agenda.
4. Listen for signals under the surface — Note frustration, disengagement, or repeated themes. Ask clarifying questions: "Tell me more about that" and "What would make this better?"
5. Cover your own topics in the second half — Feedback, context, blockers you can remove, strategic direction. Be specific and brief.
6. Deliver feedback in SBI format — Situation, Behavior, Impact. "In Tuesday's design review [S], you interrupted two teammates [B], which shut down ideas before we heard them [I]."
7. Close with one commitment each — Both parties name one concrete action before the next 1:1. Write it in the shared doc.

Rules

• The 1:1 is the direct report's meeting, not the manager's status update.
• Never cancel; reschedule the same day if unavoidable.
• Keep notes in a shared doc both parties can read and add to.
• Do not use the 1:1 to deliver surprise performance news — that requires a separate conversation.
• Rotate between professional development, project work, and personal check-in topics across weeks.

Examples

A manager notices a senior engineer has gone quiet in planning meetings. In the 1:1, asking "What's frustrating you lately?" reveals they feel their technical opinions are ignored. The manager commits to explicitly soliciting their input in the next three meetings. The engineer commits to stating their concern once in writing before meetings. Four weeks later, engagement improves measurably.

Common Mistakes

• Status-report 1:1s — Spending the whole meeting asking "what did you finish this week?" wastes the only private conversation slot for real feedback.
• Skipping when busy — Canceling during high-pressure periods is exactly when direct reports most need support and managers most need signal.
• No written record — Without notes, commitments evaporate and patterns go unnoticed across months.

When NOT to Use

• Do not use the 1:1 format to deliver a disciplinary warning or a formal performance improvement plan — those require HR-documented separate conversations with a clear record.
• Do not hold 1:1s with someone you manage as a skip-level when their direct manager is present in the org; coordinate through the proper reporting line to avoid undermining that manager's authority.
• Do not substitute 1:1s for team-wide communication on decisions that affect the whole group — announcements made only in 1:1s create information asymmetry and erode team trust.