Prototype Testing Readiness Checklist
Make sure the test will be worthwhile.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Check readiness for a prototype test. Prototype description and fidelity: [PROTOTYPE]. Test goals: [GOALS]. Date and participants: [DATE_AND_PARTICIPANTS]. Produce a checklist table: Area | Check | Ready? | Fix. Cover goals (specific questions, decisions), prototype (all task paths work, realistic content not lorem ipsum, dead ends covered with a graceful message, no confusing placeholder behavior), tasks (written, piloted), participants (recruited, backups), environment (devices, accessibility settings, recording, internet), team (roles assigned, observers briefed), ethics (consent form), and data (notes template, analysis plan). Add a pilot session plan (30 minutes with a colleague who is not on the project), a list of typical prototype problems (hotspots hidden, slow loads), and a decision rule for postponing (if critical flows do not work). Include a message to the team (80 words) with the test schedule and observer etiquette. Include a go or no-go verdict at the end with the minimum fixes required, and a fallback plan (paper walkthrough, screen sharing of static screens) if the prototype fails on the day.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.