The same label can mean different things.
LumenPay is a fictional payment-workflow product used only for a research scenario. Participants interpret a “pending” status in different ways: some expect an action, while others assume processing will finish automatically.
The researcher’s challenge is to communicate that difference without compressing the study into a universal claim about what all users need. No real financial data or customer records are used.
Preserve the moment around an excerpt.
The proposed evidence trail includes the task, the visible state, and the participant’s words. A quote alone might suggest that the label needs rewriting. The task context reveals an additional issue: the screen does not communicate whether an action is available.
Contrasting evidence stays alongside the theme. A participant familiar with the workflow understood the status, which suggests that experience and onboarding context deserve further attention.
| Observation | Interpretation | Limit |
|---|---|---|
| Participant searches for an action | Status may imply responsibility | Observed within one task |
| Experienced user waits | Prior knowledge changes interpretation | Cannot generalize to new users |
| No visible next step | Action state lacks explanation | Needs design exploration |
Synthetic excerpt · LP-032: “Pending sounds like I should do something, but there isn’t a next step here.”
Write a brief that retains the uncertainty.
The concept research brief separates observations from interpretations and proposed responses. It links to source excerpts and adds a limitations section before suggesting a design direction.
A product designer can then explore status copy, action affordances, and contextual guidance as separate hypotheses. The brief supports a decision without pretending that the research has already selected the final solution.
- Keep participant and task context with each observation.
- Use neutral theme names before proposing solutions.
- Include evidence that complicates the main interpretation.
- State the follow-up question for the next study.
Traceability protects nuance.
This story illustrates a reviewable synthesis process, not a real engagement or measured usability gain. Every organization, source identifier, and excerpt is fictional.
The lesson is to make an insight portable without removing its boundaries. A concise brief can still preserve context, limitations, and a path back to the original observation.