
Acceptance and support
Use task-based checks for the release and agree responsibility for later operating-system changes. Maintenance belongs in the project budget. 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. End each review with a named next step.
- A written brief
- Named responsibilities
- Agreed review points




