Start with exporting results. The entry pairs “Reporting problem” with “Theme A”. That pairing is useful only when it is clear why the context supports the state. Counting repeated feature names can miss several different problems, or overstate a problem raised by one vocal group.
Begin with the constraint
Store the observation and its context separately from the proposed solution. Review themes across source and user segment.
Example: Exporting results
The illustrative record contains reporting problem. Its state is theme a. 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
- Define the decision the reader needs to make. For exporting results, use “Reporting problem” as the starting context.
- Find the source behind the example record. For exporting results, use “Reporting problem” as the starting context.
- Write down the open question before choosing a state. For exporting results, use “Reporting problem” as the starting context.
A small exercise
Take one recent feedback collection 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 “Sharing a view” 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 field notes →