Plan for interrupted use
Connections fail, sessions expire, and users leave tasks unfinished. Decide what happens to pending work and show clear recovery steps instead of assuming every action succeeds immediately. Use dated records rather than relying on memory at the next review.
Prioritize frequent actions and keep input manageable. Test navigation, readable text, and interrupted tasks on real phones. Name an owner for each task so requests do not get lost.
Make the plan fit your market
Discuss whether users in Oakland need appointments, field-service access, local inventory, or delivery features. Use the actual workflow to decide whether location data is necessary; do not request device permissions merely because the app serves a local market. Check the areas you genuinely serve in Oakland, CA.
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Keep private account details out of public briefs and examples.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities