First 1:1 with a New Report How-to
Your first dedicated 1:1 with a new report is not a status meeting wearing nicer clothes. It’s a relationship OS install: cadence, communication prefs, decision rights, and how you handle bad news. Optimize for working agreements. Project updates can wait.
Time box: 30-45 minutes. For first-time and experienced managers, including resets after an org change. Stage home: New Manager hub. Ongoing rhythm: how to run a 1:1 meeting. Report-side ramp: New Hire hub and the First-week question list play.
When to use (and when not to)
Schedule the first 1:1 in week 1 when someone joins your team (new to company or new to you). If you inherited a team mid-stream, run a “first 1:1 with me” within the first two weeks for each report – same play, reset framing.
Do not treat a hallway hello, standup chat, or Slack thread as the first 1:1. Do not combine this meeting with a performance warning, PIP talk, or compensation negotiation. Those need their own container.
HR does not belong in a normal first 1:1. Involve People/HR when policy or risk requires it, not as a default third wheel.
Who is involved
- You (manager)
- Your report
- Optional note-taking on a shared doc both can see
Manager prep (10-15 minutes before)
- Re-read role context: what success looks like for this seat in the next 30-60 days.
- Draft your proposed team norms lightly (cadence, update style) as a starting offer, not a decree.
- Set a listening goal: leave with their preferences written down, not with your monologue completed.
- Clear the calendar buffer so you don’t sprint out at minute 29.
- If they’re brand new to the company, expect orientation questions; if they’re new to you only, expect history and reset needs.
Agenda (30-45 minutes)
| Time | Segment | Goal |
|---|---|---|
| 0-3 min | Purpose | “This is your meeting. Here’s how we’ll use it” |
| 3-12 min | Their story | Listen: strengths, working style, support needs |
| 12-22 min | Role success | Align on near-term “good,” priorities, landmines |
| 22-35 min | Working agreements | Cadence, feedback, decisions, bad-news path |
| 35-45 min | Recap + docs | Write agreements; book the recurring 1:1 |
If you only have 30 minutes, protect purpose, listening, and working agreements. Shrink status to zero.
Questions that build trust (pick, don’t interrogate)
- What does support from a manager look like at its best for you?
- How do you prefer feedback (live, written, same day, in 1:1)?
- What are you optimizing for in the next few months?
- What’s one thing that usually gets in your way when starting with a new team?
- How do you like to get information: docs first, chat, or talk it out?
- Anything you want me to know about how you work best (schedule constraints, focus needs)?
Stay away from questions that pressure people to disclose private health, family, or other protected information. Keep it professional and voluntary.
Scripts
Opening purpose:
This first 1:1 is about how we’ll work together, not a project download. I’ll ask a few questions, you’ll ask yours, and we’ll leave with working agreements: cadence, how we share bad news, and what “good” looks like for the next month. Going forward, this meeting is primarily yours.
Closing recap:
Let me read back what I think we agreed: we’ll meet [cadence], you’ll update me via [channel], decisions you own include [X], and if something’s going sideways you’ll ping me [how/when]. I’ll put this in our shared doc – edit anything I got wrong.
If they only bring status:
Status can live async. What I most need today is how we should run this relationship so status never surprises either of us.
Output: working agreements one-pager
Working agreements: [Manager] + [Report]
Date:
Cadence: [e.g., weekly 30 / biweekly 45]
Agenda owner: Report brings topics; manager adds as needed
Update style between 1:1s: [chat / doc / email]
Decision rights: Report owns [ ]; bring to manager [ ]
Feedback prefs: [ ]
Bad news: how we’ll escalate early
Near-term priorities (30 days):
Open questions / follow-ups:
Next 1:1:
Sample (fictional): Manager Chris and report Avery agree on weekly 30s Tuesdays, async Friday bullets, Avery owns ticket triage decisions within SLA, Chris wants early heads-up on customer risks, feedback same-week in 1:1 unless urgent. They paste the doc and book the series.
Document agreements both need. Keep private notes (your coaching hypotheses) out of the shared doc. Don’t write anything you’d be ashamed to see forwarded.
Watch-outs
- Monologuing. If you talked most of the time, you ran a briefing, not a 1:1.
- Only status. You’ll recreate a standup and wonder why trust is thin.
- Promising what you can’t control. No guarantees on promo timing, headcount, or other teams’ behavior.
- Skipping the write-down. Verbal norms fade by week three.
- Stacking hard topics. First 1:1 is install day, not judgment day.
Hand-off to weekly cadence
Book the recurring series before you leave the room. Point them to report-side tools: first-week questions, first 90 days, onboarding checklist. Your ongoing operating system is the weekly 1:1 play/guide at how to run a 1:1 meeting. If you’re new to managing, keep first-time manager playbook and first 90 days as a new manager nearby.
One strong 1:1 does not “fix engagement forever.” It installs the channel you’ll use to do the real work together.
You’re done when working agreements are written, the next 1:1 is on the calendar, and both of you can say how bad news travels.