TL;DR
AI delegation is already happening inside ordinary work, often before leaders decide where the boundary should be.
Advanced AI users in Microsoft’s survey are more likely to pause and decide what belongs with AI versus a human, while repeatable handoff rules remain uncommon.
Pick one recurring workflow and find the steps you deliberately handed to AI versus the ones it took over by habit.
An employee asks AI to summarize a report. Then they ask what matters most. A week later they ask which options the team should consider, and eventually the AI recommendation becomes the first version everyone reacts to. No single step feels like a governance decision. Nobody announces that part of the company’s judgment is moving to a model. The boundary just moves.
A 2026 article in Organizational Dynamics calls this the formation of AI delegation norms. The author argues that organizations often don’t design in advance which reasoning tasks people should keep and which they should hand to AI. Employees make useful local choices, leaders model behavior and coworkers copy what seems to work. A pattern becomes normal before formal governance catches up.
The paper is conceptual. It doesn’t measure how often this happens across companies, and the author reports that no data were used for the research described. I wouldn’t use it as proof that every organization has this problem. I think it names a problem that current workplace data makes hard to ignore, and it’s exactly what I’m seeing when I’m brought in to consult with companies.
The Policy Forms Before the Policy
Microsoft’s 2026 Work Trend Index combines a survey of 20,000 workplace AI users with separate Microsoft 365 Copilot usage analysis. In that usage analysis, 49% of classified Copilot conversations supported what Microsoft calls cognitive work. Microsoft included analysis and problem-solving in that category, along with evaluation and creative thinking. People are already using AI to analyze and evaluate, not just draft.
Microsoft found another difference. Fifty-three percent of the survey’s most advanced AI users, a group Microsoft calls Frontier Professionals, said they pause before starting work to decide what belongs with AI versus a human. Among other AI users, 33% said the same. What matters is the pause. These users stop and decide where the line goes.
Documented handoffs are much less common. Even among those advanced users, 26% said agent workflows, human handoffs and quality standards were documented and repeatable at team level, 29% at function level and 25% at organization level. The numbers were lower for everyone else.
BCG found another sign that AI is changing what people do at work. In its 2026 survey of 11,749 workers across 14 markets, 72% said AI had considerably changed the skills expected in their roles. Forty-seven percent said they were spending more time managing and directing AI than doing the underlying work themselves.
Those numbers don’t tell us where the human-AI boundary should be. They show why leaders shouldn’t assume the boundary is waiting for them to define it.
Repetition Teaches the Organization
Technology doesn’t simply perform a function. Once it becomes part of daily life, it can also change behavior and what people come to treat as normal. You can see that inside a company.
A manager starts using AI to prepare a strategy memo, and the team sees the result and copies the practice. A weekly report that used to begin with someone reading the underlying material now begins with an AI summary. A vendor review that used to start with people comparing evidence now starts with an AI-generated recommendation.
Those may be good changes. But repeated use can settle the question before leadership ever asks it. After six months, asking whether the workflow should begin with an AI recommendation feels like adding friction. The habit has become part of the job.
That’s why I wouldn’t reduce this to an AI policy problem. Policies are documents. Norms are what people actually do when nobody is discussing the policy.
This Is a Different Delegation Problem
I wrote about the human version of delegation in The Delegation Illusion. That problem starts after a leader decides to delegate. The failure is handing over a task without enough of the reasoning and decision criteria for the other person to act well. This problem starts earlier: who decided the reasoning should be delegated at all?
I wrote about another boundary in Your AI Agent Can Commit the Company. That article asks who decides what an agent may actually do: issue a refund, offer a discount, move money or make a promise to a customer.
An AI system doesn’t need that kind of authority to change how a company thinks. If the model decides which evidence gets summarized and which recommendation everyone sees first, it can shape the decision long before it has permission to execute anything. That doesn’t make the workflow wrong. It makes the boundary worth choosing on purpose.
Run a Delegation Audit
Shabad proposes a Delegation Audit. Here’s how I’d apply that idea: pick one recurring workflow where people already use AI. A vendor selection works. So does a hiring review or quarterly planning process.
Write down the actual steps. For example:
Gather the information.
Decide what is relevant.
Generate possible options.
Compare the options.
Recommend a choice.
Make the decision.
Take the action.
Review what happened.
For each step, write down how the work is split between people and AI, and who is accountable for the result. Then ask one question: Who decided that boundary?
There are good reasons to let AI do a lot of this work. It can search and compare faster than a person starting from a blank page. This isn’t an argument for keeping humans in every box. It’s a way to separate an intentional handoff from a habit.
For any handoff to AI nobody remembers choosing, ask what the person sees before accepting the output, what should send the work back to a human and when the team last checked whether the split still makes sense. You don’t need a new committee for this. You need a visible decision about where the thinking happens.
Decide Before Habit Decides for You
The Organizational Dynamics paper argues that early delegation norms are cheaper to shape than settled ones. That seems reasonable, but the article doesn’t provide organization-wide experimental evidence for the size of that cost difference. We don’t need to pretend it does. We know something simpler: once a habit is established, people start expecting the workflow to work that way.
If a team has spent six months letting AI produce the first recommendation, asking people to return to primary material may feel like extra work. If managers routinely use AI summaries before meetings, reading the original documents may start to look inefficient. If employees are measured on speed while leaders say they should preserve human judgment, speed has a very good chance of winning. That’s how an unspoken delegation choice becomes part of the job.
Pick one important workflow this week. Map where the thinking happens now, then keep the delegation that makes sense and change the part that doesn’t. But make somebody say the boundary out loud.
If nobody ever decided where the line should be, you don’t have an AI delegation policy yet. You have a habit.
Resources
Vsevolod Shabad, “The norm architects: How AI delegation norms form before anyone designs them”, Organizational Dynamics, 2026. Conceptual article on how AI delegation norms can emerge through repeated organizational behavior; the article reports that no data were used for the research described.
Microsoft, “2026 Work Trend Index: Agents, human agency, and the opportunity for every organization”, May 5, 2026. Survey of 20,000 workplace AI users across 10 markets plus separate Microsoft 365 Copilot usage analysis.
Boston Consulting Group, “AI Is Reshaping Jobs Faster Than Companies Are Reshaping Work”, June 3, 2026. Global survey of 11,749 workers across 14 markets.
The Consilience Project, “Technology is Not Values Neutral: Ending the Reign of Nihilistic Design”, June 26, 2022. Broader argument that technologies shape behavior, attention and values as they become embedded in everyday life.
Evidence note: Shabad’s article supplies the norm-formation framework, not a prevalence estimate. Microsoft’s survey measures self-reported workplace behavior and organizational conditions; the 49% cognitive-work figure comes from separate Copilot usage analysis. BCG’s results are self-reported survey findings.
Analytical note: Shabad supplies the norm-formation argument and proposes a Delegation Audit. The workflow checklist here applies that idea to the examples above; the recommendations are my synthesis of the sources.