An Afternoon, or a Restructure

Someone tells you they are transforming their company with AI, and you have no idea what they mean.

They might mean they built a habit last Tuesday that gives them back an hour a day. They might mean they took their whole org chart apart and rebuilt it around how the work actually happens now. Those are not the same project. They do not share a budget, a timeline, a risk profile, or even the same person’s signature. But we file both under one word, transformation, and the word does most of the damage. It lets a drawer full of clever habits pass for a strategy, and it lets a strategy deck stand in for a drawer full of habits nobody has built yet.

There are five sizes. Each one is roughly an order of magnitude more scope, more time, and more risk than the size below it. The smallest fits in an afternoon. The largest is a restructuring you will live inside for the better part of a year.

The five sizes

One. The Personal Practice. You, one habit, one afternoon. You find a way to use a model that quietly changes how you spend an hour of your day. The productivity is almost beside the point. The real product is belief: you, or a respected colleague, doing the thing in front of everyone else, which is how adoption has always actually spread. A century of research on how new practices move through a group says the same thing, that it starts with a few credible people and their social proof, not with a mandate (Rogers, Diffusion of Innovations). This rung looks trivial. It is the one everything else stands on.

Two. The Workflow. One process, re-run a different way. Days to weeks. Here is the first real trap. The temptation is to bolt a model onto the process you already have and call the faster version a transformation. Michael Hammer named the mistake more than thirty years ago and it has not aged a day: don’t automate, obliterate. Speeding up a broken workflow only gets you to the wrong place sooner. The move is to ask what you would build if you designed the process today, knowing what these systems can now do, and then close the gap to that.

Three. The Amplified Role. One person’s whole responsibility stack. Weeks to months. Not one of their tasks, all of them: the regulatory lead, the head of clinical operations, the founder wearing four hats. You go deep on everything one person owns until the role itself works differently. This is the vertical move, and it is often where a small company gets its first real leverage, because in a small company one amplified role is a meaningful fraction of the whole.

Four. The Re-formed Function. A whole team’s work, all at once. A quarter. The horizontal twin of the amplified role: not one person going deep, but a function changing across the board. The entire regulatory group, all of clinical operations. This is where it stops being personal and starts being an operating decision, because now other people’s work depends on the change holding.

Five. The Re-Aligned Enterprise. The company rebuilt around how the work is actually done now. Multiple quarters. New reporting lines, new decision rights, new definitions of whose job is what. This is the rung everyone points at when they say the word, and it is the rung almost nobody reaches, because most companies announce it before they have built a single one of the rungs below it. The data is blunt: across a large annual survey, only around seven percent of organizations report AI that is fully scaled, and the blockers are not the models, they are workflow rigidity and operating-model inertia (McKinsey, The state of AI).

They are not five buckets. They nest.

Look at the diagram again. These are not five separate options on a menu. Each one is built out of the one inside it. A workflow is a bundle of habits. A role is a bundle of workflows. A function is a bundle of roles. The enterprise is a bundle of functions. The ladder is not five different projects. It is the same unit of change, composed upward.

That is why the order is not optional. Rung five is literally made of rung four, which is made of rung three, and so on down. A re-aligned enterprise with no re-formed functions inside it is an org chart with nothing running in it. You cannot restructure your way to habits nobody has built. You compose your way up.

The two ways to get it wrong

Almost every company gets the scope wrong in one of two directions.

They think too small: a drawer full of clever personal practices, a team that is quietly good at prompting, and nothing that has changed at the level of a process or a role. Real, useful, and invisible on any measure the board cares about. Or they think too big: a rung-five announcement, a transformation office, a slide that says the company will be AI-native by a date, and underneath it not one workflow that runs a new way. That is how a strategy becomes a pilot in purgatory.

The discipline is to name the rung honestly, pick the largest one you can actually make real this quarter, and then climb. It is the same lesson as solving small to unlock the institutional: the point of the small rung is not the small rung, it is that it is the only honest way to reach the big one.

Scope is one axis of three

The ladder tells you how much has to change. That is one axis, and it is silent on two others that matter as much, so the case studies against this ladder are tagged on all three. Scope is the rung, from individual to enterprise. Intervention is how you did it: enablement, governance, automation, workflow redesign, a product, infrastructure, or organizational redesign. Outcome is the win, and there is more than one: efficiency, risk reduction, decision quality, new capability, or translational capacity, the rate at which the whole institution turns science into therapies.

The outcome axis has more than two values because the cases forced it. Squeezing every one into efficiency or new capability distorted the evidence: a policy taught to a whole company is enablement whose payoff is translational capacity, not an hours-saved efficiency play, and a trivial automation whose real result was belief is not measured in hours. For a biotech the outcome that matters most is the last one. Efficiency gives you back hours. New capability and translational capacity give you science you could not otherwise do, which is the only kind of win that reaches a patient.

One honest caveat for clinical-stage readers. Every rung here lives inside your company, and yet most of your science lives outside it, across your CROs and CDMOs. Changing how work flows across that boundary is a scope of its own, above the enterprise and harder than all of it, because you do not control the people on the other side. We will get there. Build the rungs inside your walls first.

Monday morning

Take the loudest AI initiative in your company right now, the one with a name and a champion. Say out loud which rung it actually is. Not which rung it was announced as, which rung it is: a habit, a workflow, a role, a function, or the whole company.

Then ask the only question that matters. Is the rung below it real yet? If you are aiming at a re-formed function but no single role inside it has been amplified, you have found your real starting point, and it is one rung lower than you thought. Start there. That is not a retreat. That is how you build something that holds.

The full framework, the five rungs and the two axes, lives on The Scope Ladder.

Cheers,
-Titus