Questions to Ask When Joining a New Team
For a new hire or an internal transfer in the first few weeks with a new team. Twenty questions to put to your manager and your new colleagues about what the team owns, how decisions get made, what is written down, and how you will be judged.
The questions
Open any question for the note
What does this team actually own, and what do people wrongly come to us for?
Why ask it
The second half is where the real map is. Every team fields requests that belong somewhere else, and knowing which ones lets you redirect politely instead of quietly absorbing work that was never yours.
What are you hoping I take off your plate first?
Why ask it
Managers usually hire against a specific irritation, and it is often narrower than the job description implied. Naming it in week one prevents the common failure where you optimise something nobody was worried about.
What would a good first three months look like from where you sit?
Why ask it
You are asking for a definition you can be measured against, ideally two or three concrete outcomes. If the answer is only about settling in and learning, ask again at the thirty-day mark when they will have a real answer.
Who should I meet in my first two weeks, and what should I ask each of them?
Why ask it
This produces a warm introduction list rather than a directory, and the reason attached to each name is the useful part. It also reveals which relationships your manager considers load-bearing, which is a map of the team's real dependencies.
Where does our work come from, and who decides what we do next?
Why ask it
Intake is the mechanism that determines whether the team is planned or reactive. Look for whether requests arrive through one queue or through individual messages, because the latter means priorities are set by whoever asks most persistently.
How does work get tracked here, and what counts as finished?
Why ask it
The definition of done varies wildly, and getting it wrong early makes you look careless rather than new. Ask to see a recently completed piece of work end to end, including whatever documentation or handover was expected.
Which decisions can I make alone, which need a heads-up, and which need approval?
Why ask it
Most early friction comes from misjudging this line rather than from poor judgement itself. Ask for the boundary in money, scope, or blast radius, and ask for one recent example of someone getting it wrong.
What is the meeting rhythm, and which meetings are optional in practice?
Why ask it
Calendars are inherited and rarely pruned, so some recurring meetings exist only because nobody cancelled them. Asking which are genuinely optional saves hours a week and tells you where decisions actually get made.
How do people prefer to be reached, and what is the expectation on replying?
Why ask it
The gap between a team that treats chat as asynchronous and one that treats it as urgent causes a surprising amount of early tension. Ask specifically about evenings and weekends, and watch what people do rather than what the policy says.
What is written down, and where do I actually find it?
Why ask it
There is usually an official location nobody uses and a real one that is a folder, a pinned message, or a person. Ask which documents are current, because outdated instructions confidently followed are a classic way for a new joiner to break something.
What is the unwritten rule that someone new usually breaks?
Why ask it
This works because it invites a story rather than a criticism, and every team has one: a person who must be copied in, a system nobody touches on Fridays, a phrase that lands badly. Ask several colleagues and note where the answers agree.
What is the team frustrated by right now?
Why ask it
The answer tells you what has been tried and failed, which stops you proposing it again in week three as though it were novel. Recurring frustrations that nobody has escalated also indicate how much authority the team believes it has.
How does feedback happen here, in both directions?
Why ask it
Ask for the mechanism and the last real instance, since the mechanism often exists on paper only. A team where nobody can recall recent critical feedback is a team where problems surface at review time or not at all.
Who outside the team has strong opinions about our work, and how do they express them?
Why ask it
Every team has stakeholders who can escalate, delay, or veto, and they rarely appear on the org chart in a way that shows their influence. Knowing who they are before your first disagreement is considerably cheaper than learning it during one.
What is the team currently disagreeing about?
Why ask it
Live disagreements tell you what matters here and who holds which position, and it is the one question that reliably reveals real dynamics. If you are told there are none, ask what the team decided most recently and how the decision was reached.
What happened with the last person in my role?
Why ask it
Promotion, a sideways move, and a departure each set very different expectations for you. If they left, ask what they found difficult, because that difficulty is usually structural and still there waiting for you.
How will my performance be judged, and by whom?
Why ask it
You want the actual mechanism: who writes the review, what evidence they use, whether peers contribute, and on what cycle. Vague reassurance now becomes an unwelcome surprise at the first formal review.
What is coming in the next quarter that will change how we work?
Why ask it
A reorganisation, a system migration, a departure, or a launch will affect your first months more than anything in your onboarding plan. People will usually tell a new joiner plainly when asked directly.
What would you tell me not to touch for the first month?
Why ask it
This gives colleagues permission to protect the fragile thing, whether that is a legacy process, a sensitive client, or a relationship with another team. It also signals that you intend to learn before rearranging, which buys you goodwill.
Six months from now, what would make you glad I joined?
Why ask it
Colleagues answer this more usefully than managers do, because they describe the gap they personally feel rather than the one in the hiring plan. Ask two or three people, and where their answers overlap is your real mandate for the year.
Your First Weeks on a New Team
Practical guidance for the conversation itself
Ask Different People Different Things
Your Manager: Scope and Judgement
Expectations, decision boundaries, how performance is assessed, and what they hoped hiring you would fix. Book a recurring one-to-one in the first week even if they did not offer one, and bring specific questions rather than a general update. Managers answer precise questions far better than open ones.
Your Peers: How Work Actually Happens
Where the real documentation lives, which meetings matter, what the last new joiner got wrong, who to avoid annoying. Ask individually rather than in a group; people are markedly more candid one to one, especially in the first fortnight while they still think of you as an outsider.
Adjacent Teams: What We Look Like From Outside
Ask two or three people in teams that depend on yours what your team is good at and what frustrates them. It takes twenty minutes each and gives you information your own team either cannot see or will not say. It also makes the first request you send them much easier.
The Person Who Joined Six Months Ago
They remember what was confusing and have not yet forgotten which parts of onboarding were useless. They will also tell you honestly what surprised them, which is the closest thing to a briefing you will get.
What the Answers Tell You
- If nobody can define what finished means, expect rework and get your interpretation confirmed in writing before you start anything visible.
- If priorities arrive through individual direct messages rather than a queue, the loudest requester sets the roadmap. Plan to negotiate rather than to receive.
- If the answer to what the team disagrees about is nothing, either the team avoids conflict or it has stopped caring. Both are worth understanding before you raise your first objection.
- Notice whether people describe their manager's decisions with reasons attached. Teams that cannot explain why get told rather than consulted, which sets a ceiling on your own influence.
- If several colleagues independently name the same unwritten rule, treat it as a real constraint rather than a quirk.
- Take note of anything described as temporary that has been temporary for over a year. That is where the team's actual pain lives, and often where a new person can be genuinely useful.
A Workable First Month
- 1Week one: meet people, take notes, ask how things work, and change nothing.
- 2Week one: read the last quarter of team decisions, retrospectives, and incident notes if they exist. Old threads explain more than any onboarding document.
- 3Week two: take one small, real, unglamorous piece of work end to end so you learn the process by using it.
- 4Week two: write down every question you had to ask someone. That list is the onboarding document nobody has written yet.
- 5Week three: confirm your understanding of priorities back to your manager in writing, and let them correct it.
- 6Week four: raise one improvement, small and well evidenced, and ask what has already been tried before proposing it.
- 7End of month one: fix the onboarding notes for the next person while your confusion is still fresh.
Common Pitfalls
Proposing Changes Before Understanding History
Most obvious improvements have been attempted and blocked by something invisible from the outside: a compliance rule, a fragile integration, a stakeholder relationship. Ask what has been tried before suggesting anything. The suggestion will land far better when you can say you know why it failed last time.
Comparing Everything to Your Last Job
Your previous team's methods may genuinely have been better, and saying so in the first month reliably makes people defensive rather than curious. Bank the observations, wait until you have delivered something, then raise them one at a time with local reasoning.
Mistaking Onboarding Silence for Freedom
Where nobody has told you the expectations, they still exist. Absence of instruction usually means the team assumes you know, or that your manager is stretched. In either case ask explicitly rather than inventing your own standard and discovering the difference in a review.
Only Talking to the Friendly One
New joiners naturally gravitate to whoever was warmest on day one, and end up seeing the team through one person's grievances. Deliberately have a conversation with the quiet member and with anyone described as difficult. The composite picture is much more accurate.
Letting the First Month Pass Without a Check-In
Ask directly at four weeks how it is going and what you should be doing differently. It is a small amount of discomfort in exchange for correcting course early, and it prevents the situation where a manager's concerns accumulate quietly until a formal review.