Home / Work / CommBroker

Enterprise B2B platform

CommBroker

Turning a portal people navigated by memory into a platform they could actually trust.

CommBroker is the primary digital platform for mortgage brokers to find policy, manage loans, and complete compliance-heavy work. The redesign challenge was not cosmetic. Brokers needed a clearer structure, faster access to answers, and a platform that could become the source of truth again. I led the redesign direction from IA research through concept selection, helping product and engineering reset the platform around broker tasks rather than internal ownership.

Role
Lead Product Designer
Team
1 Designer, 1 PM, 1 researcher, 6 engineers, Accessibility, Compliance
98%
Discoverability success in concept testing
36%
Content reduction through audit and restructure
219
Brokers and assistants across research and validation
CommBroker home screen with actions, updates, and broker dashboard content

The redesign centered the product around what brokers were actually trying to do, not how CommBank was internally organised.

Challenge

A critical platform had quietly become dependent on bookmarks, memory, and support calls.

Brokers used CommBroker to find policies, manage applications, and keep up with compliance-heavy processes. But the platform had become increasingly difficult to navigate. Content was duplicated. Information lived in the wrong places. The right answers often existed, but brokers could not reliably find them when they needed them.

In practice, the product had stopped behaving like the source of truth. Brokers were relying on personal workarounds and institutional knowledge instead.

Heuristic findings

  • Navigation mismatched broker mental models
  • Inconsistent page structures and templates
  • High cognitive load at key decision points
  • Weak accessibility compliance

Content audit findings

  • Significant duplication and outdated content
  • Broken links and unclear ownership
  • No dependable single source of truth
  • Structure optimised for internal teams, not broker tasks

Research

The key insight was simple: the problem was navigation, not the quality of the information.

I grounded the redesign in a multi-layered research program: heuristic review, content audit, Treejack IA testing, moderated concept evaluation, and usability testing. The data consistently pointed to the same thing. Brokers were not confused by the policies themselves. They were frustrated by how much work it took to locate them.

Method 01

Content audit across the platform to understand duplication, obsolescence, and structural sprawl.

Method 02

Treejack IA testing to measure where the current structure failed before any redesign work began.

Method 03

Concept testing with real brokers and assistants to compare familiar and divergent navigation models.

Method 04

Moderated usability sessions to validate whether brokers could complete real tasks with confidence.

"
It feels like a guide-book.
Broker response to the chosen IA direction

Strategy

Two concepts went into testing. The decision was made by evidence, not internal taste.

I developed two directions. One stayed closer to the existing structure. The other made a more decisive IA shift, consolidating fragmented destinations into clearer hubs. Testing revealed a sharp difference: the bolder structure delivered much higher discoverability and broker confidence, even if it asked users to learn a new model.

67% Discoverability success for the more familiar concept.
98% Discoverability success for the stronger IA direction.
9 to 7 Top-level navigation simplified through restructuring and consolidation.

The critical tradeoff was accepting a short learning curve in exchange for a far more coherent system. Brokers told us the new structure felt more intuitive once they understood it, and the data supported making that bet.

Solution

The redesign treated information architecture as the product, not a layer beneath it.

The final experience reorganised content around broker intent rather than internal ownership. I introduced a central Resource Centre as the primary entry point for policy, process, and forms, reduced navigation noise, and created more direct routes to applications, loans, and supporting tools.

CommBroker redesign overview showing multiple screens
The new platform model was designed as a coherent ecosystem rather than a collection of disconnected pages.
CommBroker resource centre redesign with search and category navigation
Resource Centre as a single entry point for policy, process, and forms.
CommBroker application detail screen in dark theme
Application views gained clearer structure and stronger progress visibility.
CommBroker applications listing with status table
Status-heavy broker workflows became easier to scan, filter, and follow.
CommBroker broker dashboard concept showing pipeline projection, commission forecast, and top-performing brokers
Dashboard explorations tested how the platform could surface performance, pipeline, and broker risk at a glance.

Pillar 01

Validate IA with real brokers before styling or detailing isolated pages.

Pillar 02

Centralise fragmented knowledge into one dependable entry point.

Pillar 03

Organise pathways around intent so brokers can find answers the way they think.

Outcomes

The platform moved closer to doing what brokers assumed it should have done all along.

The headline number is 98 percent discoverability in concept testing, but the deeper outcome was a more reliable self-service experience. Brokers could find what they needed without escalating to support, relying on out-of-date bookmarks, or checking with peers to confirm policy details. That moved the platform closer to the self-service model the business actually needed.

98% Discoverability success for the chosen direction in concept testing.
36% Content streamlined through the IA and content-structure overhaul.
219 Participants across broker and assistant research, testing, and validation.

Reflection

The most critical part of this work was resisting the urge to start with the UI.

This project reinforced that information architecture does not merely support the experience in enterprise products. It is the experience. The platform got better because the structure got better, not because individual screens became more visually polished.

It also created the conditions for later work. The Gen AI pilot that followed would not have been trustworthy on top of inconsistent, fragmented content. This redesign made future capability possible.

Next case study

Broker Assist

How I designed a broker-first Gen AI experience around guardrails, confidence, and operational usefulness.

Read the next case study