Sign in or create a free account to save this Card to your Deck.

Practice Card · Evidence of progress

Design operating work before tool selection

DESIGN THE WORK BEFORE BUYING THE AUTOMATION.

Automation works best when the business has already defined the job the automation is meant to perform. If purpose, ownership, inputs, decision rules, exceptions, acceptance criteria, and handoffs remain ambiguous, technology usually makes the ambiguity faster and harder to see. Process design does not require every detail to be perfect before a pilot begins. It requires enough clarity that the team can tell what the system should do, where human judgment remains necessary, and how it will know whether automation improved the work.

Expanded teaching

Expanded teaching

Describe the work before the software

Write the operating job in business terms. Identify the trigger, input, owner, major steps, output, customer or internal recipient, acceptance standard, and the point where the work is complete.

Make exceptions visible

Routine happy-path automation is easy to demo. Operating reliability depends on what happens when information is missing, a customer requests an exception, confidence is low, a deadline changes, or a consequential decision requires approval.

Clarify human decision rights

Mark where people must review, approve, negotiate, interpret ambiguity, protect sensitive information, or accept completed work. An automation flow should not silently acquire authority because the software is technically capable of taking an action.

Redesign before automating waste

Remove unnecessary steps, duplicate entry, unclear handoffs, and approvals that add no value before encoding the process. Automation should operate the improved design rather than preserve every historical habit.

Where AI can help

AI can interview process owners, draft process maps, identify missing rules, compare alternatives, and simulate exception cases. Staff who perform and own the work verify the map and decide the authorized workflow.

Then select the tool

Once the process is sufficiently defined, compare tools against required capabilities, integrations, permissions, reliability, cost, and the evidence needed from a pilot. The software decision becomes simpler because the work has already specified what it needs.

Diagnostic inquiry

Questions to ask, not conclusions

Could two competent people describe and execute the work consistently enough that you can state what an AI or automation system should do, where it should stop, and how success will be judged?

Questions that distinguish possible explanations

  • Which exceptions currently force employees to improvise?
  • Where is human approval or judgment required even if the technology could act automatically?
  • Which current step should be removed or redesigned rather than automated?

Practical application

Practical application

Choose one workflow being considered for AI. Map its trigger, inputs, owner, steps, exceptions, decision rights, output, and acceptance criteria. Remove one unnecessary step or weak handoff, then write the tool requirements from the redesigned process.

Ask Atria

Talk through this Card

Talk it through with us

If this Card describes your week, a free conversation is the fastest way to see what it means for your company and what to do next.

Book a free conversation