Google Wave Overreach

Evidence note: This is a switching-cost + coordination case. The cleanest evidence is in contemporaneous timelines and founder retrospectives.

BS-0069

Key Result (reported): The creator later noted the tool was “too powerful (and therefore hard to learn) for most people,” reflecting behavior-fit and learning-cost issues.

BS-0069

Case snapshot (schema) 

context: "Google Wave failed because it required users to abandon multiple entrenched behavior models simultaneously (email + documents + chat)."
company: "Google"
industry: "Collaboration / Tech"
confidence: "validated"
population: "Teams attempting real-time collaboration across email, docs, and chat"
target_behavior: "Replace email threads + docs + chat with Waves"
constraints:
  - "Identity: unclear (\"I'm a wave user\" is not an identity people hold)."
  - "Capability: low initially; required learning new interaction patterns."
  - "Context: low; requires multi‑party coordination (everyone you work with must adopt)."
measurement:
  denominator: "invited and active users (reported)"
  window: "2009–2012"
  metrics:
    key_metric: "The creator later noted the tool was \"too powerful (and therefore hard to learn) for most people\", reflecting behavior-fit and learning-cost issues."
results: "Google Wave failed because it required users to abandon multiple entrenched behavior models simultaneously (email + documents + chat)."
limitations:
  - "Network effects and group coordination make adoption unusually fragile; interoperability constraints mattered."
sources:
  - "See Sources section"
evidence_ids:
  - BS-0069

Summary

Google Wave is a clean example of a high‑quality product that failed due to behavioral switching costs. It required users to change multiple paradigms at once. It also required whole groups to switch together.

Target behavior (operational)

  • Population: Teams attempting real-time collaboration across email, docs, and chat
  • Behavior: Replace email threads + docs + chat with Waves
  • Context: (see case narrative)
  • Window: daily communication and document collaboration

Constraints (behavioral)

  • Identity: unclear (“I’m a wave user” is not an identity people hold).
  • Capability: low initially; required learning new interaction patterns.
  • Context: low; requires multi‑party coordination (everyone you work with must adopt).

Fit narrative (Problem → Behavior → Solution → Product)

  • Problem Market Fit: Real. Teams needed better collaboration and communication.
  • Behavior Market Fit: Low. Wave required abandoning entrenched behavior models simultaneously.
  • Solution Market Fit: Technically impressive, but high learning costs and unclear “first behavior” path.
  • Product Market Fit: Shutdown within roughly a year after launch.

Behavior Fit Assessment (example)

Target behavior: “Replace email threads + docs + chat with Waves.”

  • Identity Fit: unclear (“I’m a wave user” is not an identity people hold).
  • Capability Fit: low initially; required learning new interaction patterns.
  • Context Fit: low; requires multi‑party coordination (everyone you work with must adopt).

What this illustrates

  • Behavior change is expensive. Even if the destination is better, switching costs kill adoption.
  • Change one behavior at a time. Successful products usually preserve most mental models while altering one key behavior.

Measurement (window/denominator stated)

  • Window: 2009–2012
  • Denominator: invited and active users (reported)
  • Behavioral KPI (conceptual): % of teams that migrate an existing email workflow end-to-end (requires multi-party coordination)

Results

  • Outcome: Google Wave failed because it required users to abandon multiple entrenched behavior models simultaneously (email + documents + chat).

Limitations and confounders

  • Metrics may be company- or press-reported; isolate the target behavior and window where possible.
  • Effects are context-dependent; avoid generalizing beyond the population and constraints described.

Sources

BS-0069

See also