Planning a supervised pilot

How to choose your first workflow automation pilot

Start with a process your team repeats, understands, and can measure. A useful first pilot has a clear beginning, a specific finished result, and someone responsible for deciding whether it works.

Choose a bounded process

Describe the workflow in one sentence: when a request arrives, the operator checks the required details, prepares a record, obtains approval, and verifies the result. If the description includes several departments and unrelated outcomes, reduce the scope.

Email intake into a reviewed CRM record can be a candidate. It is only a suitable pilot if the team has approved access, known field mappings, and a way to identify exceptions. Do not assume an application is supported before technical assessment.

Compare candidates with five questions

1. Repeatability: Can the team describe the normal sequence and the common exceptions?
2. Volume: Does the process occur often enough to observe comparable examples during the pilot?
3. Ownership: Is one person accountable for the workflow and acceptance decision?
4. Control: Can consequential actions pause for approval, and can mistakes be detected and recovered?
5. Measurement: Can you record operator time, correction work, and a verified finished result?

Write down what the pilot will not do

For an intake pilot, the initial scope might end at an approved CRM record. Billing, customer communications, scheduling, and changes to historical records can remain separate. A narrow boundary makes the acceptance decision easier to assess.

Prepare the inputs before access is granted

• A workflow owner and the people who currently perform the work.
• A sample process with sensitive details removed.
• The systems involved, required permissions, and approval rules.
• Examples of missing information, duplicate requests, and conflicting records.
• An agreed definition of a completed and correct result.

Share only a high-level description through the public inquiry. Arrange credentials and operational data through an agreed onboarding process.

Decide when to postpone automation

Postpone a pilot when nobody owns the process, the team cannot agree on the correct result, or changes cannot be checked. Resolve those gaps first. Automation will not settle an unresolved business rule.

Next, define how you will measure savings and where human approval is required.