In 30 seconds

A workflow that was worth building may not stay worth running. Periodically weigh the value it delivers against its real cost, including maintenance and errors. If the balance no longer holds, changing or retiring it is a good decision, not a failure.

Why this comes up

Workflows accumulate. Each one seemed worthwhile when built, and none is ever quite reviewed for whether it still earns its place. Over time you can end up maintaining systems that deliver little, cost attention, and quietly carry risk. Measuring value against cost keeps your effort where it matters.

Measure the value

Value is whatever the workflow was meant to deliver. Estimate it honestly:

  • Time saved, or work handled that would otherwise need people.
  • Errors or delays avoided.
  • Better outcomes: faster responses, fewer complaints, more consistent decisions.

You do not need precision. You need enough to say whether the value is large, modest or negligible, and whether it is holding up or fading.

Measure the real cost

Cost is more than the obvious running fees. Include:

  • The service or model costs to run it.
  • The maintenance effort: reviews, fixing failures, keeping knowledge current.
  • The cost of its errors, weighted by how bad they are. See how to think about the cost of errors.
  • The attention it takes from the owner and the team.

A workflow that needs constant babysitting can cost more than the manual process it replaced.

Compare, and be willing to stop

Put value and cost side by side. Most workflows fall clearly into "worth it" or "not." For the marginal ones, ask whether a change, narrowing scope, simplifying, improving a source, would restore the balance, or whether it is time to retire it.

Stopping is a valid, healthy outcome. A workflow that no longer earns its place should be retired cleanly, not left running out of habit.

A small example

A team reviewed an AI step that flagged unusual orders. It caught a few real issues but produced many false flags that staff spent hours dismissing, and it needed frequent tuning. The cost outweighed the value. They narrowed it to only the highest-risk orders, which restored the balance, and would have retired it otherwise.

What this does not solve

Measuring value against cost tells you whether to keep, change or stop a workflow; it does not make a struggling one succeed. It is a decision tool, used regularly, that keeps your portfolio of workflows honest and your effort focused. See the monthly production review checklist.

Good enough to move on when

  • The workflow's value is estimated honestly.
  • Its full cost, including maintenance and errors, is estimated.
  • Value and cost have been compared.
  • A clear decision, keep, change or retire, has been made.