7. The Door: How Do You Adopt It Without Taking Anything Away?

In the film: Elena switched off agentive mode with a gesture, bought shoes the old way for eighteen minutes, and came back. No one ever took anything away from her — and that is exactly why she never wanted to go back. This chapter explains why that reversibility is not a courtesy: it is the entire strategy.

A superior paradigm that cannot be adopted is an academic curiosity. The four faces are already on the table; this chapter takes on the managerial question that makes them reachable: how does a real organization — with its real people and their real attachment to their tools — get from the channel to the real-time enterprise without a mutiny?

Don’t sell by taking away

The first law of this transition belongs to the psychology of change: people don’t buy abstract benefits when they feel something concrete is being taken from them. The announcement “we are going to eliminate chat” does not produce a discussion about productivity; it produces a visceral reaction whose entire content is the word eliminate. The objection won’t be conceptual — it will be “so how do I send a message to my colleague now?”, and you will have lost the room before showing your first slide.

The correct formulation doesn’t take away: it renders unnecessary. You don’t take anyone’s tool from them — you take away, one by one, their reasons for using it. The distinction sounds rhetorical and is structural: the first formulation promises a loss and demands faith; the second offers an alternative and lets reality make the argument.

The mode, not the replacement

The design implication is the most important product decision in the entire paradigm: this world is not deployed as a replacement but as an optional, reversible mode of operation that coexists with the traditional tools. The platform keeps chat, email, documents; it offers, in addition, a mode in which everything goes through the agent. We call that switch agentive mode — and the name is exact: the question that divides the two worlds (do you still open applications to do your work?) gets answered here person by person. Turning on agentive mode is crossing the Nadella Line from chapter 1 — but individually, with a gesture, and with the freedom to come back with the same gesture, on a Tuesday at ten, if it doesn’t win you over.

The exact analogy is a humble one: dark mode. No one was forced to use it; it existed, someone tried it, and never went back. The adoption physics that humility enables is the difference between two worlds:

The last row deserves executive emphasis: the mode is also the honest test. Ideas that need imposition to survive are usually confessing something.

The four steps

Adoption progresses by steps, and none of them can be skipped — each one builds the trust the next one consumes:

1. The full platform, with an assistant. All the familiar tools; the agent helps whoever asks for help. Nobody changes how they work.
2. Agentive mode, available. Those who turn it on, turn it on; those who don’t, stay in their channels. Both coexist without friction: the migrated user’s agent delivers into the channels of the one who didn’t migrate.
3. Agentive mode as the default for the teams that already live in it, with classic mode one click away.
4. The full mode. The day — years later, without ceremony — when someone notices the operational channels have been empty for months.

The early adopters are predictable and worth cultivating: the desperate — executives drowning in channels, field people who never managed to inhabit them. Their first week of briefings instead of two hundred messages produces the evangelists no internal communications plan can buy.

The risks, with their mitigations

An honest adoption chapter also names what can go wrong — and how it is managed. The first objection is one of trust: what if the agent hides something important from me? The answer is radical transparency — the briefing states how many items it processed and how many it classified as noise, “show me everything” is always available, and every delivery is auditable. The second is the prioritization error — something critical waiting because it was misclassified —: the urgency threshold is calibrated conservatively at first, because the cost of a false-urgent (one interruption) is lower than that of a false-routine, and the system learns from every correction. The third is dependency — if the agent goes down, does communication go down? —: classic mode never gets uninstalled; it is permanent redundancy, not an emergency backup. The fourth is the perception of surveillance, and its mitigation is a matter of governance, not technology: the agora is not listened to, contexts don’t cross without authorization, and “off the record” exists. And the fifth is the generational gap: step 1 demands no change at all, and the entry analogy — a human assistant who reads everything and tells you each morning what needs your decision — is intelligible to any generation.

The migration of species

Let’s close the chapter by naming what adoption really is. An organization that climbs the four steps didn’t migrate tools — it migrated species: from an interruption factory to an absorber. And it did so without taking anything from anyone, letting each person discover at their own pace that the weapon they were defending was the cage.

The book’s last question remains: what happens to hierarchy — the oldest invention of human organization — when the four faces operate together. That story has to be told from the beginning.

The essentials

• Don’t sell by taking away: chat is not eliminated — its reasons for use are taken away.
• The door is an optional, reversible mode — agentive mode; the unit of adoption is one user, not the company.
• The mode is also the honest test: if nobody turns it on twice, the idea dies cheap.
• Four steps, none skippable; the risks are managed with radical transparency and permanent redundancy.