Control the maintenance burden
Frameworks, libraries, devices, and operating systems change. Document dependencies and update responsibilities so ongoing compatibility is part of the plan rather than an unexpected expense. Turn the findings into a short list of actions and owners.
Test supported screen sizes, resumed sessions, interrupted tasks, and slow connections. Preserve state where the task requires it. Try the main customer task on a phone before signing off.
Data and permissions
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Keep a record of permission for any customer story used publicly.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. A written brief should explain what will change and what will stay.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities