Practice
Beyond the designs
The work I do around the work: facilitating, reviewing, raising the accessibility bar, and even fixing front-end details in code, so good design ships and the whole team gets sharper.
Scope
Ongoing at PayByPhone
Cadence
Weekly and continuous
Works with
Designers, Developers, PMs, Researchers
Focus
Craft, process, accessibility, design to code
The idea
My job doesn't end at the handoff
A lot of what makes design good happens outside my own files: the quality of a critique, whether the live app holds up, how accessible it is, and how cleanly it survives the trip from design into code. I put real energy into that surrounding work.
Right now that means turning our accessibility audit into shipped fixes and learning to close the design-to-development gap with code. It also shows up in the analytics I use to measure impact, the rituals I run, the reviews I lead, and what I share with the team about working faster with AI.
Spotlight · in progress
Turning an accessibility audit into action
An external partner audited the PayByPhone app against accessibility standards. I own the path from findings to fixes: interpreting each issue, scoping what belongs to design versus engineering, taking on the design work directly, and delegating the rest with clear context so it lands. Accessibility is an area I am deliberately deepening, and I treat it as a baseline for quality rather than a checklist.
1
Interpret the audit and assess the impact of each finding
2
Scope what belongs to design and what belongs to engineering
3
Own the design fixes, delegate the rest with clear context
4
Drive the work through to shipped, verified improvements
Currently underway
Spotlight · in progress
Closing the design-to-development gap
Pre-release reviews often turn into cycles of back and forth: I flag a font, color, or spacing issue, then wait on engineering to resolve it. I am removing that bottleneck by learning to make the changes at the source myself.
Using AI to accelerate the learning curve, I am starting to write code and open PRs for small front-end corrections, so visual details get fixed directly rather than handed back. The aim is fewer review cycles, faster releases, and a shared language with the engineers I partner with.
Learning, in progress
Beyond my own projects
Ways I contribute to the team
Data-driven design
Measuring impact with analytics
I build dashboards and funnels in Amplitude to track how people actually use what I design: conversion and drop-off, time on task, and other UX metrics. It keeps my decisions grounded in real behaviour, and lets me see the impact of a design after it ships.
Live quality
App and Play Store review analysis
I ran bi-weekly review sessions with Designers and PMs, turning user feedback from the app stores into prioritised, actionable roadmap input.
Visibility
Showcasing design company-wide
I presented my design work company-wide at Show and Tell, making design's impact visible and building shared understanding well beyond the design team.
A few more ways I show up
Critique
Design reviews
I run regular design review sessions, keeping critique specific, kind, and actionable so craft stays high across the team.
Facilitation
Workshops
I've led cross-disciplinary workshops that turn fuzzy problems into shared direction.
Enablement
AI in our practice
I explore how AI can sharpen our craft and speed up everyday work, then share those learnings with the team to lift everyone's productivity.
Systems
Design system
I've added components and documentation to PayByPhone's design system, supporting consistency and smoother handoff.
Reflection
Why this matters to me
A design only counts once it reaches people in the quality you intended. The work beyond the screen, the rituals, the accessibility, the time in the codebase, is how I make sure the quality survives all the way to release. It also keeps me learning, which is the part I enjoy most.