The email killer?
summary
Argues Slack reduces internal email by making team communication public, searchable and integrative, so new hires start with a full history and lateral transparency; handles ~20,000 customer tweets and ~15,000 help tickets monthly plus a few dozen bugs a day, indexes Google Docs/Dropbox links for search, enforces SOC 2 and background checks, grows bottoms-up with no outbound sales, powers automations like a receipt-to-expense Slackbot, and focuses on being a platform rather than a consumer app.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:46Will email die
- 4:15Never say never
- 4:27Most innovative use cases
- 5:11Playing your cards
- 6:59Security
- 8:02Pivoting
- 10:40Human interaction
- 13:29Selling Flickr
- 15:46Selling Slack
- 17:14Lauries background
- 18:45Dealing with failure
related talks
08mInterview with Stewart Butterfield
25mCollision 2015 - Stewart Butterfield of Slack with Jonathan Krim of The Wall Street Journal
27mHow we Build APIs and Workflows at Slack
05mSlacking Like a Boss
20mUnlocking the Future: Next-Gen Slack Platform Revealed!
28mSlack App Security: Securing Your Workspaces From a Bot Uprising
19mReducing Context Switching & Unplanned Work Through Platform Engineering
45mSlack like a pro: strategies for 10x engineering teams