STAGE 06 / CHAPTERS 19-20
Pilot and accept
Observe a bounded live use, learn from the work, and separate software acceptance from permission to expand.
THE WORK TO DO
- 01
Choose participants, provider/date inventory, support coverage, and conditions for stopping or pausing enrollment.
- 02
Keep one process authorized to write the transferred schedule. Observe complete tasks and record any help people need.
- 03
Correct findings and inspect the current candidate. Make acceptance and opening decisions from their own evidence.
WHAT YOU LEAVE WITH
A pilot record, observations, corrections, acceptance results, and explicit operating gaps.
BEFORE MOVING FORWARD
The next audience has the required protection and coverage. Existing commitments remain supported.
The service provider's lunch break reveals a problem in the daily view. A bounded pilot gives the team a chance to correct it before wider use.
WHO DOES WHAT / STAGE 06
Watch real work within a controlled boundary.
Senior Administrator
Coordinates staff work and records misunderstandings.
Designer
Observes whether people can finish without coaching.
Analyst
Distinguishes a confusing screen from an incorrect rule.
Tester
Rechecks corrections on the pilot candidate.
Client
Accepts the agreed results and decides priorities.
THE HANDOFF
Pilot observations + repeat checks → accepted scope
Customers and service providers try the tasks. The Senior Administrator brings observations back; the team corrects the cause and repeats the affected checks.
Work with: Project Manager, Tech Lead, Frontend Developer, Backend Developer, Support Specialist.
Additional expertise when the work needs it: User Researcher, UX Designer, Product Analyst.
See the team across all eight stages →