Concept

What is the ABC Framework?

Most teams ask which tool to use. ABC asks which layer of the role to assign.

The ABC Framework decomposes any role into three layers — A: judgment and relationships (human-owned), B: structured expert work (mixed), C: routine operations (agent-owned). It is how MING Labs assigns ownership when designing human-agent teams.

Last updated: April 2026 | Next review: October 2026 Proprietary evidence Machine-readable record
Based on articleWe fired an AI agent after 13 days

The ABC Framework is MING Labs’ internal taxonomy for splitting work between humans and AI agents inside a hybrid organisation . Every role decomposes into three layers: A — judgment and relationships, B — structured expert work, C — routine operations.[S1]

The framework was extracted from operating MING Labs since January 2026 — including the failure that forced us to name it. When we fired an AI agent after thirteen days , the diagnosis was that we had given the agent a capability without assigning a layer to own.[S2] ABC is the corrective: every agent gets a domain, not just a verb.

The split looks like this in practice:

DimensionHuman roleAgent roleOutcome owned
A — Judgment & relationshipsOwnerNoneTrust, accountability
B — Structured expert workDirectorExecutorQuality of analysis
C — Routine operationsReviewer of exceptionsOwnerThroughput, accuracy

Layer A is non-negotiably human: hiring, pricing, client trust. Layer C is non-negotiably the agent’s: inbox triage, data preparation, pipeline hygiene. Layer B is the contested middle and the place where most “AI initiatives” stall — without a supervision loop, B work either gets dumped on the agent (quality drops) or hoarded by the human (throughput stalls).

ABC is not a job-replacement model. It is a role-design model. The role stays; what changes is which layer each party owns. The framework forces a question most “AI strategy” decks skip: for any given role on the org chart, who owns A, who owns B, and who owns C? When the answer is “the human, with AI assistance,” nothing changes — the AI is a tool, not a colleague, and the productivity story stays anecdotal.

The opposite failure is just as common: assigning C to an agent without naming the outcome it owns. That is how Major Tom shipped 764 messages and zero value. The fix is not a better prompt; it is a better contract. ABC is the organisational counterpart to Agent Experience on the outside: clear ownership inside, clear legibility outside. Both ride on the same insight — agents need a domain, not just a verb.

Sources

[S1]
ABC Framework — internal taxonomy for human/agent role decompositionMING Labs · 2026-02-01 Supports: three-layer taxonomy definition
[S2]
Major Tom failure audit — capability vs. accountability findingsMING Labs (internal) · 2026-03-30 Supports: Major Tom capability-without-domain diagnosis

Frequently asked questions

Why three layers and not two?
A binary human/agent split forces a premature choice on structured expert work — analysis, drafting, reporting — that is best done as a supervised collaboration. Layer B exists to name that contested middle so it can be designed deliberately rather than defaulted into a tool.
Is the ABC Framework a job-replacement model?
No. It is a role-design model. It assumes the role stays; what changes is which layer of the role each party owns. Layer A (judgment, relationships, accountability) is non-negotiably human.
Where did the ABC Framework come from?
It was extracted from operating MING Labs as a hybrid organisation since January 2026 — including the failure of Major Tom, which forced us to name the difference between giving an agent a capability and giving an agent a domain.
All Insights