Talented rivals get named to so many prestigious, unrelated projects that their effort spreads too thin to excel anywhere, and turning one down reads as a lack of ambition.
An example
Six months after a private-equity firm bought a commercial cleaning company, the operations director for the western region was the obvious candidate to run operations nationally. The chief operating officer, who wanted the job for an ally, praised her at the quarterly leadership meeting and asked her, in front of the deal partner, to lead the pricing task force. Within the quarter she was also on the safety program, the systems migration, the acquisition-integration team, and a customer-retention pilot. None of them shared stakeholders or a meeting rhythm. When she asked the chief operating officer which mattered most, he said they all did and that he had expected her to welcome the exposure. By the annual review three of the five were behind schedule, and the national role went to the ally.
Why it works
Each assignment arrives as a vote of confidence, and saying yes is what ambitious people are expected to do, so acceptance is the easy path. Refusing has no respectable language in a culture that reads stretch work as reward, and declining in front of sponsors gets a person marked as not executive material, which makes the alternative both less attractive and more expensive. The damage lies in the portfolio as a whole, while each piece looks reasonable alone. It works when the person behind it controls assignment flow, the culture equates load with talent, and the target is ambitious enough to keep saying yes.
The thinking behind it
Herbert A. Simon Designing Organizations for an Information-Rich World (1971) argues that attention is the scarce resource in an organization full of information and demands. A portfolio of unrelated projects spends a rival's attention across many fronts, so none receives the sustained focus that produces visible excellence. Portfolio caps and a single named priority protect that scarce resource directly.
Erving Goffman The Presentation of Self in Everyday Life (1956) describes performances given in a front region before an audience. Offering a prestigious assignment in front of sponsors puts any refusal on that stage, where saying no damages the rival's performance as an ambitious leader. Taking the portfolio question to a sponsor privately moves it to a back region, where priorities can be discussed without that cost.
Warning signs
One performer's name appears on a disproportionate share of new task forces in a single quarter. The assignments share no stakeholders, skills, or cadence. Offers come in public or in front of sponsors, where refusing is awkward. Asking for priorities is read as being uncommitted, and the same person is the source of most of the offers.
How to defend yourself
Audit the portfolio as a whole: list each assignment with its stakeholders, skills, and rhythm, and count the hours.
- Take the list to a sponsor senior enough to review it with you and help turn a no into a focused commitment.
- Keep explicit time accounts and ask for written priorities, so the trade-offs are on paper.
- Note who is making the offers. If it is mostly one person, tell your sponsor, calmly and with the list.
- Accept new work only when something named comes off.
A culture that gives people a normal, penalty-free way to decline opportunities takes most of the force out of this.
How a leader shuts it down
Make assignment allocation visible, with a cap on concurrent projects per person and a single named priority for anyone on more than two. Review your strongest people's whole portfolios at least quarterly. Judge output by the depth of results, and give everyone a standard way to say no without penalty.