You Can’t Coach What You Don’t Observe

When you first step into leadership, letting go of the actual job is harder than anyone admits.

You were promoted because you were good at the work. You knew the details, the shortcuts, the judgment calls. Suddenly, you’re told that doing the work is no longer your job, and that message often lands as stop touching anything at all. Most new leaders struggle here, just in different directions.

Some hang on too tightly. They keep executing, correcting, and stepping in because that’s where they feel competent. Others swing to the opposite extreme and disappear from the work entirely, convinced that distance equals maturity.

Both reactions are understandable.

Neither works.

The Awkward Middle

Early leadership is a constant negotiation with yourself. You’re trying not to redo people’s work. You’re trying not to jump in with answers. In short, you’re learning how not to be the person doing the work anymore (more on that here). It is not a leader’s job to do the work, that part is true and important.

Where things go wrong is what comes next.

Many leaders conclude that if they shouldn’t do the work, they also shouldn’t be close to it. Leadership starts to mean distance. If you stay above the noise (looking at dashboards, summaries, and end-of-quarter results) it feels strategic. And you’re not wrong about the value of perspective.

But you are wrong about the cost of never stepping onto the floor.

Letting go of execution is not the same as letting go of understanding. New leaders often miss this distinction. In trying not to micromanage, they stop observing altogether.

How Fear of Micromanaging Creates a New Problem

Micromanagement gets a lot of attention, and rightly so. But fear of micromanaging creates its own failure mode.

Leaders stop asking to sit in on meetings. They avoid reviewing work in progress. They wait for polished outputs instead of watching the process. Coaching becomes reactive because the leader only engages once something has already gone wrong.

Ironically, this often leads to harsher corrections later. Without context, feedback feels abrupt. Decisions feel second-guessed. The leader ends up intervening more aggressively because they intervened too late. Micromanagement isn’t caused by observation. It’s caused by control without trust.

How to Observe Without Taking Over

Good observation is quiet, intentional, and disciplined. It starts with watching how work happens, not just what gets delivered.

1. Be Explicit About Why You’re There

Observation goes wrong when people don’t know what it is. If you show up unannounced or silent, teams assume evaluation. If you jump in too early, they assume correction. Both shut down real behavior.

Set the frame clearly:

• “I want to understand how this work actually flows.”
• “I’m here to observe, not to change anything today.”
• “Don’t adjust for me, I need to see it as it is.”

This removes pressure and helps people act normally instead of defensively.

2. Watch the Process, Not Just the Outcome

Leaders often focus on what’s produced: the deck, the decision, the metric. Observation means paying attention to how those things come into existence.

Look for:

• Where decisions get delayed or rushed
• What information people wait on
• Who carries risk quietly
• Where handoffs break down
• What people avoid talking about

These signals never show up in final outputs, but they shape every result.

3. Listen More Than You Speak

The fastest way to take over is to talk too much.

When observing, treat silence as a tool. Let conversations unfold without redirecting them. Notice who speaks first, who hesitates, and whose ideas get traction.

If you ask questions, make them reflective, not corrective:

• “What made that option feel safest?”
• “What would have happened if you’d waited?”
• “Where does this usually go off track?”

If your question leads directly to an answer you already have in mind, it’s probably control disguised as curiosity.

4. Separate Observation From Intervention

One of the hardest disciplines for leaders is not acting on what they see immediately. Just because you notice something doesn’t mean you need to fix it in the moment. Observation and intervention are two different activities and mixing them erodes trust.

Capture patterns privately. Let them accumulate. Ask yourself:

• Is this a one-off or a system issue?
• Does this require coaching or clarity?
• Is now the right moment or just the most tempting one?

Delayed coaching is often more effective than instant correction.

5. Take Notes on the System, NOT the Person

When leaders observe, it’s easy to mentally score individuals. That’s rarely useful.

Instead, document:

• Repeated constraints
• Conflicting incentives
• Unclear ownership
• Assumptions people seem to share
• Places where judgment is overloaded

When coaching later, this allows you to focus on conditions and choices rather than personalities.

6. Coach From Shared Reality

When you do step in, anchor feedback in what you actually saw.

• “I noticed that when priorities shifted, three different people made the call independently.”
• “I saw how much time was spent clarifying expectations after the handoff.”
• “I watched the team avoid that tradeoff, help me understand why.”

7. Know When to Step Back Again

Observation isn’t permanent presence. Once you understand the system well enough to coach effectively, step back. Let the team apply what they’ve learned. Check in periodically, not constantly.

The goal isn’t to stay close forever but to build enough understanding that distance no longer equals ignorance.

Where Micromanagement Actually Begins

Observation becomes micromanagement the moment curiosity turns into control.

You’ve crossed the line from observing to micromanaging when:

• You feel uneasy if the work isn’t done your way
• You start correcting decisions before understanding the reasoning behind them
• You give answers faster than you ask questions
• People begin to look to you for approval instead of judgment
• Work slows down when you’re in the room

Before stepping in, pause long enough to ask:

• Do I actually understand why this decision was made?
• Is this uncomfortable because it’s wrong or just because it’s not how I would do it?
• What happens if I let this play out?

Instead of correcting execution, you should help people see their own patterns. Over time, something important happens. People stop performing for the leader and start thinking with them. Decisions improve even when you’re not in the room, which is the real test of leadership.

Wrapping Up

The balcony gives perspective. The floor gives truth. Strong leaders move between the two. Not to control, but to understand.

You don’t need to do the work anymore.

You do need to understand it.

If you found this article valuable:

• Follow me for more articles on remote team processes, tips and hiring ⇢ Milos Eric
• Check out OysterLink, a new platform for restaurant and hospitality careers. Find jobs, career tips, and insights. Learn and grow with us ⇢ https://oysterlink.com/