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. Agree whether the evidence supports keeping, changing, or stopping the approach.
Explain device permissions when the related feature is used. The app should handle refusal without confusing the user. Keep a record of permission for any customer story used publicly.
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. Review consent and privacy requirements before adding tracking.
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