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. Leave the team with a decision, an owner, and a review date.
Prioritize frequent actions and keep input manageable. Test navigation, readable text, and interrupted tasks on real phones. Agree whether the evidence supports keeping, changing, or stopping the approach.
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. Keep private account details out of public briefs and examples.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Define the deliverables and exclusions before work starts.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities