Heuristic review

Open the prototype. For each step, ask whether the product shows status, uses real language, lets people undo, stays consistent, prevents errors, shows options, stays efficient, stays simple, recovers from errors, and offers help when needed.

List issues with the heuristic name and a short fix. Prioritise blockers first — things that stop the job — then polish.

• Issue — what went wrong.
• Heuristic — which rule it breaks.
• Fix — the smallest change that helps.