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. Agree whether the evidence supports keeping, changing, or stopping the approach.
Document what existing apps fail to provide and which custom steps are essential. Build around the user task rather than novelty. 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. Agree a secure handover process for accounts and source files.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Confirm the output, owner, and review date for each task.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities