First-time manager mistakes that feedback can fix

Most first-time-manager advice splits cleanly into two unhelpful categories. The first is the motivational variety — "trust your team, listen actively, lead with vulnerability" — true in the abstract, useless in the moment. The second is the comprehensive checklist with forty-seven items, organized by quarter, color-coded by priority, impossible to actually act on. This list is shorter, and narrower on purpose. Eight specific mistakes that feedback — properly asked for and properly received — surfaces faster than any other intervention. Plus the framework for telling which mistakes feedback can fix and which need a different lever.

What feedback can and can't fix

Not every first-time-manager mistake is a feedback problem. Some need training. Some need time. Some need a coach. Some need a different role entirely. Before you spend a feedback round on a specific mistake, run it through two filters.

Visibility filter. Is the mistake visible to people around you in specific, recallable moments? Avoiding hard conversations is visible — your team notices the topics that keep not getting raised. Imposter syndrome mostly isn't — it's an internal experience that shows up in your behavior only intermittently and ambiguously. Visible mistakes are feedback-tractable. Invisible ones are coach-tractable.

Gap filter. Is the lever the gap between how you see the mistake and how others see it? Some mistakes you already know about — you just don't know how to fix them. For those, feedback adds noise without adding signal; what you need is technique, not visibility. The mistakes worth running through feedback are the ones where what you don't yet see is the obstacle. The eight below are all gap-mistakes: the people around you can see them, you mostly can't, and once the gap closes the path forward becomes obvious.

If a mistake passes both filters — visible to others, gap is the lever — feedback is the fastest fix you have. The eight below pass both.

Eight first-time manager mistakes that feedback specifically surfaces

1. Doing the work yourself when you should be coaching someone to do it

You got promoted because you were good at the individual contributor work. The reflex that made you valuable as an IC — "I'll just take this, it's faster" — is now exactly the wrong reflex. The mistake isn't visible from inside your own head, because from in there it looks like being helpful. From outside, it looks like not trusting the team.

What feedback surfaces it: "You redo my work without telling me." "I don't know which parts of the project are mine to own." "I've stopped suggesting things because you'll just do them." The fix isn't delegate more. It's notice when you're about to absorb something, pause for ten seconds, and ask whether absorbing it is making you faster this week and slower next year. Usually it's both.

2. Solving the problem when the report came to think out loud

A direct report walks into your 1:1 and starts describing a tricky situation. Within ninety seconds, you've offered a solution. They thank you, you feel useful, the meeting moves on. From inside your head, you helped. From their head, you cut off the actual conversation they came for — the slow one, the one where they were going to figure out the answer themselves if you'd waited.

What feedback surfaces it: "I wanted to talk something through; you answered in thirty seconds." "I leave 1:1s feeling more managed than developed." The fix is asking "do you want me to react, or do you want me to just listen?" at the start of the conversation. Most reports want the second more often than you assume.

3. Mistaking your discomfort with conflict for the team's discomfort

Most first-time managers avoid certain conversations and quietly believe the team is grateful — "nobody wants to litigate this, we're all busy." What's actually happening, often, is that the team has been waiting for you to raise the topic, and concluding from your silence that you don't think it's important.

What feedback surfaces it: "There's a conversation about X that we keep not having." "You changed the subject when Y came up in standup." "I think we're avoiding the elephant." The fix is to ask once a quarter, in a 1:1, "is there a conversation you've been waiting for me to raise?" The answers will be specific. The discomfort was always yours.

4. Treating 1:1s as status updates instead of development conversations

The temptation, when you're a new manager juggling six new responsibilities, is to use 1:1s for the thing that feels most urgent: making sure work is on track. So your 1:1s become status meetings — useful for you, mediocre for the report. They get the same coverage in any standup. What they don't get is the conversation only you can have with them: about their work, their growth, the parts of the role they're stuck on, the parts they're underused on.

What feedback surfaces it: ask each report "what would make our 1:1s more useful for you?" and listen for specifics. "More about my work, less about the project status" is the most common answer. The fix is putting status into a different channel and reclaiming the hour.

5. Giving feedback only when something's wrong

If you came up as an IC in a culture where you only heard from your manager when there was a problem, you'll reproduce that pattern without noticing. Your reports will work for weeks not knowing whether anything they're doing is landing — because nothing has landed badly enough for you to mention. The signal-to-noise ratio of your feedback collapses; every comment becomes high-stakes.

What feedback surfaces it: "I rarely know if I'm doing well, only when I'm not." "You only weigh in when you're worried." The fix is the cheapest one on this list: name something specific your report did well, in writing, once a week, for a month. After a month, check whether the relationship feels different. It will.

6. Performing manager instead of acting like one

Almost every first-time manager goes through a phase of imitating a previous boss — using their phrases, mirroring their meeting style, copying the gravitas they remember being impressed by. From inside, it feels like trying to look the part. From outside, it reads as inauthentic, and the authenticity gap shows up in small ways: the voice you use in meetings doesn't match the voice you use in 1:1s, your written feedback uses words you don't use in conversation, your reports start to wonder which version of you to trust. INSEAD's Herminia Ibarra named exactly this dynamic — the authenticity paradox — in her work on leadership transitions: treating "be yourself" as advice traps you in a previous version of yourself, when the role is precisely asking you to grow into someone you haven't yet been.

What feedback surfaces it: "You sound different in big meetings than in 1:1s." "Some of your written feedback doesn't sound like you." "I can tell when you're saying what you actually think versus what you think a manager would say." The fix isn't be yourself — that's another piece of useless abstract advice. It's notice the moments where you switch voices, and ask why. Usually the manager-voice is covering for an uncertainty the human-voice would have to address directly.

7. Over-committing upward, then squeezing the team to deliver

You say yes to your boss because that's the move that made you visible as an IC. As a manager, the same move means your team takes the hit when scope catches up with reality — and your team notices, even when you think you've shielded them. The cost lands later: trust erodes, and the next time you ask them to push, you have less goodwill to draw on than you think.

What feedback surfaces it: "Every quarter we're scrambling at the end." "You don't push back upward when you should." "I think you over-promised on this, and we paid for it." The fix is harder than the others on this list, because it requires you to push back on your boss — but the feedback round at least makes the pattern visible to you. Most first-time managers don't see it as a pattern until someone names it.

8. Treating your team the way you wanted to be treated

This one is the most universal and the least obvious. You assume that the autonomy, recognition, structure, and feedback cadence that worked for you as an IC are the ones that work for your reports. They aren't, mostly. Some reports want more direction than you wanted. Some want less recognition than you'd want. Some want clearer expectations; some want more room to define their own. The mistake is using your own preferences as a default and not noticing that defaults need to be calibrated per person.

What feedback surfaces it: "You give me autonomy I don't actually want; I'd like more direction." "You over-explain; I'd rather you trusted me to figure it out." The fix is to ask each report directly, once: "what kind of management style works best for you, and where am I getting it wrong?" The answers are usually surprising. They're also usually actionable within a week.

How to actually run feedback that catches these

Knowing the eight mistakes doesn't help if your feedback round doesn't surface them. Three things make the difference.

Ask behavioral questions, not trait questions. "Am I a micromanager?" gets you nothing. "When did I last redo your work without telling you?" gets you a moment. The questions in this article's sibling — 50+ 360 feedback questions that actually surface useful answers — are calibrated for this. Pull from there for your first round.

Self-assess first. Write your own answers to the same questions before you send them. The interesting signal isn't what others think of you; it's the gap between your view and theirs. (More on why the order matters: Why self-assessment comes before peer feedback.)

Send to two or three people, not the whole team. A first-time manager running a six-respondent 360 in their first quarter is going to read the synthesis and then misread half of it because the volume is too much. Two or three answers, read carefully, beat six answers skimmed. You can always run another round in three months.

What to do next

If you're reading this in your first six months as a manager, pick the two mistakes from the eight above that match the loudest voice in your head — usually one feels embarrassingly familiar and one feels "I'd never do that, but actually...". Those two are the ones to test against feedback first.

For each, pick one or two questions from the 360 feedback question list that target the behavior. Self-assess first. Send to one or two people whose honesty you've already tested in smaller settings. Compare. The gap is the work.

If you want a structured way to run this — same template every quarter, your self-assessment side-by-side with theirs, the same questions re-run six months later so you can see what actually changed — that's what Mirorly's templates handle. The Library is where the per-context templates live. Two of the early templates are calibrated specifically for the first eighteen months of a management role, where most of the mistakes above show up first.

For the broader manager-development arc — onboarding into the role, the conversations with your own boss, building a development plan that's actually about growing rather than performing — feedback is one input among several. Our sister site, First-time Managers, covers the rest. The two sites are designed to read together: feedback techniques on this side, the wider role on that one.

Most of the eight mistakes above are not technique problems. They're visibility problems. You don't see yourself doing them, because nobody told you, because you didn't ask in a way that made it possible to answer. Ask in a way that makes it possible. Then act on the first answer that surprises you. That's the loop. Run it once a quarter for a year and the manager you become is materially different from the one you'd be without it.