Questions to Ask When Transitioning into a New Role
Twenty questions for the people you will work alongside in a new role: teammates, peers in other functions, and whoever has been there longest. They are aimed at how work actually gets done here, which is rarely what the onboarding document says.
The questions
Open any question for the note
What does this team do that would not be obvious from the org chart?
Why ask it
Most teams carry work nobody assigned them: a report another department depends on, a system they inherited, a relationship they maintain. Finding this in week one prevents you proposing a change that quietly breaks something downstream.
What are you working on this week, and what is slowing it down?
Why ask it
The best opening question with a new colleague, because it is specific and easy to answer. The blocker they name is usually the most honest thing you will hear about the organization all week.
How does work reach you, and where does it go when you are done with it?
Why ask it
Asking each person this builds a real map of the workflow, which almost never matches the documented process. The handoffs people describe casually are where delay and rework actually live.
Where do things get stuck most often?
Why ask it
Ask several people and look for the name or the stage that keeps recurring. One person's complaint is a preference; three people naming the same approval step is a finding you can do something about later.
What do people here complain about that never gets fixed?
Why ask it
The word never is doing the work. It surfaces the things that are either genuinely hard or politically protected, and knowing which is which saves you from proposing the obvious fix in your first month.
What did the last person in my role do that made your job easier?
Why ask it
This gives you a concrete list of services your colleagues valued, some of which are nowhere in your job description. It is also a gentler way to learn what your predecessor was actually good at.
What did they do that made your job harder?
Why ask it
Ask it right after the previous question so it reads as balance rather than gossip. People answer more openly than you expect, and the pattern across several colleagues is usually the real reason the role turned over.
Who do I call when something breaks at 6pm?
Why ask it
The answer is almost never the person listed in the documentation. Every team has one or two people who actually know how things work, and identifying them early is worth more than any onboarding checklist.
Which documents should I actually read, and which ones are out of date?
Why ask it
New joiners waste two weeks reading a wiki that stopped being true two reorganizations ago. Asking a teammate to point at the three live documents is a five minute conversation that saves days.
Where do decisions actually get made around here?
Why ask it
A meeting, a thread, a private conversation before the meeting, or one person's inbox. Knowing this determines whether your good idea needs a document, a hallway conversation, or a slot on an agenda.
What does a normal week look like here, and what does a bad one look like?
Why ask it
The bad week is the honest description of the job: quarter end, an outage, a launch, an audit. If nobody can describe a bad week, either the team is unusually calm or you are being managed.
How do people disagree here, in the meeting or afterwards?
Why ask it
This is the fastest read on a team's culture. Where disagreement happens after the meeting in private messages, consensus in the room means nothing, and you will need to do your own soundings before you propose anything.
What is the unwritten rule that someone new always breaks?
Why ask it
Every team has one: do not reply-all, do not book that room, do not go to that director directly, do not push on Fridays. People enjoy answering this, and it saves you a small avoidable embarrassment.
Who has been here longest, and what should I ask them?
Why ask it
Institutional memory sits with one or two people who are rarely senior. Asking a colleague to nominate them, and to suggest the question, gets you a warm introduction and a reason for the meeting.
What do you wish someone had told you in your first month?
Why ask it
The most productive question to ask anyone who joined in the last two years, because their memory of being new is still sharp. Long-tenured colleagues will answer with company history; recent joiners will give you something you can use tomorrow.
Which of our tools do you dislike, and what do people use instead?
Why ask it
Shadow processes are where the real workflow lives: a personal spreadsheet, a side channel, a script one person maintains. Knowing about them prevents a change that breaks the thing nobody admits to relying on.
How does this team decide something small, and how does it decide something expensive?
Why ask it
The two paths are usually completely different, and mixing them up is how new people stall. Ask for a recent example of each rather than a description of the process.
What does the rest of the company think this team does?
Why ask it
The gap between how the team sees itself and how others see it is the political weather you have just walked into. Colleagues are usually candid about it, and it will shape how your work is received outside the team.
If I could take one thing off your plate this month, what would help most?
Why ask it
Ask this in your second week and then do the thing. It generates real goodwill, it is a fast way to learn a process from the inside, and the answers tell you where the team is genuinely short-handed.
Three months from now, how will you know whether I have been useful to you?
Why ask it
Your manager's version of success and your colleagues' version are rarely identical, and only one of them sits next to you every day. Asking peers directly gets you a standard you can actually meet.
Learning How the Work Really Gets Done
Practical guidance for the conversation itself
Running Your First Round of Introductions
Book 25 minutes, not an hour
Short meetings get accepted, and a good one runs over naturally. Send two of your questions in advance so people arrive with something to say rather than wondering whether this is an interview.
Ask about their work before you talk about yours
Most new joiners spend the first half of an introduction explaining themselves. Reversing it, three questions about their week before anything about you, is the difference between being remembered as attentive and as one more person to brief.
Talk to the people outside your team early
The functions you depend on, and the ones that depend on you, form their opinion of your team from whoever contacts them. Meeting them in week two, before you need anything, is unusual enough to be worth doing.
Come back with what you heard
Two weeks in, tell a few colleagues the pattern you noticed across conversations and ask whether it sounds right. This is how observations become credibility, and it surfaces the thing everyone knows and nobody said to you directly.
What to Write Down After Each Conversation
- The blocker they named, and whether anyone else named the same one
- Who they said to talk to next, and why
- Any document, dashboard, or channel they mentioned by name
- The unwritten rule they warned you about
- One thing you could do for them, with a date next to it
- How they described your team, in their words rather than your summary
- Whether they seemed free to speak candidly, which is data about the culture
If Your New Colleagues Were Recently Your Peers
- Say the change out loud in the first conversation rather than waiting for it to become awkward
- Ask what they want to be different now, and what they want kept the same
- Expect to be tested once on whether the old informality still applies, and decide your answer beforehand
- Be explicit about what you will and will not pass upwards
- Do not lean on shared history in a disagreement, since it reads as leverage
- Accept that one or two relationships will cool, and that this is the cost of the move rather than a failure
Things You Might Hear That Are Worth Noting
- Several people naming the same colleague as the bottleneck, in careful language
- Nobody able to describe what a bad week looks like
- A documented process everyone quietly works around
- Disagreement that only ever happens after the meeting
- Your role described differently by three colleagues
- A warning about a stakeholder that nobody will elaborate on
- Recent joiners who have already stopped asking questions