The Immediate Check-In

The chair hadn’t even fully swiveled back before the first message dropped. I was still tasting the cheap coffee from the meeting room, the kind that scalds the back of your throat if you think too long about its origin.

“I trust you to run with this,” she’d said, leaning back in a way that signaled absolute confidence, absolute hands-off autonomy. Five minutes later, the screen flashed. *Ping.*

“Just checking in! Did you decide on the platform yet? Have you thought about trying X?”

I hadn’t even opened the project file. The meeting had ended at 10:01 AM. This was 10:06 AM. I ignored it, focused on pulling up the initial requirements document. I was trying to honor the spirit of the instruction: *own it.* Ownership means tackling the messy start, charting the territory, not reporting on every tentative step taken in the first 301 seconds.

The Euphemism of Control

You are told to drive the bus, but your boss has glued themselves to the passenger seat with their own set of auxiliary, non-functional pedals, constantly stomping and giving directions for where you already intended to turn.

This dynamic isn’t coaching, and it certainly isn’t empowerment. It is fear dressed up in motivational speech. And it kills initiative faster than a budget freeze.

The Cost of Micro-Precision: Antonio Y.

I watched it happen to Antonio Y. Antonio was a phenomenal subtitle timing specialist-the best I’d ever worked with. His job wasn’t glamorous; it involved getting dialogue to sync perfectly with emotional beats, sometimes shifting a subtitle by mere milliseconds, 11 milliseconds to be exact, to match a character’s intake of breath before the line. He dealt in micro-precision, but he needed macro-trust.

Antonio told me he spent 91 percent of his initial project bandwidth just managing the report, instead of coding.

“They tell me to be proactive,” he sighed, pushing his glasses up his nose, “but what they really mean is, ‘Please show me your work so I can tell you exactly what I would have done, thereby making it my work, but still your fault if it breaks.’ I’m not owning the project; I’m owning the paperwork, and they own the decisions.”

And here’s where the contradiction hits: Antonio was a professional. He knew, for example, that certain legacy systems needed a soft migration period, requiring 171 temporary files. His manager read the Confidence Index Report, saw the large number 171, panicked, and demanded an immediate, hard cutover, citing “efficiency.” Antonio tried to explain the technical debt, the instability risk. The manager dismissed it as Antonio “not wanting to run with the vision.”

So Antonio did it the wrong way. He followed instructions. The system crashed three days later, at exactly 2:21 PM. The manager’s response? “Well, Antonio, this was your project. What did we learn about execution?”

The Escape from Mental Clutter

It makes you want to step away entirely, to find a place where the air is clear and the control over your own movements is absolute. When the tension gets that high, when every pixel and every pause is questioned, the mental clutter becomes suffocating.

That cycle-being held accountable for a choice you weren’t allowed to make-that’s how you cultivate learned helplessness. Employees, brilliant ones like Antonio, quickly figure out the safest strategy: *Do nothing until specifically told.*

The Eleven Conflicting Emails

I’ve been guilty of this myself, though I never announced it. Early in my career, trying desperately to prove I was ‘hands-on,’ I assigned a critical process improvement task to a junior analyst named Marcus. I told him, “Run with it! I want you to be the expert.” Then, within 71 hours, I sent him eleven separate emails containing links to articles I’d read, each with the subject line: “Just a thought, don’t feel obligated!”

Of course, he felt obligated. He abandoned his own innovative approach and tried to integrate all eleven conflicting suggestions, resulting in a process that was convoluted, slow, and frankly, ridiculous. When I reviewed the final product, I criticized the lack of coherence. I criticized him for not simplifying.

It’s a pattern of power display that has nothing to do with mentorship. Genuine coaching involves setting boundaries, providing resources, and then stepping back-allowing failure to be a teacher, not a weapon. Micromanagement, conversely, is the constant display of institutional superiority, a subtle yet destructive form of control that undermines the very confidence it purports to build.

Belief, Not Proximity

We need to stop confusing proximity with support. Just because a manager is *near* the work, constantly monitoring the dashboard, doesn’t mean they are *supporting* the worker. Often, they are merely projecting their own anxieties onto the productive space. This requires the employee to manage the manager’s emotions, adding a heavy, undocumented layer of labor to the actual project scope.

True belief requires you to be quiet when you feel the urge to interject, to allow the subordinate to make a $51 mistake in a $5,001 project, just so they can learn the cost of velocity versus precision, and own the subsequent fix entirely.

The Psychic Parrot Test

If your team’s greatest skill is predicting what you, the manager, want them to do, rather than figuring out the objectively best way to serve the client or the product, then you haven’t empowered them. You’ve simply hired very expensive, highly educated psychic parrots.