Why the first process matters

A first project teaches the team how to describe work, make rules explicit and test a change without disrupting everything else. That is why a smaller, well-defined process is usually a better starting point than a broad promise to “digitise the business”.

Choose a process that is frequent, understood and worth improving. A process can be valuable even when it is not the most visible source of frustration.

Compare four practical signals

  • Frequency: the task happens often enough for a simpler workflow to matter.
  • Impact: it affects customer response, reliable records, team time or a meaningful operational decision.
  • Clarity: the normal steps and common exceptions can be explained with a real example.
  • Ownership: one person can confirm the current rules and decide whether the result is useful.

Use a simple first score

List a few candidate tasks and give each one a simple low, medium or high rating for frequency, impact, clarity and ownership. A task with high frequency but unclear rules is not automatically the best first project. It may first need a clearer manual procedure.

Good first candidate

A recurring enquiry, document handover or report where the same information moves through known steps.

Needs more discovery

A broad complaint such as “our admin is chaotic” without a shared view of what happens first.

Needs a manual fix first

A task whose rules change every week or depend on undocumented personal judgement.

Worth delaying

A rare process where improvement would consume more effort than the time it saves.

Observe one real example

Before choosing technology, follow one item from the moment it arrives until the work is complete. Note each handover, copied field, wait, approval and place where someone searches for information. The record does not need to be formal; it only needs to reflect the work that actually happens.

This observation often reveals that one small connection between existing tools is more useful than replacing an entire system.

Define success before work starts

  • Choose two or three measures such as minutes per item, time to first response, number of manual transfers or missed follow-ups.
  • Set a boundary for what the first version will not handle yet.
  • Agree who tests the result and who can approve the next step.

Want a second view on your first candidate?

Bring one real example of the work as it happens today. We can identify the smallest practical change before discussing a larger project.

Discuss your workflow