Keep permissions proportionate
Ask only for access needed by a defined feature. Explain the reason at the appropriate time and provide a useful path when a user declines an optional permission. Agree how sensitive material will be shared and stored.
Check maintained packages, permissions, licenses, and required device features. Dependencies need an upgrade and support plan. Record the starting conditions so comparisons remain fair.
Integration boundaries
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Separate essential work from optional additions in the proposal.
Test representative devices, permissions, interrupted connections, and failed inputs. Define acceptance checks with the people who will use the product. Verify the next step while there is still time to correct a problem.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities