Product Frameworks I Actually Use at Scale

I have a confession: I hate most product frameworks.

They look beautiful on a slide deck. The "Double Diamond," the "Kano Model," the "Hooked Model." But when you're in the trenches, dealing with a server outage, a furious key customer, and a sales team demanding a new feature by Friday, those diamonds tend to look more like scribbles.

However, frameworks are useful when they are stripped down to their utility. Over 9 years of scaling products, I've abandoned 90% of them and kept the 10% that actually help me move faster. Here they are.

1. The "Working Backwards" (Amazon Style)

Use When: Defining a new feature or product line.
The Core: Write the Press Release first.

Most PRDs start with technical constraints. "We have this database, so we can do X." This is backwards. Start with the customer experience. If you can't write a compelling one-page press release about why a customer would care, you shouldn't build it.

2. RICE Scoring (Simplified)

Use When: Prioritizing a messy backlog.
The Core: (Reach × Impact × Confidence) / Effort.

The most important variable here is Confidence.

• 100% Confidence: We have user data / signed contracts.
• 80% Confidence: We have strong survey results / usability tests.
• 50% Confidence: "I have a gut feeling" / The CEO wants it.

If you have low confidence, your RICE score tanks. This forces the team to go get data (Discovery) before building (Delivery).

3. The "Pre-Mortem"

Use When: Before launching a high-risk initiative.
The Core: "Assume it's 6 months from now and the project failed. Why did it fail?"

Post-mortems are sad. Pre-mortems are strategic. By forcing the team to envision failure, you uncover the hidden risks—legal compliance, operations load, customer confusion—that usually get ignored in the excitement of a launch.

How to Apply These Tomorrow

Don't announce "We are now using RICE!" to your team. Just start using the language. Ask "How confident are we in this impact?" in your next meeting. Write a mock press release for your next feature and share it. Frameworks work best when they feel invisible.