A product or sales leader brings a real, documented client commitment to the prioritization meeting, so the committed project moves up the list and arguing for its rivals means arguing against the customer.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Before the quarterly roadmap review at a payroll software company, the head of sales sent the engineering leads the signed order form from a hospital chain: single sign-on with its scheduling system by March 31, with a service credit of $40,000 a month if it slipped, on a contract worth $2.4 million a year. A week earlier she had asked the client's chief information officer whether April would do. It would not. In the meeting she put the clause on the screen and named the two projects that would have to move to make the date. The vice president of engineering argued for the security fixes his team had wanted since summer. The committee moved them to the next quarter, recorded the client clause as the reason, and assigned a team to single sign-on that afternoon.
Why it works
The commitment does three things to the decision. It makes the committed project easier to approve, because the debate becomes a question of honoring a signed obligation. Rival projects look worse beside a customer with a date and a penalty. And arguing for them looks costly, since whoever does is arguing for a breach that risks revenue and the company's reputation for delivery. The move works best where customer commitments carry real weight, the commitment can be shown on paper, and sales has the standing to bring it to the table.
The thinking behind it
Robert B. Cialdini Commitment and consistency, from Cialdini's Influence (1984): once people have taken a position, especially a public or written one, they feel pressure to act in line with it. A signed promise to a client is the company's own written position, so honoring it feels like consistency and dropping it feels like going back on its word. That pressure carries the project up the list before anyone has weighed it against the rivals.
Thomas C. Schelling Credible commitment, from The Strategy of Conflict (1960): a party that visibly removes its own option to retreat forces the other side to adjust. A commitment made to an outside client works the same way inside the company. The option of putting the project off has been given away, so internal rivals must adjust to it. The same logic says that commitments which bind the company should be made only by people entitled to bind it.
When it fits
Use it when a client commitment is real, written, and material: a contract term, a dated order form, a penalty, a renewal that depends on it. You need the document, a relationship with the client good enough to ask about flexibility, and a seat in the forum where priorities are set. It suits commitments made by someone with the authority to make them.
How to use it well
Bring the paper. A commitment shown in writing ends an argument that a remembered one only starts.
- Send the clause, the date, and the contract value to the engineering leads before the meeting.
- Ask the client in advance whether the date has any give, and report the answer honestly.
- Name the projects that would have to move, so the trade-off is on the table.
- Ask that the minutes record the commitment as the reason.
Afterward, help fix how commitments get made, so engineering is consulted before the next one is signed.
What it costs and where it backfires
Engineering pays for your commitment, and it keeps score. If you invoke commitments often, or ones that turn out padded, people start auditing every claim, and the person who used the move most is hurt most when the pattern shows. Everything here depends on the document. Citing a promise the client never made, inflating its terms, or hiding that it could be renegotiated turns fair pressure into a lie about the customer.
When it is used on you
Ask to see the commitment in writing, and ask whether it is binding and whether the client would accept another date. If it is real, the debate moves to what gives way. If it is verbal or vague, have that recorded, and push for a commitment review before any large promise counts as a constraint on the roadmap.