When stakeholder pressure is peaking, I lean on a simple ritual: a 30‑minute weekly “trade or kill” review with the folks who create most of the load (eng, design, sales, support, success). The rule is boring but effective—if someone wants to add X, they have to name what we trade or kill this sprint/quarter. No trades, no add. I pair it with a one‑pager that sets guardrails: the one metric we’re moving, the non‑goals, and who gets to decide when we’re at an impasse. In the meeting, I use three prompts: Which metric does this move? What slips if we say yes? Who owns the fallout? I also keep a decision log so “we agreed last week” isn’t a memory test. This has cut the drive‑by asks and lowered PM stress more than any framework deck I’ve ever made. Curious how others structure this. Who’s in the room, how strict are your trades, and what scripts actually get buy‑in from execs and sales without burning bridges?
trade-or-kill works until a VP strolls in and says “this is a board ask.” then your ritual becomes theater. the only way it sticks is if your boss will back a “no” in writing. otherwise, you’re running a weekly disappointment circle. make the cost visible in dollars or SLAs and ask, “who owns the miss?” people suddenly remember what “priority” means when it’s tied to their scorecard, not your roadmap.
if you want exec buy‑in, stop talking frameworks and show a burn chart with headcount hours. i literally put two lines: planned vs. actual. then i ask, “which feature dies?” awkward silence, then decisions. sounds harsh, but cosplaying alignment doesn’t ship. also, don’t pretend “stretch” is free. stretch = unpaid scope. call it out, in plain english, every time. you’ll be unpopular for a week and oddly respected by next quarter.
i started a tiny version: 15‑min “swap or stop” in our squad. small but it helps. i just ask “what are we dropping if we add this?” still figuring out who should be in the room tbh.
quick q: do you share the decision log publicly? i’m nervous about stepping on toes but i’m tired of the “we never agreed” gaslighting haha.
i don’t have execs showing up, so i screenshot jira capacity and use that as my “no.” messy, but it works 60% of the time. any better receipts i can bring?
A structure that consistently works for me: keep the room small and accountable—EM, Design Lead, Ops/Support rep, and one GTM lead who can speak for sales, not every deal. Start with a single slide: goal, non‑goals, current capacity, and the decision backlog. For each request, tie it to the goal, then force the explicit trade using pre‑ranked backlog items. If a VP escalates, invite them to name the trade on the spot; do not accept “we’ll find a way” without an owner. Publish the decision log within 24 hours. Over time, the log becomes your defense and your culture artifact; people learn that “yes” always has a partner: “instead of.”
We tried something similar after blowing a quarter chasing “VIP deals.” I renamed it “What Gives” Friday because that’s how it felt. First two weeks were awkward—sales kept saying “we’ll absorb it.” Week three, support showed churn risk from a slipping bugfix. That’s when it clicked. We made the trade public in Slack with a short blurb: what we said yes to, what moved out, and why. No fireworks, but the drive‑bys dried up. Folks stopped asking for “just a tiny tweak.”
In my last org, unplanned scope averaged 32% of sprint capacity. After instituting a weekly 25-minute trade review with a visible capacity chart (people-hours by squad) and a public decision log, unplanned scope dropped to 17% in six weeks. The keys were fixed inputs: a single quarterly goal metric, pre-ranked backlog, and a rule that any “yes” must reference capacity and a displaced item. We also tracked decision latency; keeping it under 48 hours prevented end‑runs. The data made enforcement impersonal and repeatable.