Slack
Featuring Stewart Butterfield
Slack, now a fixture of how companies talk to each other, was never meant to be a product at all. Stewart Butterfield and his team at Tiny Speck were pouring themselves into a strange, ambitious browser game called Glitch — and it was failing. By late 2012 they shut it down. But along the way they'd quietly built something to coordinate their own distributed team: a chat tool with file sharing and searchable history that did what email and IRC couldn't.
For founders and operators, this case is a prompt to look sideways at what you're inadvertently inventing while doing the real work. The scaffolding, the internal workaround, the integration hack — any of it can outvalue the main thing on the roadmap, because a problem that hurts you enough to solve probably hurts others too. It sharpens attention on the internal tool outsiders keep asking about, and what it would take to recognize the byproduct as the real business.
Frequently asked questions
What is the Slack case study about?
The Slack case is about a byproduct becoming the real business. Stewart Butterfield and his team at Tiny Speck were building an ambitious browser game called Glitch, which was failing. Along the way they built an internal chat tool to coordinate their distributed team, and that tool became Slack.
What was Slack originally before it became a communication product?
Slack was originally an internal tool that Tiny Speck built to coordinate its own distributed team while making a browser game called Glitch. It offered chat, file sharing, and searchable history that email and IRC could not. When Glitch was shut down in late 2012, the internal tool became the company's real product.
Why did Slack succeed when the game it came from failed?
It succeeded because the internal tool solved a problem painful enough that the team built it for themselves, and that pain was widely shared by other companies. A problem that hurts you enough to solve probably hurts others too. The scaffolding turned out to be more valuable than the game on the roadmap.
What can founders learn from the Slack case study?
The lesson is to look sideways at what you are inadvertently inventing while doing the real work, because an internal workaround or integration hack can outvalue the main roadmap. Pay attention to the internal tool outsiders keep asking about. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.