Org-level Audience Management

B2B
Feature
Prototypes
Usability
Permissions
A re-imagined admin experience and permissions model for managing your organizations internal newsletter recipients within Axios HQ.
Context

In 2024, facing rising non-renewal rates, our team investigated seven at-risk enterprise accounts. Through targeted customer interviews, we discovered a clear priority: organization-level audience management. This critical feature was developed by a team of seven engineers, our VP of Product, and myself.

Scaling audience management

Organization-level audience management allows admins to centrally control recipient lists across all newsletters. Previously in HQ, each newsletter required creating new audiences from scratch - even when using the same recipients or segments from existing newsletters. This meant users had to repeatedly import and segment the same recipient lists through directory syncs or CSV uploads, creating redundant work when managing multiple newsletters.

The Problem: How might we create a seamless experience to manage audience and recipients data in a systematic way.
Discovery and creating scope

It was common to hear  users discuss how much work and time it is to keep their audiences and semgnets updated in interviews:

“Another thing that is challenging is the email list, adding people and clearing it out, there’s always new email addresses.” - Ellyn

What does 'managing audiences' mean? This question guided research calls with regular users, resulting in a list of minimum requirements and additional features to explore. Audience management at the admin level, a standard feature offered by competitors like Poppulo and Workshop, emerged as an essential table-stakes feature. Following this discovery, my I surveyed current users to prioritize key functionalities.

A 4-question survey, with 39 filtered responses, revealed that users primarily manage audiences through directories (already supported by HQ) rather than HRIS systems. It also highlighted the importance of CSV uploads for data population. Using the top 5 most important functionalities, I began designing this feature.

Top: Overall satisfaction of managing their audience in HQ. Bottom: Most important sources needed top populate audience in HQ.
Overall most important features needed for audience management.
Design

This feature centers on creating a centralized database of all recipients. To guide design, I drew inspiration from database tools like Airtable and Attio and reviewed HQ's existing table components.

Concept design for audience management that can pull in and/or store data about recipients.
Concept design for a dynamic segment that can update based on given rules.
Usability Testing

Once main primary user journeys were designed out, I embarked on creating prototypes to do usability testing with some of our users. I listed out the primary tasks for our users to do to ensure the designs were intuitive.

  1. Find the audience management tab
  2. Add new recipients
  3. Create a new segment of recipients
  4. View an existing segment
  5. Change a segment’s permission
  6. Add access for members to access said segment
  7. View the audience management settings
Launch and outcome

Org-level audience management launched with a beta initially with our customers that are on a beta list, as well the strategic accounts we identified earlier. We ended up saving six out of seven strategic accounts resulting in saving $1 million+ in accounting rate of return (ARR).

Back Home