Help offered publicly by a rival, in staff or resources, introduces complexity, delays, or flaws that surface late, so the project fails and the blame stays diffuse.
An example
With a demo due in ten weeks, the enterprise sales vice president at a national telecom carrier had won approval to pilot a private wireless network for a large port operator. The network engineering vice president, who had argued for a different pilot customer, offered two senior engineers in front of the executive team. Declining would have looked territorial. The engineers attended meetings and logged hours. Their configuration work arrived late each sprint, and in week nine testing showed the core network settings were wrong for the port's equipment, a problem the engineers said they had raised in a document no one could find. The demo slipped six weeks. The port operator signed with a competitor. At the review, the failure was put down to an ambitious timeline, and the network vice president was thanked for lending staff.
Why it works
Refusing a competitor's public offer of help looks paranoid or ungracious, so accepting is the easy path, and going alone looks worse, recast as silo-building. Visibly declining in front of executives carries a real reputational cost. The saboteur never argues that the target should accept; they only make refusal look bad. A culture that praises collaboration supplies the cover, and the rest comes from technical complexity that keeps flaws from looking deliberate, a helper who can point to genuine effort, and defects that surface late, when fixing them is expensive and blame is spread around.
The thinking behind it
Robert B. Cialdini Robert Cialdini's Influence (1984) describes reciprocity: people feel obliged to accept and repay what others offer, including favors they did not request, so refusing an offer can feel like a breach. Help offered in front of executives carries that pressure, and the team that declines looks ungracious. Treating offered help as an input to be quality-checked like any other takes the obligation out of the decision.
George A. Akerlof George Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) shows how trade goes wrong when one side knows the quality of what is offered and the other cannot tell. The helpers know how good their work is, while the receiving team often cannot judge until defects surface late. An independent quality check, and work made observable week by week, close that gap before it becomes expensive.
Warning signs
Unsolicited help arrives from a peer with a stake in the outcome, usually offered in front of executives or in writing. Output from the helpers falls far below their demonstrated work elsewhere, and they hold a bottleneck such as a sign-off, a specialist skill, or a handoff. Defects surface late, close to the delivery date. The helper argues only that refusing would be ungracious and never makes a case for accepting.
How to defend yourself
One-sided pressure, all on the cost of refusing and none on the merits of accepting, is the tell. When you see it, decline on those grounds, politely and in writing, or accept on terms.
- Run offered help through an independent quality check, such as a red team, an outside reviewer, or your own lead engineer.
- Keep critical work with people whose competence and incentives are not in question.
- Make the helpers' work observable as it happens, with deliverables due weekly.
- If output stays poor, ask your sponsor, on the record, for a replacement.
How a leader shuts it down
Make it acceptable to decline help without explaining why, and avoid praising collaboration in ways that make refusal costly. Put independent quality review on projects where a rival is contributing staff. When a project fails after a peer's help, review the help along with the timeline.