samarv/consumer-product-readiness-stack

The Consumer Stack is a diagnostic and strategic framework designed to ensure a team has the foundational "stack" of capabilities necessary to win in the fickle consumer market. Use this to move beyond general product management and focus on the specific rigors of consumer-facing growth.

The Pre-Check: Company-Product Fit

Before applying the stack, ensure the product belongs in your organization. A company is a portfolio of unique strengths. Ask:

• Strategic Alignment: Assuming this is successful, does it serve the right place in our portfolio?
• Competitive Advantage: Can we do this better than anyone else because of our existing DNA?
• Permission to Play: If the company culture is enterprise-focused, do we have the sponsorship to build a consumer-grade team?

The Five Pillars of the Consumer Stack

Evaluate your team or project against these five pillars. Use an A-D "report card" style to identify where the stack is broken.

1. Design-Led Thinking

Consumer products require a level of craftsmanship where "good enough" is a failure.

• Focus on Delight: Move beyond utility to emotional resonance.
• Sweat the Details: Review transitions, pixel-to-pixel accuracy, and the "feel" of moving between screens.
• High Bar: If the product isn't beautiful and intuitive, consumer pull will never materialize.

2. Radical Focus and Prioritization

Avoid the "20-feature trap." Most successful consumer launches solve one problem exceptionally well.

• Identify Critical User Journeys (CUJs): Map the 1-2 paths that define the product's value.
• Limit the Scope: A launch should have very few features, but those features must be executed at an A+ level.
• Say No: Protect the team from "line extension" ideas that dilute the core experience.

3. Metrics and Instrumentation

You cannot optimize what you haven't codified.

• Define "Active": Don't just track DAU; define exactly what "Active" means for your specific product (e.g., "completed one search" vs. "opened app").
• Instrument Early: Never debate a metric that hasn't been properly instrumented.
• Create a Single Source of Truth: Use dashboards that are accessible to every engineer and designer, not just PMs.

4. High Ship Velocity and Experimentation

In consumer tech, the speed of learning is your primary competitive advantage.

• Experimentation Culture: Build the infrastructure to check in code, see results, and iterate within days, not months.
• Optimize for Learning: If a feature fails, but you learned a fundamental truth about user behavior, it is a success.

5. Talent and Empathy

Consumer building requires a specific type of builder who can empathize with a heterogeneous, global user base.

• Diverse Perspectives: Ensure the team reflects the global nature of consumer patterns (localized in language/pricing, but universal in UI).
• Builder DNA: Hire people who are "technology optimists" and are driven by the scale of reaching millions.

Operational Strategy: The "Quick Win" Loop

When morale is low or the market is tough, use the "Win" tactic to jumpstart the stack:

1. Pivot to the Short Term: Find a feature that can be soft-launched in 4 weeks instead of a major release in 6 months.
2. Soft-Scale: Put the feature in front of a small group of users (even 10-50).
3. Celebrate the Momentum: Use the high-fives from a small ship to fuel the energy needed for the larger roadmap.

Examples

Example 1: Diagnosing a Stalled Launch

• Context: A large tech firm's new messaging app is seeing high churn.
• Application: The PM uses the Stack Scorecard. They find "Instrumentation" is an A (data is clear), but "Focus" is a D (the app has 15 confusing tabs).
• Output: The team cuts 12 features to focus exclusively on the "Video Message" CUJ, leading to a 20% increase in retention.

Example 2: Preparing for a Global Expansion

• Context: An Uber-like service is moving from the US into India.
• Application: Instead of building a "Market Specific" app, the team applies the "Universal Pattern" principle. They keep the core UI/UX the same but focus Pillar 3 (Metrics) on local connectivity issues and Pillar 1 (Design) on language localization.
• Output: The product scales rapidly because the core "five-minute ETA" promise is universal, despite local nuances.

Common Pitfalls

• Process over Progress: Becoming so married to sprint planning or "the PM way" that you stop shipping. Process should enable the ship, not prevent it.
• The "PM as CEO" Myth: Acting as a dictator rather than an enabler. In the Consumer Stack, the PM is a high-leverage facilitator whose job is to create clarity and energy for the experts (engineers/designers).
• Ignoring Followership: Focusing only on "The What" (impact) and ignoring "The How." If designers and engineers don't want to work with you, you cannot execute a high-velocity stack.
• Not Admitting Mistakes: Failing to be humble early in your career. Consumer behavior is unpredictable; if you can't admit a hypothesis was wrong, you'll never find product-market fit.