A review of finding history should explain the transition to “Theme C”, rather than treating the label as self-explanatory. Counting repeated feature names can miss several different problems, or overstate a problem raised by one vocal group. Store the observation and its context separately from the proposed solution. Review themes across source and user segment.
Review the next move
SuperPH explores feedback collection that preserves the user problem before grouping suggestions into product themes.
Example: Finding history
The illustrative record contains navigation problem. Its state is theme c. 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
- Compare the proposed next step with the original objective. For finding history, use “Navigation problem” as the starting context.
- Review the assumption that would change the outcome. For finding history, use “Navigation problem” as the starting context.
- Leave a dated explanation for the next person. For finding history, use “Navigation 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 “Exporting results” 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 →