Evaluating Trade-Offs

The Guide

5 key steps synthesized from 3 experts.

1

Establish a primary strategic lens

Identify a single clarifying question or core metric that acts as a filter for all competing options. This cuts through the noise and ensures the team is focused on the most important goal rather than trying to optimize for everything at once.

Featured guest perspectives

"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?"

— Lenny Rachitsky

2

Conduct a shaping phase to uncover hidden costs

Before committing resources, involve senior engineers to surface technical constraints and potential architectural rabbit holes. Use this time to verify infrastructure requirements and predict the long-term maintenance burden of the work.

Featured guest perspectives

"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."

— Ryan Singer

"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?"

— Lenny Rachitsky

3

Evaluate the build-vs-buy spectrum

Move beyond binary choices by using SaaS for foundational needs while building proprietary layers for competitive advantage. Consider how AI-assisted engineering might lower the cost of internal builds compared to traditional software procurement.

Featured guest perspectives

"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."

— Austin Hay

4

Quantify ROI and the cost of delay

Analyze technical or design investments by comparing the outcomes of immediate action versus doing nothing. Calculate the compound impact of delaying a project and visualize the operational costs to provide a clear picture of the stakes to leadership.

Featured guest perspectives

"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?"

— Lenny Rachitsky

"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?"

— Lenny Rachitsky

5

Structure the decision for alignment

Present the strongest version of every stakeholder request to demonstrate you understand the business opportunity. Proactively discuss specific tradeoffs rather than treating decisions as having only positive outcomes to build maturity and trust with your team.

Get this guide as an AI skill for Claude Code

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill evaluating-trade-offs

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills

View on GitHub →

Manual Installation

1

Download the skill

Download Skill (.zip)

2

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/evaluating-trade-offs/SKILL.md

3

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with evaluating trade-offs

Guest Perspectives

Deep dive into what 2 podcast guests shared about evaluating trade-offs.

Austin Hay 1 quote

Listen to episode →

"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."

Tactical:

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.

View all skills from Austin Hay →

Ryan Singer 1 quote

Listen to episode →

"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."

Tactical:

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.

View all skills from Ryan Singer →

From Lenny's Newsletter

4 newsletter posts cover evaluating trade-offs.

Balancing outcome-thinking with design and technical requirements ⚖️ 1 quote

Read the post →

"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?"

Tactical:

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.

How to communicate tradeoffs so leaders will listen 1 quote

Read the post →

"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?"

Tactical:

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.

The inside story of Facebook Marketplace 1 quote

Read the post →

"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."

Tactical:

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.

What working at Figma taught me about customer obsession 1 quote

Read the post →

"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?"

Tactical:

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.