Use representative test data
Empty screens and ideal inputs can miss real problems. Test long names, missing values, repeated actions, and larger records so the app behaves predictably in ordinary use. Use several relevant signals rather than one isolated result.
Check maintained packages, permissions, licenses, and required device features. Dependencies need an upgrade and support plan. Record the starting conditions so comparisons remain fair.
A limited first release
Separate essential tasks from later features. Build the smallest release that can be used and evaluated, with explicit exclusions and a change process. Turn the findings into a short list of actions and owners.
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Agree a secure handover process for accounts and source files.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities