DEV Community

Before You Automate: A 30-Minute Process Audit

Automation projects fail less often because of tools and more often because the process was never described. A 30-minute audit is enough to decide whether a process is worth automating.

  1. Write the trigger. What event starts the process? An email, a form submission, a payment, a scheduled date?
  2. List the inputs and the output. If the output cannot be named, the process is not ready.
  3. Mark the decisions and exceptions. What happens when data is missing, a customer replies differently, or a document arrives in the wrong format?
  4. Measure the current cost. Hours per week, error rate, delay per step. If the number is small, fix the process manually first.
  5. Choose one narrow segment for a pilot: one request type, one document, one report.

A broader checklist for mapping a process before automation is here: https://sverdlov.pro/uslugi/ (the site is in Russian).

The goal of the audit is not to buy a tool. It is to find the one or two places where automation removes real work without breaking the neighbouring steps.

Top comments (0)