Slack is Fumbling Developers

But They Didn't Want Developers?

The obvious proximate cause of course, is that I am professionally and personally highly attuned to developer communities, and Slack has actively pushed away developer communities. Quote Harry Hedger:

Slack lost Reactiflux bc they wanted $70k/month to support them.

Sure, I get that this was a deliberate decision. Storage costs money. But how much are we talking? Further, every company understands the logic of running "loss leaders" in order to seed stickiness and future growth. While literally every other company on Earth is throwing all sorts of free benefits to attract developers, Slack found developer communities growing like a weed on it, and flicked them away like so much dandruff. Stewart Butterfield is like the anti-Ballmer.

I'm not here to argue that Slack lost developers because it didn't want developers. That's a tautology. I'm here to argue that this is a strategic fumble that opened up the field to whatever will eventually replace Slack for startups (Microsoft Teams' success is difficult to assess so I will ignore it here).

Slack Losing Its Way

Developers are your canary in the coalmine for user experience - because they create the damn things!

Slack's original appeal was that it had a much better user experience than prior work chat/email/collaboration tools including the now-dead HipChat and Campfire. Reams of VC pitch decks were made about the "Consumerization of the Workplace" thanks to Slack's approachable design (as MetaLab never fails to remind you) and early touches like emoji reactions and bots. The theory was that we demand the UX polish that we see in our personal lives, in our professional lives as well.

Fast forward to today: "I’ve been using Discord a ton lately. Slack for work and Discord for hobbies." That's from Marc Grabanski, who knows a thing or two about developer trends.

I'll raise you another point: In 2016, Slack was originally backronym'ed into the Searchable Log of All Conversation and Knowledge.

Fast forward to today and advice from the curiously high amount of "how to work from home" content you've undoubtedly been receiving is overwhelmingly Communicate Asynchronously and Use Anything But Slack for Long Lived Knowledge.

The Game is Changing

Meanwhile the UX bar has risen in the past 5 years:

• Slack makes you create a email and password anew every time you join a new Slack. Clicking a Discord invite immediately lands you in the channel as long as you're logged in.
• Slack walks you through the full onboarding experience every time you join a new Slack. I've joined probably 80 Slacks, I'm tired of the "👋 Hi, Slackbot here!" welcome messages on how to use Slack, or the downright buggy step through guide that prompts me to put in my profile picture even though Slack clearly figured out that I use the same damn picture every time and is already displaying it. Discord does exactly none of this.
• You need to repeat the whole email and signup song and dance when you move to your phone. Discord is cross-platform-first - sign in on desktop and you're also signed in on mobile.
• (Developer specific) The new WYSIWYG editor rolled out last year made it annoying for developers accustomed to What We Type Is What We Get Thank You Very Much. Not only does Discord not get in the way of your typing, it offers SYNTAX HIGHLIGHTING if you add language identifiers to your code fenced blocks! (More on HN on this)

The past year or so in Office Productivity has been a free-for-all as other companies moved into Slack's open flanks. Notion has torn it up as the Searchable Knowledge Base to beat today. Zoom has overwhelmingly captured video chat, despite Slack also offering it natively. Even a bootstrapped startup like Tuple has become successful despite Slack buying the literal category maker in the space. And of course Discord and even Telegram have made inroads in real time chat.

My intuition is that the Great Unbundling has come for Slack. Whether or not it survives will probably depend on this: Is text chat really a feature or a product? Either way, having to answer that question is an undesirable strategic position for Slack to be in. There is no victory in this fight.

Note: if you feel lost right about here, I released the Developer's Guide to Tech Strategy chapter of my upcoming book recently, feel free to pause and check it out.

Not Over Yet

Slack has fumbled a ball, but it still has a strong lead. Two features still make Slack a strong fit for realtime workplace communication: threaded messages, which Discord refuses to build, and Shared Channels, which I've gone on record as saying will add years' worth and billions of dollars of revenue. Both were introduced in 2017, probably the peak year of innovation for Slack before creating the Slack fund in 2018 and then its 2019 IPO.

From my limited anecdata, the no-code Workflow Builder hasn't yet had significant adoption, but I would be happy to see this change over time. All great platforms eventually add low/no-code automation.

Slack has also made heavy investments for Enterprise Adoption, with things like Enterprise Grid (also in 2017! hmm...). I of course don't have any insight into Slack's growth in the Enterprise. I'm fully aware of the economic incentives of going upmarket and forsaking low end customers.

Communities Over Teams

The net result of all this is that Slack is now very much not the operating system for your team that it set out to be. However its entire user experience is tied to teams.

More specifically - having one single home team, interacting with that team on one device, and the assumption that you don't join or change teams very often. Perhaps this is the disconnect we are sensing.

Slack's focus on teams may be becoming outdated in this new world we live in, where Deep Work and organized knowledge bases come at a premium, and our professional work crosses professional and personal boundaries, and spans across multiple devices, modalities and even multiple communities we both lead and participate in. Discord's focus on communities may win hearts and eventually wallets. Here's Kurt Kemple on Discord's community features, for thought:

Discord is more community friendly IMO. Things like moderation, roles, boosting, group A/V, all make it a great place for a more democratized and scaleable platform.

By focusing on communities instead of siloed teams, Discord becomes a friend of community leaders. In other words, Discord aggregates aggregators. In a world of Aggregation Theory, this is a very good thing.

I thought it was Paul Graham or Benedict Evans who said this, but am unable to find the source: "What hackers do for fun today, we will do at work tomorrow".

Edit: It was Chris Dixon: "What the smartest people do on the weekend is what everyone else will do during the week in ten years"

Hackers are deserting Slack in droves. Slack should be on high alert.

Recommended reads:

• Mule's Dark Horse Discord: How a gaming chat platform is secretly connecting the internet, and defining the future of work: https://mule.substack.com/p/dark-horse-discord
• Kevin Kwok's The Arc of Collaboration: https://kwokchain.com/2019/08/16/the-arc-of-collaboration/
• Protocol on Discord https://www.protocol.com/discord#toggle-gdpr

Postscript

Here's a full inventory of emails you opt in to EVERY DAMN TIME you sign up for Yet Another Slack:

• NAME_OF_SLACK on Slack: New Account Details
• Confirm your email to join NAME_OF_SLACK
• You're all set up on NAME_OF_SLACK in Slack
• New messages from 2 conversations in NAME_OF_SLACK
• Join your team's conversations on NAME_OF_SLACK workspace
• Notifications from the NAME_OF_SLACK workspace
• Slack account sign in from a new device

Just f right off with this engagement spam.