Your First 1:1 With a New Manager — The Template That Works

The first 1:1 with a new manager is the single highest-leverage meeting in your first year. Handled well, it sets operating norms, clarifies expectations, and builds the calibration that will protect you through every ambiguous moment for the next twelve months. Handled badly — or worse, left to small talk — it leaves you working off assumptions your manager doesn't share. In 2026, with average manager tenure at 14 months and org charts shuffling every two quarters, the cost of a vague first 1:1 has never been higher. This is the template that works, delivered as directly as the meeting itself should be.

The first 1:1 is not a meet-and-greet — treat it as a working session

Most candidates walk into their first 1:1 expecting rapport-building. Their manager, if they're good, is expecting a working session. This mismatch costs you. Use the meeting to get real answers on the things you'll need to reference for the next year: operating norms, definitions of success, escalation paths, and the manager's own operating style. Rapport builds across the first 10 meetings, not the first one. The first meeting is where you extract the scaffolding.

Your first 1:1 is the only meeting where your manager is contractually obligated to tell you exactly how they operate. Don't waste it asking what they did over the weekend.

Come with an agenda, written, shared 24 hours in advance. This alone will put you in the top decile of new-hire signaling. Most new hires show up with nothing; the ones who show up with an agenda get treated like operators from day one.

The agenda — 30 minutes, six sections

Here is the agenda to send the day before. Adapt wording; don't change the structure.

1. Check-in and operating-style (3 min): How you both prefer to communicate, async vs. sync, Slack vs. email, response-time norms.
2. What success looks like in 90 days (7 min): Their definition, not yours. In concrete terms.
3. The team's current state (5 min): What's working, what's fragile, where the fires are, who the informal leaders are.
4. Your open questions and assumptions (5 min): Your list, 3-5 items, each a concrete question.
5. Cadence and escalation (5 min): Meeting rhythm, how to flag issues, when to interrupt them vs. wait.
6. Decisions needed from them in week one (5 min): Tools access, expectation-setting with the team, any commitments you need them to make to others on your behalf.

Why 30 minutes: most managers only block 30 for a first 1:1, and the discipline of a tight agenda forces signal. If you get 60, use the extra time for section 3 — their read on the team's current state, which is where the most useful qualitative information lives.

Ask for their definition of success at 30, 60, and 90 days — concretely

The single most important question in a first 1:1: "What does good look like at 30 days, 60 days, and 90 days in this role?" Not "what are my goals" — that gets you the official goals document. Ask for their personal, concrete, operating definition of success. Most managers haven't articulated this explicitly, and forcing them to do so produces information you can't get any other way.

Listen for specifics. "Build strong relationships" is not an answer; "be trusted enough by the infra team lead that they'd brief you before an incident" is. If they give you fuzz, push: "If I were sitting here with you in 90 days and things had gone well, what would we be saying about my first three months?" This reframe unlocks specifics.

Things to get concrete on:

• 30-day success: Usually about orientation, relationships, and context. Get their specific list.
• 60-day success: Usually about first visible work. What should you have shipped or started?
• 90-day success: Usually about trust and scope. What should others be saying about you at this point?
• The failure mode: "What would a version of this first 90 days look like that didn't go well?" This surfaces the specific risks they're worrying about.
• Their read on the previous occupant: If you're replacing someone, what do they want more of, and what do they want less of?

Write all of this down. Reference it in the 30-day check-in. Reference it explicitly again at 60 and 90. Managers notice when their expectations are treated as contracts.

Surface operating-style preferences before you get them wrong

Most new-hire friction in the first 90 days comes from operating-style mismatches, not substance. The manager who wants async updates feels micromanaged by the new hire asking to walk through everything in person; the manager who wants sync feels blind when the new hire defaults to Slack. Surface these explicitly, in the first meeting:

• Communication channel: Slack, email, async doc, or sync meeting? For what kinds of updates?
• Response-time norms: When do they expect you to respond to them? When should you expect them to respond to you?
• After-hours: Do they work after hours? Do they expect you to? What's urgent vs. what can wait until morning?
• Written updates: Weekly status emails? Monthly reviews? Never?
• Meeting culture on the team: Camera on/off, document-first vs. slide-first, decision logs or none?
• How they want to hear about problems: Early and speculative, or late and diagnosed?

That last one is the most important and the most often missed. Some managers want to hear about problems as soon as you notice them, even if you don't have a plan yet. Others find early problem-surfacing stressful and want you to come with options and a recommendation. You cannot guess this. Ask.

Pre-commit to a cadence and a set of escalation patterns

End the meeting with two commitments: a meeting cadence and an escalation pattern. Without these, the 1:1 becomes a floating recurring meeting that gets bumped whenever anyone's busy — and the busyness is often a signal of exactly the moment when you most need the meeting.

Cadence to negotiate: weekly 30 minutes for the first 12 weeks, moving to biweekly only if both parties agree it's working. Weekly in the first quarter is non-negotiable at most well-run companies; if your manager pushes for biweekly from day one, treat that as a yellow flag on their available attention.

Escalation patterns to define: what triggers an ad-hoc meeting outside the 1:1 (i.e., this is urgent), what triggers a Slack DM (this is important but not urgent), what can wait for the next 1:1 (this is contextual). Most managers will appreciate you asking; the ones who don't have a clear answer are telling you something about how their team operates generally.

Also discuss: the meeting notes format. Will you take them, will they take them, or will no one take them? Recommend that you take them in a shared doc that persists meeting-to-meeting, with action items tracked. This pattern — a living 1:1 document — is the single most useful habit across your entire relationship with this manager. It creates institutional memory, makes expectations explicit, and becomes invaluable at performance-review time.

Close with a calibration question they'll remember

In the last three minutes, ask one calibration question that signals how you plan to operate: "I'd like to check in again in 30 days to calibrate on how the first month went — what's the best way to structure that conversation?"

Why this works: it signals you treat expectations as checkpointed, not set-and-forget. It gives them a chance to set the 30-day meeting's shape. And it establishes that calibration is a routine you expect to run, not a performance-review surprise.

If your manager pushes back on a 30-day check-in — "no need, we'll just talk as things come up" — treat that as a small-but-useful signal about how they handle feedback. Some managers really do prefer continuous feedback; most who say this actually mean they don't want to give feedback at all. Gently hold the line: "I'd appreciate even a 20-minute calibration, even if things are going well, just so I can correct course early if needed." Most managers relent when the framing is about your development, not their evaluation.

Also consider closing with one specific ask you need from them in the first week: tool access, introduction to a specific person, a decision about scope that's blocking you. Don't leave the meeting without one concrete action item from them. This sets the norm that 1:1s produce decisions, not just conversation.

Next steps

Before your first 1:1, do three things. First, draft the agenda above and send it 24 hours in advance. Second, prepare your list of 3-5 open questions — the real ones you need answered, not filler. Third, have a tentative meeting-notes document ready to open on shared screen or distribute after.

In the meeting, lead with the agenda, ask for concrete 30/60/90-day success definitions, surface operating-style preferences, set the cadence and escalation patterns, and close with a calibration question and a concrete action item. Take notes in a living shared document you'll carry across every future 1:1.

The first 1:1 is a one-shot meeting in the sense that the norms set in it will persist. Treat it like the working session it is, and the year one that follows gets dramatically easier.

Related guides

• New-Manager Onboarding Playbook — First 90 Days as an EM — The first 90 days as an EM at a new company determine the next two years. Here's the week-by-week playbook for listening, shipping, and earning trust.
• The 30-60-90 Day Plan Template for a New Job in 2026 — By Role and Seniority — A strong 30-60-90 plan turns a new job from vague onboarding into a visible operating plan. Use this role-by-role template to learn fast, build trust, ship early wins, and avoid overpromising in your first quarter.
• First-Day Questions to Ask Your Manager: The Year-One List — The specific questions to ask in your first one-on-one that set up year-one success. No filler, no soft-pedaling — a checklist you can bring into the meeting.
• Counter-Offer Letter Template 2026: Wording That Wins More Comp — The exact counter-offer email that gets recruiters to move in 2026, plus the leverage math, timing, and mistakes that leave money on the table.
• First Week Playbook for Data Scientists: Access, Baselines, Stakeholders — A concrete first-week plan for data scientists in 2026: get data access on day one, establish baselines, and map the stakeholders who will act on your work.