Loop 071
The product journey feedback loop
A product research workflow that observes target personas across the complete user journey, separates usability friction from unmet needs, and ranks evidence-backed feature suggestions.
Ready-to-use prompt
Copy the loop
Define two or three target-audience personas from the product positioning, asking if the positioning is unavailable. For one persona at a time, walk the full journey from landing and signup through core workflow, secondary features, limits, return visit, and offboarding using only what that persona could realistically see. Observe only. Record expected versus actual behavior, friction, confusion, delight, and comparable-product mental models. Split findings into usability friction, unmet needs, and feature suggestions tied to a specific journey moment. Stop after one pass per persona and return the personas, journey map, evidence log, ranked suggestions, and any approval boundaries before roadmap or production changes.
Verify / stop
Every suggestion traces to an observed persona journey moment.
The final report includes persona definitions, journey-step evidence, expected-versus-actual notes, and a ranked list where every suggestion names the persona, goal, journey moment, expected impact, effort, and existing feature it could extend.
Context and guidanceWhen to use it, steps, safety notes, and related loops
Use this when
Use this when a product needs grounded feature and UX feedback from realistic user journeys before deciding what to build or improve.
How to run it
- Define realistic target personas from current positioning or ask for positioning before starting.
- Walk one persona at a time through the full visible journey without changing the product.
- Record expected versus actual behavior, friction, confusion, delight, and comparable-product mental models.
- Separate usability friction, unmet needs, and feature suggestions so fixes and roadmap ideas do not blur together.
- Rank suggestions by impact-to-effort and stop after the agreed persona pass.
Why it works
Product ideas become more useful when they are tied to a specific persona, journey moment, and observed gap rather than brainstormed in the abstract.
Implementation note
Do not touch production data, real accounts, pricing, or roadmap commitments without approval. Treat the output as product evidence, not a decision to build.