B2B

Mobile

Case Study

Slack: a mobile update for increased huddle adoption

Slack: a mobile update for increased huddle adoption

B2B

Mobile

Case Study

Slack: a mobile update for increased huddle adoption

Summary

This mobile update boosts Slack Huddle adoption by introducing a built-in calendar and scheduling feature, making it easier for highly collaborative teams to align, connect, and stay in sync without the back-and-forth.

92% of users tested had a positive reaction when interacting with the new slack calendar.

92% of users tested had a positive reaction when interacting with the new slack calendar.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

63.9 seconds was the average duration of time users spent scheduling a huddle.

63.9 seconds was the average duration of time users spent scheduling a huddle.

My Role

Product Designer

Tools

Figma
Dovetail
Google Forms
Maze

Project Timeline

5 weeks

My Role

Product Designer

Tools

Figma
Dovetail
Google Forms
Maze

Project TImeline

5 weeks


The Problem

How can we improve Slack so that it becomes the primary platform for team meetings and huddles? Eliminating the need to leave the app and disrupt workflow.

“My company uses Zoom whenever we need to have a meeting, regardless of how in depth it is.”

“Why not use Slack Huddles?”

“We’ve talked about it, but there’s no easy way to schedule huddles in advance. It just feels simpler to send a Zoom invite.”

The Solution

The solution is to introduce a calendar and scheduling component to Slack, making it the go-to platform for both quick and lengthy team syncs.

Summary

This mobile update boosts Slack Huddle adoption by introducing a built-in calendar and scheduling feature, making it easier for highly collaborative teams to align, connect, and stay in sync without the back-and-forth.

92% of users tested had a positive reaction when interacting with the new slack calendar.

92% of users tested had a positive reaction when interacting with the new slack calendar.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

63.9 seconds was the average duration of time users spent scheduling a huddle.

63.9 seconds was the average duration of time users spent scheduling a huddle.

My Role

Product Designer

Tools

Figma
Dovetail
Google Forms
Maze

Project Timeline

5 weeks

Research

The goal of this survey and data synthesis was to gather and highlight key insights about users’ experiences with Slack Huddles.

Key Takeaways

Huddle scheduling being introduced was a constant and emphasized response from our survey.

With the introduction of huddle scheduling, the ability to localize, find, and access all meetings and weekly activities within a built-in calendar would become a necessity.

Competitor Analyses, Mind Mapping and User Flows

Recognizing the primary outcomes gave us insight into the design options we pursued for Slack. This drove us to conducting a very specific competitor analysis. We identified Discord and Microsoft Teams as direct competitors, while Zoom and Monday remained indirect.

Recognizing the primary outcomes gave us insight into the design options we pursued for Slack. This drove us to conducting a very specific competitor analysis, identifying Discord and Microsoft Teams as direct competitors, with Zoom and Monday as indirect.

Recognizing the primary outcomes gave us insight into the design options we pursued for Slack. This drove us to conducting a very specific competitor analysis, identifying Discord and Microsoft Teams as direct competitors, with Zoom and Monday as indirect.

Research Thoughts

"At this point in the project, we began to establish a solid foundation for what the Slack updates will look like. The competitor analyses and IA were pivotal for when we began laying out our users journey."

Wireframes

With all of the prior research and ideation done, the wireframes you see below were quite easy to lay down. We focused primarily on the calendar and scheduling components of our update.

The Design System

The primary goal when working with Slack's design system was to incorporate elements that meshed well with the pre-existing components in the program but also signified our upadates.

New Feature Signifiers

We wanted to ensure that introducing any new feature did not disrupt a company's pre existing workflow. To do this, we seamlessly integrating signifiers for all new features.

1.

Calendar quick action button

2.

Create/start huddle FAB

3.

New feature alert banner

Schedule an Event

This scheduling flow was built to be seamless and time efficient. The entire process can be completed in a matter of minutes and could be considered easy to use for individuals of all technical capabilities.

Slack Calendar Onboarding

Introducing a feature as complex as a work related calendar can cause some disruption. To ensure this didn't happen, a small onboarding flow was added to help familiarize users with the feature. Below are a few of the necessary screens.

Navigating the Calendar

The mobile Slack calendar was designed to be easy to navigate and understand. Color coded departments are optional but not required.

Usability Testing

The primary goal of our testing was to evaluate user reaction and confirm that scheduling in Slack was a task manageable by all.

Outcome

Usability testing suggests this update will drive increased Huddle usage by introducing seamless scheduling within Slack’s ecosystem. By eliminating the need for third-party tools, it reduces workflow interruptions and gives teams a clearer, more efficient way to stay aligned.

92% of users tested had a positive reaction when interacting with the new slack calendar.

92% of users tested had a positive reaction when interacting with the new slack calendar.

92% of users tested had a positive reaction when interacting with the new slack calendar.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

100% of users tested had direct or indirect success completing the "schedule a huddle" task.

63.9 seconds was the average duration of time users spent scheduling a huddle.

63.9 seconds was the average duration of time users spent scheduling a huddle.

63.9 seconds was the average duration of time users spent scheduling a huddle.

My Final Thoughts

"Researching and designing for this Slack update gave me experience in designing for productivity by focusing on implementing new features that do not disrupt the work flow of a company. Throughout the process, I found myself constantly thinking about how someone will perceive these updates as they are rolled out, and what disruptions they could lead to."