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

Why do intermittent and electrical faults still beat me?

You can trace a steady fault to its source almost by instinct now. Then a problem shows up, vanishes before you can test it, and comes back a week later. You start doubting your own hands. This is not proof you've hit your limit. It is a different kind of problem. You are using the wrong method on it. A steady fault holds still for you. An intermittent one does not hold still. It needs more than one set of eyes, watching over time. Stop blaming your own skill. Build a system instead. Keep a shared log. Agree on one repeatable test. Write down the exact conditions every time the fault shows up. This is work for a crew. It is not a job for one expert chasing a ghost alone.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
More to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
Intermittent fault-finding needs a real method to learn, but getting a team to actually log, test, and stay patient together is where coaching does the heavy lifting.
How the two dials adapt to you →
What’s really going on

You have mastered the faults that announce themselves. The ones that hide are different — they punish impatience, not skill. Stop hunting the part. Hunt the conditions. Write down exactly when it fails, who was there, what changed. The pattern is data your team must build together, not a flash of genius you lack.

🔒 What you’ll build togetherUnlock by starting
A moveLog every failure with your team: time, place, who was present, what changed just before.
A moveAgree as a crew on one test that can reproduce the fault, even partially, before anyone touches a part.
A moveSplit the roles: one watches, one stresses the suspect area, one records. Never hunt alone.
A moveRule out the steady causes first, out loud, so the team doesn't re-check what's already cleared.
A moveSet a time limit per session. If the fault won't show, stop and compare notes instead of guessing.
PractiseThe Ghost Log · a Pod of 4 · 30 min

What changes unlock by starting

  • A shared fault log your whole team trusts, instead of scattered memory.
  • Fewer repeat visits for the same hidden problem.
  • A team that catches patterns one person alone would miss.
  • Less wasted time swapping parts that were never the cause.

Related problems

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.