Evaluating Trade Offs

# Evaluating Trade-offs - All Guest Insights

*40 guests, 42 mentions*

---

## Alex Komoroske
*Alex Komoroske*

> "Trying to ignore it by trying to pin it down with fake numbers that you just made up for yourself at great expense is a really bad idea... It doesn't really matter if it's 1,000 or 1,001, who cares? It orders a magnitude larger than the alternative, and so it is better."

**Insight:** In highly uncertain environments, focus on order-of-magnitude differences rather than wasting effort on 'false precision.'

**Tactical advice:**
- Avoid over-analyzing minor numerical differences in long-term forecasts.
- Prioritize directions that offer significantly higher potential returns (orders of magnitude) over those that are merely slightly better.

*Timestamp: 01:12:56*


## Anuj Rathi
*Anuj Rathi*

> "In my opinion, when you have to make a choice, think more and ship better. Most experiments should be thought experiments. They should not even be tried out because they're obviously going to fail which is contrary to, 'Let's try it out, and then let's see.' I think that wastes a lot of company time."

**Insight:** Prioritize excellence over speed by using rigorous 'thought experiments' to eliminate weak ideas before they reach the engineering stage.

**Tactical advice:**
- Use 'metathinking' to predict experiment failure and save company resources.
- When forced to choose between shipping fast and shipping better, choose excellence to ensure the product is noteworthy.

*Timestamp: 00:49:19*


## Annie Duke
*Annie Duke*

> "Waste is a prospective problem, not a retrospective one... if you wouldn't start this today, then that means that everything that you're putting into this going forward is the actual waste."

**Insight:** To evaluate whether to continue a project, ignore sunk costs and ask if you would start the project today with the current information.

**Tactical advice:**
- Ask: 'If I weren't already in this project/relationship/job, would I start it today?'
- Recognize that continuing a failing path is the true waste of future resources.

*Timestamp: 01:13:35*


## Bob Baxley
*Bob Baxley*

> "Tenets are really decision-making tools and it's sort of like... A classic one is paper versus plastic. It's just too complicated to reconsider that every time you're at the grocery store. So you sort of make a rule for yourself and you're just a paper person or a plastic person, you move on from there."

**Insight:** Effective tenets are 'this over that' choices that eliminate recurring debates by setting a permanent direction.

**Tactical advice:**
- Identify debates the team has repeatedly and create a tenet to decide the direction once and for all.
- Ensure tenets are specific enough that someone could reasonably argue for the opposite (unlike platitudes like 'be simple').

*Timestamp: 00:38:20*


## Bret Taylor
*Bret Taylor*

> "If you're a great engineer, the answer to almost every problem in your business is engineering... you probably by default should question it."

**Insight:** Avoid the bias of applying your primary skillset as the solution to every problem; the real solution may lie in a different discipline.

**Tactical advice:**
- Question solutions that fall too comfortably within your own area of expertise

*Timestamp: 00:22:14*


## Dan Hockenmaier
*Dan Hockenmaier*

> "But then you have all these teams that are really managing some tension in the business, which is totally different than a funnel. So say if you have a marketplace quality team... if I let on a bunch of new supply to a marketplace, probably the first thing that happens is our GMV or our revenue goes up... but if those are on average lower quality, it's going to degrade the kind of customer experience and reduce retention over time. And so the model that they're trying to build is how to manage that tension."

**Insight:** Certain teams must build models to manage inherent tensions (e.g., quality vs. quantity) rather than simple linear funnels.