The product launch tier framework: how PMMs prioritize launches without burning out their teams

Every launch gets a launch plan. That's the problem.

Open a recipe and it calls for a stand mixer and a food processor. You have a bowl and a fork.

The recipe isn't wrong. It was written for a kitchen that isn't yours.

Most launch plans are that recipe. They were written for the biggest release the team ever did, and now every release inherits them.

So product ships faster than we can absorb it. Sales wants enablement for all of it, marketing wants a press release for every release note, and we have exactly the hours we had last quarter.

Then a PM asks the question that has no good answer yet. "Why isn't this getting a full launch?"

The standing special

Read a specials board long enough and you learn what it is. The special is often the thing with the shortest clock, which is a different matter from the kitchen's best idea.

Launch calendars grow the same board. A release gets full treatment because a PM will be upset otherwise, or because an exec name-checked it in a QBR.

Call that a standing special. It's a launch that gets the full treatment by default, forever, because nobody wants the conversation that would downgrade it.

Wasted hours are the least of it. Sales, CS, and the market lose any way to tell which release deserves their attention, so eventually they stop looking.

Tier frameworks usually get sold as capacity planning, and that undersells them. The work happens before any planning starts.

We stop asking what this launch needs and start asking what it's worth. The second question answers the first.

What each tier buys

The names matter less than the shared language. Gold, silver, bronze works. Major, minor, micro works.

What can't survive is the exception. The first "this one is special" is the end of the framework.

A T1 is a release that changes the business. New platform capability, entry into a segment, a repositioning that rides on a product shift, anything that needs a coordinated announcement.

It gets eight to twelve weeks. Full positioning and messaging development rather than a refresh, executive alignment, message validation with real customers before launch, media and analyst briefings where they're warranted, a complete enablement package, a dedicated page, a launch moment, and a ninety-day measurement plan that starts the day after.

Staffing it means a named PMM lead, a PM partner, sales enablement, demand gen, PR, and an executive sponsor who shows up.

A T2 is a real feature that changes one conversation and leaves the overall positioning alone.

A major integration. A workflow that removes a daily annoyance. Something that answers the objection we keep losing to.

It gets four to six weeks. Messaging built for that feature's buyer, an enablement update, a targeted email to the accounts most likely to care, a blog post, an in-app note, and an internal announcement. PMM leads, PM partners, CS handles the customer comms.

A T3 is a small improvement that matters to the people who asked for it and moves nothing at the company level.

A performance fix. A new filter. An export format.

It gets one to two weeks, most of which is waiting. A clear changelog entry, a help doc update, an in-app note if it changes a workflow, and one sentence to sales and CS so nobody gets ambushed on a call. Nothing else.

Scoring before planning

Without a rubric, every PM argues their feature is a T1 and the loudest room wins.

Score each release from one to three on four dimensions, then add them up.

• Revenue potential, weighted 40 percent. A three opens new pipeline, reaches a new buyer, or goes straight at the competitor we keep losing to.
• Addressable audience, weighted 20 percent. A three is relevant to most of the customer base or to every active prospect.
• Competitive differentiation, weighted 20 percent. A three is something competitors don't have and can't quickly copy.
• Strategic alignment, weighted 20 percent. A three is central to a priority the company already committed to.

Ten to twelve is a T1. Six to nine is a T2. Five or below is a T3.

Run it with the PM and the business stakeholder before any planning begins. The conversation is worth more than the number it produces.

It also changes what an argument sounds like. "Walk me through the scoring, what's the revenue potential here" is a different room than "why won't you give us a full launch."

And it settles the hardest one without anybody having to play the villain. When a sales leader wants full treatment because one enterprise account is thrilled, one happy customer doesn't buy a tier on its own. Closing a gap that shows up in every competitive deal might.

Bring the framework to leadership as capacity planning. Land it as a gate and the room closes on you. "We're shipping more than we can support, and I want the biggest releases to get everything they need" gets a different hearing than "not everything gets a launch."

Run the first scoring session with the CPO, CMO, and CRO in the same room. The scheduling friction is worth it once.

Capacity is the constraint

Most teams tier correctly and then never hold the tiers up against the calendar.

Set a ceiling of two T1 launches per quarter and make people trade against it. Adjust for team size, but publish the number.

"We have room for two. Which two score highest?" is a better meeting than quietly staffing a full launch for everything that walks in the door.

Where tiers rot

Every launch escalates. Vague criteria plus a persuasive PM equals inflation. Lock the rubric and require evidence for a move, because argument alone shouldn't buy a tier.

T3 becomes no work at all. The changelog still has to be readable, and sales still needs that one sentence. Skip it and the first customer question lands on someone with no answer.

The framework arrives mid-quarter. Tiering releases whose plans are already underway makes enemies and fixes nothing, so start at roadmap planning instead.

The T1 stops on launch day. Most of the revenue impact arrives in the ninety days after, and a framework with no post-launch commitment hands that back.

Whether it's working

A framework nobody checks turns into a filing convention.

Two questions belong in the quarterly review. Are T1 launches producing the pipeline they were scored for, and how often did a tier get escalated after the initial scoring?

A high escalation rate means the criteria are too soft to hold. Fix the rubric before anyone starts questioning discipline.

The third question is quieter. Ask sales and CS whether T3 releases are generating customer questions they can't answer, because that's how we learn the lightweight version was too light.

A T3 that drove real upsell conversations is telling us the same thing from the other direction. Update the criteria and move on.

The board

When everything is a special, the board stops being information.

Take something off it.

What to do next

If every release on next quarter's roadmap is heading for a full launch, more hours won't fix it. The tiering has to happen before the planning does.

If you want help running that first scoring session with your PM and exec stakeholders, start here. The first conversation is free.