The prototype example highlights a different part of the process: one useful screen. Define one question to answer and a small artifact to build. Review what you learned before expanding the scope. Compare it with review before assuming that both items require the same response.
Work through the specimen
An ambitious project can stall because the first task depends on decisions that have not yet been tested.
Example: Prototype
The illustrative record contains one useful screen. Its state is experiment. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Check the current condition against the stated context. For prototype, use “One useful screen” as the starting context.
- Identify which role can verify the information. For prototype, use “One useful screen” as the starting context.
- Record the exception as well as the expected path. For prototype, use “One useful screen” as the starting context.
A small exercise
Take one recent personal project planning example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Review” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More journal →