Module · M1 · The gap between capable and safe

Four postures: deflect, assist, gate, human-only

Lesson 2 of 21 · 9 min

Before you automate anything, you have to decide how much authority the automation gets. There are four answers, and choosing between them is a five-minute conversation that prevents most of the expensive mistakes in this field.

The four postures. Most teams have only ever used the first two, then jump straight to the fourth after an incident.

Posture	What it means	Who decides	What it costs you when it is wrong
Deflect	Answer it. No human involved, no state changed.	the machine	a bad answer, and a customer who asks again
Assist	Draft it, summarise it, prepare it — a human sends or commits.	a human, faster	wasted review time; the human is the backstop
Automate with a gate	The machine proposes and prepares everything; one approval releases it.	the machine, subject to a human	a delay — which is what you are buying
Human-only	The machine may gather and draft, and may not act. Ever.	a human	nothing automated, deliberately

Deflect

What it means: Answer it. No human involved, no state changed.
Who decides: the machine
What it costs you when it is wrong: a bad answer, and a customer who asks again

Assist

What it means: Draft it, summarise it, prepare it — a human sends or commits.
Who decides: a human, faster
What it costs you when it is wrong: wasted review time; the human is the backstop

Automate with a gate

What it means: The machine proposes and prepares everything; one approval releases it.
Who decides: the machine, subject to a human
What it costs you when it is wrong: a delay — which is what you are buying

Human-only

What it means: The machine may gather and draft, and may not act. Ever.
Who decides: a human
What it costs you when it is wrong: nothing automated, deliberately

The four questions that choose the posture

Volume. How often does this happen? Rare things rarely repay automation.
Variance. How much do the cases differ? High variance is where a machine’s confidence outruns its competence.
Cost of being wrong. Not the average cost. The cost of the worst instance you can imagine, times how plausible that instance is.
Reversibility. If it is wrong, can you undo it — and can you undo it in the customer’s eyes, which is a different question.

Reversibility is the axis people skip. Volume and cost are easy to argue about in a meeting because they are numbers. Reversibility is the one that decides whether a mistake is an annoyance or an incident, and it is almost never on the slide. A refund can be clawed back on paper and not in the relationship. A credential a student has already put on a public profile cannot be recalled at all.

Worked, on a real business

Here is the same triage applied across the lifecycle of an online academy — the business this course is set in. Note that the posture is not a property of the department. It is a property of what the action does.

One business, five postures. The pattern is not “the risky department”; it is “the irreversible action”.

Stage	The work	Posture	Why
Acquire	answer “is this course for me”, qualify, route	Deflect	high volume, low variance, the answer is already written
Convert	pricing questions, discounts, payment links	Assist, and gate any discount	a discount is money; past a threshold it needs a person
Onboard	provisioning, access failures, first-value tracking	Automate with a gate	the queue is mechanical; the failures are not
Support	content questions, extensions, disputes	Deflect, then Assist	most of it is in the documentation; the rest needs judgement
Certify	exam results, issuing the credential	Human-only	irreversible in reputation, whatever the database says
Refunds and compensation	authority thresholds, who may approve what	Automate with a gate	always — this is the spine of the course

Acquire

The work: answer “is this course for me”, qualify, route
Posture: Deflect
Why: high volume, low variance, the answer is already written

Convert

The work: pricing questions, discounts, payment links
Posture: Assist, and gate any discount
Why: a discount is money; past a threshold it needs a person

Onboard

The work: provisioning, access failures, first-value tracking
Posture: Automate with a gate
Why: the queue is mechanical; the failures are not

Support

The work: content questions, extensions, disputes
Posture: Deflect, then Assist
Why: most of it is in the documentation; the rest needs judgement

Certify

The work: exam results, issuing the credential
Posture: Human-only
Why: irreversible in reputation, whatever the database says

Refunds and compensation

The work: authority thresholds, who may approve what
Posture: Automate with a gate
Why: always — this is the spine of the course

The two failures this prevents

Teams get this wrong in two directions, and the second one is more common than anybody admits.

Automating the irreversible thing first, because it is the one with the obvious cost saving attached. This is how an agent ends up authorised to move money in week one.
Refusing to automate anything after an incident, which throws away the deflect and assist work that carries most of the volume and none of the risk. The incident argues for a gate, not for a freeze.

Do this before the next module. Take three things you are actually thinking of automating. Assign each a posture, and write one sentence per axis defending it. If two of your three are “automate with a gate”, the rest of this course is about how to build that gate properly. If all three are “deflect”, start there — it is cheaper and it works.