THE STARTING POINT
Choose practical evidence before deciding whether to extend a change.
Understand the starting process.
Record how the selected workflow operates before the pilot, including the conditions and exceptions that affect it. Choose observations relevant to the problem being addressed. Avoid comparing a carefully supported pilot with an undocumented baseline and then attributing every difference to the new tool.
Agree the evidence and limits.
Define what the team will review, who will collect it and how much participation is needed to understand the workflow. Include user feedback and operational issues alongside any agreed measures. Document what the pilot cannot establish, especially when only a small part of the process is included.
Make expansion a separate decision.
Review the findings with the workflow owner and identify unresolved requirements. Decide whether to adjust, repeat or extend the pilot. A positive demonstration does not remove the need to plan wider support, integration and adoption before other teams begin depending on the change.
TAKE THE NEXT STEP
Your discovery checklist
- Document the current process and its conditions.
- Agree observations, feedback and pilot limitations.
- Review support and adoption before extending the scope.