Research Project

Alias & Shared Accounts

Shared accounts and email alias flow
COMPANY
Bananatag (Staffbase Email)
TEAM
1 designer, 1 PM
TIMELINE
2020

Bananatag started with a focus on individual contributors, but soon communication teams were sending from shared emails like "[email protected]".

Problem

  • For communicators, shared accounts were becoming increasingly complex to navigate and unsafe for large organizations.
  • For Bananatag, system limitations were starting to affect user satisfaction and preventing us from winning larger accounts.

Goal

Identify existing pain points and external workflows for internal teams sharing group email addresses.

My Role

As the only designer on the project, I planned and conducted research to understand how users worked with email aliases outside and inside the platform. I summarized and presented results, and leveraged insights in team planning conversations.

Outcomes

Results showed that the work didn't have to focus exclusively on building a complex alias feature from the ground up, and that we could make small incremental improvements until the team had enough resources to create a central alias management area.

Results

Insights shaped multiple team roadmaps. Data helped us focus on:

  • display name and reply to (✓released)
  • list permissions (✓released)
  • sharing automation (pending investigation)
  • alias (✓released)

Favorite Learning

The importance of context from outside the product. This research proved that problems can have different solutions when the entire user context is clear.

Need more details?

Email me for a full case study walkthrough: