Use for a new or confusing user journey, competing interaction choices, or a gap between the requested outcome and proposed flow. A cosmetic change with an established pattern may need only a focused consultation.

Brief inputs

Name the target user, their goal, the actual entry point, and the accepted behavior. Supply the current flow, relevant user feedback, screenshots or a usable build, and established interaction conventions. State whether the deliverable is an interaction proposal or an assessment of implemented behavior. Name any available design or user-research skill and the tools that can inspect the actual surface. Screenshots alone cannot establish keyboard or recovery behavior; record the missing access.

Working questions

Can the user complete the goal from the stated entry point without knowing implementation details? Follow the task through success, cancellation, loading, empty and failure states that affect this flow.
Does the interface make the next action, current state and consequence clear? Separate observed confusion from a hypothesis requiring user research.
Which existing convention should the change preserve? If a departure is necessary, show the user benefit and the smallest coherent alternative.
Where do choices change accepted product behavior? Present those choices to the lead with consequences; a design recommendation is not a user decision.

Deliverable

Provide an annotated flow or concrete interaction proposal, the alternatives that could change the decision, and observable acceptance criteria. For a review, link each finding to a reproducible user step and show the effect on completion or understanding. Name inaccessible states and untested assumptions. For accessibility-specific uncertainty, use the accessibility profile rather than asserting that a visual review establishes accessibility.

Record interaction decisions you helped originate in the contribution section. Proposed project lessons should name their source and revalidation condition.