Door 03. Fix It.

Something doesn’t do what it’s supposed to. Let’s find out why.

Most broken systems aren’t actually broken. They’re just doing what they were built to do, badly. A workflow that eats three hours a day. A dashboard nobody trusts. An account that’s been bleeding money because nobody had time to audit it properly. That’s the work: find the actual fault, not the symptom, and rebuild it so it stops happening again.

Tell me what’s broken →
Figure VII: a pipe runs from a source tank to a dripping tap. The drip at the tap is the symptom. Tracing back past two sound junctions finds the crack upstream, which is the real fault. Source The symptom The fault where you notice it where it actually is readings downstream look wrong too the usual patch ✓✓✓ trace it back, one joint at a time soundsoundsound
Fig. VIIThe drip is downstream. The crack is upstream. Fix the crack.
How it works.

Plainly.

  1. 1 You describe what’s actually going wrong, not what you think the solution is.
  2. 2 The real problem gets isolated. Usually it isn’t what you first thought.
  3. 3 A fix gets built and handed over. Working, not theoretical.
Fault reports, closed.

What this looks like in practice.

a · a workflow fix A three-hour daily PDF assembly job, traced to its real bottleneck and rebuilt into a two-minute automated run.
b · a reporting fix A dashboard nobody trusted, followed back to one broken data source and repaired so the numbers finally hold.
c · a recovery resolved A Google Ads account quietly overbilled for months. Audited, disputed under the CGA, and the overspend recovered.
wrong door? Build It, nothing exists yet → Train It, your team needs to think with AI →