Hiding the losers from the pitch guarantees resistance you never see coming, because the resistance forms in rooms you're not in. Intent changes who holds power on a team. Some roles gain. Some lose. Some will actively resist adoption and have legitimate reasons to do so. Here is the honest map.
If you are adopting Intent in an organization that has any of the "actively resist" roles — and most orgs over 50 people do — you have a political problem, not a methodological one. Intent's technical merits do not survive contact with a PMO that needs weekly velocity rollups. Either the PMO gets translated-for (which is expensive and ongoing) or the PMO learns a new language (which is a change program, not a tool adoption).
Naming this upfront is not pessimism. It is honesty. If you try to adopt Intent without addressing the resistance, you will fail in month 3 and the failure will look like "the methodology didn't work" when the actual failure was unaddressed political gravity.
For the roles most affected, here is what the transition actually looks like — what's lost, what's gained, and what the role becomes. Intent does not make these humans less valuable. It changes what their value is.
The craft of running standups, retros, and planning disappears with the ceremonies themselves. That's real. But the deeper craft — facilitating a team learning conversation, holding space for disagreement, noticing the silence before it becomes disengagement — is more valuable in Intent, not less. Intent's psychological safety contract (Promises 1, 2, 5, 6) depends on someone holding the meta-view of team dynamics.
This is the transition Intent is most honest about being unsolved. Junior engineers traditionally developed craft by implementing tickets — the productive struggle of turning a story into working code is how judgment develops. When agents do that work, juniors lose the scaffold. We haven't fully figured out what replaces it. Current best answer: structured apprenticeship in spec-shaping, where a junior pairs with a senior on the four-persona protocol and learns by watching specs come together.
PMs whose daily work was running prioritization meetings, writing tickets, and facilitating between stakeholders lose most of that work. PMs whose daily work was customer discovery, outcome definition, and spec clarity gain leverage. The shift is from managing the coordination layer to managing the clarity layer. Torres-trained PMs already operate this way; Jira-trained PMs don't.
PMOs translate engineering work into stakeholder-legible reports. Intent's event streams don't roll up into the formats stakeholders expect. This is a hard break, not a soft one. The PMO can either learn a new reporting language (which is months of work and their stakeholders don't understand the new format) or push back on Intent adoption (which is often the right call for the organization). We are not pretending this is a win-win. It isn't.
Intent is explicitly for teams of 2–7. Over 7 is out of scope. If your career identity is built around successfully managing 20-person teams, Intent says that team shape 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 for engineering work. Your craft is real. Intent is not for it. That is honest, not dismissive.
Before you adopt Intent, share this page with everyone who will be affected. Let them read it. Then have a hard conversation about who in your specific org will lose and who will gain. Identify which "actively resist" roles you need to work with, not against. Build your Kotter Step 2 guiding coalition around the honest reality, not the optimistic pitch.
If reading this page makes you realize Intent isn't right for your org, good. That is a valid outcome of honesty. We'd rather lose you here than six weeks into a failing pilot.