Bahcall's distinction between P and S type loonshots explains why Pan Am failed while others succeeded, making this a vital read for leaders navigating innovation traps.
Loonshots: Reader Reviews & Ratings
Loading…
Write a Review
Your Review
0/500
Other reviews
24 total
This book taught me to look past surface failures and ask why tests failed before giving up on great ideas.
Bahcall's framework on P and S type loonshots helped me understand why Pan Am failed while ignoring quiet strategic shifts.
This book changed how I see innovation in my own team.
This book changed how I see failed ideas.
The Pan Am case study really hit home for me. It shows how past success can blind leaders to new strategies, making the Moses Trap concept feel very real and dangerous.
Bahcall explains why Pan Am failed by ignoring quiet S-type loonshots while chasing flashy P-type tech, creating a Moses Trap where leaders become blind to strategic shifts needed for survival despite having brilliant teams and resources that could have saved them if they balanced both innovation types instead of doubling down on past successes.
Great book but some parts felt a bit too technical for my taste.
Beginner-friendly without being shallow.
The concept of false failures resonated deeply with my experience in tech startups. Recognizing that early test results might be flawed due to context or variables saves valuable resources and prevents us from discarding potentially life-changing ideas too early.
Bahcall's P and S type loonshot framework is essential for balancing short term wins with long term survival.
This book taught me why my team killed our best idea too soon.
The distinction between P-type and S-type loonshots changed how I view my team's recent failures.
The Pan Am collapse example feels too harsh for a book that mostly pushes a single optimistic vision.
The Pan Am story really shows how past success can blind leaders to the quiet S-type innovations they need to survive.
The Pan Am story really shows how past success can blind leaders to new strategies.
I learned how to spot false failures and protect fragile ideas from being killed too early. The distinction between P-type and S-type loonshots is especially useful for understanding why some innovations fail while others succeed despite similar initial conditions. Understanding phase transitions and Dunbar's number helps me see how team size can accidentally kill creativity before it starts. The advice on separating artist teams from soldier teams gives a clear structure for balancing innovation with core business needs without letting either side dominate the organization entirely. Implementing these principles requires careful planning but the payoff of catching breakthrough ideas early is worth the effort.
Bahcall explains how phase transitions kill innovation when teams grow too large.
While the science behind phase transitions is interesting, the advice feels too theoretical for busy managers.
This book changed how I see innovation and helped me protect my team's wild ideas from early rejection.