Redesigning Watchtower’s navigation so it keeps working as new modules are added

Company

Paystack
Internal admin tool

Role

Product designer
UX researcher

Users

Reviews, User Ops,
Refunds & Disputes teams

Methods

Discovery research
Information architecture
Prototype usability tests
Survey & moderated interviews

FintechInternal toolsInformation architecture

The goal

The top nav on Watchtower was overflowing, and every new module made it worse.

Watchtower is the internal tool Paystack’s operations teams use to look up merchants, transactions, disputes and payouts. Each new module added another item to the top navigation, until the menu no longer fit. We redesigned it by grouping related items into mega menus.

Objective 01

Fix the overflow, so every module is reachable from the top nav.

Objective 02

Make sure it doesn’t come back when more modules are added in future.


01 · Discovery

Understanding the problem, and who it affected

Research

We grouped similar modules, and retired the ones no one used

Research with the teams who live in Watchtower showed which items belonged together and which were no longer in use. That led to a few clear decisions:

  • Group every customer or merchant initiated record, such as all transactions, transfers and debit orders
  • Keep all merchant details in one group, so compliance sits with merchants rather than on its own
  • Deprecate items that were no longer in use

Synthesis

A new information architecture for the nav

Five top-level groups (Merchants, Collections, Disbursements, Treasury and Admin) each open into second and third levels, so new modules have a home without adding to the bar.

Information architecture tree: Watchtower splits into Merchants, Collections, Disbursements, TREVI and Admin, each with grouped sub-items, plus a user profile menu
The information architecture behind the new nav.

Group the nav so it can grow without breaking.

The principle

02 · Solutions

Mega menus and a typed search

Mega menus

Five groups replace a bar that kept running out of room

Each group opens into the modules within it. Collections, for example, holds Transactions, Terminal and Disputes, and each of those opens to its own pages.

Watchtower top nav with the Collections menu open, showing Transactions, Terminal and Disputes, and the third-level pages each one opens
The Collections menu and the pages under each item.

Search

Jump straight to a record by type and ID

A search in the nav lets teams pick what they’re looking for (transactions, transfers, debit orders, merchants or compliance) and enter an ID or reference. The placeholder changes with the type, for example “Name or Email” for merchants.

Search control in the nav with a type menu listing Transactions, Transfers, Debit Orders, Merchants and Compliance

03 · Testing

Is the grouping intuitive, and is search useful?

Usability test

Three teams, one realistic task each

We sent prototype links to the User Ops, Reviews and Refunds & Disputes teams with a short form about their experience, then followed up with moderated interviews.

Reviews

Find a merchant’s compliance information from its ID.

Refunds & Disputes

Find a specific transaction for a merchant who hadn’t been settled.

User Ops

Find the disputes page from the main nav and open a dispute.

6participants across three teams
4–5out of 5: how everyone rated the search, and every participant used it
1participant struggled to find a transaction, and the label was why

What we heard

The grouping worked. Two things needed another look.

They rarely search by transaction ID. To find a transaction, they start from card details or an email, and only learn the ID afterwards.

Renaming “Transactions” to “Collections” may not land. The team is used to a Transactions bar, and adjusting would be a struggle.

I like the idea of navigating straight to a merchant’s compliance page using their ID.


04 · Next steps

From test findings to the next iteration

Search and naming

  • Talk to the Refunds & Disputes team about how they find transactions today, and widen search beyond IDs
  • Revisit the Collections label, and test whether Disbursements should become Outflow

Clean up what the redesign touched

  • Remove page-level tools the new search replaces, like the search box and “Go to Merchant” on the Merchants page
  • Move old KYC details into the Compliance tab, to match the Reviews team’s new compliance flow

Next project

Extending the footprint of a digital service provider in rural Zambia

Read next case study