If you are looking for one on one meeting questions that do more than fill 30 minutes, you are in the right place. A one on one is the most useful meeting most managers underuse. It is the only recurring space where a direct report can talk about work, roadblocks, and growth without an audience watching. The catch is simple: a bad one on one produces nothing but small talk, while a good one produces trust, clarity, and faster decisions.
Most teams already drown in status meetings. What they lack is a private, regular conversation where the human behind the tasks gets airtime. This guide gives you a ready set of questions, a reusable template, and a real example pulled from an actual manager report. Use it to run your next one on one without the usual prep paralysis.
What goes in your one on one meeting
A one on one is not a status meeting. Status belongs in your weekly update (see our weekly report template for the format). The one on one is for the things status reports leave out: how the person is doing, what is blocking them, and where they want to go.
Cover four buckets every time, and resist the urge to add a fifth:
- Work and priorities — What is the most important thing you are working on, and is anything slowing it down?
- Blockers and support — What do you need from me or the team to move faster?
- Growth and feedback — What do you want to learn, and what feedback do you have for me?
- Wellbeing and fit — Are you overloaded, under-challenged, or unclear about direction?
Keep the ratio tilted toward the person, not the project. If you talk 80% of the time, it is not a one on one. A good rule is that the report should set at least one agenda item and drive half the conversation.
Frequency matters as much as content. For most teams, a 30-minute one on one every week or two is the sweet spot. New hires and struggling reports need it weekly. Stable, senior reports can drop to every two weeks — but never let it lapse for more than a month, or the habit dies and the candor goes with it.
A reusable question template
Copy this skeleton and adjust it each week. Fewer questions, asked well, beat a long checklist nobody answers honestly.
ONE ON ONE AGENDA (30 min)
1. Quick check-in (3 min)
- How are you doing this week, really?
2. Priorities and progress (8 min)
- What is the most important thing you shipped since we last met?
- What is the biggest thing you are working on right now?
3. Blockers and support (8 min)
- What is slowing you down that I can remove this week?
- Is anything unclear about priorities or expectations?
4. Growth and feedback (8 min)
- What do you want to learn or take on next?
- What is one thing I should start, stop, or keep doing as your manager?
5. Wrap-up (3 min)
- What is your one commitment before we meet again?
That template works for both new and tenured reports. The only part that changes is the depth of the growth conversation as trust builds. If you want the full timing and follow-up breakdown, our one on one meeting agenda covers the mechanics step by step.
Real example from a manager one on one
Here is a trimmed, transcript-style example. Names are changed, the structure is real, and every line maps to the template above.
Manager: How are you doing this week, really?
Report: Honestly a bit stretched. The data migration ate two extra days.
Manager: What is the most important thing you shipped since we last met?
Report: We cut API response time from 900ms to 320ms. That part is done.
Manager: What is the biggest thing you are working on now?
Report: The billing refactor. On track, but I need the staging slot.
Manager: What is slowing you down that I can remove?
Report: Staging is booked by QA through Thursday. Can you swap us in?
Manager: What do you want to learn or take on next?
Report: I want to lead the next incident review. I have not run one yet.
Manager: One thing I should start, stop, or keep doing?
Report: Keep the Friday no-meeting block. It is my only deep-work time.
Manager: Your one commitment before we meet again?
Report: Move billing to staging and draft an incident-review plan.
Notice what surfaced. The manager learned about a hidden blocker (staging access), a growth ask (lead an incident review), and a wellbeing signal (need for focus time) — none of which would appear in a status report. That is the entire point of the meeting.
Common mistakes in one on one meetings
Most one on ones fail for predictable reasons. Watch for these:
- Turning it into a status meeting. If you are reading a task list together, you are wasting the format. Status lives in written updates.
- Skipping it when things get busy. The weeks you are slammed are exactly the weeks your report needs the space most.
- Only asking about work. People quit for reasons that never show up in a project plan. Ask about fit and load.
- No follow-up on commitments. If you promise to remove a blocker and forget, trust drops fast. Write it down and close it next time.
- Letting the manager dominate. The report should drive at least half the agenda. Silence is not agreement.
- Saving feedback for reviews. A one on one is where small corrections happen so the yearly review has no surprises.
A strong one on one is a habit, not an event. The questions above give you a stable backbone so the conversation stays useful even on off weeks, and so new managers do not have to invent the wheel each time.
Ready to run a better one on one this week? Pick three questions from the template, send the agenda 24 hours early, and let your report set the first topic. Small change, steady payoff.
Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →