Codrison — Code to Rise
Home/Insights/Operations
Operations

Trace the process before you automate it

Two weeks of watching how work actually happens will change what you build. It usually shrinks it.

Muhammad Faizan · 9 June 2026 · 7 min

Written byMuhammad FaizanCodrisonShare: LinkedIn · X

Clients ask us to automate a process. We ask to watch it for two weeks first, and the request almost always changes.

A process trace records every step, exception and handoff with timings. Written down, most processes reveal steps that exist only because a previous system could not do something — steps that should be deleted rather than automated.

The trace also surfaces the exceptions, which is where automation projects go to die. If 18% of cases are exceptions and the plan only handles the happy path, the project will not deliver its business case.

The output is a map with three colours: automate, keep human, delete. The deletions are usually the cheapest win on the page.

If you cannot measure the change, you cannot defend the system that caused it.

If this is the kind of problem you are working on, we are usually happy to compare notes — even when it does not become an engagement.

Get in touch

Let's work on something that has to work.

Contact us