Episode Summary
Executive Summary: Stuart Butterfield argues Slack’s value is not as a chat app but as a horizontal layer for organizational coordination across tools, teams, and workflows. The conversation focuses on Slack’s pandemic-driven growth, remote-work practices, product design choices, and how Slack competes with Microsoft by being better at internal communication and interoperability rather than trying to copy suites like Teams or Zoom.
Main Topics: Pandemic-driven growth and scaling (Priority: 5/5): Slack saw a major surge in usage as companies shifted to remote work; Butterfield describes the technical, support, and customer-success scramble to keep up while automated scaling helped handle demand. Remote work, etiquette, and organizational agility (Priority: 5/5): Butterfield distinguishes Slack as a tool for organizational agility, emphasizing training around communication norms, channel discipline, notification etiquette, and how companies adapt to distributed work. Product philosophy: async communication and channel structure (Priority: 5/5): He explains that Slack works best when every project or team has a clear place to communicate, with mention-based notifications and async workflows reducing overload and making work searchable. Competition with Microsoft and Teams (Priority: 5/5): Butterfield frames Microsoft as a powerful incumbent using bundling and competitive pressure, but argues Teams is not a direct product equivalent to Slack and that Slack’s customer growth shows resilience. Why Slack beat earlier competitors (Priority: 4/5): He credits Slack’s early advantage to a key UX feature: synchronized read state across devices in every channel, plus better design and integrations, which reduced cognitive friction. Future product direction and AI (Priority: 4/5): Butterfield discusses future improvements around search, reminders, notifications, scheduled sending, and AI-assisted navigation, while rejecting a move into full Zoom-like calling or consumer social tools. Horizontal platform strategy and software ecosystem (Priority: 4/5): Slack’s growth is framed as helping users work across many vendors and software tools, not replacing them; its value rises as enterprises adopt more software and need interoperability.
Key Arguments: Slack’s pandemic growth reflected both necessity and product fit: remote work accelerated adoption, but the product also supported mission-critical workflows in newsrooms, healthcare, research, and response teams. Successful Slack adoption depends on communication norms, not just software setup; users must learn channel etiquette, direct mentions, and notification discipline. Slack is designed for async or sync use as needed, but its strength is reducing interruption and helping people know where to go for updates, questions, and decisions. The biggest threat from Microsoft is bundling and default placement in Office 365, not product superiority; Teams benefits from being included, even if Slack is better for channel-based work. Slack’s competitive edge came from reducing friction, especially by preserving read position across devices, which made multi-channel work cognitively manageable. Slack should not try to become a social network or a full video-calling suite; it should integrate deeply with best-of-breed tools like Zoom and other enterprise systems. As enterprises adopt more software vendors, interoperability becomes more important, making Slack more valuable as a cross-tool communication fabric. Product evolution should focus on better search, reminders, notification controls, and AI help rather than forcing users to change established workflows too abruptly.
Data Points: Slack users: 10 million to 12.5 million - Butterfield cites a rapid increase in simultaneously active users during the early pandemic surge. Pandemic growth time window: a couple of days or a week - The jump in users happened very quickly as work-from-home adoption spiked. Slack usage intensity: a couple of hours a day for paid users - He describes Slack as being used intensively by paid users, implying high daily engagement. Slack internal company size: about 2,100 employees - Referenced when discussing how Slack itself operates and scales as an organization. Slack message archive: 15 million messages - Butterfield says new employees can search a large internal archive to get up to speed faster. Office 365 revenue exposure: $30 million worth in a site license - He uses this as an example of the magnitude of enterprise suite purchases tied to email and core productivity tools. Enterprise software usage: a thousand different cloud services - Butterfield argues that large enterprises now rely on vast numbers of software tools, increasing the importance of interoperability. Slack vendor count: 450 different vendors - He says Slack itself buys from 450 vendors, illustrating the complexity of modern software ecosystems. Microsoft software share: around 6% or 7% of all software revenue - Used to emphasize the long tail of the software market and limits of incumbent dominance. Teams-style user cap example: 5,000 people per instance / 200 channels per instance - Butterfield cites these limits as reasons a company might eventually move from Teams to Slack. Slack vs Microsoft growth: revenue doubled and doubled - He points to continued enterprise growth despite Microsoft’s competitive efforts. Notification defaults: 8 p.m. to 8 a.m. - Slack implemented default do-not-disturb hours by local time zone and let bosses change them.
Pivotal Quotes: "“Slack is the workplace communications tool that came out of nowhere a few years ago and is now dominant in enterprises of all sizes.”" — Neil I: Intro framing of Slack’s market position and relevance. "“If you don’t kind of implicitly trust that people mention your name anytime something requires your attention, then you see all 100 of those channels as things you had better check.”" — Stuart Butterfield: Explaining why Slack etiquette and mention discipline are central to usability. "“Microsoft is perhaps unhealthily preoccupied with killing us.”" — Stuart Butterfield: His blunt characterization of Microsoft’s competitive stance through Teams and Office bundling.
Implications: Slack’s future depends on staying the best coordination layer across a fragmented software stack, not becoming another bundled suite. The interview suggests remote/hybrid work will continue pushing organizations toward better async communication, search, and notification controls.
About The Vergecast
The Vergecast is the flagship podcast from The Verge about small gadgets, Big Tech, and everything in between. Every Friday, hosts Nilay Patel and David Pierce hang out and make sense of the week’s most important technology news. And every Tuesday, David leads a selection of The Verge’s expert staffers in an exploration of how gadgets and software affect our lives – and which ones you should bring into yours.