Strict adherence to a new methodology gets rewarded above business results, so compliant failures are promoted, effective workarounds are written up, and people learn to follow the ritual.
An example
A payroll software company adopted a scaled agile framework and tied manager scorecards to ceremony attendance, story-point hygiene, and completed planning artifacts. That year two teams stood out. The billing team ran every ceremony on schedule, filled every template, and missed its release by a quarter; its manager was promoted and presented at the next town hall as an example of the new way of working. The tax-filing team skipped two planning increments to fix a calculation error before the January deadline, shipped on time, and kept a large customer from leaving. Its manager received a written warning for deviating from the cadence. By spring, three other teams had stopped escalating customer problems whose fixes would require breaking the sprint plan.
Why it works
Visible compliance becomes the currency of recognition, with process champions at town halls and promotion cases written in the methodology's vocabulary, so following the ritual looks better. Getting results through judgment looks worse, since off-process results are labeled cowboy work, and review flags and audit findings make workarounds costly. Control of measurement and promotion is the precondition, along with business outcomes noisy or slow enough for proxy metrics to fill the gap and sponsors who treat the methodology as the deliverable. Once people internalize the goal, they police themselves. The cost arrives later, when reality reaches an organization trained to optimize the wrong thing.
The thinking behind it
A. Michael Spence Spence's Job Market Signaling (1973) shows how a costly, visible action can communicate qualities an observer cannot see directly. Where business results are slow or noisy, ceremony attendance and completed artifacts become the visible signal of a good manager, and people invest in the signal that gets noticed in place of results that do not. Reporting outcomes beside compliance gives managers something worth signaling with.
Herbert A. Simon In Administrative Behavior (1947), Simon analyzed organizations as systems of decisions shaped by premises the organization supplies, such as goals, information, and procedures. A scorecard that counts methodology compliance is such a premise, and managers who decide by it will choose the ritual over the workaround that would keep a customer. Putting outcomes on the scorecard changes the premise, which is why the leaders' remedy starts there.
Warning signs
Compliant failures are promoted and non-compliant successes are written up. Scorecards count ceremonies attended, templates completed, and artifacts delivered, and business results are missing from them. Audit findings name people who deviated from the process even when their work succeeded. Teams stop raising problems that would require breaking the process, and promotion narratives start to sound like methodology training material.
How to defend yourself
Restore outcome visibility, because the pattern lasts only while results stay out of view.
- Report compliant failures and non-compliant successes side by side, with their business results, to the sponsors who fund the methodology.
- Tie your own reviews, and your team's, to outcomes that are sharp and immediate: cash, churn, safety, on-time delivery to customers.
- When you deviate from the process for a business reason, document the reason and the result at the time, and send it to your manager before anyone else frames it.
- Find a sponsor who owns a P&L. Owners of revenue and margin tolerate the gap between ceremony and results less than anyone.
Argue for the methodology's useful parts while you do this. Opposing it wholesale lets its owners treat you as resistance.
How a leader shuts it down
Put business outcomes on every scorecard that counts methodology compliance, and weight them more heavily. Review promotion cases for candidates whose projects missed their targets. When a team breaks the process to deliver a result, examine the process before you examine the team.