← All insights

Governance

AI Suitability Is Not Automation Suitability

AI can be useful inside a workflow without being ready to run that workflow. Capability and authority are different decisions.

Christopher Lewis 5 min read

Capability answers only one question

Can the AI do the task?

That is an important question.

It is not the whole decision.

A system may be very good at drafting a customer response, summarizing a case, preparing an analysis, or recommending the next step.

That does not automatically mean it should send the response, change the record, approve the case, move the money, or make the final decision.

Capability and authority are different.

Assistance and automation carry different consequences

There is a meaningful difference between AI that produces a suggestion and AI that takes an action.

With assistance, a person can inspect the output before anything changes.

With automation, the system may alter a customer-facing state, a record, a permission, a payment, or another consequential part of the workflow before a person sees it.

The same model can be acceptable in one role and unacceptable in another.

That is why "the AI is accurate" is not enough to decide how much authority it should have.

Look at consequence and reversibility

The higher the consequence of an error, the stronger the case for explicit human review or a tightly bounded action.

Reversibility matters too.

A bad draft can be deleted.

An internal recommendation can be ignored.

A message sent to a customer is harder to take back.

A changed permission, denied request, financial transaction, or external commitment may be harder still.

As the cost of being wrong rises and the ability to reverse the action falls, the decision about automation should become more conservative.

More capable systems can require new controls

AI systems do not stay still.

Models improve. Tools are added. Context windows expand. Integrations connect more systems. Permissions change. Agents move from suggesting actions to executing them.

That can create a subtle governance problem.

A control that was reasonable when the system could only draft text may be inadequate after the same system can access records, call tools, communicate externally, or execute a multi-step process.

A material capability change should therefore trigger a fresh look at the workflow assumptions and controls around it.

The old approval was made for the old capability.

Increase authority because the evidence supports it

There is nothing wrong with increasing automation over time.

But authority should expand because evidence supports the change, not simply because the technology can do more.

A sensible progression is to observe how the system performs, let it assist, require confirmation for consequential actions, and automate only the parts where failure modes, review, recovery, and ownership are sufficiently understood.

The exact progression will vary by workflow.

The principle does not.

AI can belong in the work before it is ready to run the work.

Proof · 6 min read

Did AI Actually Improve the Work?

Deployment is not proof. The useful question comes after implementation: what changed, compared with what, and was the result worth keeping?

← All insights

Assess where AI is worth the investment.

Assess Your AI Opportunity