Building your product strategy stack | Ravi Mehta (Tinder, Facebook, Tripadvisor, Outpace)

Jan 19, 2023 Episode Page ↗
Overview

Ravi Mehta, former CPO at Tinder and co-founder of Outpace, discusses product strategy, leadership, and the differences between big tech and startup roles. He shares frameworks like the product strategy stack and product management competencies.

At a Glance
17 Insights
1h 21m Duration
13 Topics
7 Concepts

Deep Dive Analysis

Ravi Mehta's Career Arc and Current Venture

Startup vs. Large Tech Company: Speed, Decisions, and Networks

The Product Strategy Stack: Framework for Strategic Alignment

Visualizing Strategy: The Importance of Wireframes

Tinder vs. Hinge: Product Strategy Stack in Action

Tinder's Resistance to Filters and User Discovery

Tinder Monetization: Understanding 'Whales' and New Features

Why Goals Should Follow the Roadmap in Strategy

The Frontier of Understanding: Setting Goals Based on Knowledge

Product Management Competencies Framework

Exponential Feedback for PM Growth

Selective Micromanagement as an Effective Leadership Style

AI's Role in Amplifying Coaching at Outpace

Product Strategy Stack

A framework to separate and define terms like goals, roadmap, and strategy into clearly defined parts. It helps teams understand the logical flow from company mission to daily tasks, enabling better decision-making and debugging of strategic issues.

Speed vs. Latency (Startups)

Startups don't necessarily have higher velocity (quantity of work) than larger companies, but they excel in latency, which is how quickly they can go from an idea to testing it and learning from the results. This tight cycle time allows for rapid validation of hypotheses.

Conviction-Oriented Decision Making

Unlike large companies that rely on experimental, data-driven decisions with large user bases, startups often need to shift to a conviction-oriented approach. This means gathering enough data to form informed conviction and then moving forward, rather than waiting for statistically significant results that may take too long.

Frontier of Understanding

This concept describes the boundary between what a team knows and doesn't know regarding how to achieve a goal. It suggests that goals should be set based on the current understanding, focusing on increasing knowledge or execution if the levers for an outcome are not yet clear.

Product Management Competencies

A framework consisting of 12 competencies across four areas (Product Execution, Customer Insight, Product Strategy, Leadership) designed to help PMs identify skills needed for effectiveness and create a plan for growth. These competencies apply to PMs at all career stages, with the specifics evolving with seniority.

Exponential Feedback

Feedback that provides compounding returns by focusing on underlying behaviors and root causes rather than just surface-level symptoms. By addressing core competencies, individuals can diagnose their own performance more effectively and continuously improve over time.

Selective Micromanagement

An effective leadership approach where a leader temporarily and tactically zooms into details when confidence in the team's direction is low. The goal is to guide the team back onto the right path and provide frameworks, ultimately enabling a return to scalable leadership with increased team autonomy and confidence.

?
What are the biggest differences between being a product leader at a large company versus a startup?

Startups have higher latency (faster decision-making and course correction) compared to large companies' higher velocity (quantity of work). Startups rely more on conviction-oriented decision-making due to fewer users for experimentation, and require connecting with a different, early-stage focused professional network.

?
Why should founders network with early-stage communities even if they're currently at a large company?

Early-stage networks (like Indie Hackers or Everything Marketplaces) consist of generalist builders, freelancers, angels, and investors who are passionate about entrepreneurship. This network provides different knowledge bases for marketing, growth, and building, which are crucial for success when starting a company.

?
Why is it important to include wireframes or visual representations in product strategy documents?

Words alone often lead to different interpretations of a strategy among team members. Wireframes provide a concrete, conceptual blueprint of what the product will look like when the strategy is implemented, creating much more alignment and helping to identify necessary tradeoffs due to limited screen space.

?
Why did Tinder largely resist adding extensive filters to its dating app?

Tinder's product philosophy aimed for a lightweight, serendipitous experience where people get to know each other through interaction, rather than being a 'search engine for people.' This approach helps users meet individuals they might not have considered otherwise, fostering different types of connections.

?
Why does Ravi Mehta's Product Strategy Stack place goals after the roadmap?

Placing goals after the roadmap ensures that goals are set within the context of a clear destination (mission and strategy). This prevents teams from optimizing solely for a metric without understanding its alignment with the overall strategic direction, similar to knowing a road trip's destination before setting a mileage goal.

?
How should product teams set goals when they don't fully understand how to move a specific metric?

If a team lacks understanding of the levers that move a metric (understanding risk), the initial goal should be to increase that understanding, not to commit to moving the metric itself. This can involve dedicated time for customer conversations, analysis, and forming strong hypotheses before setting outcome-based goals.

?
What are the two common failure modes for new product leaders regarding micromanagement?

The first is actual micromanagement, where leaders don't grant autonomy, leading to distrust and limited scalability. The second is a completely hands-off approach, where leaders provide autonomy but lack context or guardrails, potentially leading to teams going off track without proper guidance.

1. Practice Selective Micromanagement

If you lack confidence in your team’s direction, tactically and temporarily micromanage to guide them towards the correct path, then pull back to restore autonomy. This prevents teams from going in the wrong direction and fosters understanding.

2. Define Strategy Before Goals

Establish your company and product strategy (the destination) before setting specific goals (the miles driven) to ensure efforts are structured and aligned with the ultimate purpose. This prevents teams from optimizing for goals that might undermine the true strategic direction.

3. Leverage Product Strategy Stack

Use the Product Strategy Stack (Company Mission, Company Strategy, Product Strategy, Product Roadmap, Product Goals) to define strategy top-down or debug issues bottom-up, ensuring all product decisions are aligned and value-driven. This framework clarifies how different elements of strategy connect and inform each other.

4. Visualize Strategy with Wireframes

Include conceptual wireframes in your strategy documents to create clearer alignment on the product’s visual implementation, as words alone can lead to varied interpretations. PMs should learn sketching or use tools like Balsamiq to develop this critical skill.

5. Focus on Startup Latency

For startups, prioritize “latency” (how quickly you can test an idea and learn) over “velocity” (quantity of work), enabling rapid iteration and validation of hypotheses. This allows for quick course correction and learning.

6. Embrace Conviction-Based Decisions

In startups, where user data for experiments is limited, cultivate a conviction-oriented approach to decision-making. Gather enough data to form informed conviction, then move forward rather than getting stuck in analysis paralysis.

7. Cultivate Early-Stage Networks

If you plan to start a company, actively build a network of early-stage builders, freelancers, investors, and angels now. This provides crucial connections and knowledge distinct from larger company networks.

8. Align Goals with Understanding Frontier

Assess your “frontier of understanding” (understanding, dependency, execution, strategic risk) before setting goals. If you don’t know how to move a metric, set a goal to increase understanding, rather than committing to an outcome you can’t reliably influence.

9. Proactively Seek & Reward Feedback

Proactively invite your manager and others to give you real-time feedback, emphasizing your desire to improve. Always respond with enthusiastic gratitude, even if the feedback is difficult, to encourage more feedback in the future.

10. Self-Assess PM Competencies

Use the 12 PM competencies (Product Execution, Customer Insight, Product Strategy, Leadership) to rate your own performance and ask your manager to do the same. This provides a structured way to identify growth areas and facilitate deep feedback conversations.

11. Give Exponential Feedback

Provide feedback that addresses underlying behaviors and root causes, rather than just symptoms, to enable compounding returns on personal growth. This helps individuals diagnose their own performance more effectively over time.

12. Talk to Users, Especially “Whales”

Regularly engage in one-on-one conversations with users, especially high-spending “whale” users, to understand their psychology, value perception, and specific use cases. This can reveal surprising insights and inform product development.

13. Offer Premium Tiers & Enhanced Features

Introduce premium subscription tiers (e.g., Tinder Platinum) and enhanced, higher-priced features (e.g., Super Like with a note) that break core product rules to cater to users with intense use cases and higher willingness to pay.

14. Resist Filters for Serendipity

Consider resisting extensive filtering options in products designed for discovery to foster serendipitous connections and prevent users from narrowing their options too much. This can lead to unique user experiences.

15. Frame Product Cost as Alternative

When pricing or understanding user spending, consider how users frame the cost relative to alternatives, not just other subscriptions. Tinder users framed app spending against the cost of traditional dating, revealing a higher perceived value.

16. Ask “Product You Love” Question

In interviews, ask candidates to describe a product they “love” to understand their values, product sense, and engagement. Follow up with questions about why they love it, what they’d build, and how they’d measure success.

17. Leverage AI for Amplification

View AI as a tool to amplify human capabilities and efficiency, rather than a replacement. Use AI to provide starting points or suggestions, allowing professionals to tailor and refine the output.

The speed that startups have is not really about velocity. Bigger companies can always get more done. They can always spend more. They can always move with a higher degree of velocity than smaller companies. The advantage a smaller company has really is in latency.

Ravi Mehta

The analogy I like to use, it's a little bit like working with an architect. You would never work with an architect that didn't provide you a blueprint of the house that they want to build for you.

Ravi Mehta

Hinge's mission is designed to be deleted. This is something that is prevalent throughout all of the marketing, which is come to our app. We know that if our app works for you, you're going to find someone, you're going to kick off a long-term relationship and you're going to delete our app. And we consider that a success. Versus Tinder's mission is really to make single life more fun.

Ravi Mehta

If you go on a few dates a month, that's probably a couple hundred dollars. Anyway, it could be even more than that, you know, depending on whether you're in New York City or other places. And so they thought about that spend of a couple hundred dollars a month on Tinder as a small investment to make sure that they could date the people that they wanted.

Ravi Mehta

I think one of the most interesting things about it is not AI as a replacement for people, but AI as a way to amplify people and make them more effective.

Ravi Mehta
3 to 6 months
Time to hire an experienced PM in Boston (at TripAdvisor) Too long for growth goals, leading to the creation of a product rotational program.
6 months
Duration of product rotations in TripAdvisor's program Four rotations over two years for new PMs.
3 times more likely
Likelihood of matching when sending a Super Like on Tinder Compared to a regular swipe.