William Bridges' research on transitions is unambiguous: transformations fail when the ending is unacknowledged. Not because the new thing is bad — because the old thing held meaning the change ignored. Before Intent's new beginning, there's an ending. Here is what it asks you to release.
The loss: predictable two-week cadence, the shared "done this sprint" closure moment, the retrospective as team metabolism.
Sprint planning, retro, review, demo. These aren't trivial — they provide predictable rhythm, social cohesion, and the closure of "done." Intent's continuous loop offers none of these by design. Teams that adopt Intent will feel arrhythmic for weeks. That is expected. It is also a real loss, not a cosmetic one.
The loss: story points, velocity, burndown charts, capacity planning — an entire shared language.
When AI collapses implementation cost, velocity becomes noise. Story points were a calibration tool for human labor, not for agent throughput. Estimators lose a craft. Stakeholders lose a coordination proxy. Finance loses a headcount allocation mechanism. The vocabulary took years to learn and now belongs to a defunct operating model. Grief is a rational response.
The loss: the small closure moment when a ticket moves to Done and the person who wrote it feels completion.
In sprint-based work, every team member has a weekly satisfaction loop. Intent's event streams are continuous — there is no "done this week" moment. For people who run on weekly completion satisfaction, Intent is emotionally flat. We haven't solved this yet. If your team's motivation system depends on that weekly rhythm, adopting Intent will degrade motivation in the short term. That's an honest limitation, not a bug to minimize.
The loss: the standup as a daily moment where teammates see each other's faces, hear each other's obstacles, and feel part of a whole.
Standups aren't just about coordination — they're where social presence happens. Intent replaces standups with async signal capture, which replaces social presence with text. That's a loss, not a neutral substitution. Teams adopting Intent need to replace the social function explicitly — probably with something other than a work-coordination ritual. If you skip this, you'll get a team that ships more and feels lonelier.
The loss: a professional identity built around being the calm center of the ceremony stack.
Scrum Masters, team leads, delivery managers, PMOs, operations roles — many humans built identity around being the person who runs the process. Intent makes that specific identity obsolete. The humans are still valuable (often MORE valuable — their psychological safety work and team facilitation craft is exactly what Intent needs). But the craft of orchestrating human coordination through ceremonies is not what Intent requires. That's an identity loss, which is heavier than a skill loss.
The loss: the ability to call yourself "the person who runs a 20-person team well."
Intent is explicitly for teams of 2–7 (sweet spot 2–5). Over 7 is out of scope. If your career identity is built around successfully managing large teams, Intent says your coordination craft is a symptom of the wrong operating model — not because you're bad at it, but because AI shifts the economics so that large teams become harder to justify. That's a hard thing to hear. It may not be true in your specific context. But it is the implication of Intent's target, and we'd rather name it than hide it.
"Transition starts with an ending. Paradoxical as it may sound, change is not the beginning of the transition. It starts with the ending of something. People only gradually let go of the old ways and the old identifications, and until they do, change will be at best an empty form and at worst a painful setback."
— William Bridges, Managing Transitions (2009)
Before you adopt Intent with a team, hold a 60-minute meeting. Read this page together. Name which losses will land hardest for which people. Let people say what the old way gave them that the new way doesn't yet match. Write down what they said. Use that list as the starting point for designing your neutral zone (see below).
Do not skip this step. It is the single most common change-management failure in our field — jumping to the new beginning without acknowledging the ending, then wondering why the team resists six weeks in.