Why does a 1 on 1 with a perfectly competent engineer end after eight minutes with both of you saying “all good”? The work is on track, there are no open conflicts, and the sprint board already answered every status question before the meeting started. So you sit there, one of you offers to give the other 22 minutes back, and the meeting quietly dies for the third week running.
An empty 1 on 1 is a symptom, not a schedule problem. It usually means the meeting has become a status check, and status is the one thing you no longer need it for.
Why the meeting runs out of things to say
Status drift: the gradual shift of a 1 on 1 from the report’s agenda to a progress update the manager could have read elsewhere. It happens because status is safe, easy and always available, so it fills the space when nobody prepared anything else.
Report owned agenda: the principle, set out by Andy Grove in “High Output Management”, that a 1 on 1 is the subordinate’s meeting. The report brings the topics; the manager’s job is mostly to ask and listen.
Put those two definitions together and the empty meeting makes sense. When the report has no burning issue and the manager falls back on “how’s the project going?”, there is nothing to discuss that the ticket tracker did not already show. Michael Lopp, writing as Rands, described 1 on 1s as tending toward three modes: the update, the vent and the disaster. A healthy team in a calm month produces mostly the first kind, which is exactly the kind you can skip.
There is a second, quieter reason. Some people do not raise career worries, friction with a colleague or doubts about the roadmap unless they are explicitly invited, and an open “anything else?” is not an invitation. They need a specific question, asked more than once, before they believe you want the answer. A 1 on 1 that has “nothing to talk about” for six weeks is often a 1 on 1 where the real topics are waiting for that question.
The questions below are grouped by what they are for. You do not need all 24 in one meeting; two or three good ones fill half an hour.
Questions about the work that skip status
The goal here is to talk about the work without asking for an update. These questions pull out friction, judgement and context that a dashboard never shows.
- What took longer this week than you expected, and why?
- If you could delete one recurring task from your week, which one?
- What decision are you waiting on from someone else right now?
- Where did you have to guess because the requirements were unclear?
- What is one thing about our codebase, process or tooling that slows you down every week?
- What part of your current project would you design differently if you started today?
Question 1 is the workhorse. It turns a status question into a diagnosis: the answer is usually a dependency, an unclear spec or a tool that broke, and each of those is something a manager can act on. Question 3 often surfaces a blocked decision that would otherwise sit for days. Ask question 5 at most once a month, or it becomes a complaint ritual.
Use these early in the meeting, in the first 10 minutes. They warm up the conversation with concrete material and give you something to follow up on next week, which is what makes the following 1 on 1 less empty too.
A worked illustration of the follow up: a developer answers question 1 with “the payment API review took three days instead of one, because security had to look at it.” You note it. Next week you ask whether the review queue is still slow, and you learn that every change touching card data waits for one of 2 reviewers. That is a staffing and process topic worth 20 minutes of real discussion, and it came from a single question about one delayed task.
Questions about the person, their energy and their growth
Calm weeks are the best time for career conversations, because nothing urgent is crowding them out. The questions here need a little more trust; ask one at a time and leave silence after it.
- What part of your job gives you energy, and what part drains it?
- What did you learn in the last month that you are proud of?
- What skill do you want to be noticeably better at in 6 months?
- Which project in the company would you join tomorrow if you could?
- Is there anything about your role that is different from what you expected when you joined?
- On a scale of 1 to 10, how sustainable does your workload feel? What would move it up by one point?
Question 12 works because the number itself matters less than the follow up. A 7 that drops to 5 over three meetings is an early warning you would otherwise see only when someone resigns. Kim Scott’s “Radical Candor” makes a similar point about asking for criticism directly: a specific prompt with a scale gets more honest answers than a general “how are you doing?”.
Question 9 sets up an individual development plan without calling it one. Write the answer down. If the same skill comes up twice, the next step is a stretch assignment, a course budget or a pairing arrangement, and that is a topic for the next several meetings.
Be careful with question 10. If you ask it, be ready for an answer you cannot act on this quarter, and say so honestly. A manager who asks about internal moves and then never mentions them again teaches the report that growth questions are small talk.
Questions about the team, the manager and the company
Reports see things managers miss. These questions invite feedback on the environment and on you, which most people will not volunteer.
- Who on the team has helped you recently, and do they know?
- Is there a conversation you have been avoiding with someone on the team?
- What is one thing I could do differently that would make your work easier?
- What is something I said or decided recently that did not make sense to you?
- What do you hear from other teams that I might not be hearing?
- If you were running this team for a month, what would you change first?
- How clear is our team’s priority for this quarter, from 1 to 5?
- What would make you consider leaving?
Question 15 is the one most managers ask and the one that gets the vaguest answers, because it is too open. Question 16 works better: it points at a recent concrete moment, and people find it easier to disagree with a decision than to critique a person.
Question 20 sounds risky and is worth asking once or twice a year in a calm period. The answer is rarely “I’m leaving”. It is usually a list of 2 or 3 conditions, such as no promotion path or a project they dread, that you can address before they become reasons.
When nothing comes back, try the lighter variants: 21. What is something outside work you are looking forward to this month? 22. What is a small win from this week that nobody noticed? 23. What should we stop doing as a team? 24. What should we talk about next time?
The last one is the most useful. It hands the agenda back to the report and gives both of you a week to think.
A 30 minute structure and a check for a dying meeting
Questions help, but structure keeps a quiet 1 on 1 from collapsing into small talk. This split works for weekly 30 minute meetings:
- Minutes 0 to 5: the report’s topics first, if any. Wait at least 10 seconds before filling silence.
- Minutes 5 to 15: one work question from the first group, followed up properly.
- Minutes 15 to 25: one person or team question, rotating weekly between growth and feedback.
- Minutes 25 to 30: agree on any follow ups and ask question 24.
- Before the next meeting: read your notes from the last two sessions and pick one open thread.
- Once a month: replace the work question with a longer career conversation.
A shared running document helps more than any question bank. Both people add topics during the week, and the empty meeting becomes rare because topics accumulate.
To tell whether the meeting is healthy, track one number over time:
Report-raised share = topics raised by the report / all topics discussed
Rolling window: last 6 meetings
Healthy: above 0.5
Warning: below 0.3 for 3 or more meetings in a row
If the share stays below 0.3, the meeting has become yours, not theirs. That is the moment to say so out loud and ask what format would be more useful. Some people prefer every other week, some prefer walking meetings, some prefer async notes with a shorter call.
The counterargument deserves space: sometimes there really is nothing to discuss, and cancelling is respectful. A senior engineer in a stable period may genuinely prefer 15 minutes every two weeks. The difference is who decides. Shortening the meeting by agreement is fine. Letting it die by mutual awkwardness means the next real problem arrives without a channel.
Where 1 on 1s are heading is already visible in many remote teams. More of the status and coordination load is moving into written updates and tools that summarise work automatically, which removes the last excuse for spending the meeting on status. What remains is the part no tool replaces: trust, career and the uncomfortable topics. Expect 1 on 1s to get shorter on average and harder in content, with managers judged less on cadence and more on whether people actually tell them things.