Why do your stakeholders agree, then derail the sprint?
Leon Festinger published cognitive dissonance theory in 1957. The finding: when people publicly commit to a position, they experience psychological discomfort if they later act inconsistently with it. They adjust their behavior to restore consistency. Private beliefs are malleable. Public commitments are sticky.
This explains the single most frustrating pattern in product management.
The Pattern
You meet with a stakeholder one-on-one. They agree Feature B is more important than their Feature A this quarter. They nod. They say “makes sense.”
Two weeks into the sprint, the same stakeholder emails: “Hey, checking in on Feature A, when can my team expect it?”
You reference the previous conversation. They say: “I don’t remember agreeing to that timeline.”
They’re not lying. They’re not playing politics. The private agreement you extracted carried zero psychological weight. There was no dissonance cost to ignoring it because nobody else witnessed the commitment.
The Fix: Public Commitment Forums
Instead of getting alignment in private and hoping it sticks, design a forum where stakeholders commit in front of each other:
- Quarterly prioritization review. All stakeholders in one room. The tradeoff conversation happens in the open. “We can do X or Y this quarter, not both. Which one ships?” Each stakeholder states their position publicly.
- Biweekly sprint demo. Stakeholders see working software. If what’s shipping doesn’t match expectations, they say so, publicly. The commitment gets reinforced or corrected every two weeks.
- Written, shared decision log. After every prioritization decision, publish who agreed to what. One paragraph. Public, searchable, permanent.
The point isn’t to trap stakeholders. It’s to create conditions where their private incentive (push for their feature) is balanced by a public commitment cost (being seen as the person who derailed the sprint).
Why This Feels Uncomfortable
Most PMs avoid public commitment forums because they fear conflict. “What if stakeholders argue in front of each other?” That’s the point. The conflict already exists, it’s just happening asynchronously, disguised as polite one-on-one meetings, surfacing as scope creep two weeks into a sprint. Better to have it in the room, once, with everyone watching.
The biweekly demo is, in I/O terms, a cognitive dissonance intervention. When stakeholders see working software every two weeks and hear peers acknowledge progress, the private pressure to push their own feature is replaced by public acknowledgment of what is shipping. Scope creep is not a sign that stakeholders are unreasonable. It is a sign that the commitment mechanism was too weak to survive.
Cognitive Dissonance and AI
When an AI agent generates a prioritization recommendation, who experiences the dissonance if it’s wrong? The PM who approved it? The agent doesn’t have a self-concept to protect. The human does. Every AI-assisted decision needs an unambiguous human owner, not because the human is always right, but because accountability requires a self that experiences dissonance. Agents don’t have one.
Private yeses don’t stick. If your stakeholders keep derailing sprints two weeks after agreeing to the plan, the problem isn’t them. It’s your commitment mechanism. Make the forum public and the decision log shared. s@spencervaradi.com.
Related: ‘The Team Owns It’ Is a Recipe for Nobody Owning It.