Everything Went Right
Bad advice is worse than no advice
The drive landed on my porch in two days.
I’d done everything right. I gave my source everything it needed. Make, model, specs. It came back confident. SATA. So I bought SATA.
I cloned the old drive. Installed the new one. The case slid back in place. It booted clean. Everything that could go wrong went right.
And then nothing worked.
Shortcuts were missing. Programs wouldn’t load. It took one click in File Explorer to understand what had happened: the drive I’d disconnected to install the new one was my data drive. Not the OS drive. Not the one filling up. My C: drive was an M.2 stick tucked behind the motherboard. Right advice, but wrong drive.
The execution was clean. The diagnosis was wrong.
I’ve been in enough organizations to know what that moment feels like at scale. The campaign that launched on time and landed flat. The restructure that ran smoothly and solved nothing. The new software that got adopted and didn’t fix the problem. Everyone did their job. The thing still didn’t work.
Bad advice isn’t neutral. It’s worse than no advice.
No advice leaves you uncertain. Uncertain people ask more questions. They slow down. They look around. Uncertainty is uncomfortable, but it’s honest. It keeps you in the problem longer.
Bad advice closes the loop prematurely. It feels like clarity. You have a diagnosis, a plan, a part on the way. You stop asking questions because the question feels answered. And the better you are at execution, the deeper you get before you realize the premise was wrong.
The most dangerous moment isn’t when things go badly. It’s when everything goes right and nothing works.
The hard question, and the one that rarely gets asked, isn’t “what’s the solution?” It’s “are we solving the right problem?”
That question requires something most advice-giving skips. It requires sitting with the problem long enough to understand it. Not pattern-matching to a familiar answer. Not reaching for the closest available solution. Actually asking: what’s really going on here?
For me, it took pulling the service manual. Slowing down after the pivot didn’t work. Reading the actual specs of the machine in front of me. That’s when I found the extra SATA port I didn’t know existed. And realized the work I’d written off as wasted was actually done. The clone was good. It would boot from the new location. The false start wasn’t a failure. It just wasn’t useful yet.
The fix came. But only after I stopped executing and started diagnosing.
Here’s what I’ve come to believe after years of working inside organizations that were stuck: most execution problems are diagnosis problems in disguise. The plan is fine. The team is capable. The effort is real. But somewhere upstream, someone answered a question nobody fully asked.
What you actually need — before the plan, before the solution, before the confident advice — is someone willing to ask whether you’re working on the right drive.