Method

A practical method for turning AI ideas into operating workflows

Most companies do not need another impressive AI demo. They need a way to decide which workflow is worth changing, where AI should assist, where humans should review, and how success will be measured.

First, in plain business language

First, in plain business language

The method uses AI terms only when they are useful. The real question is simpler: which part of the work is painful, repeatable, risky, and worth improving?

Workflow

A piece of work that moves from request to decision to output.

Example: a customer question arrives, someone checks policy, writes a reply, and records the outcome.

AI pilot

A small test on one real workflow, not a company-wide transformation project.

Example: test AI on one support category for four weeks before expanding to the whole inbox.

Human review

A clear point where a person checks AI's work before it affects customers, money, compliance, or trust.

Example: AI drafts the answer, but a service lead approves replies about refunds or contracts.

Operating model

The practical agreement about who owns the workflow after launch.

Example: who updates the source documents, checks quality, handles exceptions, and decides whether to expand.
Why the method starts with workflow

Why the method starts with workflow

Recent research points in the same direction: companies that see more value from AI are more likely to redesign workflows, define human validation, and create leadership ownership. The issue is rarely only model quality. It is whether AI fits the operating process.

MIT NANDA: the GenAI Divide

The 2025 report describes a sharp divide: many pilots show no measurable return, while a small group of integrated pilots extracts value by fitting tools to specific processes and business outcomes.

MIT NANDA / State of AI in Business 2025

McKinsey: high performers redesign workflows

McKinsey's 2025 global survey found AI high performers are nearly three times as likely as others to fundamentally redesign workflows, and more likely to define when model outputs need human validation.

McKinsey State of AI 2025

Deloitte: scaling still depends on governance and risk

Deloitte's enterprise GenAI research highlights that regulation, risk management, data quality, and workforce concerns remain barriers, especially as more AI systems can take multi-step actions.

Deloitte State of Generative AI
The three-layer method

The three-layer method

1. Workflow Fit

Should this workflow use AI at all?

We first evaluate repetition, volume, cost pressure, pattern clarity, source material, input quality, risk, human review, integration, measurement, and ownership.

Example: A support inbox with repeated policy questions is usually a stronger first candidate than a once-a-quarter strategic planning discussion.

2. Workflow Design

What should the AI-assisted workflow look like?

We map the trigger, input, classification, retrieval, draft or action, review point, escalation path, output, feedback loop, and success metric.

Example: AI may classify an incoming request, retrieve policy references, draft a reply, and send uncertain or sensitive cases to a human reviewer.

3. Operating Model

How will the workflow keep working after the pilot?

We define ownership, source maintenance, review responsibility, exception handling, quality monitoring, user adoption, and the metrics used to decide whether to expand.

Example: A knowledge assistant needs someone to maintain source documents, review answer quality, and decide when outdated material should be removed.
The method as a practical decision path

The method as a practical decision path

The method is not a theory exercise. It is a sequence of decisions that helps a business leader avoid oversized AI projects and focus on one workflow that can be tested.

1

Find the work

Name the workflow in ordinary language: who asks, who decides, and what output is needed.

2

Score the fit

Check whether the work is repeated, painful, source-grounded, reviewable, measurable, and owned.

3

Design the handoff

Decide what AI prepares, what a person approves, and what must be escalated.

4

Run a small pilot

Test with a narrow category, a real team, and a short feedback cycle.

5

Measure the result

Compare time saved, quality, risk, adoption, and whether the team actually uses it.

6

Expand or stop

Scale only when ownership, quality review, and source maintenance are clear.

What makes a workflow a good AI candidate?

What makes a workflow a good AI candidate?

A good first workflow is usually not glamorous. It is repeated, costly enough to matter, structured enough to improve, and safe enough to test with human review.

Repeated

It happens often enough that improvement compounds.

Patterned

Cases vary, but they are not completely unique every time.

Source-grounded

There are documents, rules, examples, or prior decisions AI can use.

Reviewable

A person can check important outputs before they create risk.

Measurable

The team can compare time, speed, quality, cost, or volume before and after.

Owned

A business owner is accountable for the workflow after launch.

When AI should not be the first move

When AI should not be the first move

The process is not defined

If nobody can describe how the work happens today, AI will likely automate confusion.

The risk is high and review is unclear

If mistakes affect customers, money, compliance, or trust, human review must be designed before automation.

There is no owner

A pilot without a business owner usually becomes a demo that nobody maintains.

There is no measurable pain

If the workflow is not slow, expensive, error-prone, or strategically important, it may not justify custom AI work.

Where the same method can apply

Where the same method can apply

The business domain changes, but the questions stay similar: what work repeats, what knowledge is needed, what risk needs review, and who owns the result?

Finance

Invoice checks, expense questions, month-end explanations, and document review where a person still approves exceptions.

HR

Policy questions, onboarding support, candidate intake, and internal request routing with clear source documents.

Legal or compliance

First-pass document summaries, policy lookup, clause comparison, and risk flags that are reviewed by accountable experts.

Operations

Email-to-task triage, shipment or order exception summaries, document extraction, and handoff coordination.

Leadership

Weekly issue summaries, decision logs, customer feedback themes, and follow-up tracking across teams.

Sales

Inbound qualification, account research summaries, proposal drafts, and next-step recommendations for review.

Examples of the method in practice

Examples of the method in practice

Customer support

Before
Agents repeatedly answer similar questions and search policy documents manually.
Design
AI classifies the request, retrieves approved policy references, drafts a reply, and escalates sensitive cases.
Measure
Measure first-response time, manual triage time, consistency, and escalation accuracy.

Internal knowledge

Before
People ask the same internal questions because SOPs and documents are scattered.
Design
AI searches approved sources, answers with references, and flags missing or outdated source material.
Measure
Measure search time, repeated questions, onboarding speed, and answer confidence.

Sales intake

Before
Inbound requests arrive with uneven detail, and staff manually judge priority.
Design
AI extracts intent, asks for missing details, scores readiness, and routes the lead to the right follow-up path.
Measure
Measure qualification speed, handoff quality, response delay, and conversion from qualified leads.
Start with one workflow

Start with one workflow

The method is intentionally practical. Pick one workflow, score its fit, identify risks, and decide whether it deserves a structured follow-up before any tool is bought or built.