Pick one repeatable unit of work
Start with a task you can describe in a sentence: preparing a proposal, responding to an inquiry, onboarding a client or producing a weekly report. A broad goal such as “make operations efficient” is too vague to measure. Write down the trigger, the person responsible, the intended output and what counts as completion. Choose a workflow that occurs often enough to observe, but is small enough to change without redesigning the business.
Follow the work, not the organization chart
Watch one real example from start to finish. Record where information comes from, where it is copied, who checks it and what happens when it is incomplete. A spreadsheet may not be the problem; the problem may be that nobody knows which row is current. A slow approval may be caused by unclear decision rights rather than a missing app. Keep the first map simple: trigger → input → action → handoff → result. Record exceptions beside the main path instead of pretending every case is identical.
Name the failure at the handoff
For each handoff, ask what the next person needs and whether it arrives in a usable form. Look for duplicate entry, waiting for missing context, unclear ownership and repeated clarification. Separate active work time from elapsed time. A task that takes fifteen minutes of work but waits three days for approval needs a different intervention from one that takes three hours of repetitive entry. Do not use a single optimistic number as your baseline; observe a small representative sample and note its limitations.
Simplify before choosing software
Remove steps that no longer serve a purpose. Standardize the inputs with a short checklist or template. Decide who owns the work and how an exception is escalated. Only then ask whether automation would help. Automating an unstable process makes its mistakes faster. Prefer the smallest change that addresses the actual friction, such as one shared intake format or a single status field, rather than replacing every tool at once.
Run a bounded experiment
Write down the expected improvement, the observation period and a rollback route. Measure the same task before and after the change. Include review time, exceptions and maintenance, not just the time saved by a script. A good pilot can also reveal that automation is not worthwhile. Record that result; avoiding an unnecessary subscription is a useful outcome. The free workflow-audit canvas below provides a client-independent starting point. Keep sensitive details in your own approved system.
Download the free canvasDrafted with AI assistance and prepared as general operational guidance. This is not legal, regulatory or individualized professional advice. Use your own approved systems for confidential information.