How to Run a 1:1 Meeting (Agenda + Script)
It’s Thursday at 10:02. Your weekly 1:1 starts two minutes late. The first twenty minutes are ticket updates you both already saw in the project tool. At 10:28 someone says “any career stuff?” and there’s no time left. You both smile, book nothing, and leave feeling busy but not better.
That’s how most one-on-ones die: not from bad intent, but from status eating the slot. A useful 1:1 is a private operating and development conversation. It is not a standup, not a performance ambush, and not therapy. This guide gives you a reusable 1:1 meeting agenda template, talking scripts, and a simple split that protects growth time when the week gets loud.
It’s for new managers learning the craft, ICs who want to drive their weekly 1:1 with their manager upward, and directors who want a shared cadence across a team. For broader meeting hygiene, pair this with how to run effective meetings. If you’re still ramping, the first 90 days at work shows how early 1:1s should tilt toward clarity and early wins.
What a 1:1 is for (and what should move elsewhere)
Use the 1:1 for: priorities and tradeoffs that need a shared call; blockers the other person can remove or escalate; feedback both ways; career and growth in small regular doses; trust topics that don’t belong in a group.
Move out of the 1:1: pure status that belongs in a doc, ticket, or channel; decisions that need three other people; long project reviews; announcements that should be written once for the whole team.
If the meeting only exists to re-read a dashboard, cancel it and send the update. Save the live minutes for judgment, coaching, and relationship.
How often and how long
There is no universal cadence that fits every role. Match frequency to how fast the work changes and how new the working relationship is.
Practical starting points (adapt, don’t worship):
- Weekly, 30 minutes for most ICs and new manager–report pairs
- Weekly, 45–50 minutes when someone is new, struggling, or in a high-change role
- Biweekly, 30–45 minutes for senior ICs with stable priorities and strong async habits
- Shorter pulse plus a longer monthly deep dive if calendars are brutal and both people prep well
Protect the slot. Reschedule when you must; don’t delete. Constant cancels teach people the relationship is optional.
Who owns the agenda
Shared ownership, employee-led prep. The manager owns the cadence (the invite exists, happens, and produces follow-up). The employee should own most agenda items, because they live closest to the friction. Managers add coaching themes, feedback, and org context.
If the manager always builds the whole agenda, the 1:1 becomes a status interrogation. If the employee never brings anything, it drifts. Both people add to a shared doc before the meeting. The person who needs the conversation most (usually the employee) gets first claim on the timeboxes.
The ops vs. development split (protect growth time)
Here’s the move that saves most failing 1:1s: split the meeting into operations and development/trust, and protect the second half.
- Operations (15–20 minutes max): priorities, blockers, decisions needed this week, quick feedback on live work
- Development / trust (protected time): career, skills, working relationship, longer feedback, how work is actually feeling
If operations always eats the whole slot, growth conversations never happen. When that pattern sticks, schedule a separate 15-minute weekly priorities sync (or push status fully async) so the 1:1 can stay human and developmental. Don’t wait for a quiet week. Quiet weeks don’t arrive.
Name the split out loud the first time: “We’ll do ops for the first half, then save the last 10–15 for development. If we’re deep in a blocker, we book a follow-up rather than steal the whole hour.”
Shared 1:1 doc structure
Keep one living doc per pair. Newest week on top.
# 1:1 - [Name] <> [Manager]
Cadence: weekly / 30 min
Norms: employee drives agenda; ops max 20 min; notes are for follow-up, not surveillance
## Running list
- Open commitments (owner + due date)
- Parking lot
- Career themes (ongoing)
## Week of YYYY-MM-DD
### Pre-read / async prep (both)
Employee:
- Wins / progress worth naming:
- Priorities this week (top 3):
- Blockers / asks:
- Feedback request (specific):
- Career / development item (optional):
Manager:
- Topics I want to cover:
- Feedback I owe:
- Org / context they need:
### Live agenda (timeboxed)
1. Check-in (2–3 min)
2. Operations: priorities, blockers, decisions (12–15 min)
3. Feedback both ways (5–8 min)
4. Development / trust (8–12 min)
5. Commitments + close (2 min)
### Notes / decisions / owners
-
30-minute timeboxed agenda
| Minutes | Segment | Job |
|---|---|---|
| 0–3 | Open | Human check-in + confirm agenda |
| 3–18 | Operations | Top priorities, blockers, decisions |
| 18–23 | Feedback | One specific ask each way if needed |
| 23–28 | Development / trust | Career, skills, working relationship |
| 28–30 | Close | Owners, due dates, what moves async |
If you’re at 45 minutes, expand development, not status. Status expands forever if you let it.
Opening scripts
Manager opening:
“Thanks for the pre-read. I saw your top three and the blocker on the vendor. Anything change since you wrote it? Let’s knock ops in fifteen minutes max, then I want time for the career note you flagged.”
Employee opening:
“I put three priorities and one ask in the doc. Biggest need from you today is help unblocking the legal review. If we have time, I also want five minutes on whether I should lean into mentorship or keep my head down on delivery this quarter.”
A short human check-in is fine. Don’t let small talk become the whole meeting when someone is blocked.
Async prep checklist
Employee (about 10 minutes the day before):
- [ ] Top 3 priorities and what “done” means this week
- [ ] Blockers with a clear ask (decide / escalate / advice / air cover)
- [ ] One win worth naming
- [ ] One feedback ask tied to a concrete artifact or moment
- [ ] Optional: one career or development line
Manager (about 10 minutes before):
- [ ] Read the doc; don’t make them re-present it live
- [ ] Note decisions only you can make
- [ ] Prep one piece of specific feedback (observation + impact + ask)
- [ ] Flag org context they need
- [ ] Protect the development block on your clock
Question bank managers can rotate
Don’t ask all of these every week. Rotate.
Priorities: What are the three things that matter most this week, and what are you saying no to? Where are we pretending something is on track when it isn’t?
Blockers / collaboration: What’s slow that shouldn’t be? Who do you need me to talk to so you don’t keep chasing? Where are handoffs fuzzy?
Feedback: What’s one thing I did last week that helped or got in your way? On [doc/meeting/customer email], what’s one change you’d make?
Career / growth: What skill do you want more reps on in the next six weeks? What work would make you proud at the next review cycle? Are you bored, stretched, or buried, and what’s the evidence?
Wellbeing at work (practical, not clinical): Is your workload sustainable for the next two weeks? What’s draining energy that we can redesign? Do you need cover, a deadline move, or fewer meetings?
If someone shares serious distress, listen, don’t diagnose, and point them to company resources or HR/People support as appropriate. A 1:1 is not a substitute for professional care.
What employees should bring every time
- Top priorities (three or fewer)
- One clear ask
- Risks you see early
- A feedback request tied to real work
- A development crumb at least every other week so career isn’t a once-a-year panic
Driving your employee 1:1 agenda is not needy. It’s how adults run a working relationship.
When the 1:1 turns into pure status
Name it and redirect:
“We’re narrating tickets we can both read. Let’s park the green items. What’s the decision or blocker that actually needs us live?”
Then finish the decision fast and return to development, or book a 15-minute priorities sync and reclaim the 1:1 for coaching and trust. If status keeps winning, fix the system: async updates before the meeting, tighter tickets, or a separate ops huddle.
Notes, remote, and cancel-heavy managers
Take light notes in the shared doc: decisions, owners, due dates, feedback themes. Avoid secret dossiers. Close every meeting with what you decided, who owns what by when, what moves async, and what you’ll revisit next time.
Remote 1:1s need slightly more structure. Keep the doc open and edit commitments live. Check energy and workload explicitly. Treat hybrid pairs as remote meetings so the remote person isn’t locked out of a hallway conversation.
If your manager cancels constantly:
“We’ve slipped the last three 1:1s. I can keep sending a short written update, but I need a reliable 20 minutes every other week for blockers and growth. Can we protect Thursdays, or pick a backup slot?”
If there’s never an agenda:
“I’ll keep a shared doc with priorities, asks, and one development topic. If you add anything by noon, we’ll cover yours first. Otherwise I’ll drive from the doc so we don’t spend the whole time on status.”
Manager one-on-one best practices (quick list)
- Keep the invite sacred; reschedule, don’t ghost
- Read prep; don’t make people perform their doc
- Cap operations; protect development
- Give feedback early and specific
- Ask for feedback on your management and act on one thing
- End with owners
- Escalate blockers you uniquely can move
Directors standardizing across a team: publish the shared doc format and the ops/development split as a default. Let pairs customize questions; don’t customize away the protected growth time.
FAQ
How do I prepare for a 1:1 if I’m the employee?
Spend about ten minutes the day before. Write top three priorities, one ask, one risk, and one feedback request tied to real work. Put it in the shared doc. In the meeting, lead with the ask that needs your manager’s power, not the longest story.
What if we only have 20 minutes?
One-minute check-in, one ops decision or blocker, one feedback or career crumb, then owners. Push pure status async. A tight 20 beats a sloppy 30.
Should 1:1s include personal life?
Only what the employee chooses to share and what affects work sustainably. Stay respectful. Don’t pry. Don’t play therapist. Point to company resources when issues are bigger than a manager can hold.
How is a 1:1 different from a skip-level?
A 1:1 is your ongoing operating relationship with your direct manager. A skip-level is occasional pattern-sensing with a leader above. Don’t use your 1:1 only as rehearsal for politics, and don’t use a skip-level as a secret second manager for routine priorities.
What should new managers do in the first 1:1s?
Listen more than you prescribe. Ask how they like feedback, what good looks like in the role, and what’s been frustrating. Establish the shared doc and the ops/development split early. Big process rewrites can wait until you understand the system.
Effective 1:1s at work are mostly a design problem. Cap operations, protect development, put the agenda in a shared doc, and leave with owners. Do that weekly and the meeting stops being a status tax and starts being the quiet place where priorities get honest and careers get real reps.