
Product boundaries
Define the users and main task before planning screens. Agree what the first release will not attempt. List the required outputs before setting the delivery schedule.
Test a complete task from entry to confirmation, including missing or invalid input. Screen-by-screen visual approval does not test the workflow. Review the whole path instead of judging one screen in isolation.
- A written brief
- Named responsibilities
- Agreed review points




