Most product managers carry two documents into a meeting: the one on the slide deck, and the one in their head. The novelist Elias Canetti spent decades studying what he called the 'command residue' — the psychological trace that an order leaves behind in the person who receives it, long after the order has been obeyed or forgotten. His central observation, buried in *Crowds and Power* (1960), is that human beings don't simply execute instructions and move on; they accumulate them, and the residue shapes future behavior in ways neither the commander nor the recipient consciously tracks. Now apply that to a product org. Every strategic pivot, every urgent re-prioritization, every 'we're changing direction but trust the process' moment deposits a residue in your team. Engineers start building in hedges. Designers prototype at half-investment. PMs quietly pad timelines. Nobody announces this. Nobody even decides it. It just accretes, directive by directive, until the team's actual behavior diverges significantly from the behavior the org chart describes. The uncomfortable implication: your roadmap's real constraint isn't resources or technical debt — it's the accumulated weight of past commands that were obeyed but never fully resolved. The practice Canetti points toward isn't just better communication going forward. It's periodically surfacing what the team is still carrying, naming the residues explicitly, and deciding together which ones to put down.

Name one decision made in the last quarter that your team technically accepted but never fully put down — what behavior is still showing up because of it?

Drawing from European Political Anthropology / Literary Philosophy (Elias Canetti) — Elias Canetti (Crowds and Power / Masse und Macht, 1960)