An executive stays away from a project until a critical moment, swoops in to redirect it and claim credit or assign blame, then disappears again until the next visible milestone.
An example
For seven months, the senior vice president sponsoring a new analytics product at a business-software company skipped every working session and sprint review. The product lead ran the roadmap, settled a pricing fight with sales, and shipped a beta to twelve customers. Ten days before general availability, the sponsor arrived at the launch review, declared the onboarding flow "not enterprise-grade," and ordered a redesign that pushed launch back five weeks. He presented the launch to the executive team himself, with a slide titled "Course correction." When adoption came in below plan the next quarter, his note to the chief executive put the shortfall down to "execution gaps on the team." The product lead thought about raising it with the chief product officer, a peer and friend of the sponsor, and decided against it.
Why it works
Going along costs the team nothing new. The sponsorship structure already exists, and letting the routine continue takes no confrontation and no drafted escalation. Escalating looks worse, because the sponsor's name on the charter and the steering committee makes any complaint read as a team that cannot manage upward. It is also costly: the sponsor can defund, reassign, or damage whoever names the pattern, and the interventions are episodic enough that a complaint can be recast as a team that needs hand-holding. Three conditions keep it going: sponsorship that grants authority over outcomes with no duty to stay engaged, escalation paths that all run through the sponsor's peers, and credit that follows visible interventions.
The thinking behind it
Jonathan Baron Outcome Bias in Decision Evaluation (1988), by Baron and Hershey, found that people grade decisions by their outcomes even where the outcome says nothing about the decision. Whoever is in the room when results arrive collects the credit or the blame. The helicopter sponsor arranges to be present at exactly those moments, the launch review and the steering committee, and absent from the work in between. A record of who decided and delivered what at each milestone is the counterweight.
Jeffrey Pfeffer In Power in Organizations (1981), Pfeffer locates power in structural position, including control of the decision process. Formal sponsorship gives authority over outcomes with no duty of engagement, and escalation paths that run through the sponsor's peers add to it. That is why showing the project's value does nothing: it leaves the position untouched. Measuring sponsor engagement and opening an independent route to the executive team change the position itself.
Warning signs
The sponsor is absent from working sessions and present at every steering committee, launch review, and photo opportunity. Interventions arrive late and large: a redesign ordered days before a deadline, a reversal of a settled decision. Executive updates attach credit for milestones to those interventions and describe shortfalls as team execution. Complaints go nowhere because the people who would hear them are the sponsor's peers.
How to defend yourself
Showing that the project is valuable or the team competent will not change this, because neither touches what keeps it going. Work on the record and the escalation path.
- Keep a record, visible to peers, of who decided and delivered what at each milestone: decision logs, release notes with names, steering minutes that note the sponsor's attendance.
- Push for sponsor engagement to be measured, through attendance at working reviews or 360 feedback that reaches the sponsor's own boss.
- Build a line to the executive team that does not run through the sponsor's peers, such as a board demo, a customer advisory group, or a skip-level meeting.
When the sponsor intervenes late, ask for the change and its reasons in writing, and log the schedule effect next to it.
How a leader shuts it down
Define sponsorship as continuous work: attendance at a set share of working reviews, named duties between steering meetings, and feedback from the team that reaches the sponsor's superior. Credit milestones from the record of who did the work. Give project teams an escalation route that bypasses the sponsor's peer group; a team that can reach the executive team directly is much harder to treat this way.