Back to all work

RBC Wealth Management

Year
2026
Role
Product Designer
Team
Digital Design
With
1 UX Researcher,
1 Product Designer

(tl;dr)

1 redesign shipped for the document builder
100+ pages of documentation written for the handoff

Jump to solution Jump to key metrics

Full case study is password protected.

Enter the password to view the full case study, or email me if you'd like to chat!

See a preview

Mission

Consolidated 6 legacy applications into a unified document builder for investment advisors, focusing on streamlining complex workflows and introducing modern, high-value features. The goal was to redesign the existing designs we inherited from a third-party designer.

New core capabilities

  • In-line editing: Introduced direct, in-platform editing to eliminate external workarounds.
  • Bulk exporting: Implemented batch generation and exporting to reduce manual processing.

The problem

The legacy experience was hindered by severe context switching. Advisors had to pull data from siloed applications and repeatedly execute the same redundant document creation flows from scratch, making the reporting process incredibly tedious and inefficient.

Design research

I synthesized findings from 10 user interviews conducted by our UX Researcher, conducted usability testing on legacy designs received from a third-party designer, and analyzed top market competitors.

  1. Analyzing user interviews

    1. 10/10 expressed that the biggest pain point was the inability to batch-generate multiple reports for household accounts at once.
    2. 9 of 10 participants could not edit table data independently.
    3. 10/10 users expected a template to automatically save upon creation.
    Research notes on user interview pain points: same client with multiple report types, one report type across multiple clients, and the volume of manual report prep
  2. Competitor research

    I benchmarked top-tier document builder applications to identify best-in-class UI patterns and address critical pain points discovered during user interviews. Key findings included:

    1. Thumbnail navigation The pain pointUsers struggled with heavy cognitive load and excessive scrolling when trying to scan or navigate long documents. The solutionImplemented a persistent left-hand page viewer providing visual thumbnails, enabling quick structural scanning, reordering, and direct page jumping without endless scrolling.
    2. Clean UI & content hierarchy The pain pointUsers experienced cognitive overload due to cluttered layouts and excessive text density on a single screen. The solutionAdopted a clean, streamlined UI with intentional whitespace and progressive disclosure to reduce visual clutter and keep focus strictly on the active task.
    Competitor research notes on template creation, report editing, and the discoverability of the edit-table interaction

User journey

I made a revised user journey and low-fidelity sketches to share with the senior product designer and product designer on our team.

My primary focus was translating the critical user research findings directly into actionable structural solutions specifically targeting the pain points around manual context-switching, table editing, and reporting efficiency.

Due to a strict project timeline, formal user testing at the low-fidelity stage was skipped. Instead, I relied on rapid internal critique loops with the product designer and senior product designer to validate the user journeys before moving forward.

Revised user journey for the document builder, from the Templates entry point through template creation and setup to the template builder
Notebook pages with low-fidelity sketches of the document builder

Document builder redesign

Solution

I presented a full case study to the director of design and senior manager, including a journey for three different use cases.

The redesigned document builder: a page thumbnail strip on the left, the document in the centre, and a reorganize and add sections panel on the right
The old document builder: a form-style editing panel on the left with the page preview on the right
Drag the divider to compare the old and the redesigned document builder.
5pain points resolved
10rounds of usability testing in process (October 2026)

Key changes

  1. I shifted from screen-based to journey-driven design. Breaking down each micro-step within the user flow exposed hidden friction points, like static tables and manual saving, and allowed for a more cohesive, end-to-end experience.
  2. I focused on 3 different journeys for batch report generation: creating a new template from scratch, creating a new client batch, and bulk creation.

Like what you see? Email me to see the full case study!

Testimony

Amal Abshir
Amal AbshirProduct Designer

Sophia was an incredible asset to our team this summer.