Test the ordinary and the awkward
Use representative tasks, incomplete inputs and failure cases. A successful demonstration on one example does not establish performance across a workflow.
Make ownership explicit
Identify who owns the data, the integration, the acceptance decision and the running system. Give operators a route for reporting errors.
Plan for dependencies
APIs, permissions and model behaviour can change. Include recovery paths, monitoring and a way to assess a change before rolling it out.
Define acceptance
Agree the quality, cost and operational criteria for launch. Document the known boundaries and the process for managing exceptions.