Find where context gets lost
Start with a specific incident: a request went missing, an approver did not see a document, or data was entered twice. An incident like this helps reveal the participants, inputs and expected outcome of the process.
Describe the outcome, not a list of screens
“Create a request form” describes an interface. “Understand who needs to decide and what happens next” describes a process objective. It makes it easier to identify roles, states and completion criteria.
Build a small, complete workflow
The first scenario should run from request to result. For example: a materials request, approval, delivery and receipt. This workflow lets you test how systems interact and get feedback from the people who will use it every day.
Test in real work
A pilot is about more than software bugs. You need to see whether statuses are clear, where manual transfer remains and what exceptions arise in practice. These observations define the next iteration.