WHAT YOU WILL BE ABLE TO DO
Investigate an ordinary low-stakes problem without changing everything at once.
A plausible explanation is a starting guess. A useful test has a predicted result and a way to compare it with what happened. You may learn that your guess was wrong, that several causes interact, or that you need better evidence. Those are useful outcomes too.
You will need
- Paper or a simple note
- A low-stakes problem you can safely repeat
- A reversible change you are able to undo
THE METHOD
Step by step
Describe what actually happens
Write the action, expected result and observed result. Replace “the printer is broken” with “this two-page file prints blank from this application.” Specific description makes comparison possible.
Check the starting conditions
Note when the problem occurs and when it does not. Can you repeat it? What changed recently? A single memory of a failure is less useful than a clear, repeatable example.
Choose one hypothesis
State one possible cause and a prediction: “If this file is the issue, a known-good file should print from the same app.” Keep other relevant conditions stable.
Run a small reversible test
Make only the chosen change. Observe and record the result before trying something else. If the test requires deletion, disassembly or unfamiliar settings, choose a safer test or seek help.
Interpret narrowly
A different result supports a narrower conclusion, not certainty about the whole system. A known-good file printing points toward the original file or how it is handled; it does not prove that every other part is perfect.
Confirm and decide the next step
If safe, repeat the comparison. Keep a simple record of what worked and what failed. Restore temporary changes. Either make the supported small fix or give a helper your clear observations.
SEE IT IN PRACTICE
Labels keep printing at the wrong size
Describe the mismatch, then compare the application’s print scale with the required label setting. If you change scale, keep the file and paper the same and use a plain-paper test. Measure the result. Changing paper, file, printer and scale at once might work, but it would not tell you what helped.
Illustrative exampleIf it does not go to plan
- Changing several settings and trusting the last one
- Return to a known state where safe, then make a controlled comparison.
- Calling one successful attempt proof
- Check repeatability and whether some other condition changed at the same time.
BUILD THE SKILL
A little more capable each time
- First attempt
Write a precise description of an everyday inconvenience.
- Use it for real
Make one harmless comparison with a prediction written first.
- Take it further
Explain the evidence and remaining uncertainty to someone who did not observe the test.
CHECK YOUR LEARNING
Can you do it?
Judge the result against these signs. If one is missing, return to the relevant step and try again.
- The hypothesis predicts an observable difference.
- The test changes one relevant thing.
- The conclusion does not claim more than the result supports.
Explain it to yourself
Try answering before opening the explanation.
The problem disappears after you change four things. What do you know?
The combined situation changed, but you do not yet know which change mattered. Avoid assigning credit to one without a better comparison.
A test disproves your guess. Was it wasted?
No. It rules out or weakens an explanation and helps choose the next useful question.