Questions to Ask When Transitioning Into a New Role
Twenty questions to put to your new manager in the first few weeks, whether you have joined a company or moved seats inside one. They cover what success looks like on a date, what you own outright, how decisions get made, and what you are not expected to touch yet.
The questions
Open any question for the note
What would you want to see from me by the end of my first month?
Why ask it
Ask for the end of month one rather than the end of the quarter, because the answer is concrete enough to be checkable. A manager who names something specific has thought about you joining; one who says settle in has not, which means you should propose your own version and get it agreed.
Ninety days in, what would make you say this went well?
Why ask it
This is the question that surfaces the unstated expectation, which is usually one thing rather than five. Write down the answer verbatim, because it is what you will point at in your first review when someone remembers the brief differently.
Why does this role exist, and what happened to the person who had it before?
Why ask it
Backfill, growth, and cleanup are three different jobs. Promoted internally, left frustrated, and role restructured each tell you what the reception from the team will be, and a manager who is vague here is often managing something they have not told you.
What is genuinely mine to decide, and what needs your sign-off?
Why ask it
Ask for examples at two sizes, a 500 decision and a 50,000 one. Ambiguity here is the most common source of early friction, because the first time you decide something you should have escalated is remembered far longer than it deserves.
What is the one thing you want fixed that has not been fixed, and what has already been tried?
Why ask it
The second half matters more. Walking in with an obvious solution someone attempted last year is how new hires spend their credibility in week three, and the reason it failed is usually political rather than technical.
Which recurring meetings do you want me in, and which can I drop or hand off?
Why ask it
Inherited calendars fill with meetings that made sense for your predecessor. Getting explicit permission now is much easier than withdrawing from something six weeks in, when the withdrawal reads as a judgment about the people in the room.
What numbers do you look at each week, and where can I see them myself?
Why ask it
You want access, not a description. If the answer is a spreadsheet one person maintains by hand, you have learned something about the operation, and if nobody looks at anything weekly you have learned more.
How and when will my work be formally reviewed?
Why ask it
Ask for the date, the format, and who else has input. Joining shortly before a review cycle can mean being assessed on six weeks of work, and mid-cycle joiners sometimes fall outside the process entirely, which affects pay later.
Whose opinion of my work matters most outside this team?
Why ask it
Every role has a stakeholder who can quietly sink you, often a peer of your manager in a function you do not report into. Managers usually answer this honestly when asked directly, and almost never volunteer it.
What budget and headcount do I control, and what is the process for changing either?
Why ask it
Ask for the number and the approval path. Roles are frequently sold with resources that require a business case nobody has written, and the gap between implied and actual authority is worth discovering before you promise anything.
How do you want to hear bad news, and how fast?
Why ask it
Some managers want the problem the hour you see it, others want it with an option attached. Getting this wrong once costs disproportionate trust, and asking makes you look experienced rather than nervous.
How often should we meet in the first two months, and what should I bring?
Why ask it
Propose weekly and ask what format is useful, since a manager who wants a written update reads differently from one who wants conversation. If they resist regular time early on, plan on being self-directed and document more.
What mistake has someone in this seat made that you would rather I not repeat?
Why ask it
Softer than asking why the last person left, and it usually produces the same information. The answer tends to be about pace or politics rather than skill, which is exactly the part no job description covers.
Where does this team have a bad reputation internally, and is it fair?
Why ask it
You will inherit the reputation on day one whether or not you earned it. Managers who can describe it accurately are worth working for; ones who insist there is no perception problem have usually stopped asking.
What are you measured on, so I know what I am actually helping with?
Why ask it
Your manager's targets are the real brief, and they are often narrower than the team's stated mission. Aligning to them early is the cheapest way to have your work noticed by the people above your manager.
What decisions are currently waiting on someone in my seat?
Why ask it
There is almost always a queue: an unsigned contract, a hiring loop paused, a vendor waiting. Clearing two of those in week two builds more credibility than a strategy document, and it tells you where the role's real friction is.
What should I not change in the first six months?
Why ask it
Asking permission to leave something alone is disarming, and the answer marks the sensitive ground: a process someone senior designed, a tool with a champion, a team member's remit. Managers rarely mention these unprompted.
Who should I talk to in my first two weeks, and what should I ask each of them?
Why ask it
Ask for names and the reason for each, then actually book them. This turns an abstract instruction to build relationships into a list, and the people your manager names tell you where they think the influence sits.
If I want to propose something significant in month three, how does that get approved here?
Why ask it
Every organization has a real path: a committee, a document format, a single person's blessing, a budget cycle. Learning it before you need it is the difference between a proposal that lands and one that circulates for a quarter.
Six months from now, what would tell you I am ready for more?
Why ask it
Asked at the start, this reads as ambition rather than impatience, and it forces a specific answer while there is no history to argue about. If the answer is vague, you have learned that progression here is discretionary, which is useful to know early.
The First Ninety Days
Practical guidance for the conversation itself
How to Use the First Weeks
Ask three or four of these per conversation, not twenty
A single meeting that runs through a questionnaire feels like an audit. Spread them across your first four one-to-ones, and bring what you learned from the last set as context, which is what makes the questions read as work rather than interrogation.
Write down the answers and send them back
After the conversation about ninety day expectations, send a short summary of what you understood and ask whether it is right. This is the single most useful habit of a new hire, because it converts a friendly conversation into a shared standard.
Deliver something small and visible in the first three weeks
Pick from the queue of decisions waiting on your seat rather than starting something new. Finishing a stalled item early buys you the room to be slow on the larger thing, and it is remembered out of proportion to its size.
Resist the urge to diagnose out loud
You will see obvious problems in week one, and so did everyone else. Keep a private list and revisit it at day sixty, when you will know which items are actually broken and which are the visible edge of a constraint you had not seen.
If You Moved Roles Inside the Same Company
- Agree an explicit end date for your old responsibilities, in writing, with both managers
- Name the person taking each thing over and introduce them yourself rather than forwarding email
- Expect to be asked for help on the old job for months and decide in advance how much you will give
- Assume your reputation from the old role arrived before you did, including the parts you would not choose
- If you are now managing former peers, say so plainly in the first conversation with each of them
- Re-establish the basics with your new manager even if you have known them for years, because assumed context is where internal moves go wrong
Questions Better Saved for Later
- Promotion timelines in the first week, which reads as being uninterested in the current job
- Detailed criticism of your predecessor's decisions before you know why they made them
- Anything about another person's performance, which puts your manager in an awkward position
- Requests for flexibility or leave beyond what was agreed at offer, until you have delivered something
- Compensation renegotiation, unless the role has materially changed from what was described
- Broad questions about company strategy that are answerable from documents you have not read yet
Answers Worth Taking Seriously
- No specific answer to what would make ninety days successful
- A vague account of why your predecessor left, especially if two people give different versions
- Authority described in the offer that shrinks when you ask for examples
- No regular time on your manager's calendar in your first month
- A stakeholder everyone warns you about and nobody will describe
- Being asked to fix something urgently while also being told not to change anything
- A review cycle you have been told you fall outside of, with no alternative offered