28 Questions to Ask Your Boss in Your One-on-Ones
Questions for a regular one-on-one with your manager, ordered from easy logistics to the harder ones about feedback and progression: what matters this quarter, what excellent looks like to them, the risks you are missing, and what you can safely drop.
The questions
Open any question for the note
What is the best use of our one-on-one time for you?
Why ask it
Ask this once and it changes every meeting afterwards. Some managers want a quick status pass so they can stop chasing you; others already know your status and are bored by it. If the answer is a shrug, that is your signal to set the agenda yourself, and they will usually be relieved.
What are the top outcomes I should focus on this quarter?
Why ask it
You are checking whether their list matches the one in your head, and how short it is. A manager who names two or three outcomes has done the prioritising. A manager who lists nine has passed the prioritising to you, which is worth knowing before you are held to all nine.
What does success look like for our team this quarter?
Why ask it
This is the question that tells you which of your tasks are actually load-bearing. If your main project does not appear anywhere in the team's success, you have found either a communication gap or a career problem, and either is better found in month one than month three.
What is the most valuable thing I could ship this week?
Why ask it
Narrow and concrete on purpose, so it cannot be answered with strategy. The gap between their answer and what you had planned to do is the useful information. If they cannot name anything, your work is probably not visible enough to them yet.
How do you prefer to be kept updated, and how often?
Why ask it
Most friction between capable people and their managers is format, not substance. Some want a Friday note, some want to be tagged in the document, some want no updates until something is off track. Getting this explicitly stops you being called both a black box and a nag.
Where should I say no, or push something to next quarter?
Why ask it
Asking for permission to drop things gives your manager the chance to protect you, and it makes overload their problem rather than a private one. If nothing can be dropped and nothing can slip, you have documented the real constraint, and you can raise it again when something breaks.
If I had a spare half day each week, where would you want it spent?
Why ask it
The answer reveals what they think is under-invested, which is often not what they talk about in meetings. Watch whether they point at your own growth or at more delivery: that tells you how they see your role, and whether development is real here or decorative.
What is one thing I could take off your plate?
Why ask it
Managers rarely delegate the thing they most dread until asked. What they hand over shows how much they trust you, and taking it usually buys you goodwill and visibility with whoever the task involves. If they refuse everything, they may be a bottleneck you will need to work around.
Which stakeholders should I keep closer this month?
Why ask it
Your manager sees whose support is quietly slipping and who will be reviewing your work later. Names here are worth more than advice. If they mention someone you have barely spoken to, that is a relationship about to matter.
How can I better support the teams we depend on?
Why ask it
This surfaces complaints about your team that people are too polite to send you directly. A specific answer means your manager has been hearing something. A vague one is a chance to ask who they would like you to check in with, and then do it.
What decisions could I be making myself that I keep bringing to you?
Why ask it
You are asking to be given more rope, framed as saving their time. The answer tells you where your actual authority sits, which is usually wider than people assume and narrower in one or two places they will now name. Confirm it in writing afterwards.
What are we still discussing that we should just decide?
Why ask it
Every team has one decision that has been reopened four times. Naming it out loud often ends it, and their answer shows whether the delay is genuine uncertainty or someone avoiding a conversation. If it is the second, ask who needs to be in the room.
What am I not seeing about the risks in my plan?
Why ask it
This works because it invites criticism of the plan rather than of you, so managers answer it more honestly than they answer requests for feedback. Expect the risks to be political and organisational as often as technical: a reorganisation coming, a team about to lose someone, a budget not yet signed.
What assumptions are we treating as settled that nobody has actually tested?
Why ask it
Useful because it gives your manager permission to voice a doubt they have been sitting on. If they name one, you have found the cheapest piece of work available to you this month. If they insist there are none, note it and revisit when something surprises you both.
What is the biggest unknown in the strategy right now?
Why ask it
The answer tells you how much your manager actually knows, and how candid they are willing to be. Someone who says the honest thing here is worth trusting with a harder conversation later. Someone who recites the strategy back at you has told you where the ceiling on this relationship is.
What is the risk if we keep working the way we do now?
Why ask it
Managers often see a slow problem coming, a process that will break at double the volume, a person carrying too much, and have no forum to say so. This question is that forum. It also gives you something worth proposing rather than another task to absorb.
What do you wish the team did more of, or less of?
Why ask it
Phrased about the team, it is easier to answer than the same question about you, and you can usually hear yourself in the answer. It also hands you something you can lead on without waiting to be asked, which is how people get noticed without asking to be.
What would make my work excellent rather than just fine, in your eyes?
Why ask it
Standards are the thing managers most consistently fail to state. The answer is often unexpectedly specific: more context in the write-up, fewer surprises late in the week, bringing a recommendation rather than options. Ask for an example of someone who does it well.
Where do you think I have added the most value in the last month?
Why ask it
This checks what actually reached them, which is rarely what took you longest. If they name something minor and miss your main piece of work, the problem is visibility, and it will hurt you at review time unless you fix how you report.
What is one thing I should start, one I should stop, and one I should keep doing?
Why ask it
The three-part shape makes it hard to escape with reassurance, because the stop is the one they have to fill in. Push gently if you only get the start and continue; the stop is the whole reason for asking.
How do I come across in writing and in meetings?
Why ask it
Communication is where quiet reputations are made, and it is the feedback people are most reluctant to volunteer. Listen for hedging words like blunt, quiet or long, and ask for the specific moment they are thinking of, since the abstract version is impossible to act on.
What would you change about how I run the meetings I own?
Why ask it
Concrete enough to get a real answer, and easy to act on within a week. Common answers: no agenda, no decision at the end, the same two people doing all the talking. If your manager does not attend them, ask who they would trust to tell you.
Where could I take more ownership without stepping on anyone?
Why ask it
The second half is the important half. It shows you have noticed the territory question, and it lets your manager warn you about the colleague who considers that area theirs, which is the thing they would not otherwise say out loud.
Who inside the company should I be learning from right now?
Why ask it
You get a name, a reason to introduce yourself, and a read on who your manager respects. Follow up in the same week and mention who sent you, because an introduction that goes unused makes the next one less likely.
Is there a project I could run end to end next?
Why ask it
End to end is the operative phrase, since owning a slice teaches you much less than owning the whole arc including the parts you would rather avoid. If the answer is not yet, ask what would have to be true first, and treat that as the real answer.
Is there a stretch assignment you would trust me with?
Why ask it
Managers hold back opportunities from people who have not asked, mostly out of consideration for their workload. Saying you want one moves you onto a shorter list. Be ready to say what you would drop to make room, or the offer will stall there.
What would need to be true for me to be at the next level?
Why ask it
You want observable conditions, not qualities: a project of a certain scope, evidence that you have grown someone else, a specific relationship. If the answer is a list of adjectives, ask what someone recently promoted had done that you have not, which is much harder to answer vaguely.
How is my work seen outside this room?
Why ask it
Save this for last, because it asks your manager to relay other people's judgements, which takes trust. It is also the answer that most often surprises people: strong internal reputations are frequently invisible upward, and quiet reservations are frequently invisible downward until review season.
Getting more out of your one-on-ones
Practical guidance for the conversation itself
Treat the meeting as yours
Bring three items, not eleven
A short list gets discussed; a long list gets skimmed. Pick one decision you need, one thing you want their view on, and one piece of feedback you are asking for. Anything else can go in a written update they read on their own time.
Send the agenda the day before
Managers arrive at one-on-ones straight from something else. A few lines in advance gives them the chance to think, to check with someone, or to warn you that the answer is not theirs to give. It also means the meeting starts at the second sentence.
Lead with what changed, not with what you did
Status is best delivered in writing. Use the time for the things that are ambiguous, blocked, or about to become expensive. If you spend every session narrating completed work, you train your manager to expect nothing else from the meeting.
Ask one growth question every time
One per meeting, not five. Career questions land better as a steady drip than as an annual ambush, and by the time a promotion cycle arrives your manager has already heard your case four or five times in small pieces.
A thirty-minute shape that holds up
- 1Two minutes: anything urgent that would derail the rest of the meeting if it waited.
- 2Five minutes: the one or two things that changed since last time and matter to them.
- 3Ten minutes: your decisions and blockers, each with a recommendation attached rather than an open question.
- 4Eight minutes: their turn. What they are worried about, what they are hearing, what they need from you.
- 5Five minutes: one growth or feedback question, asked properly rather than squeezed in at the door.
- 6Last minute: say the next steps out loud, name who owns each, then write them down and send them.
What goes wrong
It becomes a status meeting
The commonest failure, and it happens by drift rather than decision. If the last four sessions were all updates, break the pattern by opening with a question instead of a report. Nobody will stop you.
You ask for feedback in a way that invites reassurance
"Is everything okay with my work?" gets a yes. Ask about one specific thing you did recently, or use the start, stop, continue shape, so answering honestly is easier than deflecting.
Nothing is written down
Verbal agreements about scope, authority and promotion criteria evaporate, especially across a reorganisation or a change of manager. A short note after each session, sent to them, is your record and costs you three minutes.
The meeting keeps getting cancelled
Repeated cancellation is information. Ask directly whether a different slot or a shorter session would survive better, and in the meantime move your asks into writing so decisions are not waiting on a calendar.
You only raise problems once they are certain
Managers can help with a risk and can only absorb a failure. Flagging something at the point you are merely uneasy costs you very little credibility and saves the conversation where you explain why they heard about it late.
Between meetings
Keep a running record of what you shipped
Add a line each week while you still remember the detail. At review time it is the difference between arguing from memory and arguing from a list, and it makes the promotion conversation something you can prepare in an evening.
Close the loop on their advice
When you act on something they suggested, say so and say what happened. Managers who see their advice used give more of it, and better.
Note the questions that got thin answers
A vague response is not always evasion; sometimes they did not know. Bring the same question back in a month. The second answer is often much more concrete, particularly on level and scope.