How many questions should I bring to a first one-to-one?

Prepare eight or ten, ask three or four. The list is for you — it means whatever direction the conversation takes, you have something worth asking. Running the full list turns a working conversation into an interrogation, and the meeting's other job is your manager getting a read of you. Leave room for that.

What should I NOT ask a new manager in week one?

Anything that reads as an exit plan or a grievance rehearsal: promotion timelines, salary-band mechanics, whether remote days might increase, or pointed questions about a colleague. All of these have legitimate moments later. Week one questions should be about the work, the team, and how your manager operates — the ones that make you better at the job you just started.

When should I ask about progression and development?

Once you have something to attach it to — usually after your first review, or around month three when you can point at delivered work. Asking 'what would progression from this role look like?' with evidence behind you is a strong question; asking it in week one, before you've done anything, makes the job in hand sound like an inconvenience.

What if my new manager is too busy to meet me properly?

Make asking cheap: request twenty minutes, bring three questions, send them in advance, and end on time. If even that fails repeatedly, gather the answers sideways — a peer can tell you how urgency works here, the team's calendar tells you which meetings are real — and note what you've learned about the manager's bandwidth, because that is part of the operating manual too.

Should I write down what my manager tells me?

Yes, visibly and briefly — and play the important answers back afterwards in a short email: 'so month one is the handover, Thursdays are the digest, bad news same-day.' The playback does three jobs: it catches misunderstandings while they're free, it shows the answers landed, and it converts a warm conversation into an agreement either of you can point at later.

Start

Questions to ask your new manager: the first one-to-one, used properly

Updated 12 August 2026

The first one-to-one with a new manager is the cheapest meeting you will ever run and the most expensive one to waste. In week one you hold a licence that expires fast: you can ask anything — how decisions really get made, what happened to the last person, what your manager is actually judged on — and every question reads as diligence. Ask the same things in month four and they read as doubt. This page is the working set for that meeting: the questions worth the licence, what each one is really for, and worked ways to ask the delicate ones.

The aim is not rapport, though you will get it. It is calibration. Every team runs on an unwritten operating manual — what 'urgent' means here, which meetings are real, whose sign-off actually matters, what gets people quietly marked down. Your manager holds most of that manual in their head and will hand it over to anyone who asks well. People who don't ask assemble it by trial and error across six months, and the errors are the expensive part.

A note on register before the questions: bring three or four of these, not fifteen. Write them down, ask the ones the conversation makes room for, and let the rest go — a first one-to-one run like an audit teaches your manager to dread the slot. The worked answers below show the asking done warmly, including the two questions most people want answered and never quite ask out loud.

Your career — see how Start connects to the stages before and after it.

What your manager is weighing

Signal-reading. Your questions tell a new manager what you think the job is. Someone asking about the team's current pressures and the quarter's real priorities reads as already working; someone whose every question is about progression reads as already leaving.
Judgement about sequence. Week one is for how-this-place-works questions; salary-band architecture and promotion mechanics have their moment later. Managers notice who can tell the difference — sequencing is a work skill, and this meeting is your first visible sample of it.
Whether you listen to the answers. The follow-up question is the tell. Anyone can bring a list; the person who hears 'we've had three tools for this in two years' and asks 'what killed the first two?' is doing the actual job already.
Coachability, sampled early. Asking 'what would you like me to do differently?' in week three — and visibly acting on the answer — establishes a feedback channel while the stakes are tiny. Managers invest more in people they can steer.

'What should I aim to have done or understood by the end of month one — and what can genuinely wait?'

Why it's asked: The expectation-calibrating opener, and the strongest first question available. It converts the induction fog into a ranked list, tells you what your probation is quietly being marked against, and — the half people miss — asks permission to ignore things, which is the permission that protects your first weeks from drowning.

Model answerFirst one-to-one, analyst joining an insurance pricing team

Can I start with the calibration question? I've got an induction plan with eleven modules and a backlog with forty tickets, and I don't yet know which of it is load-bearing. By the end of month one, what would you want me to have actually done or understood — and just as usefully, what on that pile can genuinely wait?

[And the follow-up that makes it real:] That's helpful — so if I'm hearing it right, the renewal model handover from Priya is the thing that matters, the dashboard tickets are background, and nobody expects me near the reserving work this quarter. Can I play that back in an email so we've got the same month one written down?

One more on the same thread: when I hit something I can't move — access, a dataset, a person on leave — do you want to hear about it at the Friday one-to-one, or the day it happens? I'd rather learn your escalation taste now than guess it under pressure.

'How do you prefer to work — updates, questions, bad news? And what did your best working relationship with a report look like?'

Why it's asked: The operating-manual question. Every manager has a communication metabolism — written versus spoken, daily drip versus weekly digest, questions-anytime versus batched — and most will tell you theirs with relief, because the mismatch is what wears both sides down. The second half lifts it from logistics to pattern: what did good actually look like from their chair?

Model answerWeek one, marketing executive, national charity

Can I ask the how-you-work question while it's still week one? Concretely: when something's moving but not finished, do you want the running update or just the landing? When I hit a question I could probably answer myself in an hour, do you want the hour spent or the question asked? And bad news — found a problem, made a mistake — what's the version of hearing about it that works for you?

[Then the deepening half:] And a slightly bigger version of the same question: think of the best working relationship you've had with someone in a role like mine. What were they doing that made it work? I'm not fishing for a template — I'd just rather aim at something you've actually seen work than at my guess of it.

[And close the loop:] That's genuinely useful. So: weekly written digest on Thursdays, questions batched unless they're blocking, and bad news same-day by phone. I'll run that for a month and you tell me what to adjust.

'What's the team carrying at the moment that you'd most like taken off its plate?'

Why it's asked: The contribution-finder. Job descriptions describe the role as designed; this question finds the role as needed — the report nobody owns, the backlog everyone steps around, the stakeholder who needs more handling than the team can spare. Volunteering for one unglamorous, real burden in week two builds more standing than a month of visible keenness.

Model answerFirst week, service desk team leader, NHS trust

I've read the job description and I'll do what's on it — but can I ask the other version? What's the team actually carrying right now that you'd most like taken off its plate? Not the strategic stuff, the sandbags: the report someone compiles by hand every Monday, the rota nobody wants to own, the thing that's been 'temporary' for a year.

[On hearing it:] The out-of-hours handover log — understood. Two questions so I take it over properly rather than enthusiastically: who does it hurt when it's wrong, and is the pain the format or the chasing? If it's the chasing, I'll fix the process rather than inherit the chase.

And to keep myself honest: if I take that on, what should I visibly NOT pick up this quarter? I've watched new starters say yes to everything and become the team's overflow pipe by Easter. I'd rather carry one real thing well than six things badly.

'What happened with the last person in this role — and what should I learn from it?'

Why it's asked: The delicate one, and worth asking properly rather than assembling the answer from corridor fragments. Whether they were promoted, left happily, or left otherwise, the role you have inherited was shaped by it — the stakeholders' expectations, the half-finished projects, the sensitivities nobody mentions. Asked without appetite for gossip, it reads as exactly what it is: due diligence on your own job.

Model answerFirst one-to-one, operations coordinator, logistics firm

Can I ask about the person before me — not the personal side, the professional shape of it? Whatever you're comfortable sharing: what did they do well that I should keep going, and what would you want done differently this time round?

[If the answer is thin, the useful narrower version:] Fair enough — then can I ask it about the work instead? When I opened the shared drive I found the depot-move plan about two-thirds finished. Is that paused, dead, or waiting for me? And are there commitments made to the Barnsley site I should know I've inherited, before I meet them on Thursday and find out live?

[And the closing frame:] The reason I ask now rather than piecing it together: people will assume I know what was promised. For the first month, when I hit one of those assumptions, I'll check it with you rather than guess — and I'd rather that be a standing arrangement than a surprise each time.

'What are you measured on this year — and what part of it does my role actually move?'

Why it's asked: The alignment question almost nobody asks. Your manager has a scorecard — objectives, a service standard, a number their own boss watches — and your work either moves it or decorates it. Knowing which is which lets you weight your effort where it counts twice: once for the team, once for the person writing your probation review. Asked plainly, it lands as commercial sense, not politics.

'Who should I meet in my first month — and who does this team depend on that I wouldn't guess from the org chart?'

Why it's asked: The map question. The org chart shows reporting lines; the work runs on a different diagram — the analyst who actually owns the numbers, the PA who controls the diary that matters, the engineer in another team whose goodwill everything quietly needs. Your manager knows the real diagram. Ask for introductions, then actually book them; a name-drop from your manager opens doors cold emails don't.

'What does 'urgent' mean here — and what's the etiquette when two urgent things collide?'

Why it's asked: Sounds small; prevents your first visible failure. Every workplace has a private vocabulary of urgency — in one, 'when you get a chance' means today; in another, 'urgent' means this fortnight. Colliding priorities are where new starters get silently marked down, because the etiquette of saying 'I can do one of these by five, which one?' varies wildly. Learn it before you need it.

'How does the team like to handle disagreement — in the meeting, after it, or in writing?'

Why it's asked: Culture is mostly this: where dissent is allowed to live. Some teams argue openly in the room and decide; some decide in the room and argue in corridors; some do their real thinking in documents. Guessing wrong makes you either the person who ambushed a colleague in public or the one who seemed to agree and then didn't. One question, asked early, and you skip the whole learning curve.

'Is there anything about how I've started that you'd already like me to adjust?'

Why it's asked: The feedback-channel opener, best asked at week three rather than day two — early enough that anything raised is trivially fixable, late enough that there is something real to say. The question's power is what it establishes: that feedback flows to you easily and lands well. Managers calibrate how much steering people can take by the first steer; make the first one cheap.

'A year from now, what would make you glad you hired me — beyond the job description being done?'

Why it's asked: The closing question, and the one that surfaces the unwritten role: the thing they hoped this hire would bring that never made the advert — calm in a jumpy team, commercial thinking in a technical one, someone who finishes what the team starts. The answer is your real scorecard. Note it somewhere you will reread in month six, because your manager will remember saying it.

FAQ

How many questions should I bring to a first one-to-one?: Prepare eight or ten, ask three or four. The list is for you — it means whatever direction the conversation takes, you have something worth asking. Running the full list turns a working conversation into an interrogation, and the meeting's other job is your manager getting a read of you. Leave room for that.
What should I NOT ask a new manager in week one?: Anything that reads as an exit plan or a grievance rehearsal: promotion timelines, salary-band mechanics, whether remote days might increase, or pointed questions about a colleague. All of these have legitimate moments later. Week one questions should be about the work, the team, and how your manager operates — the ones that make you better at the job you just started.
When should I ask about progression and development?: Once you have something to attach it to — usually after your first review, or around month three when you can point at delivered work. Asking 'what would progression from this role look like?' with evidence behind you is a strong question; asking it in week one, before you've done anything, makes the job in hand sound like an inconvenience.
What if my new manager is too busy to meet me properly?: Make asking cheap: request twenty minutes, bring three questions, send them in advance, and end on time. If even that fails repeatedly, gather the answers sideways — a peer can tell you how urgency works here, the team's calendar tells you which meetings are real — and note what you've learned about the manager's bandwidth, because that is part of the operating manual too.
Should I write down what my manager tells me?: Yes, visibly and briefly — and play the important answers back afterwards in a short email: 'so month one is the handover, Thursdays are the digest, bad news same-day.' The playback does three jobs: it catches misunderstandings while they're free, it shows the answers landed, and it converts a warm conversation into an agreement either of you can point at later.