Unified Channel Manager

Eliminating years of tech debt to streamline the channel management experience for Brandwatch customer admins
  • Product Design
  • IA
Summary

The new Unified Channel Manager (UCM) allows Brandwatch’s org admins to manage channel connections to various networks, add and remove channels and define channel groups and brands for use within our products.

Brandwatch went through a series of rapid acquisitions and mergers between 2018 to 2023. Each new product solved unique problems for our enterprise customers; but also required harmonisation to address redundant functionality, new interaction patterns and mental models.

Prior to this project, there were 3 different implementations of channel connections and multiple technical variations of the same channel concepts being used across the platform. To complicate things further, these variations also used dissimilar nomenclature.

Secondary issues included:

  • Channels disconnections causing service interruptions for users across all Brandwatch products

  • Multiple, redundant means for grouping channels

Thus, the objectives for this project were to …

  1. Reduce all legacy channel implementations to their essence, and align nomenclature with industry-standard terminology

  2. Lay the groundwork for compatibility with future (potentially diverse) channel types

  3. Propose a solution for channel disconnection issues

  4. Replace existing channel grouping mechanisms with one single recommended solution

Team
Organisation
Timeframe
3 months • Early 2024
My role
  • IA
  • Product Design
  • Prototyping
Status
In Development • Q4 2024

Maintaining economy of concepts for users

I utilised first principles thinking to reduce all existing channel concepts to just three categories — owned channels, paid channels and public channels, in line with media industry nomenclature. This system is future-proof and can account for broadcast, print and any other channel types we may have to support in the future.

Old concepts (left) vs revised concepts (right)

Channel connections

I designed a new channel connection flow that accounted for all 3 channel types: owned, paid and public channels. This was perhaps the biggest win for our customers from this project.

Revising the Owned Channel flow (seen above) allowed us to fix an issue customers had been complaining about for years — channel disconnections. We did this by introducing support for partially-connected channels that only required access for specific use-cases (see step 1 above); rather than being in a binary (and rather annoying) connected or disconnected state.

Details details …

Each channel now got its own detail screen that summarized key information, user access, status and other linked channels such as ad accounts.

I introduced subtle tweaks and improvements to the overall experience to help guide novice admins through Channel Manager and reduce their anxiety about “breaking” something.

Audit log (top); and guardrails via helpful copy and task confirmations (below)

Channel groups

I reconciled the two existing channel grouping mechanisms (channel groups and brands) by expanding channel groups functionality to account for brand requirements.

Defining channel groups clearly mirrors what the user is trying to represent, and the products it will become available in

Dashboard

Finally, I designed a dashboard for users of Channel Manager to land on and get an overview of all channels in their org. Any issues with channels anywhere across Brandwatch leads to this interface, with options for resolution. Each affected channel is now associated with its user-corresponding social profile which enables bulk resolution.

Outcome and impact

Unified Channel Manager is currently scheduled for development Q4 2024, but here are some highlights from the concept testing we carried out with select users.

Pretty intuitive for the most part … I like the way it presented here and how it leads you along with specific prompts about what to do and how to do so …
[Redacted user]
[Redacted]
4.1 / 5 Customer satisfaction (CSAT) via concept testing • 8 users