Trojan Horse Initiative

Tactics of Organizational PoliticsInitiatives and OpticsA borderline tacticAlso known as Untouchable Project Shield

Contested changes travel inside a popular program they genuinely belong to, carried by the program's backing and decided as part of it.

Borderline: whether this move is justified depends on the situation, and only the person in it can judge.

An example

After a near miss with a pressure relief valve, the plant manager of a specialty chemicals site launched a process safety program with corporate's backing. The plant manager also believed the maintenance planners should report to the central reliability group, a change the planners had blocked twice. The near-miss review had found that local scheduling priorities delayed the valve's inspection by five months. So the reporting change went into the safety program's charter as item four, with the finding quoted beside it. The charter went to the site leadership team and to the planners themselves a week before approval. The maintenance superintendent objected that the change was organizational, not safety. The plant manager answered with the inspection record and offered a review after one year. The charter passed with the reporting change in it.

Why it works

The host program's backing carries over to the change, so it looks better than it would alone, and approvers decide it as part of a program they already support, which makes it easier. Opposing it becomes costlier, because the opponent has to argue against part of a safety or compliance program in public. It holds when the host is genuinely needed or popular and the change truly serves the host's purpose. Attach something that does not belong and the host itself is contaminated.

The thinking behind it

Robert B. Cialdini Robert Cialdini's Influence (1984) describes commitment and consistency: once people have taken a position, especially a public one, they feel pressure to act in line with it. Leaders who have backed a safety program in public find it hard to vote against part of it. The clean form uses that pressure honestly, by putting inside the program only changes that genuinely serve it, so that consistency with the commitment points the right way.

Erving Goffman In Frame Analysis: An Essay on the Organization of Experience (1974), Erving Goffman describes frames, the organizing principles people use to make sense of what is going on. A reporting change read inside a safety frame is a safety measure; read alone, it is a reorganization. Putting the change in the charter with the inspection finding beside it supplies the frame and the evidence for it together. Without the evidence, the frame would be doing work the facts cannot support.

When it fits

Works best where a contested change genuinely serves a popular or protected program's purpose and you can show the link with evidence. It needs a role in drafting the host program's charter, a program with real support, and enough standing to defend the link in front of skeptics.

How to use it well

Put the change in the charter, where reviewers will see it, with the evidence that it serves the program's goal.

  • Lead with the finding, incident, or requirement that ties the two together.
  • Circulate the charter to the people the change affects before the approval meeting.
  • Offer a review point, such as a one-year check, so opponents have something to win.
  • Keep the change's budget as a visible line inside the program.

If the link is challenged, defend it on the evidence, and accept separation if the evidence does not hold.

What it costs and where it backfires

Opponents may come to resent the host program, and if the link looks thin, the whole program can stall or lose credibility. The clean form requires that the change genuinely belong. Packaging a change that does not serve the host, keeping it out of the charter, or describing it as an implementation detail so reviewers miss it turns the move into concealment, and an auditor with line-item authority will find it.

When it is used on you

Say so in public when a change you oppose rides inside a program you support, and then ask which parts the program requires on its own, in writing. Request line-item detail and test each item against the stated mission. Ask for a separate vote on the embedded change.

Back to the catalog