Useful, working, improving
There is always another tweak. Aim for functions that work well and users who are happy. The first prototype helps you find what matters; it does not remove the need for reliability or permissions.
Test around 80–85%
- Ask a colleague to complete the main task.
- Watch where they hesitate instead of explaining every click.
- Ask what they expected, what was confusing and what is missing.
- Prioritise the feedback, revise with AI and test again.
Review in context
Check off as you go · resets when you leave this page0 / 7 ready
Bring feedback to your coding partner
TRY THIS PROMPT
Here is colleague feedback: [anonymised or fictional feedback]. Review it against purpose, audience, context, usability, layout, permissions, reliability and maintainability. Recommend the next few improvements and how to verify them. Keep unrelated ideas separate.
Before real school use
Apply your school’s review process for personal data and safeguarding. Confirm access, retention, backups, support ownership and the relevant workflow with the people responsible. Use fictional data until that preparation is complete.