A manager who accepts every request looks like an asset from above and behaves like a liability from below. The difference is where the unresolved decision ends up.
Refusal is where prioritisation actually happens
Priority is set by what an organisation declines, not by what it lists as important. A plan with nothing excluded from it has not prioritised anything.
Managers sit at the point where abstract priority meets finite hours. A refusal at that point is the moment a strategic intent becomes an operational fact.
When the refusal never happens, the intent stays abstract and the finite hours get allocated by whoever asked most recently or most loudly.
The decision does not disappear, it moves down
Accepting more work than a team can do does not create capacity. It hands the team an impossible set and leaves them to choose what to drop.
Individual contributors then make prioritisation decisions with far less context than the manager had, and they make them privately, without anyone recording the trade.
The organisation ends up with priorities set by the least informed layer, which is precisely the outcome the management structure exists to prevent.
Agreeableness is rewarded on a shorter cycle than its cost
Saying yes produces immediate goodwill from the requester. The cost shows up a quarter or two later as a missed date, a quality problem or a resignation.
Those later effects are diffuse and hard to attribute, so the manager collects the reward reliably and pays the cost only partially and much later.
Any incentive structure with that shape will produce more agreeableness than is good for it, regardless of what the company says it values.
Teams read the pattern faster than executives do
People notice quickly whether their manager returns from planning meetings with a shorter list or a longer one. That observation shapes how much they volunteer.
Where every conversation adds work, raising a risk early feels like inviting more of it, so problems get reported later and cost more to fix.
Attrition tends to follow the same pattern, concentrated among the people with the most options, who are usually the ones the team can least afford to lose.
A defensible no requires something to point at
Managers refuse more readily when there is an agreed list of commitments to hold up. Without one, every refusal is a personal judgement and feels like obstruction.
Making the team's commitments visible converts refusal from a stance into arithmetic, which is much easier to defend and much harder to take personally.
It also gives the requester a real choice, because they can see exactly what they would be displacing and decide whether the trade is worth making.