How to choose your first workflow to improve.

What makes a good first workflow?

Start with recurring work that has a clear beginning, a useful output, and someone who can check the result. Choose a task small enough to try on representative examples before relying on the new process.

“Improve operations” is too broad to scope. “Prepare each supplier invoice for the right approver” gives you a starting point and an end point. It also leaves room to decide which steps need better instructions, fixed rules, AI assistance, or human judgment.

List two or three candidates with the people who do the work. Look for repeated chasing, retyping, searching, or handoffs. The most frustrating task may still need a clearer owner or better information before it is ready to automate.

Is the task ready to improve?

Use these questions to compare candidates. An unanswered question is a piece of preparation work, not a reason to buy more software.

Does it happen often enough to observe?

Record frequency, the effort per occurrence, and where work waits. Include corrections and chasing, not just the first pass.

Can you describe “done”?

Name the trigger, the output, the owner, and the next recipient. If people disagree, settle the process first.

Do you have representative inputs?

Gather permitted examples of ordinary work and exceptions. Note missing information, inconsistent formats, and where the authoritative record lives.

Can you explain the rules?

Separate repeatable rules from decisions that depend on context. Identify who handles an exception when the rules do not fit.

Can a person check it before it matters?

Define a review point before a message is sent, a record is changed, or a payment is authorized. Consider how a mistake would be noticed and corrected.

Is the information appropriate to use?

Confirm who may access the inputs and which tools are approved for them. Use sample or redacted material while resolving access and data-handling questions.

Can you tell whether it improved?

Choose a baseline and a small set of checks, such as time spent, waiting time, corrections, and whether the intended outcome was completed.

Choose a candidate when the scope, owner, sample inputs, review point, and success checks are clear. Prepare those pieces first when they are missing. Delay work whose consequences cannot be adequately reviewed or contained.

Does the step need AI, automation, or a clearer process?

Make this choice for each step. A workflow does not need the same kind of help from beginning to end.

Check what your existing software can do before adding a tool. Compare the effort to maintain the new process with the problem it addresses.

Two possible starting points.

These are illustrative situations, not customer results.

Write a one-page workflow brief.

Copy these prompts into a document and complete them with the people who know the task. Describe today’s process before designing the next one.

1. The task: What starts it, and what counts as done?
2. The people: Who owns it, contributes information, reviews work, and decides?
3. The current steps: Where are the tools, handoffs, delays, and repeated effort?
4. The inputs: Which examples and source records may we use?
5. The rules and exceptions: What is predictable? What needs a person?
6. The checks: What would make an output unacceptable? Who stops or corrects it?
7. The comparison: What will we measure before and after, over the same kind of work?
8. The ongoing owner: Who updates instructions and responds when something changes?

Try ordinary examples alongside missing information, conflicting details, and an unavailable approver. A first version is ready to use when the agreed checks pass and the team understands how to handle exceptions.