Slack vs Glitch Behavior Fit

Evidence note: Some metrics are company‑reported correlations and should be treated as indicative, not universal unless linked to a primary source or the Evidence Ledger.

Key Result (company-reported): Slack reported more than 1 billion messages during the week ended January 31, 2019, alongside 143% net dollar retention at IPO scale.

BS-0006

Case snapshot (schema)

context: "Slack succeeded because team messaging had Behavior Market Fit; Glitch failed because collaborative game creation did not."
company: "Slack (Tiny Speck)"
industry: "Enterprise Software"
confidence: "working"
population: "workplace teams"
target_behavior: "Send and read team messages in channels as part of daily coordination"
constraints:
  - "Requires multi-person adoption; value increases with team activation and network effects."
  - "Workflow fit (integrations, search, cross-team visibility) drives stickiness; otherwise it becomes 'another chat tool'."
  - "Org culture and communication norms confound retention thresholds across teams."
measurement:
  denominator: "teams invited/activated"
  window: "first 30–90 days post‑launch to public beta"
  metrics:
    key_metric: "More than 1B messages during week ended Jan 31, 2019; 143% net dollar retention at IPO; ~10% of FY2018 revenue and ~8% of FY2019 revenue came from organizations converting from Free to Paid (S-1 filing)."
results: "More than 1B messages were sent during week ended Jan 31, 2019. 143% net dollar retention at IPO. 32% email reduction reported by teams. ~10% of FY2018 revenue and ~8% of FY2019 revenue came from Free-to-Paid conversions (revenue mix, not a user conversion rate). Glitch predecessor failed (low Behavior Market Fit)."
limitations:
  - "Reported thresholds are company-reported and milestone-dependent (e.g., activated teams); interpret as indicative across cohorts."
sources:
  - "See Sources section"
evidence_ids:
  - BS-0006

Summary

Slack emerged from a failed game company (Tiny Speck) building Glitch. The same team, with much of the same technical capability, achieved radically different outcomes by selecting a radically different target behavior.

Behavioral Strategy lesson: technology rarely determines the outcome; behavior selection does.

Four‑Fit narrative (Glitch → Slack)

• Problem Market Fit
  • Glitch: unclear mainstream problem; niche market with limited pull.
  • Slack: teams had a real, pervasive coordination problem across email/IM/tools.
• Behavior Market Fit
  • Glitch: “collaborative game creation” requires a niche identity and high capabilities.
  • Slack: “team messaging” matches what teams already do all day.
• Solution Market Fit
  • Glitch: complex mechanics and learning costs.
  • Slack: frictionless setup, clear first value, integrations where teams already work.
• Product Market Fit
  • Glitch: churn and shutdown.
  • Slack: sustained team adoption and retention once activated.

Target behavior (operational)

• Population: workplace teams
• Behavior: send and read team messages in channels as part of daily coordination
• Context: workday communication across projects and functions
• Window: first 30–90 days post-activation; then ongoing retention

Constraints (behavioral)

• Requires multi-person adoption; value increases with team activation and network effects.
• Workflow fit (integrations, search, cross-team visibility) drives stickiness; otherwise it becomes “another chat tool”.
• Org culture and communication norms confound retention thresholds across teams.

Behavior Fit Assessment (example)

These scores are examples; the point is the relative fit profile.

Results and measurement (window/denominator stated)

• Window: first 30–90 days post‑launch to public beta; Denominator: teams invited/activated.
• Adoption and retention metrics are frequently cited as company‑reported correlations; treat as indicative unless linked to primary sources.

Solution enablement (environment/process)

• Channels create persistent knowledge and reduce rework.
• Integrations surface events where teams already act (PRs, tickets, deploys).
• Search and mentions lower cognitive load and coordination costs.

BSM limiting factors addressed

• Abilities: Reduce setup friction; one-link team invite.
• Motivation: Fast visible value (searchable history, mentions).
• Environment: Centralize scattered updates into channels.

Limitations and confounders

• Company‑reported thresholds; network effects and team culture variability.
• Competitive landscape and freemium dynamics influence adoption.

Results

• During the week ended Jan 31, 2019, more than 1 billion messages were sent in Slack (SEC S-1).

BS-0006

• A commonly cited activation threshold is ~93% retention once teams exchange 2,000+ messages; this figure is from founder interviews/coverage, not the S-1.
• 143% net dollar retention at IPO, meaning existing teams expanded usage over time (SEC filing, S-1).
• 32% reduction in email volume reported by adopting teams (company-reported survey).
• Revenue from organizations that converted from Free to Paid: ~10% of FY2018 revenue and ~8% of FY2019 revenue (SEC filing, S-1); this is a revenue-mix disclosure, not a standalone conversion-rate metric.
• Glitch (the predecessor) failed because collaborative game creation had low Behavior Market Fit; Slack succeeded because team messaging already had high fit.

Sources

• From 0 to $1B: Slack’s founder shares their epic launch strategy (First Round Review, 2015)
• Slack S-1 Filing (SEC, 2019)
• Evidence Ledger:

BS-0006