Real prioritization names four things, not one: what you will do, what you will explicitly not do, what gets delayed, and which competing goal you're consciously choosing over another (e.g., growth over retention). Ranking everything 'high' is not prioritization.
Golubovski's diagnostic: "If you cannot really articulate the downside of a decision, you don't have a decision. If all the decisions look good, you're not making a decision." Leaders who avoid naming trade-offs are, in his framing, protecting relationships rather than the business — a softer failure mode than 'OR Organization' vs. 'AND Organization' (Trade-Off Avoidance Framing)'s outright trade-off avoidance, but the same root cause.
Frameworks as theater. Golubovski names RICE scoring, opportunity trees, and continuous discovery loops as things teams hide behind instead of doing the harder work of judgment and ownership — the framework becomes a way to defer the accountable call rather than a tool that produces one. He also notes a cultural variant of this: in Europe specifically, citing 'the right framework' functions as a credibility signal that lets a leader avoid the more uncomfortable admission — 'I don't know, but here's the bet' (see Placing Bets (Strategy-as-Bets Framing)).
See also Focus + Transparency + Placing a Bet (Strategy Quality Rubric) for the strategy-quality version of this same demand for explicitness.
Picnic idea intake (Anna Hannemann, warehouse systems domain): ideas flow in bottom-up from developers, business owners, and founders alike. Warehouse-systems leads, POs, and tech leads then convert competing options into explicit either/or trade-offs sized in work-days ('if you want this, you're not getting that') rather than blending them into a mushy compromise. These explicit trade-offs go to founders/top management for a top-down decision, and business owners are then told plainly what they get now and what has to wait. Anna describes taking this framing directly to Picnic's founders rather than obscuring the cost of a decision. See Cross-Team Dependency Pre-Alignment Cycle for how the same explicitness is applied once decisions are handed down and teams have to coordinate delivery.
At Picnic, when multiple initiative requests compete for the same warehouse-systems team capacity, WS leads/POs/tech leads convert the conflict into a sized either/or option (e.g. "Option A costs 25 work-days and displaces the payments migration; Option B costs 10 and ships two weeks later") rather than quietly promising both. Presenting leadership with the trade-off in work-days turns a decision that feels political ("no, you can't have this") into one that feels arithmetic — a business owner who sees the concrete cost stops arguing the point and starts choosing.
See Cross-Team Dependency Pre-Alignment Cycle for the process that surfaces these trade-offs before they become mid-development surprises, and Treating Your Own Alignment Process as a Product for how Picnic keeps improving the trade-off slide format itself.
— Anna Hannemann, Picnic, PT Cologne ("Managing Dependencies in Practice")