Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why do intermittent problems still leave me stranded?

You can find the broken part when it stays broken. A cracked seal, a severed wire — these hold still and let you see them. But the fault that shows for ten minutes and disappears, the one that only shows up in heat or after an hour of running, hides from you. And it costs you later, in front of someone who is now stranded and waiting. This is not a gap in your skill. It is a gap in your method. You have trained yourself to examine what is in front of you. An intermittent fault asks you to examine what is not in front of you right now — the conditions, the history, the pattern across time. That is a different discipline, and no one taught it to you because it looks like paperwork, not diagnosis. Do not call this bad luck. Luck has nothing to do with a fault you cannot reproduce because you never wrote down when it appeared. Choose the log before you choose the next tool.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The method for chasing intermittent faults is easy to state but hard to practice consistently, so the weight falls on habit-building over new facts.
How the two dials adapt to you →
What’s really going on

You are not missing skill; you are missing a method for time. Choose to log every occurrence — time, conditions, duration — until pattern replaces memory. Stop treating 'could not duplicate' as an answer. Build a fallback for the failures you have not solved yet, so being wrong costs less.

🔒 What you’ll build togetherUnlock by starting
A moveStart a fault log today: date, time, conditions, symptom, duration. Write it before you diagnose, not after.
A moveNever close a job on 'could not duplicate.' Write instead what you ruled out and what conditions you still lack.
A moveWhen someone describes a failure, ask for the conditions — heat, cold, load, time of day — even if it slows the conversation.
A moveBuild one fallback plan now for when you are wrong: a loaner, a callback line, a way to shrink the strand instead of preventing it.
A moveSet a rule: three unexplained recurrences on one system means you escalate your testing, not repeat the same check a fourth time.

What changes unlock by starting

  • You stop guessing and start collecting evidence, so patterns emerge instead of surprises.
  • Fewer people are stranded, because you build a fallback for what you haven't solved yet.
  • Your diagnostic time shortens over weeks, because logs replace memory.
  • You stop absorbing blame for what no single visit could have caught.

Related problems

The same struggle, seen by other coaches
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.