Every change has a size. Name it before you start.
Transformation is one word for five very different sizes of thing, from a habit you build before lunch to a company you take apart and rebuild. Most AI efforts fail not because the idea was wrong but because the scope was never named, so the ambition and the work were never the same size. This is the ladder that names it.
The whole framework
Five scopes, each an order of magnitude larger than the last, and each one built from the scope inside it. You do not choose a rung. You climb them, in order.
The five rungs
Each rung is defined by its unit of change, the thing that is different when you are done. The unit gets bigger every step, and so does everything else: the time, the budget, the number of people whose work has to change, and the cost of getting it wrong.
- The Personal Practice. You, one habit, one afternoon. The unit is a single behavior. The real product is not the hour saved, it is belief, spread by a credible person doing the thing in the open. We have one on the record.
- The Workflow. One process, re-run a new way, in days to weeks. The unit is a process. The trap is speeding up a broken workflow instead of rebuilding it, which only reaches the wrong place sooner. A regulatory team's version is on the record.
- The Amplified Role. One person's whole responsibility stack, over weeks to months. The unit is a role. The vertical move: everything one person owns, until the job itself works differently.
- The Re-formed Function. A whole team's work, over a quarter. The unit is a function. The horizontal twin of the amplified role: not one person deep, but a team across the board.
- The Re-Aligned Enterprise. The whole company works differently, over multiple quarters. The unit is the organization. The re-alignment can be structural, new reporting lines and decision rights, or it can be enterprise-wide enablement that changes how everyone works without moving a box on the chart. The org chart is the easy half; the human half, at Avidity, is on the record.
They nest. That is the whole point.
These are not five options on a menu. Each rung is built out of the one below 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, one order of magnitude at a time.
Which is why the order is not a suggestion. Rung five is literally made of rung four, which is made of rung three, all the way down. This is the same discipline as solving small to unlock the institutional: the small rung is not the goal, it is the only honest way to reach the large one. You compose your way up. You cannot restructure your way down to habits nobody has built.
Almost every company mis-sizes the change in one of two directions. They think too small, and end up with a drawer of clever personal practices that never became a process or a role, invisible on any measure a board cares about. Or they think too big, and announce a re-aligned enterprise with not one workflow running a new way underneath it.
The second failure has a name and a number. Across McKinsey's annual survey, roughly 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: the rungs nobody built.
Scope is one axis of three
The ladder measures how much has to change. That is one axis, and it says nothing about two others that matter as much, so every case study here is 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 kind: 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 case into efficiency or new capability distorted the evidence. A policy taught to a whole company is an enablement intervention whose outcome is translational capacity, not an hours-saved efficiency play. A trivial automation whose real result was belief is not measured in hours either. For a biotech the outcome that matters most is the last one: efficiency hands back hours, but translational capacity and new capability hand you science you could not otherwise do, which is the only kind of win that reaches a patient.
Why it bites harder in biotech
In a small clinical-stage company the rungs are closer together and the stakes on each are higher. One amplified role is a meaningful fraction of a fifty-person company, so rung three moves the whole business in a way it never could at enterprise scale. And there is a scope this ladder deliberately stops short of. Every rung here lives inside your walls, and yet most of your science lives outside them, 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. Build the rungs inside your walls first. They are the ones you can actually finish.
Name the rung, then look one below it.
Take your loudest AI initiative and say out loud which rung it actually is, not which rung it was announced as. A habit, a workflow, a role, a function, or the whole company.
Then ask whether the rung below it is real yet. If it is not, that is your true starting point, and it is lower than you thought. When you want the honest first move spelled out, read which rung to start on.