If you do not delegate, you become a bottleneck and your team stalls. If you delegate badly, you create chaos, rework, and a quiet little graveyard of “yeah I’ll own it” promises.

This playbook covers the middle path: you delegate real work with real ownership, without hovering over every keystroke. You stay informed without turning into the human notification system.

The Foundation

Delegation is transferring ownership of an outcome, along with the authority needed to achieve it.

Delegation is not:

• Assigning tasks while keeping the decisions for yourself.

• Handing off work and disappearing until it blows up.

• Using delegation as a test to see who “can handle it.”

A useful mental model:

• Task assignment: “Please do this thing.”

• Delegation: “Please own this outcome. Here is what good looks like. Here are the boundaries. You can make decisions inside them.”

Choose the Right Level of Delegation

Most micromanagement comes from delegating at the wrong level, then managing it like a different level.

Use these levels as a menu. Start at one level and deliberately move up as trust and competence grow.

1. Do it exactly this way

   • Use when: compliance, safety, high risk, or a brand new skill.

   • Your job: provide a checklist, examples, and tight review.

2. Here is the outcome. Use this approach

   • Use when: the approach is constrained by architecture, standards, or dependencies.

   • Your job: explain the constraints and why they exist.

3. Here is the outcome. Propose a plan

   • Use when: you want ownership, but you need alignment before execution.

   • Your job: review the plan, ask questions, and approve or redirect.

4. Here is the outcome. You own the plan and execution

   • Use when: you trust the person to make good calls.

   • Your job: stay informed through checkpoints and signals.

5. You own the problem space

   • Use when: you want someone to lead a domain over time.

   • Your job: coach, remove obstacles, and align on strategy.

The Structure (A Delegation Script That Actually Works)

When you delegate, cover five things explicitly. If you skip these, you will “check in constantly” because the work is not actually defined.

1. Define the outcome

Describe the result in plain language.

• “We need a reliable deployment pipeline that runs in under 15 minutes, with clear failure signals.”

• “We need an incident update process that is consistent and calm.”

Avoid delegating a vague blob like “improve performance” unless you also define what “improve” means.

2. Define what good looks like

Give concrete success criteria.

• Performance or reliability target

• User impact

• Timeline

• Quality bar

• Rollout and monitoring expectations

If there is a hard edge, say it.

• “This must be done before the next release cut.”

• “No downtime.”

• “Security review is mandatory.”

3. Define constraints and boundaries

Constraints stop you from “correcting” every decision later.

• Architecture: “We are staying within this service boundary.”

• Process: “We need a design review before implementation.”

• Risk: “No schema changes without a rollback plan.”

• People: “You can pull in one other engineer for up to two days.”

Boundaries should create freedom, not a cage.

4. Agree on decision rights

This is the part many managers skip, and then they accidentally reclaim authority mid project.

Be explicit:

• “You decide the approach. I want to review the plan first.”

• “You can trade scope for time, as long as the reliability target stays.”

• “If the plan changes the roadmap, bring it to me before committing.”

A simple rule that works well:

• If it changes scope, timeline, or risk, we talk.

5. Set check-ins and signals

Check-ins are not surveillance. They are how you stop hovering.

Pick one:

• Milestone check-ins: meet when a milestone is reached.

• Calendar check-ins: 15 minutes weekly or biweekly.

• Written updates: a short weekly note in a shared doc.

Also define signals that do not require meetings:

• A ticket board with clear status

• A short decision log

• A demo at the end of each iteration

If you do not have signals, you will manufacture them by interrupting people.

Staying Informed Without Micromanaging

Micromanagement usually starts as anxiety. Anxiety usually starts as silence.

Ask questions that improve the work

Good:

• “What options did you consider?”

• “What is the riskiest assumption here?”

• “How will we know it is working?”

Not good:

• “Have you tried doing it this way?” (followed by a detailed plan)

• “I would just…” (followed by you doing the work verbally)

If you have a strong opinion, name it as such.

• “I have a strong preference for option B because it reduces operational risk. Convince me otherwise.”

Review at the right time

Do not review every intermediate artefact.

Instead, choose moments:

• Before the work begins: align on plan and success criteria.

• At the first meaningful output: confirm direction.

• Before rollout: check risk, monitoring, and rollback.

• After: do a short retro.

Protect the owner in the room

If you delegated ownership, treat that person as the owner publicly.

• In meetings, direct questions to the owner first.

• If someone tries to bypass them, redirect: “Please work with <name> on that.”

If you answer for them, you are quietly taking the work back.

When It’s Not Working

Sometimes delegation fails because the person needs support, not because they are incapable.

Diagnose the gap:

• Skills gap: they do not know how.

• Context gap: they do not know why or what matters.

• Capacity gap: they have too much other work.

• Confidence gap: they are avoiding decisions.

Adjust without seizing the work:

• Move down one level temporarily.

• Add clearer constraints.

• Add a short pairing session to get unstuck.

If you take the work back, you get short term relief and long term dependency. If you coach, you get slower progress now and faster progress later.

What to Avoid

Delegating tasks, not outcomes: You keep having to answer “what next?”

Delegating without authority: The owner cannot get decisions, time, or support.

“Just keep me posted”: You get no updates, then you panic and hover.

Correcting every choice: The owner stops thinking and starts waiting for approval.

Disappearing: The owner feels abandoned, decisions stall, and quality drops.

The Delegation Conversation (No Template Required)

You do not need a template. You need to cover the same ingredients every time, so delegation does not turn into hovering or surprise failure.

When you hand off work, make sure you explicitly align on:

• Outcome: the result the person owns, not a list of tasks.

• Why it matters: the context that helps them make good tradeoffs.

• Success criteria: what “good” looks like, including timeline and quality bar.

• Constraints and boundaries: what cannot change and what standards apply.

• Decision rights: what they can decide alone and what needs a check-in.

• Risks to watch: the landmines you want surfaced early.

• Check-ins and signals: how you will stay informed without interrupting constantly.

If you are clear on those, you can back off and still stay confident the work is moving in the right direction.

The Bottom Line

Delegation without micromanaging is not magic. It is clarity plus trust, backed by a visibility system that prevents surprises.

Define the outcome. Align on what good looks like. Grant real authority. Set lightweight check-ins. Then let them own it.

If it goes sideways, intervene at the decision points you agreed on, not by hovering over every step.

But they don’t have to be that way. Done well, performance reviews are a useful conversation about growth, impact, and what comes next. This playbook shows you how to deliver reviews that are honest, helpful, and skip the corporate nonsense.

Before You Start

Performance reviews don’t happen in a vacuum. If you’ve been giving regular feedback throughout the year, the review should feel like a summary, not a surprise.

If you haven’t been giving feedback regularly, fix that first. Performance reviews are not the time to bring up issues for the first time. If someone is hearing critical feedback for the first time in their annual review, you’ve failed as a manager.

Understand your company’s process. Most companies have a formal review structure with ratings, calibration meetings, and forms to fill out. You still have to do that part, but this playbook focuses on the actual conversation with the person.

Preparing the Review

Good reviews require preparation. Don’t wing it.

Gather evidence. Pull together concrete examples of work, impact, and behaviour over the review period. Look at:

• Projects they shipped and their outcomes

• Feedback from peers, stakeholders, and customers

• Your one-on-one notes

• Code reviews, design docs, or other artifacts

• Incidents they handled or problems they solved

Be specific. “You’re a great team player” is useless. “You unblocked the frontend team by refactoring the API ahead of schedule” is useful. Specificity makes feedback credible and actionable.

Identify themes. What patterns do you see? Where did they excel? Where did they struggle? What growth areas stand out? Themes help you structure the conversation and focus on what matters.

Write it down. Draft the review document before the meeting. It forces you to organize your thoughts and ensures you don’t forget important points. Share it with them ahead of time so they can process it before the conversation.

Structuring the Conversation

A good performance review conversation has three parts: impact, growth areas, and what’s next.

Part 1: Impact and Strengths (15-20 minutes)

Start with what went well. This isn’t about softening bad news. It’s about recognizing real contributions and reinforcing what you want to see more of.

Be specific about impact:

• “You led the migration to the new API, which reduced latency by 40% and unlocked the ability to scale to new markets.”

• “Your design for the search feature balanced user needs with technical constraints, and it shipped on time with minimal bugs.”

Highlight growth:

• “A year ago, you were uncomfortable leading technical discussions. Now you’re running architecture reviews and helping other engineers think through trade-offs.”

Give credit where it’s due. If they did great work, say so clearly. Don’t hedge or qualify it.

Part 2: Growth Areas and Constructive Feedback (15-20 minutes)

This is where most managers get squeamish. Don’t. Constructive feedback is a gift if you deliver it well.

Be direct. Don’t bury feedback in compliments or use vague language. Say what you mean.

• Bad: “Sometimes communication could be better.”

• Good: “There were three times this quarter when you committed to a deadline and didn’t communicate when you realized you’d miss it. That created problems for the team.”

Focus on behaviour and impact, not personality. You can’t change who someone is, but you can address what they do and how it affects others.

• Bad: “You’re not a team player.”

• Good: “When you skip team meetings without explanation, it slows down decision-making and makes people feel like their input doesn’t matter to you.”

Make it actionable. Tell them what success looks like.

• “For the next quarter, I want to see you communicate blockers as soon as you identify them, not when the deadline passes. That gives us options.”

Ask for their perspective. They might have context you’re missing. “What’s your take on this?” or “Is there something I’m not seeing?”

Part 3: What’s Next (10-15 minutes)

End with a forward-looking conversation about growth, goals, and priorities.

Clarify expectations for the next period:

• What are their key priorities?

• What does success look like?

• What support do they need from you?

Discuss career development:

• What skills do they want to build?

• What kind of work excites them?

• What’s the path to the next level, if that’s what they want?

Set clear action items. Both of you should leave with commitments. Write them down.

Handling Difficult Conversations

Not all reviews are easy. Here’s how to handle the hard ones.

If the review is negative: Don’t sugarcoat it, but be human. “This wasn’t the year either of us wanted. Here’s what needs to change, and here’s how I can help you get there.” Be clear about consequences if things don’t improve.

If they’re defensive: Listen. Let them process. Sometimes people need to vent before they can hear feedback. Then bring it back to specifics. “I hear you. Let’s look at the examples and talk through what happened.”

If they disagree with your assessment: Acknowledge their perspective, but don’t back down if you’re right. “I understand you see it differently. Here’s the data I’m working from. Let’s talk about where the gap is.”

If they cry: It happens. Hand them a tissue, pause, and give them space. Don’t minimize their feelings or rush through it. When they’re ready, continue.

What Not to Do

Don’t surprise them. If the review contains information they haven’t heard before, you’ve failed to give feedback in real time.

Don’t use the compliment sandwich. “You’re great, but here’s the bad news, but you’re still great!” is transparently manipulative. Just be direct.

Don’t compare them to others. “You’re not as strong as Sarah” is useless and demoralizing. Focus on their work and their growth.

Don’t make it about the rating. If your company uses ratings, explain it, but don’t let the conversation devolve into arguing about numbers. Focus on the actual feedback.

Don’t rush. Block at least an hour. If you’re trying to get through a review in 30 minutes, you’re doing it wrong.

Delivering the Rating

Most companies require you to assign a numerical rating or label: “Exceeds Expectations,” “Meets Expectations,” “Needs Improvement,” etc.

Explain the rating clearly. “Here’s the rating, and here’s why.” Tie it back to the examples and themes you discussed.

Be honest about calibration. If the rating was influenced by calibration or forced distribution curves, say so. “I went into calibration with a higher rating, but we had to adjust based on how you compare to peers at your level across the company. Here’s what that means.”

Don’t apologize for a fair rating. If the rating is accurate, own it. Apologizing undermines your credibility and makes them feel worse.

After the Meeting

Send a summary. Follow up with an email that captures the key points, action items, and next steps. This creates a record and ensures you’re aligned.

Check in regularly. Don’t let the review be the last time you talk about performance until next year. Reference it in one-on-ones and track progress on growth areas.

Follow through on your commitments. If you said you’d unblock something, get them access to a project, or advocate for a promotion, do it. Broken commitments destroy trust.

Making Reviews Less Awful

The best way to make performance reviews better is to make them less important. If you’re giving regular feedback, having real conversations in one-on-ones, and addressing issues as they come up, the formal review becomes a formality.

Give feedback continuously. Don’t save it for the review. Address things in the moment or in your next one-on-one.

Normalize talking about performance. Make it a regular part of your conversations, not something that only happens once a year.

Focus on growth, not judgment. The review should feel like a tool for development, not a report card.

The Bottom Line

Performance reviews don’t have to be corporate theatre. Be prepared, be specific, be honest, and focus on what matters: impact, growth, and what comes next. Skip the jargon, skip the compliment sandwich, and have a real conversation. Your team will respect you for it.

Underperformance sneaks up on you. Someone misses a deadline. Then another. The quality of their work slips. They seem checked out in meetings. You tell yourself it will get better. It doesn’t.

By the time you realize you have a problem, you’ve already lost weeks or months. The team is covering for them. You’re stressed. And the person who is underperforming probably knows something is wrong but hasn’t heard it from you directly.

This playbook walks you through addressing underperformance before it becomes a termination conversation.

Start Early

The biggest mistake managers make is waiting too long. You notice someone is struggling, you give them the benefit of the doubt, you wait to see if they turn it around on their own. They don’t. Now the problem is bigger and harder to fix.

Address underperformance as soon as you see a pattern. Not the first missed deadline. Not the first subpar pull request. But once you see it happening more than once, talk to them.

Early conversations are easier. They feel like coaching, not discipline. The person still has time to course correct without feeling like they’re on thin ice.

Get Clear on the Problem

Before you talk to them, get specific about what underperformance means. Not “they’re not meeting expectations.” What expectations? What does good performance look like for their role, and where are they falling short?

Write it down. Examples:

• Missing deadlines: Which ones? How often? What was the impact?

• Quality issues: What specific work had problems? What should it have looked like?

• Communication gaps: What meetings are they missing or unprepared for? What updates aren’t happening?

Vague feedback leads to vague improvement. If you can’t clearly articulate the problem, they can’t fix it.

Check for External Factors

Before you label it as a performance problem, rule out external factors.

Is the work actually achievable given the resources and time available? Are there blockers outside their control? Did priorities shift without them knowing? Is the team dynamic making it harder for them to succeed?

Sometimes what looks like underperformance is actually a system problem. If that’s the case, fix the system. If it’s not, move forward with the conversation.

Have the Conversation

Schedule a one-on-one. Do not surprise them with this in a regular check-in. Tell them ahead of time you need to discuss their performance. This gives them time to prepare and signals that it’s serious.

Be direct. Do not soften it so much that they miss the message. Start with something like: “I need to talk about some performance concerns I’ve been seeing. I want to make sure we address this now before it becomes a bigger issue.”

Then lay out the specifics. Use the examples you prepared. Be clear about what you’ve observed and why it’s a problem.

Listen to their side. There may be context you’re missing. Maybe they didn’t know the deadline was firm. Maybe they’ve been dealing with something personal. Maybe they thought someone else was handling part of the work. This doesn’t excuse the underperformance, but it helps you understand what’s going on.

Set Clear Expectations

Once you’ve talked through the problem, define what improvement looks like. Not “do better.” What does better mean?

Be specific:

• “I need you to meet sprint commitments. That means if you commit to three tickets, all three get done or I hear about blockers early enough to adjust.”

• “Code reviews need to happen within 24 hours. If you can’t hit that, let me know so we can figure out coverage.”

• “When you’re in sprint planning, I need you prepared with estimates and questions about unclear requirements.”

Also be clear about the timeline. How long do they have to show improvement? A month is reasonable for most situations. Less time feels punitive. More time drags it out.

Document Everything

Write down what you discussed. Send them a summary after the conversation. Include:

• The specific performance issues you raised

• What improvement looks like

• The timeline for improvement

• Any support or resources you’re providing

This isn’t about building a case to fire them. It’s about making sure you’re both aligned on what needs to change. People forget details. Having it in writing keeps everyone on the same page.

Provide Support

If someone is underperforming, figure out what support might help. This doesn’t mean doing their job for them. It means removing obstacles.

Do they need clearer requirements? More frequent check-ins? Pairing time with a senior engineer? Training on a tool they’re struggling with? Adjusted workload while they get back on track?

Offer what’s reasonable. If they need help, help them. But make it clear that support doesn’t change the expectations. They still need to improve.

Follow Up Regularly

Don’t have the conversation and then go silent for three weeks. Check in weekly. Not to micromanage, but to see how it’s going and course correct if needed.

If you see improvement, say so. Positive reinforcement matters. If you don’t see improvement, say that too. Don’t wait until the end of the timeline to tell them they’re still falling short.

Know When to Escalate

If you’ve had the conversation, provided support, checked in regularly, and the performance hasn’t improved, it’s time to escalate.

This is where you involve HR, start a formal performance improvement plan, or begin the process toward termination. That’s outside the scope of this playbook, but the point is: you gave them a fair shot. You were clear about the problem and the expectations. If they didn’t meet them, you did your job.

What Not to Do

Don’t avoid the conversation. It won’t get better on its own. It will get worse, and by the time you address it, you’ll have even less goodwill to work with.

Don’t make it personal. This is about performance, not personality. Stick to observable behaviours and outcomes.

Don’t assume bad intent. Most people who underperform aren’t doing it on purpose. They’re overwhelmed, unclear on expectations, dealing with something outside work, or genuinely don’t realize there’s a problem.

Don’t let it drag on forever. If you’ve given someone a reasonable timeline and support, and they’re not improving, don’t keep extending the deadline. It’s not fair to you, them, or the team.

Why This Matters

Underperformance doesn’t just affect the person who is struggling. It affects the whole team. Other engineers pick up the slack. Deadlines slip. Quality suffers. And if the team sees you ignoring the problem, they lose trust in you.

Addressing it early, clearly, and fairly is the kindest thing you can do for everyone involved. It gives the person a real chance to improve. And if they don’t, you’ve done everything you reasonably could.

This playbook walks you through the retention conversation: what to ask, what to offer, and when to let go.

The First Five Minutes

When someone tells you they’re considering other opportunities, your first job is to not panic. Take a breath. Thank them for telling you. Then listen.

“Thanks for sharing this with me. I want to understand what’s going on. Can you walk me through what you’re thinking?”

That’s it. Don’t jump to solutions. Don’t make promises. Don’t try to talk them out of it. Just listen.

What you’re listening for:

• Is this about compensation, growth, work, team dynamics, or something else?

• How far along are they? Casually browsing or actively interviewing?

• Is this fixable, or have they already made up their mind?

• What’s driving the timing? Is something urgent or has this been building?

Take notes. You’ll need them later.

Understanding What’s Really Happening

People rarely leave for just one reason. There’s usually a constellation of issues, and the thing they tell you first isn’t always the real problem.

If they lead with compensation: Money is rarely the only issue. It’s often a signal that they don’t feel valued. Ask: “What else is on your mind?” and “Do you feel like your contributions are recognized here?”

If they lead with growth: This usually means they’re bored, feel stuck, or don’t see a path forward. Ask: “What kind of work do you want to be doing?” and “What skills do you want to build?”

If they lead with work-life balance: Something is unsustainable. Ask: “What’s changed?” and “What would need to be different for this to work?”

If they lead with team or culture: This is often the hardest to fix. Ask: “Can you give me an example?” and “How long has this been an issue?”

If they’re vague: They might not trust you yet, or they haven’t fully figured it out themselves. Ask: “What would make you excited to stay?” and give them space to think.

What You Can (and Can’t) Fix

Be honest with yourself about what’s in your control.

You can probably fix:

• Boring work or lack of interesting projects

• Unclear growth path or skill development

• Workload or work-life balance issues

• Visibility and recognition

• Some team dynamics issues

You probably can’t fix:

• Compensation that’s significantly below market (you can try, but budget cycles are slow)

• Deep cultural misalignment

• Toxic relationships with senior leadership

• Personal life changes that require relocation or significant flexibility

• A team member who’s genuinely outgrown the role and there’s nowhere for them to go

You definitely can’t fix:

• Their partner got a job across the country

• They’re starting their own company

• They fundamentally want to do something different

If it’s fixable, say so. If it’s not, don’t pretend. False hope is worse than honesty.

Making Your Case (If You Have One)

If you think you can address their concerns, now’s the time to talk about it. But be specific. Vague promises don’t work.

Bad: “We really value you and want you to stay.”

Better: “I hear that you want to work on more architecture problems. We have the search rewrite starting in Q2, and I think you’d be perfect to lead the design. Can we talk about what that would look like?”

Bad: “There’s a lot of opportunity for growth here.”

Better: “You’ve been saying you want to move into a tech lead role. I think you’re ready. Here’s what that would involve, here’s the timeline, and here’s what we’d need to see from you to make it happen.”

Bad: “We can probably get you more money.”

Better: “I’m going to talk to finance about adjusting your compensation. I can’t make promises, but here’s the process and here’s the timeline. I’ll have an answer for you by end of week.”

Specificity shows you’re serious. Vague reassurances show you’re stalling.

What Not to Say

Some things will make the situation worse:

“I’m really surprised to hear this.” This tells them you haven’t been paying attention. If someone is unhappy enough to consider leaving, there were signs.

“What will it take to keep you?” This sounds like you’re bidding against an offer, and it puts all the power in their hands. It also suggests you could have addressed their concerns earlier but chose not to.

“You should have told me sooner.” Maybe. But now’s not the time. Focus on what you can do now, not what they should have done before.

“Let me see what I can do.” Too vague. Be specific about what you’ll do and when.

“You won’t get [benefit X] anywhere else.” This is defensive and dismissive. If they’re leaving, they’ve already thought about the tradeoffs.

“This is a bad time for the team.” It’s always a bad time. Don’t guilt them. It’s manipulative and it doesn’t work.

The Counteroffer

If you’re going to make a counteroffer, do it quickly and make it real.

A good counteroffer includes:

• Compensation adjustment (if that’s part of the issue)

• A specific change to their role, responsibilities, or growth path

• A clear timeline for when things will change

• Your personal commitment to making it happen

A bad counteroffer is:

• Money alone with no other changes

• Vague promises about “the future”

• Things you don’t have the authority to deliver

• Rushed or desperate

The reality of counteroffers: They often don’t work. If someone has already started interviewing, gotten an offer, and told you about it, they’ve mentally moved on. Counteroffers can buy you time, but they rarely solve the underlying problem.

If you make a counteroffer and they accept, follow through immediately. The first week after they decide to stay is critical. Show them they made the right choice.

When to Let Go

Sometimes the best thing you can do is make it easy for them to leave.

Signs they’re already gone:

• They have an offer and a start date

• The issues aren’t fixable or would take too long to fix

• They’ve been unhappy for a long time and this isn’t sudden

• They’re leaving for reasons that have nothing to do with work

• They seem relieved to be having this conversation

If that’s the case, say so: “It sounds like you’ve thought this through and you’re ready to move on. I’m going to miss working with you, but I get it. Let’s make the transition as smooth as possible.”

This does two things: it respects their decision, and it keeps the relationship intact. People remember how you handled their exit. Stay classy.

After the Conversation

Once the immediate conversation is over, you have work to do.

If they’re staying:

• Follow through on everything you promised, fast

• Check in frequently over the next few weeks

• Watch for signs that the situation isn’t improving

• Don’t hold it against them that they considered leaving

If they’re leaving:

• Work out a transition plan

• Be supportive publicly and privately

• Don’t badmouth them to the team

• Keep the door open for them to come back

Either way:

• Reflect on what you missed. Were there warning signs?

• Look at the rest of your team. Is anyone else feeling the same way?

• Fix systemic issues if they exist. One person leaving is a data point. Two is a pattern.

The Bigger Picture

Retention conversations are often a symptom of earlier failures. If you’re having a lot of them, something’s broken.

Good managers know:

• Who’s happy and who’s not

• What people care about and what they want to learn

• When someone is getting bored or frustrated

• How people feel about compensation and growth

If someone quitting is a complete surprise, you haven’t been paying attention.

The best retention strategy is to create an environment where people don’t want to leave. That means interesting work, clear growth, fair compensation, trust, and a team they like working with. Get those right, and you’ll have fewer of these conversations.

The Bottom Line

When someone tells you they’re thinking of leaving, listen first. Understand what’s really going on. Be honest about what you can fix. Make specific commitments if you have them. Let go gracefully if that’s the right move.

And then take a hard look at whether this could have been prevented.

How you deliver bad news matters. Do it well and you preserve trust. Do it poorly and you create resentment, confusion, and distrust that takes months to repair.

This playbook walks you through how to tell your team bad news with honesty and respect.

Before You Deliver the News

Make sure you understand it yourself. You can’t explain something you don’t fully grasp. If the decision came from above and you’re confused, ask questions until you understand the reasoning, even if you disagree with it.

Know what you can and can’t say. Some information might be confidential or not finalized. Be clear on the boundaries before you talk to the team. If you accidentally promise something you can’t deliver or share something you shouldn’t, it will make everything worse.

Decide on timing. Tell people as soon as you can, but not before you’re ready. Rushing into a conversation without preparation creates confusion. Waiting too long erodes trust when people find out through other channels.

Plan how you’ll communicate. Should it be in person, over video, or in writing? For big news that affects everyone, gather the team. For individual news, do it one-on-one. Don’t deliver bad news in Slack or email unless there’s no other option.

Delivering the Message

Start with the news. Don’t bury it in preamble or try to soften it with unrelated good news. Get to the point quickly.

• Bad: “Thanks everyone for joining. First, I want to say how great the team has been this quarter. We shipped some amazing work. On another note, I have some news about the budget...”

• Good: “Thanks for joining. I have some difficult news. Our project has been cancelled, effective immediately.”

Be direct and clear. Use plain language. Don’t hide behind corporate speak or euphemisms. People need to understand what’s happening.

• Bad: “We’re realigning our strategic priorities to focus on core business objectives, which means some initiatives will be deprioritized.”

• Good: “Leadership decided to cancel the redesign project. We’re shifting resources to the API work instead.”

Explain what you know. Give context about why this is happening, even if you disagree with the decision. People can handle hard truths better than vague reassurances.

• “The company is cutting costs across all departments. Every team is losing headcount or projects.”

• “The executives decided to pivot strategy based on the latest board meeting. This project no longer aligns with where they want to go.”

Be honest about what you don’t know. If you don’t have all the answers, say so. Don’t make things up or speculate.

• “I don’t know yet whether this affects our hiring plan. I’m meeting with my manager tomorrow to find out.”

• “I don’t have visibility into why this decision was made at the executive level. What I do know is that it’s final.”

Acknowledge the impact. Recognize how this affects people. Don’t minimize or dismiss their feelings.

• “I know this is frustrating. You’ve put months of work into this project, and it’s disappointing to see it cancelled.”

• “This is going to change your role significantly, and I understand that’s unsettling.”

What Comes Next

After delivering the news, tell people what happens next.

Be specific about immediate changes. What happens today, this week, this month? What stays the same? What’s different?

• “Starting today, we’re pausing all work on the redesign. You’ll transition to the API project over the next two weeks.”

• “Your role isn’t changing. This affects the roadmap, not the team structure.”

Clarify what’s uncertain. If things are still being figured out, say so and give a timeline for when you’ll know more.

• “I don’t have details on the new project yet. I’ll have more information by Friday, and we’ll talk through it then.”

Set expectations for communication. Let people know when and how you’ll update them.

• “I’ll send a follow-up email tomorrow with written details.”

• “We’ll have a team meeting on Wednesday to discuss next steps once I have more clarity.”

Handling Reactions

People react to bad news in different ways. Some will be angry. Some will be quiet. Some will ask a lot of questions. Your job is to hold space for those reactions without getting defensive.

Let people process. Don’t rush to fill silence or move on. Give people time to absorb the information and respond.

Answer questions honestly. If you don’t know, say so. If you can’t share something, explain why.

• “I don’t have that information yet, but I’ll find out and let you know.”

• “That’s confidential right now, so I can’t share details. I wish I could.”

Don’t sugarcoat or overpromise. Trying to make people feel better by downplaying the situation or promising things you can’t deliver backfires. Be real.

• Bad: “I’m sure this will all work out fine. These things always do.”

• Good: “This sucks, and I don’t blame you for being frustrated.”

Don’t badmouth leadership. Even if you disagree with the decision, don’t throw other people under the bus. You can be honest about your perspective without undermining the organization.

• Bad: “Yeah, I think this decision is idiotic too. Leadership has no idea what they’re doing.”

• Good: “I pushed back on this decision and shared your concerns, but ultimately it wasn’t my call to make.”

Validate emotions without wallowing. Acknowledge how people feel, then help them move forward.

• “I know this is disappointing. Let’s take a few minutes, and then we can talk about what comes next.”

Following Up

Send a written summary. After the conversation, send an email or message that recaps what you said. People often miss details when they’re processing bad news, and having it in writing helps.

Check in with individuals. Some people won’t speak up in a group setting. Follow up one-on-one to see how they’re doing and answer any additional questions.

Keep your commitments. If you said you’d find out more information or provide an update by a certain time, do it. Trust is fragile when people are already upset.

Be present. Don’t disappear after delivering bad news. Be available for questions, concerns, and venting. Visibility matters.

What Not to Do

Don’t let people hear it from someone else. If the news affects your team, they should hear it from you first, not from Slack, email, or the rumour mill.

Don’t make it about you. Even if you’re also upset or affected, this isn’t the time to center your own feelings. You can process with your peers or your manager later.

• Bad: “I’m so stressed about this. I don’t know how I’m going to handle everything now.”

• Good: “I know this is hard. Let’s focus on what we can control.”

Don’t lie or mislead. Even if you think it will make things easier in the short term, it destroys trust when the truth comes out.

Don’t wait too long. The longer you delay, the more anxiety builds. Deliver bad news as soon as you’re able to do it well.

Don’t dump and disappear. Dropping bad news and then going offline or into back-to-back meetings signals that you don’t care. Make time to be present afterward.

When the News Affects You Too

Sometimes the bad news hits you just as hard as it hits your team. You still have to show up as a leader, even when you’re struggling.

Be honest about your limitations. You don’t have to pretend everything is fine, but keep the focus on the team.

• “I’m processing this too, and it’s not easy. But I’m here, and we’ll figure it out together.”

Process your own feelings separately. Talk to your manager, your peers, or people outside of work. Don’t vent to your team about how hard this is for you.

Ask for help if you need it. If you’re overwhelmed, loop in your manager or HR. You don’t have to carry everything alone.

Rebuilding Afterward

After delivering bad news, your job is to help the team move forward.

Focus on what you can control. You can’t change the decision, but you can help people understand what happens next and what they can influence.

Reinforce stability where it exists. If certain things aren’t changing, make that clear. People need to know what’s solid ground.

• “Your roles aren’t changing. The team structure isn’t changing. The roadmap is shifting, but we’re still intact.”

Give people meaningful work. After bad news, people need to feel useful and engaged. Help them focus on work that matters.

Follow through on commitments. If you said you’d advocate for them, get them more information, or make a change, do it. Rebuilding trust requires consistency.

The Bottom Line

Bad news is part of management. You can’t avoid it, but you can deliver it with honesty, clarity, and respect. Don’t hide, don’t sugarcoat, and don’t disappear. Be direct, be present, and be human. That’s what people need from you when things get hard.

The first week sets the tone for everything that follows. Get it right and you build trust, establish credibility, and create momentum. Get it wrong and you spend months digging yourself out.

This playbook walks you through what to focus on in your first week.

Before Your First Day

If you have any lead time before you officially start, use it to prepare.

Talk to your manager. Understand their expectations for your first 30, 60, and 90 days. Ask about team dynamics, current priorities, and any immediate challenges. Find out what success looks like.

Review team documentation. Get access to whatever you can: team goals, project plans, architecture docs, recent retrospectives. You don’t need to master everything, but you need context.

Understand the org chart. Who reports to you? Who are your peers? Who are your stakeholders? Map it out.

Day One: Show Up and Listen

Your first day is not about making changes or proving yourself. It’s about showing up as a human being who is genuinely interested in the team.

Meet your team individually. Schedule 30-minute introductory one-on-ones with each person. Keep them casual. Your goal is to start building relationships, not to assess performance or solve problems.

Ask good questions:

• What are you working on right now?

• What do you enjoy most about your work?

• What’s frustrating or slowing you down?

• What should I know about the team?

• What do you need from a manager?

Listen more than you talk. Take notes. Don’t make promises you can’t keep. If someone brings up a problem, acknowledge it and say you’ll follow up once you understand the situation better.

Don’t try to fix things yet. You don’t have enough context. Resist the urge to jump in with solutions or changes. Just listen and learn.

The First Few Days: Understand the Landscape

Once you’ve met everyone, start mapping out the bigger picture.

Understand current work. What projects are in flight? What’s blocked? What’s coming next? Where are the dependencies? You should be able to explain what your team is doing and why.

Identify stakeholders. Who depends on your team? Who does your team depend on? Schedule introductory meetings with key stakeholders to understand their expectations and concerns.

Attend team meetings. Observe how the team works together. Who speaks up? Who stays quiet? How are decisions made? What’s the energy like? Don’t change the format yet. Just watch.

Review recent retrospectives. If your team does retros, read the last few. Look for patterns in what’s working and what’s not. This gives you insight into recurring issues and team culture.

Talk to your peers. Other engineering managers or team leads can give you valuable context about how things work, where the landmines are, and what resources are available.

Building Trust

Trust is your most important asset as a manager. Here’s how to start building it in your first week.

Be present. Show up to meetings, be available for questions, and make time for conversations. If you’re remote, be visible in team channels.

Follow through. If you say you’ll do something, do it. If you can’t, explain why and reset expectations. Reliability matters more than anything else.

Be honest about what you don’t know. You’re new. No one expects you to have all the answers. Saying “I don’t know, but I’ll find out” is infinitely better than bullshitting or making something up.

Respect existing relationships. If you’re managing people who used to be your peers, acknowledge the transition. “I know this might feel weird. I want to make sure you still feel comfortable being direct with me.” Then prove it by how you respond when they are.

Don’t throw anyone under the bus. Even if you inherit a mess, resist the urge to blame your predecessor or criticize past decisions. It makes you look petty and erodes trust.

What Not to Do

Don’t make big changes. You don’t understand the system yet. Changes made without context usually backfire. Give yourself at least 30 days to observe before making structural changes.

Don’t try to prove yourself. You don’t need to demonstrate that you deserve the role by immediately solving problems or showing off your technical skills. Your job is different now. Focus on learning, not performing.

Don’t badmouth the previous manager. Even if the team brings up issues with how things were done before, don’t pile on. Acknowledge their concerns, say you want to understand the situation, and focus on the future.

Don’t overpromise. It’s tempting to reassure people that you’ll fix everything. Don’t. Be honest about what you can and can’t control, and make commitments only when you understand what’s involved.

Don’t disappear into meetings. New managers often get overwhelmed by calendar invites. Block time to actually talk to your team and process what you’re learning. If you’re never available, people will stop trying to reach you.

Setting Up Your Systems

Use your first week to establish the basic infrastructure you’ll need.

Schedule recurring one-on-ones. Get them on the calendar now. Weekly or biweekly, depending on team size. Consistency matters more than length.

Set up a team meeting cadence. If you don’t already have regular team meetings, set them up. Keep them focused: updates, blockers, decisions. Don’t let them become status reports.

Create a note-taking system. Whether it’s Notion, Google Docs, or a notebook, you need a place to track commitments, record observations, and capture feedback. Start building this habit immediately.

Clarify your availability. Let people know how to reach you and when. Are you available for Slack interruptions? Do they need to schedule time? Set expectations so people aren’t guessing.

By the End of Week One

You should have accomplished these things:

• Met individually with everyone on your team

• Mapped out current work and priorities

• Identified key stakeholders and started building relationships

• Understood immediate blockers or challenges

• Set up recurring one-on-ones

• Established basic availability and communication norms

• Built a system for tracking commitments and notes

You should not have:

• Made major organizational or process changes

• Given performance feedback or performance reviews

• Reorganized the team or changed roles

• Made commitments you can’t keep

What Comes Next

Your first week is about observation and relationship building. Your first month is about understanding the system. Your first 90 days is when you start making changes based on what you’ve learned.

Don’t rush it. A solid foundation built in the first week makes everything else easier.

In week two, start going deeper on technical context, team dynamics, and stakeholder relationships. Begin forming hypotheses about what needs to change, but don’t act on them yet.

In your first month, schedule skip-level meetings if you manage managers, start giving feedback, and begin identifying quick wins that demonstrate progress without disrupting the system.

In your first 90 days, you’ll have earned enough trust and gathered enough context to make meaningful changes. That’s when you implement new processes, shift priorities, or address structural issues.

The Bottom Line

Your first week as an engineering manager is not about proving you deserve the job. It’s about showing up as a human, listening to your team, understanding the landscape, and building trust.

Do that well and everything else gets easier.

This playbook gives you a straightforward framework that works.

The Foundation

One-on-ones are their meeting, not yours. Your job is to show up, listen, and help them solve problems. If you spend most of the time talking, you’re doing it wrong.

Frequency and duration: 30 minutes weekly, or 45-60 minutes biweekly. Pick one and stick to it. Consistency matters more than length.

Scheduling: Put them on the calendar at the same time every week or every other week. Recurring meetings reduce the mental overhead for both of you. If you need to move one, reschedule immediately. Don’t let them slip.

Location: Default to in-person or video if you’re remote. Walk-and-talks work for some people. Whatever you choose, make it predictable.

The Structure

A simple three-part structure keeps the conversation focused and useful:

Part 1: Their Agenda (20 minutes)

Start here every time. Ask: “What do you want to talk about today?”

This is where they bring up blockers, questions, concerns, ideas, or anything else on their mind. Your job is to listen, ask questions, and help them think through problems.

Common topics:

• Blockers on current work

• Questions about priorities or decisions

• Interpersonal issues with teammates

• Career development and growth

• Feedback on how things are going

• Ideas for improvements

Your role: Ask clarifying questions. Help them think through options. Remove obstacles. Provide context they might be missing. Take notes on action items.

Part 2: Your Topics (5-10 minutes)

This is where you bring up things you need to discuss:

• Feedback on their work (positive and constructive)

• Context on team or company changes

• Upcoming projects or priorities

• Performance or behaviour concerns

Keep it brief. If you have a lot to discuss, consider whether it needs a separate conversation.

Part 3: Career and Growth (5 minutes)

Reserve the last few minutes for longer-term topics:

• What are they learning?

• What do they want to work on next?

• What skills are they trying to build?

• What projects excite them?

You don’t need to solve everything in one meeting. Plant seeds, ask questions, and follow up over time.

What to Ask

Good questions unlock good conversations. Here are some that work:

For blockers and problems:

• What’s slowing you down right now?

• What would make this easier?

• Who else should be involved in this?

• What do you need from me?

For feedback and reflection:

• How do you feel about how that project went?

• What would you do differently next time?

• What went better than expected?

For team dynamics:

• How are things going with the team?

• Is there anything I should know about?

• Who should you be working with more closely?

For growth:

• What do you want to get better at?

• What kind of work energizes you?

• What are you curious about?

Avoid yes/no questions. Open-ended questions lead to real conversations.

What to Avoid

Don’t use one-on-ones for status updates. You should already know what they’re working on. If you don’t, fix your communication systems. Use this time for things that actually need conversation.

Don’t skip them. Cancelling sends the message that they’re not a priority. If you absolutely must move a meeting, reschedule it immediately.

Don’t fill silence. Pauses are okay. Give them time to think. Resist the urge to jump in with your own stories or solutions.

Don’t make it all about performance. If the only time you talk about their work is to give feedback or discuss problems, one-on-ones become stressful. Balance is important.

Taking Notes

Keep notes for yourself. They help you remember commitments, track patterns, and prepare for future conversations.

What to capture:

• Action items (for you and for them)

• Key topics discussed

• Career interests and development goals

• Feedback you gave or received

• Patterns over time (recurring blockers, themes, concerns)

Where to keep them: Wherever works for you. Notion, Google Docs, a notebook. Just make sure you can reference them later.

Don’t share your notes with HR or leadership without telling the person first. One-on-ones need to feel like a safe space.

Building Trust

Trust doesn’t happen in one meeting. It builds over time when you consistently show up, listen, and follow through.

Do what you say you’ll do. If you commit to unblocking something, following up with someone, or getting them an answer, do it. Nothing erodes trust faster than forgotten commitments.

Be honest. If you don’t know something, say so. If you can’t share something, explain why. Don’t bullshit them.

Ask for feedback. Make it a regular part of the conversation. “What should I be doing differently?” or “What’s one thing I could do to make your work easier?” And then actually listen and act on it.

Keep their confidence. If they share something sensitive, don’t repeat it unless you have their permission or it’s a serious issue that requires escalation. If you need to escalate, tell them first.

When It’s Not Working

Sometimes one-on-ones feel awkward or unproductive. That’s normal, especially early on. Here’s what to do:

If they have nothing to talk about: Ask better questions. Dig into how things are going, what’s on their mind, or what they’re learning. If it keeps happening, check whether they feel safe bringing things up.

If it feels like a status update: Redirect. “I already know what you’re working on. Let’s talk about how it’s going, or what you need from me.”

If they seem disengaged: Ask directly. “These don’t seem very useful to you. What would make them better?” Sometimes the format, time, or frequency needs to change.

If you’re always running out of time: Extend the meeting or shift to weekly instead of biweekly. Some people need more time.

Getting Started

If you’re starting one-on-ones with someone new, set expectations in the first meeting:

“This is your time. I want to hear what’s on your mind, help remove blockers, and make sure you have what you need. We’ll spend most of the time on your topics, and I’ll bring up anything I need to discuss. We’ll also save a few minutes for career and growth. How does that sound?”

Then ask: “What’s on your mind today?”

That’s it. The first one might feel a bit awkward. The second will be easier. By the third or fourth, you’ll both settle into a rhythm.

The Bottom Line

One-on-ones don’t need to be complicated. Show up consistently, listen more than you talk, follow through on commitments, and make it about them, not you. Do that, and you’ll build the kind of trust and communication that makes everything else easier.