Reflection · Would Another Person Know What to Do?

You wrote instructions that made perfect sense — to you, since you wrote them. Then another group used them, and suddenly: "wait, what does this mean?" That moment is useful, because documentation lives or dies with the person who didn't write it.

Hidden knowledge

Maybe your group assumed everybody already knows how to test a microphone, or which application to open, or what "network okay" actually means, or where the spare equipment is kept. The checklist exposed those assumptions — and that's exactly what it was supposed to do.

Reflection prompt (150-200 words)

Which assumption did your group discover during the Week 17 blind test, how did that assumption make the original checklist less reliable, and what did you change so another person could perform the process more consistently?

Your response needs:

1. the original step — what Version 1 said
2. the assumption — what knowledge the authors had that wasn't actually written down
3. the test evidence — what the other group did or asked
4. the revision — how Version 2 changed
5. the reliability gain — why the new version should work more consistently

Example

Original step: "check headset." Assumption: our group assumed everyone understood this meant testing both audio output and microphone input. Evidence: the testing group heard audio fine and marked the step complete, but the hidden microphone failure went undetected. Revision: we split the step into a separate output test and a microphone-input verification. Reliability: Version 2 makes the required functions observable instead of relying on the operator's own interpretation of "check."

That's operations reasoning — specific, evidence-backed, and honest about what the original step actually failed to say.

Go past "it was confusing so we fixed it"

That sentence explains nothing. What exactly was unclear, why, and what changed as a direct result?

The bigger idea

Week 17 isn't really about checklists — it's about externalizing knowledge: taking something one person knows and turning it into a process other people can actually use. That's a transferable professional skill in IT, events, broadcasting, engineering, cybersecurity, manufacturing, healthcare, and basically anywhere systems need to operate consistently without depending on a single expert being present.

Final sentence

Finish:

A useful checklist should reduce dependence on __________ by making __________ visible.

Use your own words.

Week 17 closeout

Week 15 asked what's in the system. Week 16 asked where the connection failed. Week 17 asked how to operate the system consistently before things go wrong. You now have inventory, dependencies, network paths, troubleshooting, verification, checklists, readiness, failure responses, and documentation — everything Week 18's lab-readiness challenge will put to use at once.