01
15 minutesThe problem
- What specific task is the pilot targeting?
- How many times per week is this task done today?
- How long does each instance take today?
- What goes wrong with the current process?
Decision framework
Scoping an AI pilot in two hours: the worksheet.
Twenty questions across five sections. Fill it out with the team that will use the tool, not just the team that will build it. Walk into kickoff with shared assumptions written down.
The five sections
What you cover and how long each takes.
02
20 minutesSuccess criteria
- What does success look like at the end of the pilot?
- How will you measure success?
- What is the no go signal that tells you to stop?
03
20 minutesConstraints
- What data does the AI need access to?
- Is any of that data sensitive (PHI, privilege, trade secrets)?
- What systems must the AI integrate with?
- What is the budget ceiling for the pilot?
- What is the time horizon for the pilot?
04
15 minutesStakeholders
- Who reviews and approves before the pilot launches?
- Who is the daily user of the tool?
- Who reviews the output during the pilot?
05
20 minutesPath forward
- Are you building, buying, or hybrid?
- What is the kickoff date?
- What is the pilot review date?
- What is the criteria for moving from pilot to production?
- Who has signed off on this scope?
Run the exercise
The fillable worksheet.
Twenty questions, sized for a two hour session.
Markdown format with prompt examples for each question. Print it, fill it out as a team, sign it at the bottom. The signed worksheet becomes the contract for the pilot scope.
Download the worksheet (.md)How ByteWorthy uses this
The signed worksheet IS the kickoff.
We facilitate this exercise during 00-discovery for every Build engagement. The output goes straight into the project folder as the canonical scope document. Any change to scope after sign off becomes a deliberate amendment, not a quiet expansion.
A pilot fails when the team that uses the tool was not in the scoping conversation. This worksheet is the device that makes sure they were.