# Evaluating Trade-Offs - All Guest Insights *14 sources, 23 insights* --- ## Austin Hay > "That's how you actually have a lot of velocity is thinking about not just build versus buy. It's build and buy now. So, you buy the tool to get 90% of the way there and then you build the cool thing on top with the other 10%. And so that architecting decision usually falls on this person." **Insight:** High-velocity teams avoid the binary choice of building or buying by using SaaS for core functionality and building proprietary layers for the remaining specialized needs. **Tactical advice:** - Buy third-party solutions for foundational needs like data routing and analytics to avoid 'reinventing the wheel.' - Deploy internal engineers only for the 'cool' 10% of functionality that provides a unique value to the product. - Analyze the long-term cost structures of SaaS vendors to ensure the business doesn't lose money as it scales to millions of users. *Source: [The ultimate guide to Martech | Austin Hay (Reforge, Ramp, Runway)](https://www.youtube.com/watch?v=B79p85DHLkU) @ 01:08:59* --- ## Bob Baxley **Insight:** Opinionated design tenets serve as cultural shortcuts that allow teams to resolve recurring debates without constant escalation. **Tactical advice:** - Identify the 'hard things' that a specific culture needs to be reminded to do. - Use tenets to infuse core company values into everyday cafeteria and receptionist-level interactions. *Source: [35 years of product design wisdom from Apple, Disney, Pinterest, and beyond | Bob Baxley](https://www.youtube.com/watch?v=X-83gvgVaWc) @ 00:38:20* --- ## Christopher Miller **Insight:** Successful growth leaders combine rigorous scientific testing with an uncompromising focus on creating massive, long-term customer value. **Tactical advice:** - Avoid chasing small wins that do not meaningfully improve the customer experience. - Maintain a hygienic approach to testing hypotheses while keeping ambitious long-term impact in sight. - Accept high failure rates in experimentation as the necessary cost of pursuing transformative customer outcomes. *Source: [Relentless curiosity, radical accountability, and HubSpot’s winning growth formula | Christopher Miller (VP of Product, Growth and AI)](https://www.youtube.com/watch?v=SzKKJwuRFZI) @ 00:34:51* --- ## Dhanji R. Prasanna **Insight:** *Source: [How Block is becoming the most AI-native enterprise in the world | Dhanji R. Prasanna](https://www.youtube.com/watch?v=JMeXWVw0r3E) @ 00:38:43* --- ## Ivan Zhao **Insight:** Success requires finding the equilibrium between building for your personal taste and building for the pragmatic needs of the market. **Tactical advice:** - Counterbalance artistic taste with the objective requirements of users and revenue. - Ensure the product addresses everyday problems to avoid creating a 'vanity project' with no audience. - Inject your unique values and aesthetics into the product to prevent it from becoming a generic commodity. *Source: [Notion’s lost years, its near collapse during Covid, staying small to move fast, the joy and suffering of building horizontal, more | Ivan Zhao (CEO and co-founder)](https://www.youtube.com/watch?v=IIPKMixTMfE) @ 00:37:36* --- ## Lenny Rachitsky > "To answer your question about how we balanced this outcome-thinking with engineering and design needs (which often don’t directly drive that outcome), it’s simple — extend your outcome thinking further out into the future. How much would this work benefit your outcome (e.g. growth, quality, retention) 1+ years out? What happens if you don’t do it? What are the chances of it being successful?" **Insight:** Evaluate major technical or design investments by calculating their long-term ROI on business outcomes and the risks associated with delaying the work. **Tactical advice:** - Analyze the impact of technical investments by comparing scenarios of doing the work now versus doing nothing. - Assess infrastructure projects based on resource consumption, duration, and how they mitigate long-term risks to business strategy. - Surface technical recommendations to leadership by framing them in terms of short-term goals versus long-term outcome health. *Source: [This Week #13: Balancing outcome-thinking with design and technical requirements ⚖️](https://www.lennysnewsletter.com/p/this-week-13-balancing-outcome-thinking-with-design-and-technical-requirements)* --- **Insight:** While reasoning by analogy is efficient for daily life, creating something truly original requires the high-effort path of first-principles thinking. **Tactical advice:** - Use reasoning by analogy for standard tasks to maintain mental efficiency. - Reserve first-principles thinking for situations where you want to build something entirely new. - Pick what to question carefully, as you cannot go through life questioning every single thing you do. *Source: [First-principles thinking](https://www.lennysnewsletter.com/p/first-principles-thinking)* --- **Insight:** Presenting the strongest version of a stakeholder's request demonstrates expertise and ensures you haven't missed a critical business opportunity. **Tactical advice:** - Collaborate closely with the requester to understand their underlying insights. - Research the data behind seemingly trivial requests to find larger patterns. - Pause and ask clarifying questions before reacting defensively to new asks. *Source: [How to communicate tradeoffs so leaders will listen](https://www.lennysnewsletter.com/p/how-to-communicate-tradeoffs-so-leaders-will-listen)* --- > "Put on your fortune-teller hat and predict the future a little bit. If we decide to take this thing on now, what happens next quarter? Next year? What ongoing costs do we take on?" **Insight:** Countering short-term pressure requires visualizing the long-term operational and morale costs that current leadership might be overlooking. **Tactical advice:** - Predict and communicate the ongoing maintenance costs of taking on new work. - Explicitly lay out the impact of 'heroics' on team morale over multiple quarters. - Contrast short-term revenue gains with long-term strategic delays. *Source: [How to communicate tradeoffs so leaders will listen](https://www.lennysnewsletter.com/p/how-to-communicate-tradeoffs-so-leaders-will-listen)* --- > "We debated for some time and finally decided that having a tab in the largest app in the world was preferable to having a separate app." **Insight:** Integrating a new product as a feature within an existing ecosystem provides distribution and discovery advantages that often outweigh the branding benefits of a standalone app. **Tactical advice:** - Utilize dynamic navigation tabs within your existing app to test and scale new product offerings. - Choose internal integration when the product relies on high discovery and existing user networks. - Only launch a separate app once the integrated experience has reached massive scale and established its own clear usage patterns. *Source: [The inside story of Facebook Marketplace](https://www.lennysnewsletter.com/p/the-inside-story-of-facebook-marketplace)* --- > "For a given user, is feature X or feature Y more valuable? What about for a room full of users? Or a stadium full of users? What decision best serves the most people?" **Insight:** When traditional metrics or strategic frameworks create ambiguity, prioritize features by asking which decision provides the most value to the largest volume of users. **Tactical advice:** - Evaluate competing features by asking which choice best serves the most people. - Avoid relying solely on artificial frameworks or metrics that prioritize internal business needs over user happiness. - Keep different levels of user goals in mind when balancing feature investments. *Source: [What working at Figma taught me about customer obsession](https://www.lennysnewsletter.com/p/what-working-at-figma-taught-me-about-customer-obsession)* --- **Insight:** PMs demonstrate maturity by proactively identifying and discussing tradeoffs rather than treating product decisions as having only positive outcomes. **Tactical advice:** - Offer to discuss strategic tradeoffs at any point during the interview conversation. - Connect tradeoff decisions back to the product's current maturity stage and company mission. - Evaluate how a specific choice affects different stakeholders, such as users, the business, and creators. *Source: [The definitive guide to mastering analytical thinking interviews](https://www.lennysnewsletter.com/p/the-definitive-guide-to-mastering-analytical-thinking-interviews)* --- **Insight:** Technical infrastructure and network design decisions often determine the success of a web3 project more than traditional product features. **Tactical advice:** - Focus on the technical attributes that drive traction, such as transaction speed, security, and network design. - Acknowledge that PMs are often secondary to protocol designers and technical architects during the 0-1 infrastructure phase. - Analyze token incentives and liquidity availability as they are more critical to product-market fit than UI features. *Source: [A product manager’s guide to web3](https://www.lennysnewsletter.com/p/a-product-managers-guide-to-web3)* --- **Insight:** Developing nuanced thinking requires moving beyond rigid frameworks to evaluate complex tradeoffs and understand the constraints of cross-functional partners. **Tactical advice:** - Practice identifying specific conditions under which an alternative decision would be superior. - Ask stakeholders deep questions until you understand the underlying implications of their concerns. - Defend recommendations during leadership discussions without becoming defensive. *Source: [Becoming a senior Product Manager](https://www.lennysnewsletter.com/p/becoming-a-senior-product-manager)* --- ## Nikita Miller **Insight:** Using a single, clarifying question to evaluate trade-offs helps teams cut through noise and stay focused on the most important goals. **Tactical advice:** - Identify a primary strategic question that helps the team filter priorities and resolve trade-off conflicts. - Consistently apply this core question in team rituals to ensure alignment on the highest-impact work. *Source: [Driving alignment and urgency within teams, work-life balance, and the changing PM landscape | Nikita Miller (The Knot, Trello)](https://www.youtube.com/watch?v=4PhfAbRQpbI) @ 00:53:08* --- ## Noam Lovinsky **Insight:** Prioritizing the company's broader roadmap over your own project's survival builds significant leadership credibility and trust within an organization. **Tactical advice:** - Evaluate your project’s impact relative to other priorities on the company roadmap. - Be honest with leadership when resources would be more effectively used on other teams. - Advocate for the organization's overall health, even if it puts your own role at risk. *Source: [The happiness and pain of product management | Noam Lovinsky (Grammarly, Facebook, YouTube, Thumbtack)](https://www.youtube.com/watch?v=a_W5Rn0bJWE) @ 00:09:50* --- ## Robby Stein **Insight:** Knowing when to shift from optimization to new product bets requires identifying the point of diminishing marginal returns on your current S-curve. **Tactical advice:** - Analyze the impact of incremental optimizations to determine if you have reached the top of the current product's S-curve. - Allocate resources toward first-principles bets when existing product improvements no longer drive significant growth. - Balance the urgency to deliver existing products quickly with the focus needed to explore expansionary new technologies. *Source: [Inside Google's AI turnaround: The rise of AI Mode, strategy behind AI Overviews, and their vision for AI-powered search | Robby Stein (VP of Product, Google Search)](https://www.youtube.com/watch?v=kOnsqqVbIeY) @ 00:26:52* --- ## Ronny Kohavi **Insight:** Radical redesigns are statistically more likely to fail than incremental iterations, making it safer to decompose big ideas into smaller, testable increments. **Tactical advice:** - Prepare teams for an 80% failure rate when launching radical new designs - Decompose large product changes into smaller increments using OFAT methodology - Test big bets incrementally to minimize risk and identify exact drivers of impact *Source: [The ultimate guide to A/B testing | Ronny Kohavi (Airbnb, Microsoft, Amazon)](https://www.youtube.com/watch?v=hEzpiDuYFoE) @ 00:36:31* --- **Insight:** For most companies starting out, buying a modern experimentation platform is more efficient than building an internal system from scratch. **Tactical advice:** - Evaluate third-party experimentation platforms before committing to an internal build - Treat experimentation infrastructure as a spectrum rather than a binary build-vs-buy choice - Focus internal engineering resources on product features rather than core testing plumbing *Source: [The ultimate guide to A/B testing | Ronny Kohavi (Airbnb, Microsoft, Amazon)](https://www.youtube.com/watch?v=hEzpiDuYFoE) @ 01:06:38* --- ## Ryan Singer > "I often use this analogy of if you're doing a home renovation, you can have the most beautiful rendering of the new bedroom and we're going to have these lamps on the side of the bed that are coming out from the wall. But if you haven't checked if there's electricity in that wall there or not, it's going to drastically change the cost and the time and everything." **Insight:** Identifying hidden technical complexities and architectural "rabbit holes" during the shaping phase prevents projects from blowing up once development starts. **Tactical advice:** - Verify infrastructure constraints before green-lighting high-fidelity designs. - Involve senior engineers during the shaping phase to surface architectural time bombs. - De-risk the core concept so you can see the end from the beginning before any code is written. *Source: [A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up,” early employee at 37signals)](https://www.youtube.com/watch?v=GF-yUANql0c) @ 00:50:29* --- ## Sri Batchu **Insight:** *Source: [Lessons from scaling Ramp | Sri Batchu (Ramp, Instacart, Opendoor)](https://www.youtube.com/watch?v=RcYCU5UAZOk) @ 00:59:18* --- ## Tanguy Crusson **Insight:** Full rewrites of products with active users are extremely risky and often lead to missed market opportunities due to long development delays. **Tactical advice:** - Favor incremental improvements over full rewrites for existing user bases. - Evaluate if a rebuild will cause you to miss a critical competitive window. - Distinguish between starting a new product and rebuilding an active one. *Source: [Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery)](https://www.youtube.com/watch?v=cZqpqb5qR5A) @ 00:15:55* --- ## Varun Mohan **Insight:** The dramatically increased ROI of engineering due to AI tools makes building custom internal solutions more economically viable than buying off-the-shelf SaaS. **Tactical advice:** - Re-evaluate build-vs-buy decisions based on the lower cost and higher speed of AI-assisted engineering. - Build minimal internal versions of tools to solve the 10% of features your company actually uses. *Source: [Building a magical AI code editor used by over 1 million developers in four months: The untold story of Windsurf | Varun Mohan (co-founder and CEO)](https://www.youtube.com/watch?v=5Z0RCxDZdrE) @ 00:49:57* ---