Transformation theater describes a change effort that adopts the surface trappings of agile/product-model work — ceremonies, new titles, retros, standups — while the underlying delivery mechanics remain a software factory. Coined in this sense by Anoir (CPTO, Palace Hotels) to describe his org's pre-transformation state: agile ceremonies existed, but requests still flowed as fixed-scope projects through a fixed end-to-end pipeline (prototype → story points → development → 'done' → deployment by a separate infra team → team dispersal).
The tell is structural, not cosmetic: teams are dissolved after each project instead of persisting around a problem area, and 'done' means a ticket closed rather than an outcome achieved. See Product Model (vs. Roadmap Model) for the target state and Earning the Right to Define Problems for why the fix started with how problems are solved rather than which problems are chosen.
About a year into the transformation, a trust crisis surfaced at Palace Hotels over what "done" actually means: stakeholder sign-off against an agreed spec (the waterfall tell) versus an outcome achieved in the market. The dispute was sharp enough that it took a full-day sit-down among the company's three owning brothers to resolve — see Family-Governance Principle for Resolving Ownership Disputes ('Protect the Company from Ourselves') for how. The episode shows transformation theater doesn't only live in ceremonies and titles; it can persist as an unspoken disagreement about the definition of success that only surfaces under pressure.
Cagan also uses "product management theater" as a companion term to transformation theater — describing organizations that adopt the surface trappings of the role (titles, ceremonies, artifacts like roadmaps or backlogs) without the substantive underlying practice (real Discovery (Product Discovery Process), real Product Strategy, genuine team empowerment). Both terms function as the same red flag: check whether the form is backed by the practice, not just present.
The clearest test for transformation theater: ask the organization to articulate why it's pursuing the product model, beyond having named and adopted surface-level practices (see Installation vs. Adoption). An organization that can describe the practices but not the underlying purpose is staging theater, not transforming.
Apply: treat 'we can't state the why in one sentence' as a red flag equivalent to a missing vision — see Vision Vacuum: No Vision, Not Bad Vision, Is the Real Failure Mode.
Из тем: Transformation in Practice