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. Use the findings to update the brief for the next stage.
Request only necessary access and provide a useful refusal path. Test camera, storage, and location functions with permissions both allowed and denied. Check the rights to photographs, quotations, and licensed material.
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