Before starting, decide which numbers, behaviors, or artifacts will prove progress within hours. Examples include response time, error count, conversion rate, or a single working prototype. Agreeing on signals with stakeholders reduces debate later and concentrates effort where improvement compounds fastest.
Invite colleagues or customers to describe exactly where effort spikes, hesitation appears, or confusion stalls progress. Request concrete timestamps, screenshots, or quotes. Friction-first feedback cuts through politeness, giving you fixable targets you can address immediately, then re-test within the same workday for proof.