Slack mechanics becoming workflow primitives
Arjun Sethi, co-CEO of Kraken, on building the Nasdaq of crypto
Slack won by turning work chat into a lightweight social game, which made people want to check it constantly and taught the rest of the market that enterprise software could feel playful without becoming frivolous. The mechanics were simple in practice, emoji reactions instead of extra messages, custom emoji that turned team inside jokes into product features, channels that made conversations feel like shared rooms, and integrations that let outside apps post live events into the same stream.
-
The clearest mechanic that spread everywhere was reactions. Slack made it normal to acknowledge a message with a quick icon instead of writing thanks or got it. Microsoft Teams now supports both standard and custom emoji reactions, and even lets reactions trigger workflows.
-
Custom emoji mattered because they gave each workplace its own language. A sales team could celebrate closes with one icon, support could mark solved threads with another. Discord adopted the same idea at server level, then built paid features around using custom emoji more broadly.
-
What looked whimsical also improved product economics. Reactions, shared channels, and app notifications increased daily habit and reduced friction in group coordination, which helped Slack become a high frequency tool. Competitors from Teams to Discord then copied the playbook, while bundling or consumer scale changed the business model around it.
The next step is that these mechanics stop being cosmetic and become workflow primitives. Reactions already trigger automation, huddles layer live presence on top of chat, and AI agents are moving into the same streams. Chat products are converging on the same lesson, the interface that feels most human also becomes the fastest place to route work.