Effective 1-on-1s — the highest-leverage meeting in your week.

01What 1-on-1s are actually for

Three legitimate purposes, in priority order:

1. Removing blockers for the report, that they can't remove alone.
2. Career and development — feedback, growth opportunities, longer-term direction.
3. Relationship — building enough trust that hard conversations are possible when they're needed.

1-on-1s are not for: status updates (these belong in async docs), assigning new work (this belongs in normal standups or async), discussing other team members (this poisons the trust required for the meeting to function).

If your 1-on-1s consist of "what did you work on this week?" you're using the most expensive 30 minutes in your week on a question Slack could answer.

02The report owns the agenda

The single biggest improvement to 1-on-1s: the report owns the agenda. Not the manager.

Why? Because the meeting exists for the report's benefit. The manager is there to listen, unblock, and coach. If the manager drives the agenda, the meeting reverts to status updates because that's what managers naturally want to know.

In practice: shared doc with rolling agenda. Report adds topics during the week as they come up. Manager can add topics too, but the report runs the discussion.

03If you're the report — what to bring

Four categories worth raising:

• Things you're stuck on. Technical blockers, organizational blockers, decisions you can't make alone. Your manager's #1 job is to unblock you.
• Feedback requests. "I sent this design doc — did you see it? Any concerns?" or "I gave a tough piece of feedback to a peer — how do you think I handled it?"
• Career topics. What's next for you. Promotion criteria. New responsibilities. What you'd want to do in 6 months.
• Strategic context you don't have. "Why did the company change priorities? What does that mean for our roadmap?"

What NOT to bring (or bring sparingly):

• Pure status updates ("I shipped X this week"). Move to async.
• Complaints about teammates. Address those directly with the teammate first.
• Decisions you can and should make on your own. Don't outsource judgment.

04Questions worth asking your manager regularly

• "What's something I should be doing differently?" — invites feedback you might not get otherwise.
• "What does promotion to the next level look like?" — opens the criteria conversation early.
• "What's the most important thing I should be working on right now?" — calibrates priorities.
• "Is there anyone on the team you're worried about?" — gives you context to help, when appropriate.
• "What's something I'm doing that you'd want me to keep doing?" — captures things to preserve, often under-recognized.
• "What's worrying you right now?" — earns trust by showing you care about their context too.

05If you're the manager — your job in the meeting

Your job in a 1-on-1 is not to give updates, give orders, or check on progress. Your job is:

1. Listen. The report should be talking 60-70% of the time. If you're talking more, you're doing it wrong.
2. Unblock. When they share a problem they can't solve alone, your highest leverage is removing the obstacle.
3. Develop. Coach through hard problems. Offer feedback on growth areas. Connect them to opportunities.
4. Share context. Strategic decisions, organizational changes, things they need to know that aren't being shared elsewhere.

If you find yourself filling the meeting with status questions, the symptom is that you don't have enough async visibility into the team's work. Fix that elsewhere; don't burn 1-on-1 time on it.

06Questions worth asking your reports regularly

• "What's blocking you that I could help with?" — primary question. Ask every meeting.
• "How are you feeling about the work right now? Is anything off?" — emotional read on engagement.
• "Is there feedback you have for me? Something I should do differently?" — asking once gets nothing; asking quarterly opens the channel.
• "What did you learn this week?" — emphasizes growth over output.
• "If you could change one thing about the team, what would it be?" — uncovers systemic issues.
• "What's something you've been thinking about that we haven't discussed?" — opens the door for hard topics.

Don't ask all of these every week. Rotate. The repetition of one or two questions over time builds trust; constantly different questions feel performative.

07Cadence and duration

Weekly, 30 minutes, recurring. The cadence matters more than the duration. Biweekly 1-on-1s drift into status updates because too much accumulates between sessions; weekly keeps the meeting tactical and current.

Exception: senior engineers who don't need much management can do biweekly. New hires, struggling reports, or anyone in a transition should be weekly.

Don't cancel 1-on-1s casually. If the manager keeps canceling, the message to the report is "you're not important enough." Reschedule, don't cancel. If absolutely necessary, both parties acknowledge it and find a near replacement.

08Skip-level 1-on-1s

Skip-level 1-on-1s — meeting with your manager's manager — are valuable but easily misused.

Good uses: understanding organizational direction, getting feedback from someone with different perspective, raising concerns that need a different audience than your direct manager.

Bad uses: complaining about your direct manager (this gets reported back, and the trust impact is severe), trying to skip your manager in the chain of command for decisions.

If you have feedback for your manager, give it to them first. If they ignore it, then escalate. Going to skip-level first burns the relationship faster than the original problem would have.

09The hard conversations

Sometimes the 1-on-1 needs to deliver difficult feedback or address a real performance issue. The patterns that work:

• Be direct. Soft-pedaling makes the feedback unclear. The person leaves not understanding what changed.
• Be specific. "Your code reviews are slow" is feedback. "You took 3 days to review my PR last week" is actionable.
• Be timely. Don't save up six months of feedback for one meeting. Give it as soon as you observe the pattern.
• Connect to impact. "When X happens, the result is Y" makes the consequence visible. People respond to impact, not to abstract criticism.
• Make next steps clear. Don't leave a hard conversation without agreed-upon changes and a follow-up date.

10The notes habit

Both sides should take notes during 1-on-1s. The shared doc serves three purposes:

• Tracks commitments — what each party agreed to do before next meeting.
• Captures recurring themes — patterns you can see over months that you'd miss meeting-to-meeting.
• Provides continuity — coming into a meeting knowing what was discussed last time.

Start each meeting by reviewing the last meeting's commitments. Did they happen? If not, why? This single habit raises the followthrough rate of 1-on-1 agreements by 5x in my experience.

∞The compound

1-on-1s done well compound. Each one builds slightly more trust, surfaces slightly more context, accumulates slightly more useful feedback. After a year of good 1-on-1s, the manager and report have a shared model of the work, the team, and the trajectory. That shared model is what makes hard conversations possible — and what makes the easy ones efficient.

Done poorly, 1-on-1s compound in the opposite direction. The report stops bringing real issues because nothing happens with them. The manager stops listening because the meetings are boring. The relationship hollows out. Eventually one party leaves.

Both outcomes are produced by 30 minutes a week. The difference is what you do with those minutes.