First-time manager: what conversations will you want to avoid, and how do you have them?

Nobody tells you this when you get promoted, but the job changes in about a week. The work you were good at is still on your plate. On top of it sit a handful of conversations that didn't exist last month, and every one of them feels like it could go wrong.

So you put them off. Everyone does. The trouble is that each of these conversations is cheapest the first time it comes up, and gets more expensive every week after. Here are the five most first-time managers avoid, with words to start each one.

The five at a glance

Conversation	Why you'll avoid it	What waiting costs	The first sentence
Managing a former peer or friend	It feels like admitting the friendship changed	You both act around it, and every later conversation carries the weirdness	"This is a bit strange for both of us. Can we talk about it?"
The first missed expectation	It's "only once" and you don't want to seem harsh	The team learns the expectation was optional	"The deck was due Thursday. What happened?"
Saying no or delegating to someone more experienced	You feel you haven't earned the right	They start making the calls, and you become a messenger	"I want your view first. Then I'll make the call."
Specific praise	It feels awkward and a little performative	Good work goes unseen, and your words lose weight	"The way you handled the client on Tuesday saved us a hard week."
Raising something with your own manager	You want to look like you have it handled	A small concern turns into a grievance	"I'm noticing something on the project. Can I flag it before it grows?"

1. Managing a former peer or friend

Why it's tempting to avoid. Last month you were complaining about the roadmap together over lunch. Now you're the one who has to explain the roadmap. Saying anything about the change feels like making it official, so you don't, and hope it sorts itself out.

What it costs to wait. It rarely sorts itself out. You start editing yourself around them. They're not sure whether the lunch conversations are still safe. The first time you need to give them feedback, you're doing two hard things at once: the feedback, and the relationship talk you skipped.

The script. Have it in the first week, ideally one to one and away from the usual desk.

"This is a bit strange for both of us, and I'd rather say that than pretend it isn't. I want to keep what's good about how we work together. Some things will be different, like I'll have to give you feedback sometimes, and I'll want you to tell me when I'm getting it wrong. What would you want me to know?"

Then do the boring part: be consistent. Treat them exactly the way you treat everyone else, in both directions. No extra favors and no extra distance.

2. The first missed expectation

Why it's tempting to avoid. The deck came in Monday instead of Thursday. It's the first time. They're probably busy. You don't want your first piece of feedback as a manager to be about a deadline, so you let it go.

What it costs to wait. The first miss is the lightest moment you will ever get to set the expectation. Let it pass and the second miss is now a pattern you've quietly accepted. By the third, you're annoyed, and the conversation you have will carry three weeks of frustration the person never heard about. It also teaches everyone watching that the deadline was a suggestion.

The script. Within a day. One sentence, one question.

"The deck was due Thursday and I didn't see it until Monday. What happened?"

That's the whole thing. Listen to the answer. If it's reasonable, agree on what happens next time. This light, early version is what the Accountability Dial™ calls a Mention, and most issues end there. If it keeps happening, here's how to get more direct, one step at a time.

3. Saying no or delegating to someone more experienced

Why it's tempting to avoid. Someone on your team has been doing this work for twelve years. You've been a manager for six weeks. Handing them a project feels presumptuous. Saying no to their proposal feels absurd.

What it costs to wait. If you never make a call, they will, and soon you're relaying their decisions upward instead of making your own. That isn't respect. It leaves them without a manager and you without a job. Experienced people usually find hesitation more frustrating than a clear decision they disagree with.

The script. Separate asking for their view from making the decision, and say which one you're doing.

"You've done more of these migrations than I have, so I want your read before I decide. What would you do, and what am I not seeing?"

And when the answer is no:

"I've thought about it, and we're not going to take that on this quarter. The reason is the launch in March. I know you see it differently, and I'd rather tell you straight than leave it hanging."

Delegating sounds like this:

"I'd like you to own the vendor review. You'll make the calls on scope. I need a short update every Friday so I can answer questions from above."

4. Giving praise that's specific instead of "great job"

Why it's tempting to avoid. It doesn't feel like a hard conversation, so it never feels urgent. When you do say something, "great job" comes out because anything longer feels awkward, like you're performing being a manager.

What it costs to wait. People can't repeat what they don't know they did well. "Great job" is pleasant and forgettable. Worse, if the only specific things you ever say are corrections, people learn that your detailed attention means trouble. Specific praise is what makes your later feedback believable.

The script. What they did, and what it made possible.

"The way you walked the client through the delay on Tuesday, before they had to ask, kept them from escalating. That saved me a very hard call. Thank you."

Send it the same day, in a sentence or two. A Slack message is fine. Praise is also the safest place to practice being direct, because the stakes are low and the person is glad to hear it.

5. Raising something with your own manager

Why it's tempting to avoid. You just got the job. You want to look like you have it handled. Bringing up a problem, especially one that involves your manager's own decisions, feels like admitting you don't.

What it costs to wait. The priorities keep shifting, the team keeps stalling, and you keep absorbing it. Eventually you raise it when you're fed up, and the same point that would have sounded sharp and observant in week two sounds like a complaint in week ten.

The script. The observation, why it matters, and a question.

"I want to flag something early. The onboarding project has changed priority three times this month, and the team is starting to wait instead of build. Can we talk about what's fixed and what's still moving?"

Managers almost always prefer hearing it early. It gives them a chance to fix something while it's still small.

The pattern underneath all five

Every one of these is avoided for the same reason: the relationship is new, and you're afraid of damaging it. And every one is easiest at the first moment it appears. The fix is the same each time. Make the first version shorter than feels natural, say it sooner than feels comfortable, and end with a question you actually want answered. If you're not sure why a particular one is so hard for you, this guide on why managers avoid hard conversations is worth ten minutes.

Where Ren helps

Ren is an AI app in Slack and Microsoft Teams for the conversations between people at work. It notices when one of these is going unsaid, helps you judge how serious it really is, drafts the first sentence in your own voice, and asks what's making it hard for you. What you tell Ren stays private, and it's never shared with your manager or HR. You can try it and start with whichever of the five you've been putting off.

---

Related: How to give feedback to an employee · How to have a difficult conversation at work · How to prepare for a 1-on-1 meeting · What is the Accountability Dial?