Skip to content

Not every process is worth automating. Here is how to spot the ones that are, and what to fix before you write any code.

Custom Software Development1 min read

Automation is easy to sell and harder to get right. A process that is slow because it is unclear will still be unclear once software runs it, only faster. Before deciding what to automate, it pays to understand why a process hurts in the first place.

Look for the repeatable work

The best candidates are tasks that follow the same steps every time, rely on information that already exists in another system, and are done often enough that the minutes add up. Re-keying data from emails into a spreadsheet, chasing approvals and building the same weekly report are classic examples.

  • The steps are the same each time, with few exceptions
  • The inputs are already digital, even if they are scattered
  • Mistakes are costly or slow to find
  • The people doing it would rather be doing something else

Fix the process before the software

Map the process as it really runs, not as the policy document says it runs. Talk to the people who do it every day. You will often find steps that exist only because of a system limitation that disappeared years ago. Removing those is free; automating them is not.

Start small and measure

Pick one process, agree what better looks like, and automate that end to end. A working result in a few weeks builds more confidence than a grand plan, and it tells you what the next process should be.

All insights