Claim
When engineering release cadence compresses from 6.4 weeks to 2.8 weeks, a PMM team without a tier system spends more time on launch triage than on launch execution. A tier decided in advance does not reduce discipline. It concentrates it.
Mechanism
Tiers pre-answer the question of whether something deserves a launch, using fixed criteria. Each release gets scored against the criteria (new audience reach, pricing impact, competitive differentiation, demand signal, sales cycle impact). The tier assignment is the human judgment call. Everything downstream of the tier is execution, not debate.
Conditions
Holds when: Release cadence is fast enough that per-release launch decisions create overhead that exceeds the value of deliberation. Works best when criteria are calibrated and reviewed quarterly.
Fails when: Every release is genuinely novel enough to need case-by-case evaluation. In that case, the tier system produces forced assignments rather than real decisions.
Evidence
Woodbridge's four-tier model is calibrated with examples from Figma, Stripe, Notion, and incident.io:
"Not every release deserves a launch. Tiers are how you enforce that discipline without it turning into a debate every time something ships."
Signals
- Launch triage meetings have shorter agendas after tiers are installed
- PMM team time shifts from debate to execution
- Tier assignments become consistent across PMs without negotiation
Counter-evidence
Tier systems create their own failure mode: releases that do not fit tier criteria get forced into the wrong tier rather than flagged for a criteria review pass. The system needs a standing review cadence to stay calibrated as product and market change.