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. Keep private account details out of public briefs and examples.
Check maintained packages, permissions, licenses, and required device features. Dependencies need an upgrade and support plan. Keep the original result alongside the updated version.
Integration boundaries
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.
Test representative devices, permissions, interrupted connections, and failed inputs. Define acceptance checks with the people who will use the product. Confirm that forms, phone links, and replies reach the right person.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities