Spot your management blind spots without coaching

A blind spot, technically, is a thing about your behavior that's visible to others but not to you. The clinical definition is useful but undersold. What it actually means in management is: there's a specific pattern in how you make decisions, communicate, react under stress, or interact with your team — and the gap between how you describe yourself doing it and how it actually lands is the blind spot. Closing that gap is roughly the entire job of self-development as a manager.

The default move when people get serious about closing this gap is to hire a coach. A good executive coach is genuinely useful — but they cost between $200 and $400 a session, take six to twelve months to produce visible change, and have one structural limitation: they only know what you tell them. The blind spots they help you surface are the ones you can articulate well enough to discuss. The blind spots that don't even rise to the level of articulation — the ones you don't have language for yet — usually don't show up in the coaching conversation at all.

This article is about how to surface blind spots without coaching, using methods that cost nothing and work on the harder, less-articulable category. You may still want a coach later. But you'll get more from coaching if you've already done this work first.

Before the methods, five categories of blind spots to know exist. Most managers have at least one in each.

Communication blind spots — the gap between what you mean and what the room hears. Common varieties: cutting people off without realizing it; using a flat tone that reads as displeased even when you're neutral; ending discussions before everyone's contributed because you've already mentally landed; using qualifying language ("maybe we could," "I wonder if") that sounds like consultation but functions as direction. None of these are visible to you in real time. All of them are visible to your team.

Decision-pattern blind spots — the systematic biases in how you call things. Common varieties: defaulting to the riskier option to avoid feeling slow; defaulting to the safer option to avoid feeling reckless (yes, the same person can have both, in different contexts); over-trusting people whose presentation style matches your own; rounding up your gut feeling into a "rational" rationale post-hoc. The decisions look reasonable to you. The pattern is visible only when someone watches the last twenty in aggregate. Wharton's Adam Grant has written extensively about why these patterns are so hard to catch alone — the same mind that produces the decision also produces the post-hoc rationalisation that justifies it.

Team-impact blind spots — the gap between how you think you affect your team and how you actually do. Common varieties: thinking you're empowering when you're actually micromanaging through the back door (asking lots of questions about implementation); thinking you're protective when you're actually shielding people from feedback that would help them; thinking you're decisive when your team experiences your decisiveness as cutting off discussion. These are the most disguised because the self-narrative is positive ("I empower," "I protect," "I'm decisive") and the team's experience is negative but rarely articulated.

Self-perception blind spots — the gap between how you describe your own role in things and what actually happened. Common varieties: framing yourself as the rescuer of projects you didn't materially affect; framing yourself as the victim of dynamics you helped create; describing yourself as low-ego in ways that are themselves ego-laden. These are the hardest to spot because catching them requires the very self-awareness whose absence you're trying to detect.

Avoidance blind spots — the things you're systematically not doing, framed as deliberate choices. Common varieties: not giving someone harder feedback because you've decided they "can't handle it" (often: you can't handle the conversation); not pushing back on a peer's decision because you've decided to "pick your battles" (often: you've picked all of them); not asking for feedback because you've decided you "already know what they'd say" (often: you don't, but the not-knowing feels worse than the imagined answer).

If you read those five categories and felt a flash of "oh shit," that flash is a blind spot starting to surface. Don't argue with it.

Why coaching alone doesn't always close these

Coaching is great at the first category (communication) and pretty good at the second (decision patterns), because both are describable in the coaching conversation. You can replay a meeting, walk through how you made a call, work on phrasing.

Coaching is much weaker on the last three (team-impact, self-perception, avoidance), for a structural reason. In coaching, you describe your behavior to the coach, who then helps you reflect on what you described. If your self-narrative is the blind spot, the coach is reflecting on the wrong thing. The coach asks: "tell me about how you handled X" — you describe your version — they help you reflect on your version. Meanwhile, the team's version of how you handled X is different, and that's where the actual blind spot lives.

The fix isn't no coach. The fix is: coaching alone is incomplete because the coach can't see your team's view directly. You need to bring that view into the conversation. Which is what the methods below do — they import the team's view into your reflection without needing a coach.

Method 1: Structured self-assessment with delta tracking

The first method works on category 4 (self-perception). It's surprisingly cheap and surprisingly effective.

The mechanic: every quarter, you write specific, dated, behaviorally-anchored answers to a small set of questions about yourself. Specifics, not abstractions. Not "I think I communicated well this quarter." Yes "On Tuesday's product review, when Dan pushed back on the timeline, I cut him off because I wanted the meeting to end. I noticed it but didn't address it." Save the answers. Don't read them.

Three months later, you write the answers again, fresh. Then you read the previous version.

What this surfaces: not the blind spot directly, but the gap between your past self-narrative and your current self-narrative. If three months ago you wrote "I'm working on listening better in meetings" and three months later you write "I'm working on listening better in meetings," the lack of delta is the signal. You haven't changed. The narrative-of-change is the blind spot — you experience yourself as working on a thing, but the thing isn't actually changing.

The method works because narrative drifts faster than behavior. You can't easily see your own behavior, but you can see what you're telling yourself about your behavior over time. If the story stays static, the behavior is probably static too, even if it doesn't feel that way.

For the question template, Self-assessment template for managers: 30 questions is what we use. The five questions in Why self-assessment comes before peer feedback are a lighter starter version.

Method 2: Asking three peers the same question across rounds

The second method works on categories 1, 2, and 3 (communication, decision patterns, team-impact). It's the workhorse.

The mechanic: pick three people whose read on you you trust. Ideally a mix — one peer at the same level, one report, one cross-functional collaborator. Ask all three the exact same question, in the same time window, every quarter.

A good starting question set: "What's a pattern you've noticed in how I make decisions? Is there a specific moment from the last 90 days that anchors that pattern? What would you change about how I work, if you could change one thing?"

Three answers from three different vantage points, captured the same way over multiple rounds. Two things become visible from this that don't become visible any other way.

First, what all three say independently is much more reliable than what any one of them says alone. If three people surface the same pattern from different angles, that pattern is real. If only one surfaces it, it might be them, not you. Confirmation across vantage points is the closest thing to objective signal you can get cheaply.

Second, what changes round-over-round. Same three people, same questions, every quarter — the deltas in their answers tell you whether your behavior is actually shifting in their experience, regardless of how it feels to you.

This is the operational core of a self-led 360 round — your self-assessment plus the same questions to a few trusted peers, gap-tracked over time.

Method 3: Feedback after specific moments, not generic surveys

The third method works on category 5 (avoidance) and is the cheapest of all.

Most peer feedback fails because it's generic. "Anything I should be doing better?" sent in a normal week gets you "you're doing great." That's not a blind spot in the sense that there's nothing to surface — it's a methodological failure in how you asked.

The fix: ask after specific moments where the content of the moment anchors what their answer can be about. Not a generic ask. A specific ask, timed to specific events.

Three highest-yield moments:

The day after a meeting that felt off. Same-day or next-day, while the moment is hot.
A few days after a project closes. Specific to the work, while specifics are still vivid.
After you make a high-stakes call. About the trade-off process, not the outcome.

The full menu of seven such contexts is in How to ask peers for feedback — 7 contexts that work. The category-5 use case here is specifically: this method surfaces the things you've been avoiding asking about, because the timing forces the question. You can't ask "anything I should be doing differently in our 1:1s?" — too vague, too generic, you'll skip it. You can ask "in our last 1:1 I had the sense the conversation got stuck around X, did it feel that way to you?" — specific enough to actually send.

Method 4: The friend-over-beer test

The fourth method works on all five categories and is the one nobody uses because it sounds too soft. It's the highest-yield single question we know.

The mechanic: alone, with a pen, sixty minutes blocked off. Imagine a specific colleague you respect — someone whose read you'd trust — describing you to a close friend over beer. Not the polite version. Not the version they'd give a hiring committee. The unfiltered, slightly tipsy, slightly indiscreet version. The version that includes the qualifier you'd cringe at.

Write that description down. Specifics, not abstractions. As if you're channeling the colleague's voice, not your own.

Most people, the first time they do this, write something noticeably more honest than they would in any other reflective exercise. The friend-over-beer frame breaks the politeness reflex by externalizing the speaker. You're not assessing yourself; you're imagining how you're assessed by someone who has stopped performing for you.

What you write down on the first pass is a hypothesis. The other methods (peers, structured self-assessment) tell you whether the hypothesis is right. But the hypothesis itself is information you didn't have before — and information you almost certainly couldn't have surfaced by asking "what are my weaknesses?"

When to actually pay for a coach

Some blind spots are worth paying for. Three signals that suggest coaching, not just methods:

You've run methods 1-4 for two quarters and the same blind spots keep surfacing without changing. This is the signal that you can identify the pattern but you can't shift it alone. A coach helps with the change part, not the identify part. If you haven't done the identify-it-yourself work first, coaching tends to spend the first six months doing what you could have done in two weekends.

There's a specific high-stakes moment you can't afford to fail on. New role transitions, taking over a struggling team, preparing for a board interaction, or a relationship at work that's costing you nightly sleep. These are moments where the cost of getting it wrong outweighs the coach's fee comfortably, and a coach gives you fast-cycle feedback on a specific situation. Different use case than general blind-spot work.

The blind spot involves something you genuinely can't see in self-reflection — usually emotional or relational dynamics. Some patterns aren't accessible without a skilled outsider asking the right question at the right moment. If you suspect this is your case (a long-running relational pattern, a reaction-pattern that you don't understand), a coach earns their fee.

For everything else, methods 1-4, run consistently across quarters, will close most of the gap.

What to do next

Pick the method that costs you the least to start with this week. Not the one that sounds most useful — the one that takes the least activation energy.

If you've never done a structured self-assessment: do the five-question version tonight. Block sixty minutes. Phone in another room.

If you have three peers you'd trust with the same question: send the message today. "I want to ask the same three questions to a few people I trust, every quarter, to track how I'm changing. Can I include you? It'll be specific and short."

If you had a meeting yesterday that felt off: send the post-meeting question to one person who was there. Don't wait until "you have time to do this properly."

The compounding insight is the core point. Blind spots aren't surfaced in one heroic exercise. They become visible across rounds, when the same questions to the same people across the same windows let you watch yourself the way other people see you. That comparison — your view of you, side-by-side with their view of you, tracked over time — is exactly what Mirorly was built to do. But none of these methods require Mirorly to start. They require sixty minutes, three trusted people, and the willingness to read your own answers from three months ago without flinching.