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. Keep the next round of work small enough to assess clearly.
Prioritize frequent actions and keep input manageable. Test navigation, readable text, and interrupted tasks on real phones. Keep the next round of work small enough to assess clearly.
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. Use only the customer information needed for the agreed work.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. List the required outputs before setting the delivery schedule.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities