Every time AI comes up in a leadership meeting, someone asks the wrong question.

"Can AI replace this job?"

The room divides. One half says yes — confidently, because they have seen the demos. The other half says no — defensively, because the question is rhetorically inflammatory and operationally useless. Both halves are wrong, because the question itself is wrong.

A job is not a single thing. A job is a bundle.

The unit is the mandate

I have been calling this unit a mandate. It is smaller than a role and larger than a task. It is not a responsibility area, a RACI cell, or an OKR. Those describe ownership, involvement, or outcomes. A mandate describes a piece of work the organization will hold someone accountable for, with the authority and context that piece of work actually requires.

Roles are compositions of mandates. A title like "Head of Growth" is a label glued to a stack of them, and most companies have never opened the stack.

That is the whole move. It is the single most useful primitive I know for thinking about AI delegation, and most companies are still planning at the role level — which is the wrong altitude.

A role is a bundle. AI delegation works at the level of the bundle's parts.

Open the bundle

Take a real role: Head of Marketing at a 200-person consumer brand.

If you ask what this person does, you get a job description. If you ask what they are accountable for, you get a list of mandates. The list is usually longer than people expect.

Ten mandates. Some of them ship work the company already knows how to delegate. Some of them require taste a model isn't close to having, and isn't getting in the planning horizon you're working in. Some of them are politically delicate and have lived with this role for so long that nobody remembers they are separable.

They are not the same kind of work. Treating them as a single "job" is what makes the AI delegation conversation impossible.

The four-quadrant sort

Once the bundle is open, each mandate sorts into one of four buckets.

Delegate to an agent. Attribution reporting. Voice-and-claim QA on draft copy. Pipeline pacing dashboards. Things that have a queryable definition of "right," that produce work an audit could verify, that don't require relationship or taste.

The bar for delegation is not that the agent is perfect. The bar is that the agent's mistakes are recoverable — that someone notices when the report is off, that the canon governs the QA pass, that there is a human reviewing aggregate output, not every line.

Assist with an agent. Content calendar drafting. Paid acquisition iteration. Email program copy generation. The mandate stays with the human; the agent absorbs the friction. The human spends fewer hours on the mechanical part of the work and more on the parts that compound.

This is where most of the real value lives in the next two years. Not full delegation. Compression of the mechanical layer.

Keep human. Influencer relationships. The press conversation. The hire-fire-develop loop. Things that depend on read of a specific person in a specific moment, where the cost of a misread is reputational and not recoverable.

The list of mandates that stay human shrinks every year. But it never goes to zero, and the company that pretends it does is the company that ships an agent into a press conversation it can't take back.

Retire. The mandate that exists because someone added it to the role four years ago and nobody has audited the list since. Most roles have at least one. Marketing sites that nobody reads. Reports that nobody opens. Quarterly rituals that produce a deck and a meeting and no decision.

The retire bucket is the cheap win. You did not need AI to find it; you needed an audit. AI was just the pressure that made the audit happen.

The useful question isn't "can AI do this job?" It's "which mandates inside this role have always been delegable?"

Why this beats job-replacement framing

The job-replacement frame produces three failure modes, every time.

One: defensive reaction. Anyone whose role is up for review reads the question as a threat and stops being useful in the conversation. The frame turns the people who know the most about the work into the people most invested in obscuring it.

Two: binary thinking. The room ends up arguing whether AI is or is not ready to replace the role, when the actual answer is that some mandates inside the role are ready today, some will never be, and the work is in the sort.

Three: the headcount-cut frame becomes the conversation. The C-suite frames the question as reduction, the workforce hears it that way, and the organization spends six months in a defensive crouch instead of doing the redesign the moment actually requires.

Mandate framing routes around all three.

It is not threatening, because mandates are smaller than roles — nobody loses their job by having a single mandate move. It is not binary, because each mandate gets its own answer. And it is not headcount-coded, because the most common outcome of a real mandate audit is not "we need fewer people" but "we need people doing fewer things." The role gets sharper. The work gets clearer. The agent shows up in a place where it can actually do useful work without taking the role with it.

Mandates are first-class

The mandate frame is not a rhetorical move. It is a structural one.

If your company starts treating mandates as first-class units — written down, owned, transferable, auditable — a few things become possible that were not possible before.

You can move a mandate between people without re-writing a job description. You can move a mandate between a human and an agent and back again as the work matures. You can audit which mandates exist, which are duplicated, which are orphaned. You can finally answer the question of what a role is actually on the hook for, without using its title.

You can also start to plan at the right altitude. The question is no longer "can AI replace this role?" It is: "for each mandate in this role, who or what is best positioned to hold it, given what we know today?"

That is a question with answers. And the answers change as the capability changes.

Closing

You do not buy an AI tool. You transfer a mandate.

And before you transfer a mandate, you have to know what it is.

The work of opening the bundle — naming the mandates that compose a role, sorting them into who-holds-them buckets, auditing the list, retiring what shouldn't exist — is unglamorous. It is also the place where AI rollouts actually live.

The jobs question goes nowhere. The mandate question has answers — and the answers move as the capability does.