Resources
Small notes that save long meetings.
Free to use. Filter by topic or search for a word.
- plan
Write a one-paragraph problem statement
Before any meeting, describe who struggles, with what, and what changes if it is fixed. It focuses the first call.
- plan
List what can wait
A short “not now” list protects the first version from growing without anyone noticing.
- design
Design the error message first
Decide what someone sees when things go wrong. It reveals hidden assumptions early.
- design
Five-person usability check
Ask five people to complete one task with a prototype and watch quietly. Note where they hesitate.
- release
Store listing checklist
Name, short description, screenshots for each required size, privacy policy URL, support contact, age rating answers.
- release
Before you press publish
Test a fresh install, check the support email works, and confirm who monitors reviews in the first week.
- it
Password and access register
Keep a private list of which accounts exist, who owns them and where recovery codes are kept.
- it
Describing a fault usefully
What you did, what you expected, what happened instead, when it started, and whether it affects everyone.
- web
Ten-second test for a homepage
Show the page to someone for ten seconds, then ask what the organisation does and how to contact it.