Skip to main content
Boermans Digital
Main menu

Best practiceAutomation

Choosing and scoping your first automation pilot

A process has been selected and the first ideas are on the table. Suddenly the trial is expected to cover several departments, exceptions and applications. A pilot is more useful when it has a clear uncertainty to resolve and explicit boundaries.

A guide to choosing your first automation pilot.

Define the question the trial should answer

A pilot should investigate something specific. For example: can existing order data be transferred without increasing the checking workload? That is clearer than proving that automation works. Agree what observations will support the next decision.

Set a start and finish. Preparing a proposal may be in scope while final posting deliberately remains manual. Identify customer groups, document types and applications that are not included.

A small fictional pilot canvas

On a narrow screen, scroll the table sideways. With a keyboard, focus the table and use the arrow keys.

Example for preparing an order, not a prescribed delivery schedule.
AreaBoundaryStill to establish
ProcessOne order type with existing product codesDoes ordinary input fit the rules?
ActionPrepare a proposal without final postingCan the reviewer spot errors?
ExceptionRoute missing information to a work queueDoes it reach the right owner?
DecisionContinue, revise or stop after reviewAre quality and remaining effort acceptable?

Include exceptions without solving everything

Choose permitted samples representing ordinary variation. Add missing information, repeated requests and uncertain outcomes deliberately. A case may be handed to a person during the trial; every exception does not need an automated solution.

Record out-of-scope cases separately. Otherwise the trial may look better because difficult inputs are ignored, or worse because new requirements are continually added.

Agree the environment and responsibilities

Use a suitable test environment where possible. Limit permissions to necessary actions and decide who may use the test data. A trial must not quietly change real orders, customer records or payments. If production testing is necessary, obtain explicit approval and agree a limited scope and recovery arrangements first. Establish who can pause the trial and who approves configuration changes.

Distinguish the people building the solution, the process owner and the reviewers assessing the results. An enthusiastic demonstration does not replace substantive acceptance by the responsible party.

Agree when to stop or change course

  • Unauthorised changes require an immediate stop and investigation.
  • Untraceable outcomes need better controls first.
  • Additional correction work may outweigh the expected benefit.
  • Missing operational ownership prevents a sustainable handover.

Set process-specific quality requirements. Do not use a universal pass rate without considering the consequences of errors.

A successful trial starts another decision

Compare the results with the original question. Record what has been demonstrated, what remains uncertain and which controls are still needed. Production may require further work on maintenance, monitoring, licensing and fallback arrangements. A reasoned decision not to proceed can also be a valuable pilot outcome.

What would you like to clarify?

Describe the process step or open question. We can explore a practical next step together.

Discuss your process

Explore your process with the Automation Scan

Adapt this framework to your systems and responsibilities. It is not a guarantee of safety, availability or readiness.

Editorial work with AI assistance. Content reviewed by Joshua Boermans in the week of 12 October 2026.

Earlier editorial notes

These notes describe previous revisions. The review above applies to the content Joshua checked in version V4.48; it is not independent validation.

Boermans Digital editorial content, prepared with AI assistance.

Approved for publication by Joshua Boermans on 3 October 2026.

A subject-matter review, including the reviewer, date and scope, has not yet been recorded.

Publication approval is not independent subject-matter validation. No independent review has been recorded.

An original Boermans Digital process framework. Subject-matter expert review is still pending.

Boermans Digital / privacy

Your cookie preferences

You decide whether Google Analytics may load. The website, scans and calculator also work without Analytics.

Completed fields, scan answers and calculator results are not sent to Analytics.

Which data and retention periods?

We remember your choice on this device for up to 180 days, including a refusal. The _ga and _ga_* Analytics cookies are configured for up to 180 days. Retention at Google is configured separately in the Analytics account.

Storage for website functionsFunctional

The website remembers your privacy choice. Only when you choose to switch language can scans, the guide and calculator temporarily carry answers within the same tab. Contact details are not stored in that transfer.

Contact form protectionAt request review

Google reCAPTCHA loads when you open the review of your completed request. Google then processes technical data and may use security cookies. This is separate from your Analytics choice. Contact by email remains available.

Analytics is off.