Collaborators who added little are written into a successful project's launch materials after the work is done, so the team that did it ends up with a smaller share of the credit.
An example
Streaming was where a cable media company expected its growth, and the team building its ad-supported tier finished ahead of schedule. The launch was set to headline the chief executive's all-hands and the board readout. The general manager who led it was the favorite for a group president role. Two weeks before launch, a divisional vice president whose own initiative had stalled added marketing operations, the distribution team, and a corporate development sponsor to the launch steering committee, citing cross-functional alignment, and joined it as well. The final launch deck credited seven functions on its title slide, and the board readout called the tier a model of collaboration across the company. The general manager's name appeared on slide nineteen. The group president role went to an outside candidate that summer.
Why it works
Late additions are framed as critical support, which gives the person adding them the look of a well-integrated organization under their stewardship, usually with themselves in the credit pool. Every added contributor mechanically reduces the original team's share, so their claim looks worse. Defending that share means publicly contesting the contributions of senior, well-networked people the team will need again, which reads as ungenerous. It takes authority to put names into formal artifacts, a window between delivery and the moment credit is allocated, a culture that rewards collaboration language, and decision-makers who see the success secondhand. It fails when the team has direct lines to the senior audience or authorship is unambiguous.
The thinking behind it
Jeffrey Pfeffer In Power in Organizations (1981), Pfeffer treats power as coming largely from position: control of resources, information, and the decision process. Credit is allocated through artifacts such as launch decks and board readouts, and whoever controls those artifacts at the moment credit is set controls the allocation. The defense works on the same ground, with a contribution record and direct lines to the senior audience in place before that moment.
Erving Goffman Goffman's The Presentation of Self in Everyday Life (1956) treats social life as performance before an audience, with those performing together acting as a team and the preparation kept in a back region. A launch is a team performance, and the audience assigns credit to whoever appears on stage. Adding names late changes who appears, which is why the team that did the work needs to be visible in the front region as well.
Warning signs
Steering committee rosters, launch decks, and press releases grow after delivery is already complete. The new names include the person adding them and their allies. Contributions are described in general terms such as alignment, enablement, or support. The team that did the work appears lower in the materials than it did in the project plan, and the person who added the names presents the result.
How to defend yourself
Credit is awarded by audiences reading artifacts at a single moment, so the defense has to be in place before that moment.
- Create a record of who did what early in the project: a contribution log, a charter with named roles, dated updates sent to the senior sponsor.
- Keep direct lines to the senior audience. A standing update to the executive who will read the launch deck makes late additions easy to spot.
- When the roster grows, ask what each new member contributed, and offer to describe each contribution precisely in the materials. Precision shrinks inflated claims without a fight.
- Credit late joiners generously for what they did. You will need them again, and specific generosity costs less than a dispute.
For technical work, authorship conventions (who is listed first, who signs the design) make late additions visible on their own.
How a leader shuts it down
Use contribution records for major projects: named roles fixed at kickoff, with any later additions dated and explained. Hear launch readouts from the team that built the product. When a steering committee grows after delivery, ask why before the materials go to the board.