WorkPlayAboutContact
All selected work

Case study 01

ClientFCAC · Consumer-Driven Banking

From rough wireframes to a scalable, accessible open banking portal.

Turning rough wireframes into an accessible, consistent portal for a federal service.

My role

Senior UX Consultant · UX design lead

Focus

Interaction architecture · RBAC · Design system

Impact

Reusable templates, a clear roles model and an accessible foundation, with senior stakeholders on board.

The challenge

Open banking launches in Canada in 2027, and FCAC oversees it. The portal started as rough, inconsistent wireframes. Sign-in, roles and navigation had to work for several kinds of users and meet Government of Canada standards.

My contribution

I set the UX direction and treated the portal as one connected service, not a stack of screens. I mapped the service end to end and turned the concepts into reusable page templates.

Before and after

BeforeAfter
Rough, inconsistent wireframesReusable page templates
Sign-up written from an engineer’s viewSign-up and sign-in built around GC Sign In
One document uploaded at a timeEvery document in one step
Roles and permissions undefinedA clear model of who can see and do what
Accessibility left for laterWCAG and GC components from day one

Design approach

Templates, not one-offs

Consistent layouts and patterns, so every new screen is quicker to build.

Simpler sign-in and access

Fewer steps for each user to reach what applies to them.

A clear roles model

Which roles exist, what each can see and do, and how that shows up on screen.

Accessible from the start

WCAG 2.1 AA built into the patterns, not patched in at the end.

Built on the GC Design System

I worked with its team, and my feedback improved components used across federal services.

Fast, realistic prototypes

Figma Make connected to live data, so we could test with real users quickly.

Extras I proposed

Five improvements beyond the brief, presented to FCAC and the Bank of Canada.

  1. Multi-file uploader

    Add every document at once. Test users strongly preferred it.

  2. User-first structure

    Reorganized an engineer’s API checklist around what people are trying to do.

  3. A familiar federal look

    With scams on the rise, looking like trusted Canada.ca sites builds confidence.

  4. Search and filters

    Find information by browsing, not by remembering exact terms.

  5. More room for content

    Navigation moved into a flyout, and next steps kept in one place.

Outcomes

  1. A foundation to build on

    Templates and patterns instead of one-off screens.

  2. Simpler key journeys

    Fewer steps in sign-in and access.

  3. Everyone aligned

    Senior stakeholders backed the direction.

01From early wireframes to finished screens

Early wireframes beside the designs that replaced them.

Before · Portal landingA generic welcome and placeholder tiles.
After · Welcome homeYour role, recent activity and services, up front.
Before · Contacts and rolesRoles hidden in long checkbox lists.
After · Role managementEach role beside the permissions it grants.
Before · Organization details and logoEvery field saved on its own.
After · Logo upload flowA guided four-step logo upload.

02Portal home and landing pages

Landing page directions and three home screens.

Landing page directionsFive hero directions for the landing page.
Welcome homeYour role, recent activity and services, up front.
Administrator viewKey numbers and six admin tools.
Compliance dashboard homeNews, deadlines and quick actions in one view.

03Dashboards, reporting and audit

Views for administrators and compliance teams.

Admin dashboardMetrics and trends above recent activity.
News and announcementsAnnouncements ranked by priority.
Audit trailEvery admin action, filterable.
Quarterly complaint reportingDrag-and-drop reporting with the rules stated up front.

05Support and accessibility

Getting help, and adjusting the portal for accessibility needs.

Contact pagePhone, email, chat and FAQ on one page.
Accessibility settingsPresets for low vision, motor and screen-reader use.

The takeaway

Design the system first, and every screen after it gets easier.

Working on something similar?

I’m open to full-time roles and contract work.

Get in touchLinkedIn