Lab: Troubleshooting Flowchart
Flowchart Navigator: follow a real diagnostic decision tree to isolate each fault, one branch at a time
A Reading a Diagnostic Flowchart (Objective 5.x)
The pieces of a flowchart
- 1Decision point. A specific test you actually run, not a guess dressed up as one.
- 2Branch. The test's REAL result determines which arrow you follow next, not the one you hoped for.
- 3Dead end. A branch that doesn't match the evidence in front of you. It costs you a diagnostic strike and isolates nothing.
- 4Terminator. The confirmed root cause the whole chain of tests was built to reach.
Why the order matters
- 1The correct next test follows from what you just observed, not from a memorized checklist order.
- 2A test that is the right call on one fault can be a dead end on a different fault with different symptoms. Read the actual result, every time.
- 3Hitting a dead end and reasoning again from the same decision point is normal flowchart behavior, not failure.
- 4Isolating the root cause is only half the job. The fix you pick has to match the CONFIRMED cause, or nothing is actually solved.
---
Diagnostic Strikes Remaining3 of 3
Isolation Progress0%
C Work the Flowchart
Decision 1
Decision 2
Decision 3
Root Cause + Fix
Navigate the Flowchart
Pick the next diagnostic branch based on what you have observed so far. A dead end costs a strike and keeps you at this same decision point.
Flowchart Trail
No branches taken yet.
Identify the Fix
The root cause is confirmed. Pick the fix that addresses THAT cause, not just a plausible-sounding one.
