Case study · Failure database
Google Dodgeball
Failure
Technology & Software
Primary gap · Demand Signal
Problem Clarity
Google Dodgeball launched in 2005 to solve a real friction point: young urbanites couldn't easily tell friends where they were in real-time. The problem was observable—people visibly missed spontaneous meetups because texting locations was cumbersome. Urban twenty-somethings experienced this most acutely, constantly juggling phone calls and group messages to coordinate. The alternative was manual communication through calls and texts. However, Google missed critical warning signs. The service required constant active check-ins, creating friction rather than eliminating it. Adoption plateaued because users found the overhead exhausting—checking in felt like another chore. Google also failed to recognize that the problem was solving itself: smartphones were arriving, and native mapping apps would eventually handle location-sharing seamlessly. By 2009, Google shut Dodgeball down, having underestimated how quickly the underlying technology landscape would shift and how user behavior would naturally evolve toward built-in solutions rather than dedicated services.
Demand Signal
Google Dodgeball launched in 2005 as a location-based social network where users texted their location to find friends nearby. Early behavioral signals showed genuine engagement: active users checked in multiple times daily and organically invited friends to join, creating organic word-of-mouth growth in Manhattan and San Francisco. The team measured real interest through check-in frequency and venue clustering rather than vanity metrics, observing that dense neighborhood adoption created self-reinforcing network effects.
However, critical warning signs emerged that demand validation missed. Adoption plateaued outside major cities where critical mass proved impossible to achieve. Users loved the concept but abandoned the service when friends weren't nearby, revealing that network density—not the feature itself—drove value. The friction of texting coordinates manually also became apparent as smartphones emerged. Google acquired Dodgeball in 2005 but shut it down by 2009, realizing the fundamental problem: location-based social networks required simultaneous adoption across friend groups, not just individual enthusiasm. The team had validated feature interest without validating the ecosystem requirements necessary for sustainable growth.
Source: https://www.failory.com/google/dodgeball
Don't repeat the pattern
ReadySetLaunch's Launch Control walks you through thirteen structured questions across the same pillars this case study failed on. You earn your readiness. You don't get told you're ready.
Pressure-test your idea