Ten mutations of the AI-native office. Some of your colleagues already have powers. Others have side effects. Most have both.
There’s a moment, somewhere around slide three, when you spot the em-dash (—). Then another. Then a cluster of them, loitering like teenagers at a mall, and your brain finishes the sentence on its own. Ah. Claude wrote this.
A year ago, that observation was an indictment. “You used AI for this?” — accusation, eyebrow, judgment, the whole symphony.
Today, the teams adapting fastest have flipped that question on its head. “You had two hours, and you didn’t use AI for this?” Same eyebrow. Opposite direction. Even more judgment.
The office mutated. Half of your company is still operating on a handbook written for the previous species.
So here is the field guide. Ten unwritten mutations I’ve been observing in companies that are quietly running a different game.
Think of it like the X-Men universe, except the mutations didn’t show up at puberty. They showed up the week your company rolled out Claude. Some people got powers. Some people got headaches. Some people got both and haven’t figured out which is which. The professor isn’t coming. There is no school. You’re on your own to figure out which mutation you have, and whether it’s the kind you weaponise or the kind that quietly eats you.
Mutation 1: Change Shape to Match the Room
Knowing how to use a pivot table used to be a flex. Today, it’s like saying you can boil water. Nobody is impressed. They’re mildly worried about you if you can’t.
The same shift is happening to AI right now, except faster. The intern who whispers “I used Claude for this” with the energy of a confession booth is doing the cultural equivalent of saying, in 2008, “I used Google to find that document.” Endearing. Briefly. The first time.
Mystique survives because she becomes whatever the room demands. The professionals coming out ahead right now are doing the same thing, except the room is changing every quarter, and the disguise is fluency, not a face.
Imagine being the only person in 2014 still proudly typing every formula by hand because using INDEX-MATCH felt like cheating. That’s the vibe.
The funny part is the apologising. The scary part is what happens to the people who don’t stop apologising. Two years from now, they aren’t in the room. They’re not even copied on the email about the room.
Mutation 2: Read the Mind Behind the Document
AI output is the starting line. The follow-up question is the finish.
Picture two people. Both presented a ten-page document. Both used Claude. One of them spent the saved two hours sharpening the argument, stress-testing the numbers, and rehearsing the awkward questions. The other one used the saved two hours to doom-scroll.
Now the meeting starts. Somebody asks, “Why this assumption and not the other one?”
Person A answers from memory. Person B starts pressing Ctrl-F on their own document.
The funny moment is watching someone Ctrl-F a doc that was supposed to be theirs. The scary moment is realising that person B was you last Tuesday. Every senior leader I know has now developed a single, brutal habit — call it the Professor X move — they ask a double-click question in the first five minutes. They aren’t testing the model. They’re testing you. And like any good telepath, they’re reading the gap between what’s on the page and what’s actually in your head.
The model can give you a starting line. It cannot give you a finish.
Mutation 3: Heal From Your Own Deleted Code
The engineers who thrive in this era have Wolverine’s healing factor — except for code instead of skin. Write it, scrap it, regrow it by lunch. No scar. No grief. No association.
There used to be a different feeling. Engineers will recognise it. You’d stay late, write 400 lines of clean, opinionated code, and feel a quiet pride in it. That’s mine. I made that. That feeling is gone, and most engineers haven’t grieved it yet.
The new normal: you generate 800 lines of code by lunch, scrap 400 of them by 2pm, and feel nothing. Not loss. Not pride. The same emotional intensity you’d apply to deleting a misspelt WhatsApp message.
The funny version of this is the senior engineer who still names his branches like they’re his children and refuses to delete his auth module even after it has been outclassed by a 90-second regeneration. The scary version is that same engineer, six months later, defending an architecture that should have been scrapped on Tuesday — because if he scraps it, he has to admit that the part of him that wrote it isn’t the part that matters anymore.
If the code isn’t precious, the judgment is. If you can’t make that switch, you’re grieving the wrong thing.
Mutation 4: Audit the Work You Used to Do
The pyramid has flipped. What was grunt became smart, what was smart became cheap, and what was cheap is now where the value lives — storytelling, problem-framing, reviewing, deciding.
This is Rogue’s problem, scaled to the entire workforce. She absorbed every power she touched and then had to learn to control what she’d taken on. AI has handed every professional an enormous new capability overnight, and the people winning are the ones figuring out how to audit what they now have access to. The rest are being run by it.
The funny version is the PM who realises that her job for the next decade is essentially to interview five customers and write three crisp paragraphs of context — and that this is the audit. The model can generate a hundred PRDs. Only she can tell which one is hallucinating the customer.
The scary version is the engineer who has spent fifteen years executing tickets — the ticket says do X, I do X, I close the ticket, I get a good review — suddenly asked to review output for a living, and discovers that he has no idea how. Reviewing demands taste, judgment, suspicion, the ability to say “this looks right, and that is exactly why I don’t trust it”. These are not skills you pick up from a Udemy course on Friday.
Factory workers became auditors. Engineers are next. The transition is not optional. The retirement plan, for the people who refuse it, is.
Mutation 5: Phase Out of the Review Chain
The chain of trust has quietly grown a new link. You write code, often with an agent. You submit a PR. An agent reviews the PR first — flags the risks, summarises the diff, and lists the suspicious bits. Then a human picks it up, already briefed by the bot. Models reviewing models. The human is the third (or the last) reviewer in a process that used to have one.
The funny version is the senior engineer who has started writing PR descriptions aimed at the AI reviewer instead of his teammates — adjusting his tone, padding the rationale, gaming whatever the bot seems to reward. A grown adult, doing the developer equivalent of writing an essay for the teacher who gives the most partial credit.
The scary version is the slow Kitty-Pryde-style vanishing of the last human who actually reads the code. She phases out one layer at a time. First, she stops reading the diff. Then she stops reading the bot’s summary. Then she stops reading the bot’s executive summary. Now she clicks the green checkmark when the dashboard turns green, because the dashboard turned green because the bot said so, because the bot was trained on a thousand previous PRs, all in the same chain, rubber-stamped. Somewhere in that loop, the last person who could spot a subtle logic error logged off for the day. Possibly the year.
The PR didn’t fail. The review chain did.
Mutation 6: Burn Through Tokens Like Flame
Word travels. Multiple enterprises have burned through an entire fiscal year’s AI budget in a single quarter. Not because someone was reckless. Because everybody, all at once, discovered they could. The fire didn’t need an arsonist. It just needed permission.
The funny version: a VP triumphantly showing the “AI usage” chart in the QBR. Beautiful trend line. Up and to the right. The CFO walks in three slides later, carrying a bill that looks like a phone number.
The scary version is the next slide, which doesn’t exist yet but is being drafted in many companies right now: “AI cost-to-revenue ratio.” That’s the slide where productivity gains have to start showing up in actual P&L. If you spent millions in tokens and you can’t point to measurable outcomes, you didn’t do an AI transformation. You did a very expensive science fair.
AI without ROI is just a hobby with a higher invoice.
Mutation 7: Multiply Yourself Into a Team
This is the headline of the decade, and most companies haven’t printed it.
The IC who learns to orchestrate three or four agents — pick the right model for each job, write the brief, review the output, catch the hallucinations, glue the work together — is doing the job of a small team. Some companies are calling the agents minions. The naming is silly. The leverage is not. It’s Jamie Madrox’s power, the Multiple Man — one body, many duplicates, all working in parallel, all needing direction.
The funny version is the twenty-two-year-old engineer who has no human direct reports and somehow has more operational complexity than your average VP, running fourteen parallel agent workflows like he’s coordinating an airport.
The scary version is what this does to the org chart. The ten-person scrum team is quietly becoming a three-person pod. In some teams I’ve seen, a two-person pod. In one, a single engineer running what used to be a sprint. Standup is now a person talking to themselves about what their agents did overnight. The retro is a Notion doc that the agents wrote. The PM is also the tech lead and the QA. Capacity didn’t shrink — the surface area each human covers expanded by an order of magnitude, and the headcount adjusted accordingly. If your last reorg cut the team by 60% and called it efficiency, this is what was actually happening.
And inside that pod, the senior engineer who has built a fifteen-year career executing well-defined tickets — never wrote a brief, never had to delegate — is now managing a fleet of agents who, like every direct report in history, do exactly what you said, and exactly not what you meant. Agents don’t read minds. Neither do your direct reports. The senior engineer who learned to manage people is fine. The one who never did is in trouble.
The headcount didn’t leave because the work left. The headcount left because the work fits in fewer heads.
Mutation 8: Freeze Mid-Decision
For roughly the last eight years, decision-making in tech orgs has been quietly delegated upward. Let me check with the PM. Let me check with the architect. Let me wait for the PRD. Let me get the ticket.
Whole cohorts of professionals have built careers without ever having to make a real call. The structure was decided for them. The hierarchy decided for them. The Jira ticket decided for them.
Now you have to manage agents. Agents need decisions. Constantly. Mid-task. With incomplete information. And here’s the Iceman trap — you can build anything out of ice, bridges, weapons, armour, an entire fortress — but if you won’t pick a direction, none of it moves.
The funny version is the engineer who asks the AI what it should do, then forwards the AI’s answer to Slack to ask his colleagues what they think the AI meant, and then schedules a meeting to align on the AI’s preferred approach. Six layers of consultation to avoid one decision.
The scary version is the senior leader who looks around at all the new tooling, all the new agents, all the new leverage, and realises that the limiting factor isn’t compute, cost, or the model. It’s that nobody in the building has the muscle to decide fast enough to keep the agents fed.
A flock of agents waiting for instructions is the most expensive idle resource your company has ever owned.
Mutation 9: See the Pattern Across Ten Thousand Pasts
Everyone is suddenly talking about taste as if it were a setting you could toggle in your Anthropic console. It is not. Taste is a graph you build over the years, node by node, by being exposed to enough things that patterns start to assemble themselves. Destiny, the precog, could see across ten thousand futures because she’d already seen ten thousand pasts. The future-sight wasn’t magic. It was pattern recognition compounded.
The funny version: an engineer who has only ever built a few apps confidently tells a designer that her layout is wrong. The designer who has used 10,000 apps quietly closes her laptop.
The scary version is that the companies winning right now aren’t winning because they have better models. Everybody has the same models. They’re winning because somebody in the building has seen ten thousand products, ten thousand workflows, ten thousand failures — and you’ve seen thirty. The graph matters more than ever, because the model will give you a hundred plausible options, and only taste tells you which one isn’t embarrassing.
You can’t shortcut this. You build it by paying attention, on purpose, to things you didn’t make.
Mutation 10: Remember the Sky Exists
To be on top of everything happening in AI, you have to be unemployed.
Storm commanded the weather because she remembered the sky existed. Most of the people frying themselves trying to keep up with AI have forgotten. The leverage is never behind another browser tab. It’s never in the next podcast. It’s in the part of your brain that you can only reach by closing the laptop.
The funny version is the director who hasn’t seen sunlight in three weeks announcing in standup, with the calm of a hostage, that he has achieved alignment with the new harness.
The scary version is that the anxiety isn’t a bug. It’s a signal — and the people who learn to read it figure out something quickly. The people who don’t are still optimising their RSS feed at 2am.
Pick one problem. Go end-to-end. Make peace with the fact that you will not be an expert on everything. Nobody is. The people who act like they are have simply outsourced their anxiety to LinkedIn.
Better than yesterday. Not better than the entire AI ecosystem. Just better than yesterday.
Closing
The old handbook was about how to do the work.
The new handbook is about what to do once the work has been done.
The em-dashes will keep showing up — like in this post. The tokens will keep getting burned. Your code will keep getting deleted by something that doesn’t know what your weekend felt like. The ten-person team will continue to become a three-person team. And every two hours, somebody at your company will save themselves a routine afternoon and then quietly throw the saved time straight into the void — into another deck, another refinement loop, another search for the perfect dashboard colour.
The one mutation that didn’t make the list, because it isn’t a mutation, it’s the whole point:
Use the saved time on the one thing the machines can’t do for you.
Talk to a customer. Sit with a problem until it tells you what it’s actually about. Have the conversation you’ve been avoiding. Make the decision your org has been pretending it’s already made.
That’s the work now. Everything else is a starting line.
The office mutated. The mutations are catalogued. The only question left is whether you used the time the machines gave you to become someone they can’t replace — or whether you spent it making prettier slides.
The machines gave you time. Spend it like it matters.
Digital Journey 