Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To combat the startup tendency of building too many features, Koah's CPO forces the team to answer, "If you could literally only work on one thing, what would it be?" This constraint cuts through noise and exposes the true top priority, accelerating focused development.

Related Insights

Instead of chasing every new tool, dedicate each quarter to a specific focus area like paid acquisition, retention, or site optimization. This framework allows the team to go deep and test everything relevant to that one area, while providing a clear reason to ignore distractions.

Pose this question: "If we were going out of business in two years and only we knew, what would we change?" This mental model forces a radical re-evaluation of current activities, revealing what is truly essential versus what is merely habit or low-impact work.

Startups often get stuck trying to do many 'important' things at once without achieving takeoff. A powerful mental model for growth should provide a unified system that clarifies the single most important action to take at any moment. This shifts the team from unfocused, frantic activity to singular, effective focus.

Startups, especially in deep tech, often get stuck trying to keep all options open. The most effective way to force focus and enable progress is to definitively answer 'Who is this for?'. This shifts the team from building generic technology to building a specific product.

Linear intentionally keeps teams small, viewing limited bandwidth not as a bug, but as a feature. This constraint forces the company to focus only on the most critical initiatives and avoid launching unnecessary features. It prevents the common startup pitfall of building things just to keep a growing team busy.

Instead of optimizing a hundred small tasks, focus on the single action that creates the most leverage. Citing Tim Ferriss, Dave Gerhardt uses this question to identify the core task that, if completed, would simplify or eliminate many other items on the to-do list.

When you're the only resource, you must be ruthless. You only build what is absolutely necessary to solve your own immediate problems. This eliminates stakeholder noise and "nice-to-have" features, teaching the purest form of MVP-driven prioritization where every feature must be critical.

To prevent team burnout and maintain focus, leaders must adopt a strict rule: never add a new priority without agreeing to stop doing something else. The word 'priorities' is a misnomer, as a team can only have one true priority at a time. This discipline forces clarity and prevents overload.

The purpose of setting impossibly aggressive deadlines isn't just to move faster. It is a strategic tool to force a team to identify the true critical path. By asking 'what prevents us from doing this in 6 months instead of 36?' you reveal the few real constraints that must be attacked or eliminated.

Counteract the natural tendency to add complexity by deliberately practicing 'relentless subtraction.' Make it a weekly habit to remove one non-essential item—a feature, a recurring meeting, or an old assumption. This maintains focus and prevents organizational bloat.