Illustration showing teammates in multiple different locations collaborating on deals through Slack. They use quotes, approvals, and celebrate when they close the deal.

Before You Design Slack Experiences, Do This

Three fundamental mindset shifts our design team made that set us up for success

  1. Deep work ➡️ Quick work
    Why? Reduce user effort with simplified UX.
  2. Pull interactions ➡️ Push interactions
    Why? Make work more efficient.
Illustration showing designing for an individual mindset (a woman working alone on her laptop) to designing for multiplayer mindset (many members of a team collaborating around a data visualization in Slack)

Mindset Shift 1: Individual users ➡️ Multiplayer teams

If your design training was like mine, you learned to focus on the individual user. Who is that person? What are their motivations? Knowing that groups convene to work in Slack’s #channels, we can actually shift that mindset to a broader user: the multiplayer team.

  • What can your app do to make an existing conversation better?
  • How do your designs help the various roles that collaborate in #channels?
  • How can your app help drive action or insight for the team?
An Illustration showing the shift from a deep work mindset (creating a marketing journey in Salesforce Marketing Cloud) to a quick work mindset (capturing next steps after a meeting)

Mindset Shift 2: Deep work ➡️ Quick work

We all know that some work requires uninterrupted time (deep work) and other work centers on small-order tasks (quick work). Slack experiences benefit from a quick-work mindset.

  • If you’re designing deep work in Slack, how can you scale it into quick work? Or is it better served by a deep work environment like Salesforce?
An Illustration showing the shift from pull interactions (a man checking his mobile phone to see how his accounts are doing today) to push interactions (a woman being notified when one of her colleges has closed a deal)

Mindset Shift 3: Pull interactions ➡️ Push interactions

You’ve likely designed pull interactions, where users navigate to a product to take action. Dashboards are a great example of this because it’s a destination where users can go to find the features they need. The mindset shift that helped me when designing for Slack experiences was to focus instead on push interactions, where users can take action right where they are. For example, we could push a notification to a manager that an employee’s travel request has been submitted, and they can quickly approve it right there within Slack.

  • When would a push notification help our users? What information do they need to quickly make a decision? What actions could they take from that notification?

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store