Good Questions to Ask Your Boss
Twenty questions to bring to a one-on-one with your manager. They cover what success in your role actually looks like, how your manager wants to be kept informed, where the team is likely to fall short, what separates your level from the next one, and how advancement decisions get made where you work.
The questions
Open any question for the note
What does a good week look like for you right now?
Why ask it
A manager under real pressure describes a good week as one where nothing broke. A manager with room describes one where something moved forward. That difference tells you how much appetite there is for new ideas from you this month.
What are the top two or three priorities for the team this quarter?
Why ask it
If the list comes out fast and in a consistent order, the priorities are real. If it takes a minute to assemble, the team is being run reactively and your own goals will keep shifting under you.
Where do you think my work has the most impact at the moment?
Why ask it
Managers often value a different part of your work than you do. If the answer names something you consider routine, you have been over-investing somewhere that nobody is watching.
What would success in my role look like six months from now?
Why ask it
Listen for whether the answer is stated as outcomes or as activity. Activity answers like staying on top of the queue mean the role has never been defined properly, and you will end up judged on impressions instead.
Is there anything I am doing that you would like me to stop or do less of?
Why ask it
Harder to deflect than asking for feedback in general, because it requests one concrete thing. Silence here usually means the feedback exists and has not been said out loud yet, so raise it again in a few weeks.
How do you prefer to be kept up to date between our one-on-ones?
Why ask it
Some managers absorb a written Friday summary; others only register what is said in a room. Guessing wrong is the most common reason solid work goes unnoticed.
When I am blocked, what is the fastest way to get a decision from you?
Why ask it
You are asking for the escalation path before you need it. If the answer is just to ping them, try it once and time the response, then plan how far ahead you need to raise things.
Which of my skills is furthest behind what this role will need next?
Why ask it
Framing it as a gap invites a real answer, where asking what to develop invites a compliment. If they cannot name anything, they either have not watched your work closely or are dodging.
What kind of work would you like to get off your plate this year?
Why ask it
Work a manager wants to hand off is the cheapest route to more scope, because taking it solves a problem they already feel. It also shows you what they consider below their own level.
Besides you, whose opinion of my work matters when advancement gets decided?
Why ask it
Those decisions happen in rooms you are not in. Naming the other people in the room tells you whose direct experience of working with you needs attention this year.
What separates someone at my level here from someone at the next one?
Why ask it
Ask for the difference in behavior, not in title. Useful answers describe scope and judgment, such as deciding without checking first. Answers about being more senior mean the ladder is not really defined.
When other managers talk about my work, what do they say?
Why ask it
Uncomfortable to ask and worth it. Second-hand reputation is what gets quoted in calibration meetings, and it often lags your actual work by a year or more.
What is a mistake you have watched people make in their first year on this team?
Why ask it
Easier to answer honestly than a question about your own mistakes. The answer usually describes an unwritten local norm that somebody broke, which is exactly the thing no handbook covers.
How much of this year's plan is settled, and how much is still open to argument?
Why ask it
Knowing which parts are still open tells you where pushing back is worth the effort. Arguing against a decision that is already locked spends credibility for nothing.
What are you being measured on that I probably do not see?
Why ask it
Your manager carries commitments that never reach your inbox. Once you know them, you can describe your own work in the terms they are already being judged against.
Where do you think the team is most likely to fall short this year?
Why ask it
A manager who names a specific risk is being straight with you and usually wants help with it. One who says everything is on track either does not know or does not yet trust you with the real answer.
If I had an idea that cut across another team, how would you want me to handle it?
Why ask it
Cross-team work is where most political trouble starts. The answer tells you whether your manager wants to carry that conversation personally or expects you to build the relationship yourself.
What is something about this work you have changed your mind about in the last year?
Why ask it
Shows whether they update on evidence. Someone who cannot name a single reversal is either not being challenged or not admitting it, which changes how carefully you need to bring bad news.
What do you wish someone had told you when you were at my stage?
Why ask it
Advice about their own earlier career tends to be more candid than advice about yours, because nothing is at stake. Listen for what they regret rather than what they recommend.
Is there anything you have been meaning to say to me but have not found the moment for?
Why ask it
This gives explicit permission for the thing that has been sitting unsaid. Most managers are holding one such item, and hearing it now is far better than hearing it in a review.
Getting real answers in a one-on-one
Practical guidance for the conversation itself
Before the meeting
Bring two questions, not twenty
A one-on-one is usually twenty-five minutes and half of it is already spoken for. Pick one question about the work and one about you, and leave the rest for later meetings. Working through a list makes the conversation feel like an interview and pushes your manager into short, safe answers.
Send the harder one ahead
Questions about levels, reputation or advancement are worth flagging in the agenda a day early. Managers give thin answers when they are answering cold, and a good answer to those questions often requires them to check something first.
Know what you would do with the answer
- If the answer is bad news, decide in advance whether you want to fix it, escalate it, or just record it.
- If you would not change anything either way, the question is small talk. Ask something else.
- Write down the answer in your own words during the meeting so you can quote it back next quarter.
Reading what you get back
Watch the specificity, not the warmth
Warm and general is worse than cool and specific. Praise with no example attached usually means your manager has not looked closely at your work recently. A precise criticism means they have.
Follow up once, then stop
One follow-up question gets the detail that the first answer skipped. A second usually makes the person defensive. Ask for one example, then let it sit.
Treat hedging as information
Phrases like it depends, we are still figuring that out, or that is above my level are answers. They tell you the decision has not been made, which means your own plans should stay reversible for now.
Afterwards
Close one loop visibly
Pick a single thing from the conversation and act on it before the next meeting, then mention that you did. This is what turns the question into a track record instead of a nice chat.
Keep a running note
Log the date and a one-line summary of anything said about your level, scope or performance. When a review or a reorg comes, that note is the only record of what you were told and when.
Re-ask the important ones
Priorities, risks and role expectations change every few months. Asking the same question twice a year is not repetition, it is how you notice a shift before it affects you.
Questions to handle carefully
- Anything about pay is a separate conversation with its own timing, usually tied to your company's review cycle. Raising it in the middle of a development discussion tends to end both topics early.
- Do not ask your manager to compare you with a named colleague. Even a favorable answer puts them in a position they cannot repeat, so you get an evasion instead.
- If your manager is new, hold the questions about reputation and advancement history for a few months. They genuinely do not know yet, and asking early just signals impatience.
- If you are considering leaving, be careful with questions that imply it. Asking what the next two years look like for you is fine; asking whether the team will still exist is not.