Automation without abdication
The conversation about AI automation often drifts toward one of two extremes. Either the automation handles everything, removing people from the process entirely. Or people remain involved in every step, making the automation little more than a faster version of the manual process.
Neither extreme is useful. The first creates fragile systems that fail at the edges. The second fails to create meaningful capacity. The better approach is to design workflows that combine automation with human judgement, each doing what they do best.
What machines do well
AI automation excels at consistency, speed and scale. An AI assistant can process the same type of work the same way every time, without fatigue, without variation and without the gradual drift in standards that affects manual processes over time.
It can also handle volume. An assistant does not slow down when the workload doubles. It processes each item with the same attention, whether there are ten or a thousand.
And it can work across systems. An assistant can pull information from email, CRM and calendar simultaneously, synthesising context that would take a person multiple searches and logins to assemble.
These capabilities make AI automation ideal for:
- Gathering and organising information from multiple sources
- Applying consistent rules and criteria to structured decisions
- Monitoring for events, changes or anomalies across systems
- Preparing output in standard formats for review and action
What people do well
People excel at judgement in situations that are genuinely ambiguous. When the right answer depends on context that cannot be fully captured in rules. When the decision involves values, relationships or trade-offs that require human perspective.
People are also better at detecting when something is wrong in a way that rules cannot capture. A slight shift in tone in a client communication. A pattern that does not quite fit the data. A situation that feels unusual even though every individual indicator looks normal.
And people own the relationships that matter most. Client trust, team morale, organisational judgement — these are not automatable, nor should they be.
These human capabilities should be the focus of workflow design. The automation should handle everything that leads up to these judgement points, and everything that follows from them. The person should be involved at the points where their judgement adds the most value.
The approval design principle
The core principle of designing AI workflows around human judgement is simple: automate the preparation, preserve the decision.
This means the assistant handles the work that surrounds a decision — gathering information, checking against criteria, preparing options, formatting output — and then pauses at a defined point for human review.
The review point should be designed so that:
- The person sees a clear summary of what the assistant has done
- The information needed for the decision is organised and accessible
- The decision options are presented with supporting context
- The action the person takes flows naturally back into the workflow
This is not a "human in the loop" in the sense of someone checking every step. It is a human at the decision point — the one place where their judgement makes the difference between a good outcome and a poor one.
Escalation as a feature
Well-designed AI workflows treat escalation as a feature, not a failure. When the assistant encounters something it cannot handle with confidence — an ambiguous case, an edge condition, a situation that requires a relationship judgement — it escalates with context.
A good escalation includes:
- What the assistant was trying to do
- What it has determined so far
- What it is uncertain about
- What it would recommend if it had to decide
- What the person needs to do to resolve it
This structured escalation means the person receives a complete picture of the situation without having to reconstruct it from scratch. They can make the decision quickly because the preparation has already been done.
Types of approval points
Different workflows need different types of approval. The common patterns are:
Review and release. The assistant prepares a complete output — a response, a report, a recommendation — and presents it for review. The person can approve, edit or reject. Once approved, the assistant sends or files the output.
Option selection. The assistant identifies several possible approaches to a situation and presents them with pros and cons. The person selects the approach. The assistant executes based on the selection.
Exception handling. The assistant processes routine cases automatically and escalates only the ones that fall outside defined parameters. The person handles the exceptions. The assistant learns from the resolution for future cases.
Threshold approval. The assistant handles cases up to a defined threshold — value, risk, sensitivity — and escalates cases above it. The threshold can be adjusted as confidence in the assistant grows.
Each pattern keeps the person involved at the point where their judgement matters most, without requiring them to be involved in the routine processing that leads up to it.
Designing for confidence growth
The approach described here is one part of a broader strategy for building trust in AI workflows. Confidence grows through a combination of transparency, demonstrated reliability and good approval design.
When an AI workflow is first introduced, approval points should be more frequent. The assistant does the preparation work and presents it for review on most decisions. This builds trust through demonstrated consistency.
As confidence grows, approval points can be adjusted. The assistant handles more routine decisions independently. The review sample shrinks. The person's time is increasingly focused on the genuinely ambiguous cases.
This is not a one-time design. It is an ongoing adjustment as the assistant proves itself and the team becomes comfortable with its role. The workflow design should make it easy to add, remove or adjust approval points without rebuilding the automation.
Thinking about your own workflows?
The best AI workflows are the ones where the division of work between assistant and person feels natural to everyone involved. The assistant handles the consistent, the repetitive and the preparatory. The person handles the judgement, the relationships and the exceptions.
At Moonshot Monkeys, we design AI assistants around this principle from the start. Every workflow includes defined approval points, structured escalation and the ability to adjust as confidence grows. The goal is automation that respects human judgement while removing the work that does not need it.