yukiha.Start a project
← Workshop journal

What Should Your Team Automate First?

Use a simple scorecard to pick the first workflow worth automating, then turn it into a small pilot your team can measure.

Every Friday, someone opens the same spreadsheets, chases the same missing figures and puts together a report the team has seen dozens of times. That job is a candidate for automation. To decide whether it should go first, compare it with the other recurring work your team handles.

Score three real workflows

Ask the person doing each job to describe the last time they did it. Write down what triggered the work, which tools they opened, where they made a judgment call and what they handed over. Then score each workflow on three measures.

  • Frequency. Give it 1 point for monthly or less, 2 for weekly and 3 for daily or more.
  • Hands-on time. Give it 1 point for under 15 minutes per run, 2 for 15 to 60 minutes and 3 for over an hour.
  • Consistency. Give it 1 point if most runs need a judgment call, 2 if exceptions are occasional and 3 if the same rules cover most runs.

In an illustrative team, the 90-minute weekly report scores 8 if the source files and checks are predictable. Daily inbox triage that takes 10 minutes and often needs judgment scores 5. Monthly invoice reconciliation that takes 90 minutes and has occasional exceptions scores 6. Reporting is the best first candidate on this scorecard.

Pilot the part you can verify

Start by pulling the source figures into a report draft. If a source is missing, flag it for the owner. Keep the current approval step and run both processes for two reporting cycles. Record how many minutes the reviewer spends, what they correct and whether the report still goes out on time.

A workflow can score well and still need groundwork. Before building, confirm who owns it, whether the source systems can supply the data and who will handle exceptions. A named owner makes it much easier to tell whether the pilot is doing its job.

Have a recurring workflow in mind? Discuss a project with Yukiha and share the inputs, tools and handoffs involved.

Browse all notes