Write a pilot scope that can actually finish
Bound one useful result, exclusions, owners, evidence and the decision that follows.
Start with the decision
- Name the decision the pilot supports and the smallest workflow that can produce useful evidence.
- Do not call discovery, setup or an open-ended prototype a pilot without a defined finish.
Keep the boundary visible
- List users, inputs, systems, environments and explicit exclusions.
- Separate pilot behavior from production reliability, scale, security operation and ongoing support.
End with evidence
- Attach an evidence method to each acceptance criterion.
- Define who reviews the result and what happens when evidence is incomplete or mixed.
Keep the result reusable
The engagement studio carries the same workflow identity into six reviewable artifacts. It does not send a request, select a vendor, create a contract or approve a purchase.