Skip to main content
To the method

Self-check: is this workflow worth automating?

13 questions about a single workflow, in five steps. At the end you see right away how well it suits automation, how much time it takes today and what to settle first.

about 5 minutes
13 questions in 5 steps
instant
Short result without email
free
No call, no sign-up

You see the short result without an email address. If you want the detailed report, I send it to you by email. You only decide that at the end.

Step 1 of 5 · Workflow

  1. Workflow
  2. Frequency
  3. Time
  4. Rules
  5. Systems

Which workflow is it about?

Pick a single workflow, ideally the one that annoys your team most.

What kind of workflow is it? *
How large is your company in total?

This shows whether the effort pays off at your size.

What the self-check asks, and why.

The self-check looks at exactly one workflow, not your entire company. Across five steps it asks how often the workflow runs, how much time it takes, whether there are fixed rules and how far the data is digital. From that come a fit score out of 100, a maturity level and a placement by impact and effort.

  1. 1/5Which workflow is it about?

    Pick a single workflow, ideally the one that annoys your team most.

    Name of the workflow
    e.g. incoming invoices, order intake, dunning
    What kind of workflow is it?
    Core business (How you earn money: orders, delivery, customer service), Supporting (Keeps the business running: accounting, HR, IT), Steering (Planning, quality, compliance).
    How large is your company in total?
    This shows whether the effort pays off at your size.
  2. 2/5How often does it run?

    A rough estimate is enough. The order of magnitude is what matters.

    How often does the workflow run?
    Daily, Weekly, Monthly.
    Number of runs per day
    Example: 10 invoices per day means 10.
  3. 3/5How much time goes into it?

    Use the average, not the worst day.

    Minutes per run
    How long does a single run take on average?
    People involved per run
    How many people touch a run on average?
    Hourly rate per person (optional, to calculate in euros)
    Fully loaded cost including overhead. Left blank, we calculate in hours only.
  4. 4/5Are there fixed rules?

    Software can only repeat what runs the same way every time.

    Is the workflow written down anywhere?
    Yes or no. Without a description there is no reliable basis for what would be automated.
    Are there clear rules for who does what, when?
    Yes or no. Rules that live only in people's heads cannot be turned into an automated workflow.
    How often does something go wrong? (1 = hardly ever, 5 = constantly)
    Frequent errors raise the value of automating and at the same time the effort for edge cases.
  5. 5/5Where does the data live?

    Only what is digitally reachable can be automated.

    Do all steps involved run digitally?
    Yes: All digital. No: Partly on paper.
    Are there many exceptions and special cases?
    Yes: Many exceptions. No: Mostly the same.

How the result is produced.

Three figures are calculated from your answers: the maturity of the workflow, its position between impact and effort, and a fit score that condenses both into one number.

Maturity

Maturity describes how reliably a workflow runs today. At level 1 automating does not pay off; it would only speed up the mess.

Level 1: Different every time
No fixed rules, everyone does it their own way
Level 2: Written down
The workflow is described but not always followed
Level 3: Consistent
Runs by the same rules every time
Level 4: Measured
Time and errors are counted
Level 5: Continuously improved
Re-measured and adjusted regularly

Impact and effort

Not every automatable workflow deserves to be tackled first. Impact and effort produce four fields:

Start here
High impact, little effort. This is where you begin.
Larger project
High impact, but also high effort. Worth it, but needs planning.
Can wait
Little impact. Look at it again later.
Better leave it
High effort, little impact. Ask instead whether the workflow needs to exist in this form at all.

Fit for automation

The fit score condenses every answer onto a scale from 0 of 100. The five bands mean:

Very well suited
The workflow is well prepared: fixed rules, digital data, enough repetition. Before automating, still check which step could go away entirely.
Well suited
A good candidate. Close a few gaps first so the automation does not get stuck on exceptions.
Suited after groundwork
Possible, but only after groundwork. Usually fixed rules are missing or there are too many special cases. Settling that often helps even without software.
Prepare first
Tidy up first. Set rules, cut steps, make data digital. Automated today, the workflow would just get messy faster.
Not suited yet
The workflow is not there yet. It runs differently every time or depends on paper. Start with a simple description of who does what, when.

What you get at the end.

The result is an assessment, not a quote. Right away and without an email address you see the short result: fit, maturity, the time the workflow takes today and what to settle first. If you want, you get the detailed report by email. Typical points in it:

  • Write the workflow down the way it really runs today
  • Set clear rules: who does what, when
  • Find out where it gets stuck: log disruptions for a week
  • Cut unnecessary steps before automating
  • Make paper and in-between steps digital
  • Find and fix sources of errors
  • Group special cases or give them their own path
  • Check which steps software can take over
  • Decide how you measure success, and re-measure

No warranty: The values are based on your own answers and simple rules of thumb. They are a first orientation, not a forecast. They only become reliable with real numbers from your day-to-day work.