The Mistake That Keeps You From Fixing Anything New

Most troubleshooting content is a lookup table. Symptom on the left, fix on the right. "Engine won't start, check the battery." "Wi-Fi keeps dropping, restart the router." It's genuinely useful advice — for the exact system it was written about.

The moment you're standing in front of something the table doesn't cover — a boat you've never worked on, a smart-home device from a brand you don't recognize, an engine type you've never touched — the table is worthless. And if fixing things has only ever meant memorizing fixes, you're stuck.

The real skill isn't the fix. It's the process.

A career troubleshooter doesn't know more fixes than you. They have a repeatable process for building a model of how an unfamiliar system is supposed to work, then comparing that model to what it'sactually doing. The gap between those two things is where the fault lives — every time, regardless of what the system is.

That process has four steps:

1. Investigate — gather signal before touching anything.
2. Assess — separate confirmed fact from assumption.
3. Theorize Expected Operation — build an explicit model of how it should work.
4. Gap Analysis — find exactly where reality diverges from that model.

Most troubleshooting advice skips straight to step 4 — or worse, skips to a remembered fix from a different system entirely. Step 3 is the one that actually makes diagnosis possible on something you've never seen.

Get the free worksheet to start running this process the next time something unfamiliar breaks — orread the full method in the book.