Plans, checklists, schedules, and decision trees
Unit ID: AIT-M09-U00 Estimated active time: 15-20 minutes
The main idea
Different planning needs call for different output formats.
A checklist confirms things are done. A schedule says when. A decision structure says which. Asking for "a plan" gets a blend that does none of the three well.
Why this matters
The format you choose determines what gets forgotten. A schedule with no checklist loses the quality steps; a checklist with no schedule loses the ordering.
Safe example
A workshop preparation task may need a checklist, while a decision needs criteria.
Two different jobs, two different documents, often for the same event.
Better working habit
Ask for the planning format that fits the job.
Decide first whether you are confirming, sequencing, or choosing. The format follows from that.
What to watch for
Do not let a tidy plan hide missing information.
A well-formatted plan with an unresolved dependency in the middle reads as complete. Formatting is not evidence.
Mini practice
Match five planning tasks to output formats.
For each, name what the wrong format would have lost.
Check yourself
Before moving on, answer:
- Am I confirming, sequencing, or choosing?
- Does the format I chose show what is still unresolved?
- What would a different format have made visible?
