Optimizing workflows for internal comms teams to send employee emails.

Role:

Product Designer

Team:

Product Manager, Engineers, Data Scientist, and QA

Employee Email Tool

SaaS

B2B

End-to-End Design

High fidelity design of the new sent emails list with the new email alias solution.

My Contribution

Validated prior research with user and stakeholder interviews, redesigned core flows from synthesized insights, and conducted usability testing. As the independent design lead for this project, I collaborated cross-functionally and presented to the design team for feedback and alignment across product areas.

Background

In large organizations, the process of sending internal company emails requires collaboration among multiple people, from ideation to execution. Internal communications teams also need to measure the effectiveness of company notices.

Problem

While the product aims to enhance internal communication, the collaborative aspects of sending emails and viewing metrics became inefficient when involving multiple users, leading to support requests, decreased productivity, and fragmented email metrics.

Solution:

Streamlined the process of sending from different email addresses by creating a system for managing email aliases, introduced alias sharing to enhance team collaboration, and improved access to email metrics by utilizing existing user permissions and sharing frameworks.

Problem:

While the product aims to enhance internal communication, the collaborative aspects of sending emails and viewing metrics became inefficient when involving multiple users, leading to support requests, decreased productivity, and fragmented email metrics.

Solution

  • Created a system for email aliases that can be shared, enabling users to send emails from different addresses.

  • Improved access to relevant email metrics by leveraging existing user permissions and sharing frameworks.

Impact

  • Reduced user interactions by ~30% by redesigning how internal communicators send emails through shared aliases.

  • Decreased support requests and churn risk by improving the collaboration experience for email communications.

Before & after: Email Sending Flow

Before (partial snapshot of flow)

To send an email from a specific address, users need to navigate to the Team page and log in as that "user" if their account allows for that, if not then they'll need to log out of their account and manually log in with the credentials of that user.

Slice of user flow (before) for selecting a different email address to send from.

After (complete flow after design solution):

The process of navigating to the Team page is removed, the internal communicator will select the alias (sender email address) directly on the Email Preview/Send page instead.

User flow (after) of sending from a selected email address.

Users described "aliases" as email addresses used to send messages - often representing different people or departments, not the actual sender.

Pain points:

  • Single email per user account: Users can't send from multiple addresses, each email address must have its own account created.

  • Restricted collaboration: Resources (drafts, templates, recipient lists, etc.) can only be shared to groups but each user can only be part of one group.

  • Rigid permissions: Analytics are only visible to the account/email it was sent from.

Imagine Marty, a communications manager juggling multiple campaigns, he needs to:

  • Send internal updates from different departments and executives.

  • Edit content and collaborate with his communications team.

  • Measure the reach and impact of emails.

But he struggles with:

  • Logging into another account when sending from a different email address.

  • Sharing send responsibilities with other members of communications team.

  • Limited visibility into email performance across his team.

Key design solutions

Select email to send from

To streamline the process of sending company emails and reduce the number of steps involved in using an email alias, internal communicators can now select from a dropdown menu of all accessible email addresses. Previously, each user account was limited to a single email address, requiring internal comms members to either access the Teams page or manually log in with the credentials of the desired account as a workaround.

High fidelity design of the send page with the new dropdown menu to selected desired alias to use.

alias management system

To reduce friction in the process of sending emails from different addresses, aliases are established as distinct entities, replacing the prior method of creating them as "users." This enhancement empowers users to share access to aliases, creating a seamless experience when collaborating on internal communications.

High fidelity design of the new email alias management page.

Creating a new alias

Users with the admin role can create and share aliases as needed through a simple process. As a result, internal communications team members can seamlessly utilize relevant email aliases for their projects, granting them greater autonomy, crucial for sending timely email communications.

more flexibility when viewing email metrics

Users with permission to view email metrics can select any or all aliases from the new dropdown menu to assess their performance over time. Internal communicators often like to compare the email metrics of communications sent by themselves and their teams.

High fidelity design of the new email metrics overview page with new filter options.

how can we make sending from different email addresses simple?

As I mapped the existing user flows I found that the current system inhibits collaboration and transparency.

Want to learn more about my design process?

let's connect

Other considerations:

Currently, all existing customers have their aliases created as a user. To make this transition from "user" to "alias" as seamless as possible for our users these are the steps that we'll need:

  1. CSM/AE of each customer account will fill out a csv template with their current users created for alias purposes.

  2. Send to our internal alias transition slack channel.

  3. Engineer team uploads the csv file into our database to convert those users to aliases.

putting the design to test

I conducted usability testing with 16 participants who interacted with a high-fidelity prototype in Figma to evaluate their experience and the usability of the new email alias feature.

Goals for the session:

  • Ease of finding the new email alias page.

  • Ease of managing other user's access to email aliases as an Admin user.

  • User comprehension of the new email card designs.

Tasks assigned:

  • Locate the Email Alias page.

  • Create a new alias and share access to it with specified users/group.

  • Change a user's access to an alias.

  • Answer questions using the new email card.

Key results:

  • 56% of all participants found the new email alias page on their first try.

  • 100% of enterprise customers found the new email alias page on their first try.

  • 100% of participants successfully shared and unshared to those listed in the task.

  • 94% of participants answered correctly on all questions related to the new email card design.

Outcome

Beta release

Launched in May 2023 to a beta group consisting of customers who opted in as well as those who were part of the user interviews and testing groups. Before the general release we added a banner to accounts with a specific set of send method configuration (affected 1 of the beta customers and less than 10% of existing customers).

General release

Launched in August 2023, the email alias feature aimed to reduce support requests and increase direct platform usage (some used third party extensions or add-ins). This new feature streamlines internal communication workflows, empowering users to manage and utilize email aliases effectively. Workflow interactions decreased by almost 30%, this feature was essential in reducing churn, especially for enterprise customers.

next project

Streamlining deactivations, decreasing customer support requests

Want the full case study?

let's get in touch