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. Record the decision as well as the numbers behind it.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Agree how new requests will affect cost and timing.
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. Agree how sensitive material will be shared and stored.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Confirm the output, owner, and review date for each task.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities