Automate, augment, or human?
Use automate, augment and human-only as planning choices for a defined task. The choice depends on the tools, data, required review and who may act. Treat it as a proposal: test representative cases and agree the boundaries with the workflow owner before deployment.
From The Agentic Enterprise (2026), co-authored by Giridhar LV, Kashi KS, and Rajan. Available on Amazon Kindle.
The three buckets
Propose a category for a clearly defined task, then review it against the actual tools, rules and evidence.
AI executes the defined task within approved boundaries. Verify outputs, exceptions and downstream effects before assigning it.
- Reconcile a balance sheet
- Draft a first-version contract
- Update a forecast model with last week's numbers
- Summarize a long document into a brief
AI drafts or analyzes; a person retains the identified decisions or approvals. Specify the handoff and the evidence that person needs.
- Present scenarios to a CFO
- Negotiate a contract with a long-standing customer
- Choose between two architectural approaches
- Update a forecast based on a business change
Keep the responsibility with a person where policy, trust or the nature of the interaction requires it. Revisit the decision when the work or requirements change.
- Hold space for a patient in crisis
- Tell a team that layoffs are coming
- Own a high-stakes judgment call with real consequences
- Sign off on a decision the board wants a human accountable for
Why three buckets, not two
A two-bucket split tells you how AI and humans share work. It does not tell you what must stay human.
Anthropic's January 2026 Economic Index reported augmentation in 52% and automation in 45% of sampled Claude.ai conversations from November 2025. Those are interaction patterns within that sample, not the proportion of all enterprise work that AI can perform.
Enterprise planning also needs to identify work that remains with people. A sample of AI conversations cannot measure tasks where AI was never used. Decisions about responsibility require the workflow context, including approvals and operating rules.
The categories are a planning framework. Their application can change with the task boundary, model, tools and business rules. Use the classification to propose trials; evaluate the observed work before assigning responsibility.
Common questions
How to use the classification in practice.