How did the Slack UX convince our team?

See which parts of Slack's onboarding made an impression and what was the magic moment for me. It is rare that a user's first experience with a product is so easy and rewarding.

How does a software convince us users to use it? It's a subjective and complex process, but in my case I'd say it's almost always by:

  1. Focus on enabling me to do my "job to be done" quickly and easily.
  2. Removing the unnecessary clutter.

I have to admit, even if 1) & 2) are not perfectly executed, I'd spend some extra time trying the service if I can feel the team has invested sufficient time in the User Experience.

Finding a chat software

Being the CEO of a startup you have to wear many hats. In the product manager role I try to take away all unnecessary distractions from our team and let them focus on their job to be done. We had been using a mix of email threads and IRC for too long — fragmentation was killing us.

After trying half a dozen alternatives over a weekend, Slack stood out before I had even invited a single teammate. The empty-state told me what to do next, the keyboard shortcuts taught themselves, and the first conversation I had with the Slackbot felt like a real welcome.

The magic moment

For me the magic moment came when a teammate replied with an emoji in the same second I posted. That tiny acknowledgment changed how I thought about chat. Suddenly the product wasn't messages — it was presence.