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. Turn the findings into a short list of actions and owners.
Prioritize frequent actions and keep input manageable. Test navigation, readable text, and interrupted tasks on real phones. End each review with a named next step.
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. Confirm permissions before sharing customer information or assets.
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.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities