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. Limit account access to the people who need it.
Check maintained packages, permissions, licenses, and required device features. Dependencies need an upgrade and support plan. Keep a change log so later results have context.
Integration boundaries
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Agree which tasks are included and which need a separate quote.
Test representative devices, permissions, interrupted connections, and failed inputs. Define acceptance checks with the people who will use the product. Check the destination as well as the message that sends people there.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities