The First 1:1 Playbook: 5 Questions Every New Manager Should Ask

As a manager, you are by far the single biggest factor in whether your direct reports thrive at work — or quietly check out.

This is backed by the research at Gallup, where they "studied performance at hundreds of companies and measured the engagement of 27 million employees and more than 2.5 million work units over the past two decades" and have found that managers account for at least 70% of the variance in employee engagement scores (source).

No pressure but this means that your very first one-on-one ("1:1") with a new direct report is where that relationship begins - make sure it's off to the right start.

TL;DR

• Your first 1:1 is a meet-and-greet, not a delivery review or performance conversation.
• Lead with curiosity. Listen roughly twice as much as you talk.
• Ask 5 specific questions (below) to build a foundation of trust.
• Avoid performance talk, deep frustration dives (unless they are constructive), overly personal questions, and salesy speeches.
• End with a clear next step, a confirmed cadence, and a shared notes doc you'll actually maintain.
• Never cancel a 1:1. Reschedule but never cancel. And no, hybrid business-as-usual chats combined with 1:1-y topics do not count.

Why the first 1:1 matters

The first 1:1 isn't just a nice-to-have meet-and-greet — it's the foundation of what should become one of the most valuable recurring meetings in both of your weeks. Establishing a real baseline of trust with someone takes six months to a year, and this meeting sets the trajectory for that timeline. No pressure, right? :-)

Process-wise: ideally you've already been introduced to the team in a group setting in your first week. After that, don't wait too long to schedule the first 1:1 with each person. I usually start weekly — especially with smaller teams — and move to every other week once the relationship has some momentum.

So what should you actually talk about? Pure freeform feels aimless; a rigid agenda feels like an interview. Aim for something in between — a conversation that's casual and authentic, but that also gives your direct report a tangible sense of who you are as a manager and what they can expect going forward.

The 5 questions to ask in your first 1:1

1. "What are you working on, and what's exciting — or not — about it?"

This is the easiest entry point and the most natural one. Most engineers warm up quickly when you ask about their actual work — it's something they have rich context on, and their answer surfaces a lot: what they care about, what's blocking them, what they're proud of, what frustrates them. Let it drift into how long they've been on the team, what tech they like, hobbies if they come up. Keep it high-level; this isn't an interview.

2. "What did past managers do well in 1:1s? What did you wish was different?"

This is the question almost no one asks, and it's gold. It signals that the meeting is partly theirs to shape, not just yours, and it gives you a cheat sheet for how to be useful to them specifically — based on real prior experience rather than your best guesses.

3. "What does growth look like for you over the next 6–12 months?"

Even a light version of this signals you're invested in them beyond shipping the current project. You don't need to solve anything in this meeting — just open the door. The answer, or the lack of one, tells you a lot about what to follow up on.

4. "How do you prefer to receive feedback?"

One of the most underrated questions you can ask in a first 1:1. People differ a lot here — some want direct, in-the-moment feedback, others prefer it in writing, some want it private, others are fine in a group. Asking this early signals you're thoughtful, that feedback will be a normal part of your relationship, and that you actually care how it lands. It also sets a quiet expectation that feedback will flow both ways.

5. "What's something I should know that doesn't usually come up at work?"

A soft, open invitation. Some people will share a constraint — a family commitment, a time-zone preference etcetera. Others will pass, and that's fine. Either way, it signals you see them as a whole person, not a unit of output. This is also a natural place to clarify what stays between the two of you and what you'd feel obligated to escalate (e.g., safety, harassment, legal issues) — direct reports often assume the worst by default, and naming it removes unspoken hesitation.

What to avoid in a first 1:1

Performance expectations and project status

This is a meet-and-greet, not a delivery review. Project status and how performance management works belong in team meetings and dedicated review conversations — not the first 1:1, where you're still building a baseline of trust.

Doing most of the talking — including diving deep on frustrations

You'd be surprised how often new managers dominate the first 1:1, either by giving long context dumps about themselves or by getting pulled into solving a frustration on the spot. Two ears, one mouth — listen roughly twice as much as you talk. If a frustration surfaces, listen, take a note, create an action item for yourself, and schedule a follow-up. The follow-up is what builds trust, not the listening itself.

Overly personal questions

Family background, age, relationship status, kids, where they grew up, politics, your own political opinions. A no-brainer, but worth saying because I've seen it happen often enough that it clearly isn't obvious to everyone.

Being overly "salesy" or posturing

Don't give a cliché speech about how you're going to be a great manager for them. Trust is earned through what you do over the next six months to a year, not promised in the first meeting. If you over-sell and then underdeliver, it backfires hard. Be yourself.

After the meeting

A couple of mechanics turn a single good first 1:1 into a durable relationship:

• Keep a shared notes doc per direct report. A simple running doc with notes and follow-ups goes a long way. Closing the loop on what you said you'd do is what builds trust faster than anything you say in the meeting itself.
• Confirm the cadence and the next step before you wrap. Summarize any action items (mostly yours), confirm when you're meeting next, and check that the cadence works for them. Plant the seed that future 1:1s will have purpose and structure — career conversations, deep-dives, feedback exchanges, etc., depending on what's most useful at a given time.

If you walk away from a 10-minute, authentic conversation about more or less nothing, that's still a win. Show up, smile, don't be too formal, be a human being.

The one unbreakable rule: don't cancel your 1:1s

If something urgent comes up, reschedule — never cancel outright. Treat the 1:1 as a near-sacred commitment. Every cancellation, especially early in the relationship, sends the message that their time isn't a priority. Reschedule the same day if you have to. Sustained over months, this single habit is one of the strongest trust signals a manager can send.

FAQ

How long should a first 1:1 be?
30 to 45 minutes is a good default. A great first 1:1 can wrap in 20 minutes if the conversation flows naturally — that's fine. The goal is a real meet-and-greet, not maximum time-in-room.

Should I send an agenda in advance?
For the first 1:1, a light heads-up beats a formal agenda. Something like: "Looking forward to chatting tomorrow — no agenda needed, just want to get to know each other." A too-structured tone early can make it feel like an interview.

How often should 1:1s happen after the first one?
Weekly is a safe starting point, especially for small teams or new relationships. Move to every other week once you've built momentum. Cadence should match the relationship, not the org chart.

What if my direct report doesn't open up?
That's normal — trust takes months, not minutes. Don't push. Ask easier questions, listen more, follow through on small action items, and try again next week. Consistency over time is what gets people to open up, not pressure in any single meeting.