The Fix-It Bay is busy. Rocket fixed a frozen app yesterday, but today he cannot remember how. "Was it close, or restart, or something else?"
Raven opens a notebook with a tag that says Fix Log. "What do you notice? If we had written it down, we would know."
Nova nods. "Would you like a hint? A technician's memory lives on paper. And when a fix is not yours to do, you ask."
Step four of the method is to write it down. A fix log is a short written record of each problem.
A good fix log has four parts. What you noticed, the problem sentence, each test, and what happened.
Writing takes one minute. Next time the same problem shows up, you already know the answer.
The fix log also helps you ask for help. A grown-up can read exactly what you tried.
| Part of the log | Example |
|---|---|
| Noticed | Screen on, volume at zero, mute sign showing |
| Problem sentence | Video should play with sound, but it plays with no sound |
| Test 1 and result | Turned mute off: sound came back |
| Fixed? | Yes. Cause was the mute sign. |
Step five is to ask. Asking is not giving up. It is part of the method.
You ask a grown-up when the next test is on the never list. That list is plugs, batteries, the case, passwords, updates and liquids.
You also ask when the easy safe tests are done and the problem remains.
When you ask, bring your fix log. Say what you noticed, your problem sentence and what you tried.
| Statement | True or false? |
|---|---|
| Asking for help means you failed. | ? |
| A fix log should include tests that did not work. | ? |
| A child may change a password to test a fix. | ? |
| Bringing your fix log makes asking easier. | ? |
You know how to keep a fix log and when to ask. Tomorrow you put all five steps together into one method.