Whoever ranks the engineering queue puts allied projects first under published priorities that encode their strategy, so favored work ships fast and rival requests wait their turn.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
On taking over the prioritization committee at a car rental company, the head of digital rewrote the published criteria for the engineering queue: revenue from direct bookings counted for half of each request's score, operating savings for a quarter, and risk for the rest. The loyalty app, run by her closest ally, scored highest under the new weights and shipped eleven features that year. The fleet operations team's request for a telematics link to its maintenance system scored below the cut line. Each quarter she sent its head the itemized score and the capacity figures behind the line. He rebuilt his case around the $2.3 million he estimated missed service windows were costing in early tire and brake replacements, which raised its savings score, and the request crossed the line in the third quarter.
Why it works
Controlling the order of a shared queue makes delivery fast and cheap for the projects that rank high: top of the sprint, the best engineers, quick passage through change control. For projects ranked low, delay raises costs on several fronts: money spent while waiting, missed windows, a reputation for promises that never ship, and the work of rejustifying the same request. Published criteria make the ranking defensible, because rivals can see how to compete. It works when the controller has authority over the criteria and executive cover for the strategy they encode.
The thinking behind it
Jeffrey Pfeffer Pfeffer's Power in Organizations (1981) locates power largely in structural position, including control of the decision process. Chairing the prioritization committee for a shared engineering team is that kind of position: the order of the queue decides which units can deliver this year. Publishing the criteria turns the position into a stated strategy that others can argue with, which keeps it defensible.
Herbert A. Simon In Administrative Behavior (1947), Simon analyzes organizations as systems of decisions shaped by the premises they supply, such as goals, information, and procedures. Scoring criteria are decision premises: once direct-booking revenue counts for half of every score, the rankings follow. Whoever writes the premises decides most outcomes, which is why a requester does best by rebuilding the case in the criteria's own terms.
When it fits
Heads of shared services, such as engineering, data, or IT, who chair prioritization and have a strategy the ranking should serve, hold the position for it. You need the authority to set criteria, the discipline to apply them as written, and capacity figures you can show.
How to use it well
Encode your strategy in the criteria, and publish them before you rank anything.
- Score every request against the same criteria, your allies' included.
- Show each requester their itemized score and the capacity behind the cut line.
- Tell low-ranked requesters what would raise their score.
- Itemize capacity and dependencies whenever they decide a ranking.
- Review the criteria every year in front of the committee.
A requester who can see the rules will spend effort meeting them, and the queue will be argued about on its own terms.
What it costs and where it backfires
Units that rank low for quarters will take the pattern to the board as a governance problem, and if their unmet needs cause losses, the cost lands on your criteria. The line is the published rules: reranking allies above the criteria, citing capacity or dependencies you will not itemize, or delaying a rival's request because they opposed you is concealment or retaliation, and delivery figures by requester will expose it.
When it is used on you
Stuck below the cut line, ask for the data: delivery by requesting unit, itemized capacity, and your own score. Put a cost on the delay in every resubmission, compare records with other units whose requests slipped, and take a consistent pattern to the sponsoring committee.