Captured a Cultural Moment to Launch Slack Huddles

This case study was created from an episode of the Product Marketing Adventures Podcast. It has been adapted into Dusted's case study format to preserve and showcase the guest's real-world experience. Written to preserve the voice of the true author, Stephanie Sosa.

In 2020, as COVID turned remote work into full-time reality overnight, life and work changed completely. It created a massive global disruption that no one was prepared for and it fundamentally changed how teams operated. Communication, collaboration, and productivity tools went from nice-to-haves to need-to-haves.

But it became clear that there was a huge gap in the market. People weren’t struggling to just communicate, they were struggling with organic communication. Suddenly everyone was virtual, stuck on formal video calls with tools like Zoom, and those spontaneous office moments (the tap on the shoulder in the hall, the quick hallway reconnection) disappeared.

This created a rare opportunity for Slack to redefine what virtual work could look like. We saw the chance to expand beyond messaging and recreate those magic, human moments inside Slack itself.

We faced two main challenges. 

The first was not just how to introduce a brand new feature, but how to expand beyond the core product of what Slack was. We knew we wanted to introduce a new mode of communication beyond messaging, but how do we do it in a way that feels natural to Slack and doesn’t add to product complexity?

The second was how do we do this in a market where there was breaking news every minute...and a new collaboration tool coming to market. How do we create an impactful moment in the market to stand out?

Through deep research with our own customers, we realized that the problem wasn’t just video conference fatigue…it was the loss of spontaneity. More meetings weren’t the answer. So we anchored our strategy around creating lightweight moments with as little barriers as possible.

To find customers to do that research, we started with 5–10 of our closest customers (CAB members, executive relationships, power users). We held candid conversations about their new remote reality and product gaps and started to formulate what we needed to run a formal beta.

Once we had a prototype, we designed a structure beta with product marketing at the helm.

1. We wrote a shared beta guide with product and design that locked goals, feedback targets, time commitment, and duration.
2. We expanded deliberately to roughly 100 users, aiming for 10–15 per industry and a mix of engineering, non-tech (sales/marketing), and operations roles as this product was going to be horizontal in nature.
3. Whenever scope creep appeared, we referred back to our beta guide to ensure we kept to our original goal.
4. We called our beta 'done' once we saw strong positive signals (around 60–70 % of participants actively using and liking it).

All of that led us to three very intentional product decisions:

1. Make it audio-only for now to reduce fatigue and friction
2. Make it instant with no links, no scheduling. 
3. Make it embedded in Slack. Reinforcing the idea that Slack is where real deep work happens

And that led us to what we now know as Slack Huddles.

But we knew this couldn't just be a product launch; this a redefining narrative moment. A moment where we could say Slack can transform the way you work and we now had the product proof. The result? "Slack is your Digital HQ" became our launch, and thus our company, narrative.

We didn't build that ourselves, either. Throughout the beta, wested messaging live with some of our more active beta customers—pitching headlines and value props, capturing the exact phrases customers used, and validating with product leadership, customers, and analysts.

For the beta, we built a relatively simple customer tracker in Google Sheets. Nowadays, there's probably a hundred kinds of tools you could use, but at the time we wanted expediency and simplicity. We had all the basics of the customer (company, industry, size, ARR, point of contact), account team information, and any specific notes or details we needed.

During the beta, we relied on Figma files and simple slide decks for early concept reviews. In the later stages, when the product was more developed, we did live product demos and gave access to the product itself to get more in-depth product feedback. Specifically, we were looking for feedback around discoverability and ease of use. We wanted to ensure the barrier to entry was low, but it wasn't disruptive. And we wanted to test new ways of in-product education to help users understand what this new thing was and why they should use it.

For launch, we had one main asset which was our messaging doc. It was our constant, living document that we would iterate on throughout the beta to ensure that what we said wasn't just in our voice, but in our customers'.

Huddles became the fastest-adopted feature in Slack history. The one-click, audio-first experience removed every barrier, the in-product nudges drove immediate use, and the larger “digital HQ” narrative gave the launch cultural weight. We emerged with battle-tested messaging, authentic customer testimonials (some even joined our CEO on the digital launch stage), and a clear playbook for turning a global cultural shift into durable product and brand momentum.