How to Run Your First 1:1 as a New Manager

A few days before my first 1:1 as a manager, I caught myself rehearsing sentences in my head. Not for a conference talk. For a thirty-minute conversation with someone I had been working next to for years.

We were peers not long before. Equals. We had argued about code reviews, complained about flaky pipelines, eaten lunch together. And now, suddenly, I was supposed to be the wise guy they come to for guidance and growth? The impostor syndrome was loud. This person might well be more technically skilled than me in half the areas we worked in. What exactly was I going to teach them in a 1:1?

When the meeting came, I opened with the only thing I honestly had: “I’m here to support you. My time is your resource.” No framework, no agenda template, no clever icebreaker question.

What happened next surprised me. The conversation was open and easy. Relaxed, even. It felt like two old friends chatting, because that’s essentially what we were. I had braced for something stiff and awkward, and instead I got the most natural conversation of my week.

That’s the first thing nobody tells you about your first 1:1: it’s also your first 1:1. All the advice out there is written as if the report is the nervous one and you are the calm professional executing a playbook. In reality, your hands are the sweaty ones. And in most cases, the catastrophe you’re rehearsing for never shows up. The person across the table is usually rooting for you.

You already know the standard advice, because it’s in every article ever written on this topic: a 1:1 is not a status update, hold it weekly, thirty minutes, don’t cancel it, ask open-ended questions. All of that is correct, and I won’t waste your time repeating it. If you want the canonical question list for a first 1:1, Lara Hogan’s first 1:1 questions are the gold standard; steal them shamelessly. What follows is the stuff those articles skip.

Your first 1:1 is not one meeting. It’s three.

“Your first 1:1” sounds like a single, well-defined event. It isn’t. There are at least three completely different versions of it, with different social dynamics, and the standard advice quietly assumes you’re in the third one.

The former peer. This is the one I was so anxious about, and it turned out to be the easiest. My first 1:1 with a colleague I had been promoted over was simply a continuation of the conversations we were already having. Same honesty, same shorthand, same jokes. The mistake would have been to manufacture formality that was never there, to suddenly show up with an agenda document and a serious manager voice. Acknowledge the elephant once, briefly: “Yes, this is a bit strange for both of us.” Then ask the only question that actually changed: “What do you need from me now that you didn’t need from me as a peer?” The relationship doesn’t restart. It gets a new dimension.

The outside hire. When I joined a team from the outside as their manager, my first 1:1s looked nothing like that. They were closer to “let’s grab a coffee and get to know each other.” I had no shared history to lean on, no credibility in the bank, and honestly, no idea how this team worked. So I flipped the direction: instead of setting expectations, I asked what they expected of me. What did their previous managers do that helped? What drove them crazy? Every answer was a free lesson, a list of dos and don’ts earned through someone else’s mistakes. I mostly listened and stayed curious. In this scenario, you are not onboarding them. They are onboarding you.

The new hire you selected. This is the only version where you genuinely set the frame from scratch. There’s no history with you and no history with the team, which means nothing to un-learn but also nothing to read from. Here, and only here, the explicit-norms conversation earns its keep: what this meeting is for, how you like to give and receive feedback, how they prefer to receive it, what they should bring to you versus solve alone. Say these things out loud precisely because this person has no other way to discover them.

Figure out which of the three you’re walking into before you prepare anything else. Most first-1:1 advice fails simply because it’s written for one of these and applied to another.

How to listen like a therapist

Most 1:1 advice tells you what to ask. Clinical psychology tells you how to listen, and it’s dramatically more useful.

Therapists have a technique framework called OARS, from motivational interviewing, and it maps onto 1:1s almost perfectly:

Open questions. You know this one. “How’s the project going?” invites a status report; “What’s been on your mind this week?” invites a conversation.
Affirmations. Not flattery. Specific, evidence-based recognition: “You caught that race condition before it hit production, and you documented it so the next person won’t step in it. That’s exactly the kind of work I want to reward.” Generic praise is noise; specific affirmation tells people what to do more of.
Reflective listening. Repeat back the meaning of what you heard, not the words, as a hypothesis: “It sounds like the frustrating part isn’t the deadline itself, it’s that the deadline moved without anyone asking you.” Half the time you’ll be wrong, and being corrected is the point. It’s how you find out what they actually meant.
Summarizing. Close the loop at the end: “So the main thing this week is the dependency on the platform team, and you want me to escalate it. Did I get that right?” Thirty seconds of summarizing is the difference between a conversation and two monologues.

Solution-focused brief therapy adds two questions worth stealing. Scaling questions turn vague feelings into something you can work with: “On a scale of 1 to 10, how supported do you feel right now?” Whatever number comes back, the follow-up is where the value lives: “What would move it from a 6 to a 7?” Not to 10. To 7. Small, concrete, actionable. And exception questions flip a problem on its head: “When was the last week this didn’t happen? What was different?” People who are stuck describe the problem fluently; asking about the exception forces them to describe the solution.

But the highest-leverage listening technique I ever adopted costs nothing and requires learning nothing: uninterrupted silence.

Everyone treats silence in a conversation as a bug, something to be patched immediately with another question. I’ve found the opposite. Silence, paradoxically, invites conversation. When I stopped rushing to fill pauses, people kept talking, and the second half of the answer was consistently more honest than the first. The first answer is the prepared one. The real one comes after the pause.

There’s research behind this. UX researchers at Nielsen Norman Group found that silence starts feeling uncomfortable after about four seconds, and their guideline for interviewers is to count to seven before speaking. Seconds five through seven are where the good material shows up. It works in user interviews for exactly the same reason it works in 1:1s: the discomfort of silence is doing the asking for you, more gently than any question could.

Count to seven. It will feel like an eternity. Do it anyway.

The reports the standard advice fails

Every piece of standard 1:1 advice, including some of the above, silently assumes a particular kind of person on the other side of the table: extroverted, neurotypical, comfortable thinking out loud, culturally at ease with telling authority figures what’s wrong. Plenty of excellent engineers are none of these things.

For introverts and internal processors, “ask open-ended questions and let them talk” can be genuinely unfair. You’re asking someone to produce thoughtful answers in real time about topics they didn’t know were coming. Send your questions in writing the day before, and watch the quality of the conversation transform. Treat silence as processing, not absence; an internal processor going quiet is working, not withholding. And offer a written channel for feedback in both directions. MIT Sloan’s research on neurodivergent employees found that specific, concrete, written feedback works better for many of them than the spontaneous verbal kind, which is worth knowing since the spontaneous verbal kind is the only kind most 1:1 advice acknowledges.

Culture is the other silent assumption. “Tell me what’s really bothering you” works fine when your report grew up professionally in a low-power-distance culture where pushing back on the boss is normal. Ask the same question to someone from a high-power-distance culture and you may get a polite non-answer, not because nothing is wrong but because openly criticizing anything within your manager’s domain can feel disrespectful or even risky. It’s not evasion; it’s manners. Ask about things rather than people (“What slows you down?” rather than “What’s wrong with the team?”), offer options instead of demanding critique, and pay attention to what’s conspicuously not being said. Directness is not a universal virtue; it’s a cultural setting.

When your best practice becomes a trap

Will Larson has a useful observation about management advice: almost every good practice, applied universally, becomes an anti-pattern. Your first 1:1s are where you’ll meet this first.

“Always let the report set the agenda” is excellent advice for a senior engineer with opinions and ambitions. Applied to a junior engineer three weeks into their career, it’s abandonment. They don’t yet know what’s safe to raise, what’s normal to struggle with, or what a 1:1 is even for. Handing them a blank agenda transfers your job onto the person least equipped to do it. Bring a menu: “We could talk about how the onboarding is landing, what’s confusing in the codebase, or anything else. What sounds most useful?”

“Never let it become a status meeting” fails differently. Some engineers build trust through the work first. Ask them about their career aspirations in the first meeting and you’ll get guarded, rehearsed answers; let them walk you through the gnarly ticket they just closed, and ten minutes later they’re telling you what’s actually bothering them. The status conversation was never the destination, but for some people it’s the only door in.

Even my beloved silence has a failure mode. For an internal processor, seven seconds of quiet is workspace. For an anxious report in their first meeting with a new boss, it can feel like a test they’re failing. The technique isn’t the point. Reading the person is the point, and every technique in this post, including the counting, is a default to start from, not a law to enforce.

Close the loop

Here’s the step that separates managers who run good 1:1s from managers who read articles about running good 1:1s: after a month, ask. “Are these meetings useful to you? What would make them better?” Then actually change the format based on the answer. Maybe weekly is too often for this person. Maybe they want the questions in advance. Maybe they’d rather walk than sit in a meeting room.

The first 1:1 doesn’t need to be perfect, because it isn’t a performance. It’s the opening move of a long game, and the feedback loop matters more than the opening. Mine went better than I feared, and if you walk in planning to listen more than you talk, yours probably will too. The anxiety you’re feeling right now isn’t a sign you’re unqualified. It’s a sign you understand the meeting matters.

If you’re at the start of the whole management journey, not just the first meeting, read Your First 90 Days as an Engineering Manager next.