You Don't Need to Be an Expert to Fix It

There's a specific kind of freeze-up that happens when something breaks and you have zero background in it. Not "I don't know the fix" — that's normal, everyone hits that. It's "I don't even know where to start," and it usually ends with either calling someone or leaving it broken.

That freeze-up comes from a false belief: that diagnosis requires expertise in the specific system in front of you. It doesn't. It requires a process — and the process is the same whether the system is a copier, a network, a boat, or a motorcycle you've never owned before.

Expertise in a system vs. a method for any system

An expert in one system has memorized how that system fails. That's genuinely valuable — for that system. It's also why experts can be strangely bad at diagnosing something just outside their specialty; they reach for pattern-matches that don't apply.

A method, on the other hand, doesn't care what the system is. Investigate what's actually happening. Assess what's fact vs. assumption. Theorize what "correct" should look like. Find exactly where reality diverges from that theory. That sequence works whether you've been doing this for thirty years or thirty minutes.

What changes once you have the process

Not that everything becomes easy — some systems are genuinely complex, and some diagnoses genuinely require expertise or specialized tools you don't have. What changes is that "I don't know where to start" stops being true. You always know where to start: investigate.

Get the free worksheet and try it on the next thing that breaks — or read the full method.