Feedback field guide
Give the revision a purpose.
1. Name the evidence
Describe an observable detail. Connect it to the agreed task and a possible effect. Use “may” when the effect has not been tested.
2. Explore the reasoning
Ask what led to the choice. Work with the constraint: “How could we keep the feature details while making the first action easier to find?”
3. Agree on the next step
Identify the change, its owner, and a time to check it. Observe a task rather than asking whether someone likes the result.
“I noticed [evidence]. For [task], that may mean [effect]. What led to that choice? Let’s try [revision] and check [behavior].”
A small internal check can expose confusion. It does not prove broader learning or business impact.