UNITY DESIGN SYSTEM
Designing for trust in enterprise AI
TOKENS
NOT HEX
CODES
8.3 pt floor
CASE STUDY 01 · CELEBRATION OF TECHNOLOGY
One page, three audiences
AbbVie’s internal UX event site brought registration, proposal submissions, event information, and day-of resources into one experience. The challenge was designing a single platform that could support different audiences at different stages of the event, from first-time visitors deciding whether to attend to speakers submitting proposals and attendees returning for schedules and resources. I rapidly prototyped and refined the experience alongside developers to make those overlapping workflows feel clear and cohesive.
TIMELINE
July - August 2026
ROLE
UX Designer
TOOLS
Figma Make for first passes
Figma for iteration
React on the internal
design system
Three audiences with various needs
that can conflict.
AbbVie runs an annual internal technology week — four days, three conferences (a UX summit, an engineering festival and a data-science conference), several thousand employees. Registration, Proposal submissions, agendas, and speakers all live on this site.
First-timers
“What even is this, and should I care?”
Needs the narrative. Will not read an agenda they cannot contextualize.
Day-of attendees
“What’s happening right now, and where?”
Needs live state, on a phone, standing in a hallway.
Returning visitors
“Just show me the agenda.”
Needs to skip everything I would write for the other two.
Rapid Prototyping
I leaned on Claude Code and Figma Make to enlarge my output. Prompting turned out to be a skill of its own.
MAIN SCREENS
HOMEPAGE
FULL AGENDA
SPEAKERS
PROPOSAL FORM
SUBMISSION CONFIRMED
Working closely with the developers.
The site is built on AbbVie’s internal React design system, so everything I designed had to be buildable with what was already there. I reviewed flows with the developers as I went — they told me what was straightforward, what was expensive, and what the library did not have. It was the part of the project that taught me the most about designing for code.
Regular reviews
They flagged problems while the flows were still cheap to change.
Components, not pixels
Designed with the Unity React components and tokens that already existed.
Feasibility shaped the design
Dev feedback changed design decisions, not just documentation.
The site’s ease of use led to more sign-ups.
Clear next steps, far less to read, and nothing to hunt for.
Sign-ups and proposal submissions both went up, and enough people came that a waitlist was added once sessions started filling.
Same event, a different medium
An extension of the same technology-week event I was contributing to: a die-cut vinyl sticker pack about the internal design system and the company’s digital accessibility branch. Built the first iterations with Claude Code, then moved the work into Figma iterate on even quicker, adding my own touches.
not hex
codes.Primary-default
WHAT I LEARNED
Three things I took from this project.
Prompting is a skill of its own.
Learning to prompt well was its own skill, and the point of it was to use the tools as an assistant to my design rather than a substitute for it. What kept it useful was staying rooted in what the user needed — keeping them at the centre, and looking at the page from every lens.
How to best use AI
I explored in Figma Make as well as hooking up my Figma MCP to Claude code, all utilizing the Unity React design system. On the stickers I ran it the other way — first iterations in Claude Code, then into Figma to iterate quicker and add my own touches.
Constraints are the same job in any medium.
A governed React component library and a die-cut vinyl sticker are the same problem in different clothes: find out what the medium will and will not permit, then make something good inside it. The developers taught me the first one. Industrial design had already taught me the second. I did not get to invent visual language here, and it turned out not to be the interesting part.
THE OTHER CASE STUDIES
← BACK TO ALL WORK