One on one meeting questions that get people talking

Most 1-1 question lists fail for the same reason. They are written as a hundred item dump, sorted alphabetically or by mood, with no indication of what the question is for or what happens after someone answers it.

The second failure is subtler. A lot of the questions in circulation are status questions in a warmer coat. What are you working on this week. Any blockers. How is the project tracking. Those are fine questions, and they belong in standup or in the tracker. Asked in a 1-1 they train the person to arrive with a delivery report, and then you have two status meetings and no relationship meeting.

So this list is grouped by what I am trying to learn. Each group has a note on when it works and one honest caution, because every one of these questions can be used badly. I have used most of them badly at least once.

How the person is actually doing

This group is for reading energy and load, not for collecting a mood score. I lean on it hardest during crunch periods, after a reorg, and in the weeks after someone has taken on something new. The answers usually arrive slowly, so I ask one of these and then leave a long silence.

The caution is that these questions get hollow through repetition. If I open with the same wellbeing question every week, by month two it is a ritual and the answer is automatic. I rotate, and sometimes I skip the group entirely because the person is visibly fine and would rather talk about the migration.

• What has your energy been like the last couple of weeks compared to before.
• Which part of your week do you dread.
• When did you last finish a day feeling like it went well, and what was different about it.
• How much of your time last week was actually focused work.
• Is there anything you are carrying right now that I do not know about.
• On a normal week, are you working more hours than you want to be.
• What has been the most annoying thing about the last two weeks.
• Is anything at work keeping you up at night.

What is blocking them

This group exists because people underreport friction. They assume the slow CI, the review queue, and the third approval step are just how things are, so they never raise them. The questions have to be specific enough to make small friction feel worth mentioning.

The caution here is that asking about blockers creates an obligation. If someone tells you the deploy pipeline is costing them an hour a day and nothing happens for two months, they will not tell you the next thing. Only ask this group as often as you are willing to act.

• What slowed you down this week that should not have.
• Where do you feel you are wasting time.
• What is the thing you keep working around instead of fixing.
• Is there a decision you are waiting on from me.
• If you could delete one recurring meeting from your calendar, which one.
• What part of our process would you change if nobody would argue.
• Who do you have to chase to get your work done.
• Is there anything you need that you have stopped asking for.

Career and growth

These are the conversations people remember years later, and they need room. I use this group deliberately, roughly once a month per person, and more often when someone is close to a promotion, restless, or freshly disappointed by not getting something.

The caution is real and I learned it the hard way. Career questions asked every week start to feel like pressure. One of my engineers eventually told me that my constant what do you want next made her feel that being content in her current role was a failure. Some people are deliberately steady for a year or two, and asking them monthly whether they are growing turns a good period into an anxious one.

• What work have you done in the last six months that you are proud of.
• Which parts of your job would you keep if you could drop the rest.
• What skill do you want to be noticeably better at a year from now.
• Whose job on this team or nearby looks interesting to you.
• What would need to be true for you to feel ready for the next level.
• Is there work happening here that you wish you were part of.
• What did you change your mind about this year.
• If you left in twelve months, what would you want to have finished first.

Feedback on me as a manager

This group is the most useful and the most uncomfortable. The trick is that vague invitations produce nothing. Any feedback for me reliably gets no, all good. Narrow, slightly self incriminating questions get answers, because they signal that you have already accepted you are doing something wrong.

The caution is that asking is the easy half. The first time someone gives you real criticism, your reaction decides whether they ever do it again. When Priya told me my written updates were too long to be useful, my first instinct was to explain why they were that length. I caught it, said thank you, cut them in half the next week, and told her I had. That single exchange bought me more honest feedback over the following year than any survey.

• What is one thing I could do differently that would make your week easier.
• Is there a decision I made recently that did not make sense to you.
• What would you push back on if you thought I would not react badly.
• Where am I giving you too much detail, and where not enough.
• Do you get enough of my time, or too much of it.
• When I gave you feedback last, did it land the way I meant it.
• What do I do that makes it harder to bring me bad news.
• If you had my job for a month, what would you change first.

Team dynamics

I use this group to see the parts of the team I cannot observe directly, which is most of it. Pairing that works, code review that has turned cold, a new joiner who is being politely ignored. People will tell you about these things, but rarely without being asked.

The caution is the obvious one. There is a thin line between understanding team dynamics and collecting gossip, and the line is what you do with the answer. I ask about patterns and working relationships, not about individuals' performance. If someone starts telling me another person is underperforming, I take it seriously and move the conversation to how it affects them and to what I should observe myself.

• Who have you learned the most from here in the last few months.
• Is there anyone you find it hard to work with, and what happens in practice.
• Where is knowledge stuck in one person's head on this team.
• How is the new joiner settling in from where you sit.
• Do reviews on this team feel useful or ceremonial to you.
• Is there something the team believes that you think is wrong.
• When something breaks, do people feel safe saying so.

Life outside work, when it is welcome

Some managers avoid this entirely and their 1-1s stay transactional for years. Some overreach in the first month and it reads as intrusion. My rule is that I follow, I do not lead. If someone has mentioned their daughter's exams or their move to another city, that thread is open and I can pick it up. If they have never volunteered anything personal in six months, that is an answer and I respect it.

The caution is timing. Personal questions during a hard delivery week can feel like a manager avoiding the real subject. Ask them when there is room for the answer.

• How did the move go, are you settled.
• What are you doing outside work that you are enjoying at the moment.
• Is your current schedule working for how your life is set up right now.
• Anything coming up in the next couple of months I should plan around.
• Last time you mentioned your exams were coming up. How did they go.
• Is there anything about how we work that clashes with your life outside it.

The question matters less than what happens to the answer

I could give you a hundred more questions and it would not improve a single 1-1, because the question is not where the value is. The value is in whether the answer survives until the next conversation.

Here is the version of this I keep thinking about. In February I asked Marco what he wanted to be doing in a year, and he told me he wanted to move toward infrastructure work and that he had been teaching himself Terraform on weekends. I remember being genuinely pleased. Then a release slipped, two people left, and in April a platform project came up that I staffed with someone else without a second thought. When Marco found out, he did not complain. He just never brought up his career again with me, and eight months later he took an infrastructure role at another company.

Asking a good question spends trust. The person tells you something they did not have to tell you, and they watch what you do with it. Forget it by next week and you have taken the deposit and returned nothing, and the next answer will be shorter.

This is exactly why I stopped relying on memory and started writing three lines after every 1-1. Those notes are what LeaderCues turns into a short brief before the next meeting, so the thing someone told me in February is in front of me in April when it suddenly matters.

If you want the format those notes live in, the 1-1 template I actually use every week is four sections and takes two minutes. For the wider practice around the questions, cadence, preparation, and follow through, there is how to run one on one meetings.

Pick three questions from this list for next week, or let the 1-1 question generator pick them for the situation you are walking into. Ask them, write down what you hear the same day, and bring one of the answers back a month later. That last step is the whole trick.