Skip to content

Automate the process, not the mess

Automation makes a clear process faster and an unclear one worse. Do the tidying first.

It is tempting to point software at whatever hurts most. Yet a process full of exceptions, unwritten rules and steps nobody can explain will not improve when automated. It will produce the same confusion more quickly.

Write it down as it really happens

Sit with the person who does the work and record each step, including the workarounds. Note where information comes from, where it goes and who decides what. The written version is often the first time anyone has seen the whole process.

Remove before you automate

Ask of each step whether it is still needed. Approvals that are never declined, reports nobody reads and data captured twice can simply go. Every step removed is one that never has to be built, tested or maintained.

Then automate the rules

What remains divides into steps that follow rules and steps that need judgement. Automate the first group and give the second group better information. Plan for exceptions from the start: when the automation cannot proceed, it should hand the item to a person with the context attached.

Keep reading

Have a project in mind?

Tell us what you are trying to fix or build. The first conversation is free, and you will leave it with a clearer plan whether or not we work together.