Playbooks

The road runs both ways

Most AI strategies imagine a one-way street from human to artificial. A serious framework has to describe the return trip with the same precision — and define it before the pilot, not after the results are known.

Twelve steps

Human → Artificial

The objective is not to “replace a person”. It is to transfer responsibility in a controlled way after demonstrating that the new design produces results equal to or better than the old one, within permitted risk.

#	Step	Control
01	Baseline	Document current performance: quality, cost, time, errors, exceptions and tacit knowledge.
02	Decomposition	Split the post into responsibilities and tasks; identify what must stay human.
03	Risk mapping	Classify decisions, data, authority and cost of error.
04	AI Role Contract	Create job description, KPIs, limits, tools, manager and escalation.
05	Knowledge transfer	SOPs, examples, criteria, policies, exceptions and history.
06	Shadow mode	The AI Employee executes without affecting production; results are compared against the human.
07	Controlled production	Limited authority and frequent approvals.
08	Performance gate	Ownership is not transferred until quality, cost and risk thresholds are met.
09	Gradual transfer	Increase scope and autonomy; keep reversibility.
10	Human reallocation	Move released human capacity toward higher-value work where that makes sense.
11	Formal handoff	Update org chart, RACI/ownership, access and communication.
12	Post-transition review	Review at 30/60/90 days and revert if performance deteriorates.

You do not substitute first and find out afterwards whether it was working. The transition is earned with evidence.

Seven triggers

Artificial → Human

The framework must be reversible. If the artificial resource produces too much risk, low quality, excessive human intervention, rising cost or relational damage, the work should return partly or entirely to human hands. A mature hybrid organisation does not measure success by the direction of the transition. It measures it by the quality of its architecture.

Activate the rollback criterion by KPI or incident.

Freeze or reduce the AI Employee’s authority.

Transfer context, useful memory and backlog to the human.

Reassign ownership and escalation channels.

Revoke artificial access that no longer corresponds.

Run root-cause analysis: model, process, knowledge, tools or bad role allocation.

Decide whether the future of the post is Human or Hybrid — do not assume it must return to being fully human.

Define the return conditions before the pilot, not after the results are known. What error rate is unacceptable? How much human intervention destroys the economics? Which incident forces suspension? Written in advance, these rules reduce the bias of defending an implementation out of pride.