In This Article
Communication skills for new managers: peer-to-boss scripts, 1:1 mechanics, feedback that actually changes behavior and the first 90 days that set the tone.
Three numbers from one study are worth reading before your first team meeting. 20% of first-time managers are rated as doing a poor job by their own direct reports. Another 26% felt unprepared from day one. Both numbers have the same cause. Roughly 58% received zero formal training when they got the role.
Those numbers come from the Center for Creative Leadership and Davidson College, and they describe a structural problem.
Companies promote their best individual contributors and hand them a new title without handing them a new skill set! So a capable, motivated person walks into a role they were never taught to do.
Sound familiar? It should also feel like a relief!
The First-Time Manager Trap
The most cited challenge in the CCL research was “adjusting to people management and displaying authority,” flagged by nearly 60% of new managers.
That’s a transition problem. And transitions have solutions we can learn!
The failure rate comes from a system that promotes people without preparing them.
The Job Is Different From the One You Were Promoted For
Think about what made us promotable. We delivered strong work, solved problems faster than our peers, had deep expertise!
Every one of those qualities is real! And every one becomes a liability if you carry it unchanged into management.
As an individual contributor, your output was the work. Your value was measured in deliverables, solutions and expertise. As a manager, that equation flips. Your team’s output is the work. Your value is now measured by what 5, 8, or 12 other people accomplish, and whether they’re growing.
This is a complete redefinition of the job. As one classic HBR study of new managers put it, new managers expect authority to flow from a title, then discover they’re “enmeshed in a web of relationships” where authority has to be earned.
The behaviors that made you excellent before undermine your team now:
- Jumping in to solve tells your team you don’t trust their judgment. Over time, you train people to wait for you.
- Working solo means your team never sees how decisions get made, which leaves them unable to make similar ones independently.
- Hoarding information creates a bottleneck. When you’re the only one with full context, every question routes through you.
Communication Is Now the Work
The single skill that bridges the old role and the new one is communication, and it’s one we can build. Clearer emails and tighter meetings matter, and the deeper kind matters more: setting direction without micromanaging, giving feedback that changes behavior and having the uncomfortable conversation BEFORE it becomes a crisis.
In your old role, you could go heads-down for a week and produce results. In your new role, a week of avoiding one hard conversation can quietly derail a project or let a small performance gap calcify into a problem that ends up on HR’s desk.
How much of that is really down to you? Gallup reports that managers account for the large majority of the variance in team engagement, though that figure comes from its internal analytics and has no peer-reviewed backing, so hold it loosely. The peer-reviewed version of the same question is narrower and harder to wave away: an analysis of manager data at a large firm found that better people-management skills measurably reduce employee attrition.1 What you say, and what you don’t say, matters more than it did.
The Peer-to-Boss Transition
Managing people who were your peers last week adds a layer of social complexity nobody warns you about. Three distinct dynamics appear:
The old friend. Your closest work friend is now a direct report. You have inside jokes, you’ve vented to each other about leadership, you know each other’s salaries. The friendship has to change, even if it survives. If you give that person more access or more leniency than the rest of the team, you’ll erode trust with everyone else faster than almost any other mistake.
The general peer. Former colleagues who respected you as a peer may quietly test whether your new title comes with any real authority. That’s normal. Authority in management is built through consistent behavior and follow-through on small commitments.
The colleague who wanted your role. This is the sharpest version: someone on your team applied for the same promotion, didn’t get it and now reports to you. Avoiding this conversation only makes it louder.
Why Week One Matters More Than You Think
The information that comes first weighs most in the impressions we form, and everything that comes later gets read through it.
In practice, your first conversations with each team member set the frame everything else gets viewed through. Week one is the data your team uses to decide what kind of manager you are!
That makes naming the awkwardness early one of the most valuable moves you have.
Silence sends these dynamics underground, where you can’t address them.
What to Actually Say
For the old-friend direct report:
“I want to be upfront about something. Our friendship matters to me, and I also want to make sure I’m being fair to everyone on the team. That might mean I’m more formal in some situations than I used to be, or that I can’t share things with you the way I did before. I’d rather name that now than have it feel weird later. How are you feeling about all of this?”
The goal is to acknowledge the change so neither of you has to handle it silently.
For the general team:
“I know this is a shift for all of us, and I’m not going to pretend it isn’t. I’m still figuring out what this role actually looks like, and I’d rather be honest about that than act like I have it figured out. What I do know is that I want to hear from you, especially when something isn’t working.”
Acknowledging uncertainty tends to make you more trustworthy in your team’s eyes!
For the colleague who wanted your role:
Have this one-on-one in the first week, before the awkwardness sets.
“I wanted to talk with you directly, because it would be strange not to. I know you were also considered for this role, and I imagine that’s complicated. I’m not going to pretend I know exactly how you’re feeling about it, but I want you to know that I see your work, I want you to succeed here, and I’m not going to let this get in the way of that—if you’re willing to give me the chance to show you.”
Then stop talking and give them space to respond. They may not say much, and that’s fine. What matters is that the conversation happened.
Running 1:1s and Delegating Without Micromanaging
The 1:1: It’s Their Meeting to Run
The most common mistake new managers make with one-on-ones is turning them into status updates. Manager asks what’s done and what’s blocked… Direct report answers. Everyone leaves feeling like they just sat through a meeting that could have been an email!
The core principle is that the meeting belongs to the direct report. Treat it as a reporting mechanism and engagement drops; let direct reports set the agenda and trust builds!
Format that works:
- Frequency: Weekly, 30 minutes. Reliability shows investment and catches small problems early.
- Who talks: Aim for the direct report to do roughly 70% of the talking. If you’re filling the silence, you’ve flipped the meeting.
- Agenda: Ask the direct report to bring one. Seed it with a standing structure if they don’t yet know how: what’s top of mind, what’s in the way, what they need from you.
Manager-centric vs. report-centric openers:
| Manager-centric | Report-centric |
|---|---|
| “Walk me through where you are on the project.” | “What’s most important for us to talk about today?” |
| “Did you finish the deck?” | “What’s draining your energy right now?” |
| “Here’s what I need from you this week.” | “Where am I getting in your way?” |
The left column is a briefing and the right column is a conversation! Both take 30 minutes; only one builds the kind of relationship where a direct report will tell you the real problem before it becomes a crisis.
A note on “Where am I in your way?”: it sounds counterintuitive, but it’s one of the most revealing questions you can ask. It brings up friction you can’t see from your position, and almost always produces something actionable.
Delegation Is a Dial With Settings
Most of us treat delegation as binary… Either do it yourself (because it’s faster) or hand it off and hope. Both extremes fail…
A more useful model is a dial, where the right setting depends on two task-specific factors. How skilled is this person at this particular task? And how motivated are they to take it on?
This is the core of the Hersey-Blanchard Situational Leadership framework. Direct empirical tests of it have produced mixed results, so treat it as a useful diagnostic and hold its prescriptions loosely. And verify your read by asking the person!
The four settings:
Setting 1, Direct. High skill needed, low current skill, high enthusiasm. New and eager. They want to succeed but don’t yet know how.
- “Here’s exactly how I’d approach this. Let’s walk through it together.”
Setting 2, Coach. Some skill, flagging motivation or confidence. They’ve started developing the skill but hit friction. Enthusiasm has dipped.
- “You’ve done the hard part. Here’s what I’d adjust going forward.”
Setting 3, Support. High skill, variable confidence. Genuinely capable but second-guessing themselves. They need permission more than instruction.
- “You know this better than I do. What’s your instinct?”
Setting 4, Delegate. High skill, high confidence and motivation. They own it. Clear outcome, defined constraints, then space.
- “Here’s the outcome I need and the deadline. How you get there is up to you.”
Then ask them. “How familiar are you with this kind of work?” and “How much guidance would be helpful?” get you the information you need without guessing.
Action Step: The next time you’re about to delegate, write down which of the four settings you’re choosing and why. Five minutes of diagnosis prevents weeks of micromanagement.
Feedback and the Conversations New Managers Avoid
New managers often give feedback too late, too vaguely, or not at all. They wait until a situation becomes undeniable. By then the conversation is ten times harder than it needed to be.
The antidote is structure.
SBI: Situation, Behavior, Impact
The underlying principle behind every good feedback framework is the same: feedback that focuses on specific, observable behavior outperforms feedback that targets personality or identity.
A landmark review of feedback studies covering more than 23,000 participants found that feedback interventions improve performance on average, but roughly a third of them actually decrease performance, almost always because the feedback pointed attention at the self, away from the task.
SBI, developed at the Center for Creative Leadership, is the most widely used model:
- Situation: Name the specific time and place. “In Tuesday’s client call…”
- Behavior: Describe the observable action without judgment. “…you cut in before the client finished explaining the timeline.”
- Impact: State the consequence. “…which means we may have missed details we need for the proposal.”
SBI is fast, portable and low-threat! It works best for in-the-moment developmental feedback, ideally within 24 to 48 hours of the event, before memory distorts the details.
Radical Candor: Care Personally, Challenge Directly
Kim Scott’s Radical Candor works as a diagnostic tool. Her 2×2 matrix asks managers to locate themselves on two axes: how much they care about the person, and how directly they challenge them.
The ideal is high on both! The failure modes have names: Ruinous Empathy (caring but not challenging, the most common trap for new managers), Obnoxious Aggression (challenging without caring), and Manipulative Insincerity (neither).
It’s common to end up in Ruinous Empathy: you soften feedback until it disappears, protect the relationship short-term and create a larger problem down the road. Use the matrix as a self-check BEFORE a conversation. Use SBI to deliver the actual feedback!
Vague forgiveness tells your team that deadlines are optional.
Three Conversations New Managers Avoid
Knowing a framework and using it under pressure are different skills! Here are the three conversations most commonly delayed.
The performance concern before it becomes a PIP.
The worst time to raise a performance issue is when HR requires it. By then, the employee is blindsided and the conversation is defensive on both sides.
Say: “I want to talk about something I’ve been noticing, and I want to do it now while we can work on it together. In the last three sprint reviews, your estimates have been off by more than 50%. That’s putting pressure on the team’s planning. I don’t think this is a motivation issue. What’s your read on it?”
Don’t say: “Everyone misses estimates sometimes, don’t worry about it,” and then document it three weeks later.
The missed-deadline conversation.
New managers often absorb missed deadlines quietly, telling themselves they’ll address it “next time.” Next time comes, and the pattern is now established.
Say: “The report was due Friday and came in Monday morning. That pushed the client debrief by a day. I need us to be aligned on what happened so we can prevent it. Was this a scope issue, a time estimate issue or something else I should know about?”
The burnout check-in.
When someone on the team is visibly depleted, our instinct is to give them space. Space without acknowledgment can feel like indifference.
Say: “I’ve noticed you seem stretched lately. Not as a performance conversation, but because I want to make sure you’re okay and that I’m not making things harder. What’s your workload actually looking like right now?”
Building Trust Quickly With a Team You Didn’t Hire
Your team is already forming an opinion of you… And they started before your first official meeting!
People make surprisingly accurate and durable assessments of each other from very short observations, what researchers call “thin slices.” We read each other fast, and those early reads stick.
Direct reports read the first conversation, the first decision, the first time you were asked something you didn’t know, and those early reads are hard to shift!
Four Things That Build Trust Fast
1. Keep small promises early, and visibly. Trust lives in the gap between what you say and what you do. “I’ll get you that answer by Thursday” followed by a Thursday answer builds more trust than a Monday all-hands about your leadership philosophy. Close the loop out loud. Don’t assume people noticed.
2. Name uncertainty out loud. When teams sense their manager is performing confidence, they stop sharing real problems, which is exactly when you need real information. Naming uncertainty tells your team you won’t hide bad news, which makes it safer for them to bring bad news to you. Try: “I don’t have a full picture of this yet” or “Here’s what I know, here’s what I don’t, and here’s how I’m going to find out.”
3. Ask before recommending. When a team member brings you a problem, your first instinct is to fix it. Resist. Ask “What have you already tried?” or “What do you think the right move is?” You’ll still share your perspective. But asking first, recommending second is the sequence that builds trust.
4. Share context generously! When we don’t know WHY a decision was made, we fill the gap with the least charitable explanation. A single sentence (“Leadership is prioritizing this because the Q3 deadline is tied to a customer commitment”) often prevents hours of hallway speculation.
Is This a Meeting?
Scheduling a meeting for something that could be a Slack message tells your team you don’t respect their time. Over-meeting is a common complaint about new managers, and it spikes in the first 90 days when new managers reach for meetings as a way to feel in control.
A simple default is that if the goal is to share status or information, it’s not a meeting. Reserve synchronous time for decisions that require real-time debate, problems that need collaborative thinking, or conversations where tone matters (feedback, conflict, anything emotionally loaded).
Before scheduling, ask: “What outcome do I need that can only happen in real time?” If you can’t answer that clearly, default to async.
Your First 90 Days: An Action Plan
Michael Watkins’s foundational work on leadership transitions in The First 90 Days makes the core argument: the actions you take in your first three months set the trajectory for everything that follows.
New managers who try to prove themselves by changing things fast tend to lose the room, and those who earn the right to lead first keep it.
Week 1: Listen before you lead.
Your only job this week is to learn! Schedule a 1:1 with every direct report. Skip the vision speech; ask questions and take notes. Run a brief listening tour: What’s working? What’s slowing people down? What does the team wish leadership understood?
Resist every impulse to fix, restructure, or announce changes. Even if you spot something obviously broken, write it down rather than act on it. Your observations are hypotheses for now!
The one non-negotiable is to have the peer-to-boss naming conversation before the week ends.
Weeks 2–4: Find one quick win. Name the team’s #1 pain.
By now you have enough information to act on something small. Look for a friction point the team has complained about that you can fix: a redundant meeting, an unclear approval process, a missing resource. Remove it.
Quick wins show that listening leads to action, which earns you the credibility to ask people to follow you on harder calls later.
At the same time, identify the team’s biggest pain point. Name it clearly and let the team know you see it; solving it can wait.
Month 2: Start making calls on team norms.
You’ve listened. You’ve built early trust. Now is the time to make your first deliberate decisions about how the team operates: communication norms, meeting cadence, how decisions get made, what “done” looks like.
These don’t need to be grand. “We’ll default to async for status updates and reserve our team meeting for blockers and decisions” is enough. State the norm, explain the reasoning, invite pushback. Norms set in month two stick.
This is also the window to have the harder feedback conversations. If there’s a performance concern you noticed in week one, month two is the outer edge of when to raise it.
Month 3: Deliver one meaningful result. Then ask for feedback on yourself.
By month three, the team should be able to point to something real that happened under your leadership: a project shipped, a process improved, a problem resolved.
Then do something that’s easy to skip: directly ask for feedback on your own communication. Ask your manager: “What’s one thing I could communicate more clearly?” Ask a trusted peer: “Have you noticed anything in how I’m running 1:1s or giving feedback that I should adjust?”
This move shows self-awareness, models the feedback culture you’ve been building, and brings up blind spots before they harden.
Ninety days is enough to become a trusted manager, and trust is the prerequisite for everything else.
Your Move
The transition from individual contributor to manager is a job change.
Seven things to carry into your first week:
- Treat the failure stats as a system problem. Most new managers get no training. Yours will be deliberate.
- Name the peer-to-boss awkwardness in week one. Have the conversation with the old friend, the team, and especially the person who wanted your role.
- Run weekly 30-minute 1:1s that belong to your direct report. They drive the agenda. You aim for 70% listening.
- Use the delegation dial. Diagnose skill and motivation on each specific task, then ask the person to confirm your read.
- Pick SBI and use it. Specific behavior, specific impact, soon!
- Build trust through small kept promises, named uncertainty and protected calendar time.
- Sequence your first 90 days deliberately. Listen in week one. Win small in weeks two through four. Set norms in month two. Deliver and ask for feedback in month three.
Communication is the work now, and it’s work we can get better at!
For more on the conversational mechanics behind these scripts, our Conversation guide goes deeper.
