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. End each review with a named next step.
Request only necessary access and provide a useful refusal path. Test camera, storage, and location functions with permissions both allowed and denied. Agree a secure handover process for accounts and source files.
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. Limit account access to the people who need it.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Set out the work, approval steps, and handover requirements in writing.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities