How to run a 30-minute one-on-one that people want to keep
Let the report own the agenda, keep one running document, and spend the last two minutes writing down what happens next. A simple time split for a 30-minute 1:1.
On this page
Key takeaways
- The person reporting owns the agenda; the manager adds items.
- Keep one running doc so commitments carry over.
- Spend the first third on what the report brings; move status updates elsewhere.
- End with written action items, owners and dates.
Why a shared running doc works
A 1:1 is the one meeting on the calendar that exists for the person reporting. GitLab’s public handbook treats it as the team member’s meeting, with an agenda in a shared document that both people add to beforehand. A running doc — newest meeting at the top — means commitments carry over from week to week.
The 30-minute split
| Segment | Time | Who leads | What goes here |
|---|---|---|---|
| Their topics | 10 min | Report | Blockers, ideas, anything on their mind |
| Priorities check | 8 min | Both | Are we working on the right things this week? |
| Feedback | 7 min | Both | One thing going well, one thing to change — in both directions |
| Growth | 3 min | Report | Progress on a development goal (monthly is fine) |
| Action items | 2 min | Manager | Owners and dates, written down before you hang up |
What goes in the running doc
- Date and names at the top of each entry.
- Their topics, then priorities, then feedback.
- Action items with an owner and a due date.
- Anything carried over from last time, ticked off or moved forward.
Recording a 1:1
If you record 1:1s, ask first and make it easy to say no — 1:1s are where people raise sensitive topics. Many teams keep recording off and paste only the action items into the running doc.
Frequently asked questions
How often should 1:1s happen?
Weekly or every two weeks is common. Pick a cadence you can keep; a cancelled 1:1 sends a stronger signal than a short one.
Should we record 1:1 meetings?
Only with explicit agreement and an easy way to opt out. Many teams capture just decisions and action items.
