Choose the primary journey
Describe the starting point, steps and outcome a user wants to achieve. Each feature should support this journey or an essential operational requirement.
Divide the scope
Use three columns: necessary for testing, possible to handle manually and later. Some backstage work can be manual during a trial, but describe honestly how the product operates.
Define done
Each task needs success criteria, empty states, error messages and a way to handle abandonment. Check which accounts can view or modify each piece of data.
Prepare the trial
Use authorised data, provide a way to recover from mistakes and collect feedback for each task. List unsupported features so participants understand the limitations.
Deliverables
Produce a journey diagram, prioritised feature list, acceptance criteria and test script. Evaluate the MVP by what you learn about users, not just by the number of screens built.
