I’m a designer who genuinely cares about people and making meaningful products. Stats background, 5+ years of experience, and a lot of curiosity to go with it.
The way I work is shaped as much by values as by craft. These are the principles I come back to when teams get messy, ambiguous, or high-stakes.
What I do outside of work.
The best way for me to show what I’m doing outside of work these days is for me to share what my camera roll has been looking like lately, unfiltered. No judgement please 😅
Sunsets
Sunsets never get old.
Food
Sometimes my phone eats first.
Baking
Some at-home baking.
Nepal
Saw some beautiful mountains on my trip to Nepal last month.
Music
Got to see Bring Me The Horizon live. 🤘
Camping
First camping trip of the year.
F1
Got to see F1 for the first time.
Nepal
Trekked Everest Base Camp on my trip.
Doodling
Some doodling to sum up my week.
Bouldering
Completed my first bouldering V4. 🧗
Himalayas
Went on my first helicopter ride in the Himalayas.
Bhutan
There were some beautiful monasteries in Bhutan.
Boxing
It also feels great knowing I can kick ass.
Bouldering
The feeling of topping a hard climb — unmatched.
Food
Always eating.
Adventure
Always planning the next one.
Royal Bank of Canada · 2022–2024
KONEK — Navigating data-sharing in an age of user distrust
Designing a clear, concise, frictionless consent experience for RBC's Pay by Bank feature — helping millions of Canadians share their data with confidence.
My Role
UX Content Designer
Team
Design Researcher Product Owner Business Analyst
Timeline
8 months
Methods
Card sorting Usability testing Content design
100
card sort participants
9
moderated usability sessions
19%
reduction in customer complaints
01 — Context
What is Konek?
Konek, also known as Pay by Bank, is a new product by Interac that enables account-based payments. While Pay by Bank is an Interac product, RBC has ownership of certain parts of the new e-commerce flow — namely, data-sharing and consent.
To use Interac's Pay by Bank method, RBC clients are required to provide data-sharing consent. The challenge: how do you design a consent experience that users actually trust?
02 — The Problem
How do we ensure users have enough information to feel confident making data-sharing decisions?
Data-sharing and terms and conditions pages are often flooded with information clients don't understand — which has built deep distrust within users over time. We needed to design something different.
"Users don't distrust sharing data — they distrust not understanding what they're agreeing to."
Design principle driving the project
03 — Research
Finding the right structure
We ran two rounds of research to validate our approach — starting with card sorting to understand information hierarchy, then usability testing to assess content clarity.
Research Objectives
Identify the best structure for the consent page
Understand if there are missing pieces of information
Assess if clients have enough context to consent confidently
Methodology
Card sorting — 100 participants
Moderated usability tests — 9 participants
Participants: online shoppers and RBC clients
Key Outcomes
Existing page structure validated by card sort
Users wanted "what's not being shared" moved up
Concerns around data-privacy page length escalated to legal
Card Sort — Popular placements matrix
Top
2nd
3rd
4th
5th
Bottom
${[
["Why you need to share your RBC…","46%","16%","16%","9%","4%","9%"],
["What you're sharing","22%","45%","18%","10%","2%","3%"],
["Opting out","21%","27%","23%","10%","11%","8%"],
["Terms and Conditions","21%","21%","17%","30%","6%","5%"],
["Consent checkbox","11%","10%","17%","19%","34%","9%"],
["Confirmation button","8%","4%","9%","9%","25%","45%"],
].map((row,ri) => `
Why am I sharing this?
Users wanted clear reasoning before they could feel comfortable consenting. We added explicit content explaining the purpose of each data point.
02
Emphasize what's NOT being shared.
Participants responded strongly to the "we won't share your client card number or password" message. We moved it to the top of the page.
03
Data-privacy page is too complex.
Users flagged the legal data-privacy page as overwhelming. We escalated this concern to the legal team to simplify the language.
05 — The Solution
Clear. Concise. Frictionless.
After rounds of research, we designed a consent experience that highlights only what users felt was most important — cutting through the noise that typically erodes trust on data-sharing pages.
✦
Clear hierarchy
Lead with why, follow with what. Structure validated by 100-person card sort.
🔒
Reassurance first
"We won't share your client card number or password" moved to the top.
✂️
Only what matters
Cut every piece of content that wasn't directly relevant to the user's decision.
🤝
Interac brand integration
Collaborated with Interac's branding team to ensure proper representation in the flow.
06 — Outcome
Content that users actually trust
All 9 usability testing participants described the consent pages as clear, easy, and straight-forward. The redesigned flow contributed to a 19% reduction in customer complaints post-launch.
The project demonstrated that in high-stakes financial UX, less is more — when users understand exactly what they're agreeing to, trust follows.
"Content was well-received. All participants described the pages as clear, easy, and straight-forward."
Usability testing summary — 9 participants
07 — Next Steps
What came next
1. Collaborate with legal
Get final approval from legal stakeholders
Provide input on simplifying the data-privacy page
2. Implement
Collaborate with product and technical stakeholders
Deliver final production-ready specs
3. Establish CX Metrics
Determine best GA tags to monitor
Measure consent completion rate and drop-off
TD Debit Card Controls
RoleLead UX Designer
EmployerTD Bank
PlatformiOS & Android
StatusShipped ✓
What I did
As the lead UX designer, I owned all interaction design end-to-end — from early discovery through to dev handoff. This included wireframes for every state and edge case, stakeholder presentations for sign-off, and close collaboration with a content designer and visual designer to bring it to final production quality.
Why it matters
TD customers who wanted to change their ATM, POS, or CNP transaction limits had no self-serve option — they had to call a branch or visit in person. It was one of TD's top customer pain points and a significant operational cost. This feature gave 5M+ customers real-time control over their own limits, directly in the app.
$0MM
Projected savings over 5 years
0M+
Customers reached on iOS & Android
$0MM
Branch cost reduction
0 → 1
Built entirely from scratch
Happy path flow prototype
Full case study coming soon
TD Automatic Credit Card Payments
RoleLead UX Designer
EmployerTD Bank
PlatformiOS & Android
StatusShipped ✓
What I did
As the lead UX designer, I owned the end-to-end design of the automatic credit card payments experience — from discovery and problem framing through to dev handoff. This included wireframes covering every state and edge case, stakeholder presentations, and close collaboration with content and visual designers to ship a production-quality feature.
Why it matters
TD customers had no simple way to set up automatic credit card payments in-app, leading to missed payments, interest charges, and avoidable customer frustration. This feature gave millions of Canadians a reliable, self-serve way to manage their credit card payments on their own terms — directly inside the TD app.
