Projects designed to fail are started and made to look like a rival's work, so the failure damages the rival's credibility and backing them becomes a liability.
An example
Margins were the complaint of an activist investor who had bought 6 percent of a packaging company's shares, and the company was bracing for a public campaign. In the spring a quick-win procurement initiative appeared in the strategy pack under the chief operating officer's function, with a savings target of $40 million in a year. The chief executive mentioned it on an analyst call. By the third quarter the savings had come in at $9 million, the activist cited the miss in a public letter, and two directors asked the chief operating officer to explain. The chief operating officer's team had no record of drafting the initiative. The slide, it turned out, had come from the office of the chief financial officer's chief of staff, and the chief financial officer was a rival for the top job. The chief operating officer reconstructed the document trail and took it to the board chair before the next meeting.
Why it works
Staged failure degrades the rival's perceived competence and judgment, so they look worse, and backing them now carries the cost of association with a visible miss, so allies hesitate and sponsors keep their distance. The rival cannot easily rebut without naming the saboteur, which sounds paranoid without proof. It depends on plausible attribution, a failure that speaks for itself, no thread leading back to the orchestrator, and a rival whose reputation is elastic enough to bend under one event. Discovery reverses it: once the author is traced, their earlier attacks look suspect too.
The thinking behind it
Erving Goffman Erving Goffman's Frame Analysis: An Essay on the Organization of Experience (1974) defines a fabrication as the deliberate management of activity so that others form a false belief about what is going on. A false flag project is a fabrication about authorship: the audience believes the rival proposed what someone else drafted. Reconstructing the document trail breaks the fabrication, and once it is broken, it discredits its author.
Lee Ross Lee Ross's The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process (1977) named the fundamental attribution error: observers explain behavior by the actor's traits and underestimate the situation. When an initiative under the rival's name fails, the audience reads it as the rival's poor judgment and rarely asks how the initiative came to exist. Confirming who actually proposed it before assigning blame is the check against that error.
Warning signs
On paper, a failed initiative traces to the rival, but no one on the rival's team recalls originating it. The documents carry the rival's name without their usual authors or approvals. The initiative's targets were unusually aggressive, and its failure was publicized quickly. Someone outside the rival's team keeps the failure in front of senior leaders.
How to defend yourself
Reconstruct the initiative's origin before anyone assigns blame: who drafted it, who staffed it, who first proposed it, and when. Pull document histories, meeting invitations, and early emails, and ask the people named on the documents what they remember. Present the trail to the board chair, the chief executive, or another senior person privately and with evidence, since an accusation without proof will sound like an excuse. Keep a clear record of what your own team originates, with dates, so the gap is easy to show next time. Once a thread leads back to the author, the tactic turns on them.
How a leader shuts it down
Attach a named originator and approver, with a document trail, to every initiative that enters the strategy pack. Before assigning blame for a failed initiative, confirm who actually proposed it. Treat an attempt to plant a failure on a rival as a dismissal-level matter, and say so.