Abstract

AI changes the task chain before it changes the org chart. That is the practical starting point for Reworking Order.

Most people still think about AI adoption as a question of roles: where do agents sit, which jobs do they replace, and what reporting line should they live under? That is the wrong unit of analysis. Organizations are not changed first by redrawing boxes. They are changed by how work is actually decomposed into steps, how those steps are coordinated, where decision rights live, how exceptions are handled, and who remains accountable when something matters.

The result is not agent-centered organization design. The more defensible frame is workflow-centered redesign: human judgment sets the direction, AI expands the option space, and the system is rebuilt around the real bottlenecks of execution. For the foreseeable future, the most useful posture is human-framed, AI-expanded, and human-authorized.

This essay argues that the practical future of work is not "agents in the org chart." It is a rebundling of tasks, decisions, and responsibilities around human-centered intention with machine-assisted execution.

The Wrong Unit

The org chart is a visible artifact. That is exactly why people over-focus on it. It is easy to draw, easy to discuss, and easy to change in slides. But it is not where most of the work lives.

The real system is the chain of steps that turns intention into output. A team receives a request, frames the problem, gathers information, drafts options, checks assumptions, reviews tradeoffs, handles exceptions, approves releases, and owns the consequences. AI can touch nearly every step in that chain, but not in the same way.

Some steps are good candidates for automation. Some are good candidates for augmentation. Some should remain human-owned because they require judgment, authority, legitimacy, or accountability. The key design problem is not to decide whether an agent exists somewhere in the org chart. It is to decide which steps should be machine-heavy, which should be human-heavy, and which should require human authorization before they become real.

That distinction matters because a lot of current AI thinking is structurally lazy. It takes the old org and inserts a new tool into it. In practice, that usually means one of two things:

  • the tool is attached to existing work without redesigning the surrounding process, so the gains stay small
  • the organization tries to reorganize around the tool too quickly, and the structure becomes brittle

Both are versions of the same mistake. They center the visible novelty instead of the actual work.

That is why the org chart is not the point. It is a lagging indicator. The workflow is the leading indicator.

Workflow Before Structure

If the wrong unit is the org chart, the right unit is the workflow.

Workflow is where bottlenecks become visible. It is where exceptions accumulate. It is where handoffs fail. It is where information gets lost, where approvals slow down, where judgment gets diluted, and where responsibility becomes unclear. It is also where AI can create value without pretending that the organization has already been redesigned.

This is a more serious and more practical way to think about AI than "automation" or "agent deployment." It treats the organization as a sequence of decisions and tasks, not a collection of static roles. That matters because AI changes the economics of specific steps before it changes the social meaning of the job title attached to them.

The best evidence for this comes from task-based research. The task approach in labor economics has long argued that work is better understood as a set of assignable tasks than as a fixed bundle of occupations. More recent AI work extends that logic: AI can automate some tasks, augment others, and create pressure to rebundle work around new coordination constraints. The 2026 paper *Chaining Tasks, Redefining Work* makes this especially clear by modeling production as a sequence of steps that can be manual, AI-augmented, or fully automated within contiguous chains.

That is closer to reality than org-chart thinking. In a real business, the important questions are:

  • Which steps can be delegated to AI safely?
  • Which steps should be drafted by AI but reviewed by a human?
  • Which steps should remain wholly human because the consequence is too high or too ambiguous?
  • Which exceptions need human judgment rather than more automation?
  • Which parts of the workflow need redesign before AI can help at all?

These are workflow questions, not reporting-line questions.

The same logic applies to decision rights. A system can become faster and still become worse if the wrong decision moves to the wrong layer. Decision authority is not just a governance formality. It is part of the economics of the system.

If the organization gets this wrong, it may create speed without learning, or output without ownership. That is not redesign. That is just an expensive way to move the same problem faster.

Human-Framed, AI-Expanded, Human-Authorized

This is the operating philosophy that follows from the research and from the practical reality of how work gets done.

The most defensible default is not agent-initiated change. It is human-initiated change that is expanded by AI and authorized by a human.

That matters because people are not only trying to make better output. They are also trying to preserve agency, learning, and responsibility. If AI starts originating changes that humans merely rubber-stamp, the system may become faster while quietly hollowing out the very judgment it depends on. That is not a theoretical risk. A 2026 Scientific Reports paper found that passive reliance on AI can reduce self-efficacy, ownership, and meaning, while active collaboration preserves them much better.

In business language, the rule is simple:

  • humans should frame the problem
  • AI should broaden the search
  • humans should define the acceptable tradeoff
  • AI should help test and compress the work
  • humans should press the trigger
  • humans should own the result

That is the first-order operating principle.

There is a continuum here, and that continuum is important. Not every item needs the same degree of human initiation or human authorization forever. As systems improve, trust grows, and the cost of error changes, the balance can move. Some tasks will become more agent-initiated. Some will become more agent-authorized. Some will remain stubbornly human-led because the consequence is too important or the environment too unstable.

So the thesis is not "humans must do everything." That would be sentimental and wrong. The thesis is:

the locus of meaningful change should remain human-centred, even when the execution is heavily AI-assisted.

This is a more durable position than "AI should lead" because it preserves accountability and learning while still allowing high levels of machine leverage.

In software, the example is obvious. A model can suggest a new feature, draft the implementation, generate tests, and surface edge cases. But a human should define the feature, explain why it matters, decide whether the tradeoff is worth it, and release it under their own responsibility. The same holds for workflow changes, pricing decisions, hiring processes, internal tools, and policy shifts.

What This Means For Reworking Order

Reworking Order should not sound like it is selling AI replacement or agent-native org charts. It should sound like a practice that helps organizations redesign how work actually functions under AI.

That means the site can make a sharper claim than "we help organizations redesign how humans and agents work together." That line is true, but it is not the strongest expression of the thesis. The sharper version is:

We help organizations redesign workflows, decision rights, and accountability so humans and AI become complementary.

That one sentence carries the whole logic:

  • workflow comes first
  • structure follows
  • humans stay centered where intention and responsibility matter
  • AI expands what is possible
  • the system is redesigned around the work, not the novelty

The business implication is straightforward. If you are building new products or new features, the early discipline should be human-initiated, AI-improved, and human-authorized. That does not mean moving slowly. It means moving with clarity. AI can accelerate exploration, reduce drafting cost, expose hidden options, and compress execution time. But the strategic frame should still come from a human who understands the problem, the consequence, and the organization.

As confidence grows, the continuum may move. Some lower-risk features, routine changes, or bounded operational steps may be agent-initiated or agent-authorized under human supervision. But that is a later-stage design choice, not the premise of the system. The premise is human judgment first, AI leverage second.

Diagram

old modelworkflow redesignROLErole oneROLErole twoROLErole threeSTEPstepSTEPstepEXCEPTIONreviewDECISIONauthorityRELEASEoutcomestep → step → exception → decision → releaseReworking Order
The old model moves work between roles. The newer model redesigns the chain itself: steps, exceptions, decisions, and releases.

Sources

  • Agrawal, Gans, and Goldfarb, *AI Adoption and System-Wide Change*

https://www.nber.org/papers/w28811

  • Brynjolfsson, Rock, and Syverson, *The Productivity J-Curve: How Intangibles Complement General Purpose Technologies*

https://www.nber.org/papers/w25148

  • Dillon, Jaffe, Immorlica, and Stanton, *Shifting Work Patterns with Generative AI*

https://www.nber.org/papers/w33795

  • Athey, Bryan, and Gans, *The Allocation of Decision Authority to Human and Artificial Intelligence*

https://www.nber.org/papers/w26673

  • Agarwal, Moehring, and Wolitzky, *Designing Human-AI Collaboration: A Sufficient-Statistic Approach*

https://www.nber.org/papers/w33949

  • Vaccaro, Almaatouq, and Malone, *When combinations of humans and AI are useful: A systematic review and meta-analysis*

https://www.nature.com/articles/s41562-024-02024-1

  • Lee, Yin, Jia, et al., *Relying on AI at work reduces self-efficacy, ownership, and meaning while active collaboration mitigates the effects*

https://www.nature.com/articles/s41598-026-42312-6

  • Demirer, Horton, Immorlica, Lucier, and Shahidi, *Chaining Tasks, Redefining Work: A Theory of AI Automation*

https://www.nber.org/papers/w34859

  • Agrawal, McHale, and Oettl, *Enhancing Worker Productivity Without Automating Tasks: A Different Approach to AI and the Task-Based Model*

https://www.nber.org/papers/w34781

  • Acemoglu, Autor, and Johnson, *Building Pro-Worker Artificial Intelligence*

https://www.nber.org/papers/w34854