Control the maintenance burden
Frameworks, libraries, devices, and operating systems change. Document dependencies and update responsibilities so ongoing compatibility is part of the plan rather than an unexpected expense. Agree whether the evidence supports keeping, changing, or stopping the approach.
Handle duplicate requests, edits, permissions, and audit needs. Confirm how records are recovered after a failed operation. Review the evidence behind a recommendation, including its limits.
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. Limit account access to the people who need it.
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