The pilot must select a journey with verifiable input, decision and outcome while retaining the exceptions essential to that service.
Index
A product covering many activities can spend its first cycle on registration without showing that operations can complete a real request.
The rule that changes the scope
The pilot must select a journey with verifiable input, decision and outcome while retaining the exceptions essential to that service.
A configurable tool can test the process; custom code is justified when the differentiating experience or rules need validation.
Select the journey by the business risk requiring testing rather than the ease of drawing an attractive screen. A representative request must cross the process's most important decision. A pilot can use assisted operations in secondary steps if declared rather than presented as finished automation. Record remaining human effort when assessing later investment. Pilot closure is an evidence-based product decision, not a mandatory success badge after a demonstration.
Specify operational deliverables
- Choose a representative request and identify who submits, performs and checks the result.
- Limit exceptions to those preventing this journey from completing and defer independent modules.
- Record pilot evidence and the decision to continue, adjust or stop investment.
Test the exception before acceptance
In a hypothetical scenario, a request returns for correction during the pilot; the journey must resume service without repeating every registration step.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring an anonymized real request and the operational hypothesis requiring first validation.