Decision standard

What should stay human in an efficient workflow?

Efficiency is not the same thing as removing people. A good workflow makes routine work easier while keeping judgment, accountability, and care in the right hands.

Four choices

Choose the kind of change before choosing a tool.

Automate

The task repeats, the inputs are stable, the result follows a clear rule, and a mistake is easy to detect or reverse.

Example: Moving a completed form into a project record after required fields are present.

Standardize

The work varies enough that a person still does it, but the starting information, order of steps, ownership, and handoff can be made consistent.

Example: A client-intake checklist that makes sure the right facts arrive before a specialist reviews them.

Delegate

The task needs context and care, but it does not require the owner’s particular authority or relationship.

Example: Preparing a routine report from an agreed template and reviewing obvious gaps before it goes out.

Keep human

The decision changes a customer relationship, carries a meaningful consequence, handles an unusual exception, or depends on judgment that cannot be reduced to a reliable rule.

Example: Responding to a distressed customer, approving a material exception, or deciding what a pattern means for the business.

Before you automate

Ask questions that reveal whether the process is ready.

If a process fails these questions, map and improve it first. Software can move a broken process faster, but it cannot make the underlying rule clearer.

  1. 1

    Is the process stable enough to describe step by step today?

  2. 2

    Are the required inputs complete and in one place?

  3. 3

    Can a wrong result be caught and reversed before it matters?

  4. 4

    Does the task require authority, empathy, negotiation, or professional judgment?

  5. 5

    Would the customer or team understand who remains accountable after the change?

Accountability does not disappear

Keep a person responsible for outcomes that matter.

For sensitive information, meaningful customer exceptions, financial or legal consequences, and decisions that change a relationship, the workflow should name the human reviewer and the point at which that person steps in. This is an operating standard, not legal, financial, security, or compliance advice.

A practical rule

Use automation to prepare, route, summarize, and flag routine work. Keep people responsible for interpretation, exceptions, approvals, and the final decision when the consequence is meaningful.

Use the automation decision framework

Need a decision about one real workflow?

The Workflow Review examines one agreed process and helps you decide what to standardize, delegate, automate, or keep human.

See the Workflow Review method