Skip to content
Redesign the Work Before You Automate It
AI

Redesign the Work Before You Automate It

Tony Ruiz
Tony Ruiz

No team enjoys hearing that its process is fragmented. Yet most important business workflows have accumulated years of approvals, spreadsheets, email handoffs, duplicate checks, and unofficial shortcuts for understandable reasons.

Adding AI on top can make the same work move faster without making it better.

This is why workflow redesign is becoming the real dividing line in enterprise AI. McKinsey's 2026 survey found that AI high performers were distinguished by fundamentally redesigning workflows instead of inserting AI into existing ones.[^2] Microsoft's 2026 Work Trend Index reached a related conclusion: organizational factors such as culture, manager support, and talent practices accounted for twice the reported AI impact of individual effort alone.[^3]

The technology matters. The shape of the work matters more.

Map the real workflow

Do not begin with the official procedure. Follow one real case from request to outcome and capture:

  • decisions and their owners;
  • data created, copied, or corrected;
  • systems read or updated;
  • approvals and exceptions;
  • waiting time between steps; and
  • rework when information is missing or wrong.

Ask the people doing the work where they use judgment and where they simply compensate for a weak system. That conversation often identifies more value than the first model demo.

Remove before you automate

For every step, choose one action:

  1. Eliminate it if it no longer protects or creates value.
  2. Simplify it if policy or process complexity is self-imposed.
  3. Standardize it if inconsistent inputs create avoidable work.
  4. Automate it deterministically if rules are stable and explicit.
  5. Use AI if interpretation, synthesis, or variable language genuinely matters.
  6. Keep human judgment where context, accountability, empathy, or consequence requires it.

This prevents a common mistake: using a probabilistic model for work that a form, validation rule, or API could handle more reliably.

Design the handoffs

The new workflow needs more than boxes labeled “human” and “AI.” Define what information crosses each handoff, how uncertainty is shown, who can approve or override, and what happens when the system cannot proceed.

A useful pattern is:

AI prepares → deterministic controls verify → a person decides when risk requires it → the system records the outcome.

For lower-risk work, the person may review exceptions rather than every case. For higher-risk decisions, AI may organize evidence while authority remains clearly human.

Measure the whole journey

Compare total cycle time, wait time, rework, first-pass completion, customer effort, employee effort, and cost per completed case. A local step may become faster while the customer still waits three days for the next queue.

The best AI project may remove half the workflow before automating what remains. That is not less ambitious. It is a better operating design.

Cayru combines product discovery, AI Product Engineering, modernization, and platform work to redesign one meaningful workflow and implement the smallest reliable system around it.

Map one workflow end to end before choosing the agent, model, or platform.

Share this post