Product and UX designer, 14 years, most of it on enterprise systems where a confusing screen costs real money. I ship production front-end and build accessibility in from the first wireframe, so what gets released matches what got designed.
Four working prototypes on this site. Click through them, they are not screenshots.
See the case studies Start with the accessibility build →
-
Experience: 14+ Years
-
Focus: Design systems, accessibility, front-end
-
Location: Charlotte, NC · open to remote
-
LinkedIn: View Profile (opens in a new tab)
-
Status: Open to senior product design roles
I spent eight years designing internal tools at the largest Coca-Cola bottler in the United States, a company serving 60 million consumers across 14 states and Washington, D.C. Enterprise work teaches a specific discipline: the people using your interface did not choose it, cannot avoid it, and will use it every day for years. It has to be right.
What separates my work is that I do not stop at handoff. I write semantic HTML and CSS, prototype in the browser when a static mockup cannot carry the intent, and implement WCAG and WAI-ARIA requirements rather than annotating them for someone else. The Innov8 prototype on this site is five working screens with keyboard navigation I verified using automated tests. That fluency is why engineering teams trust the specs I hand them.
I also use AI-powered tools throughout my process: Claude for AI-assisted prototyping in code, Figma for rapid prototyping, and Adobe for fast content and asset creation.
-
01 I work upstream with PMs and engineers
The most expensive design problems get discovered late. I get into requirements before the pixels.
I work upstream with PMs and engineers
On Authorization Tracker I partnered with a business analyst before any design started, defining which roles needed to see what and how three separate workflow tracks should be separated. That work is why the rebuild replaced the spreadsheet instead of becoming a nicer front end on the same broken process.
I bring implementation risk into the conversation early, at requirements and sprint planning rather than at design review, because I can read the codebase and see what a given design will actually cost to build.
-
02 I prototype in code, not just in Figma
When a static mockup cannot carry the intent, I build the real thing in the browser and hand engineers something they can inspect.
I prototype in code, not just in Figma
The Innov8 PSA Forecast prototype on this site is five working HTML screens with WAI-ARIA tabs, roving tabindex and arrow-key navigation, verified with automated keyboard tests. Club Coke and Authorization Tracker are clickable too.
This changes the handoff conversation. Instead of a spec document describing intended behaviour, engineers get working reference markup. Ambiguity drops, and so does the number of things that get built differently than they were designed.
-
03 I build accessibility in, not on
Retrofitting WCAG compliance costs several times what designing for it does. I integrate it at the component level from day one.
I build accessibility in, not on
I work to WCAG 2.1 AA: contrast and focus order in the design files, semantic structure and ARIA in the component library, and accessibility criteria in review checklists before code is written.
Accessible products end up being better products generally. Cleaner hierarchy, clearer language, more resilient layouts. The audit result is the byproduct, not the goal.
-
04 I build systems and the governance to keep them alive
Most design systems fail on adoption, not on design. The hard part is organizational, not visual.
I build systems and the governance to keep them alive
At Coca-Cola Consolidated I founded and chaired the Design Council, a cross-functional governance body with representation from 5+ business units, and authored its charter as a versioned organizational document written for executive and IT leadership.
The component library and Digital Brand Guide gave the standards something concrete to point at. The council gave them a forum with authority. Neither works without the other.
Five case studies, each on its own page. Four include something you can click through right now: three working prototypes and a live component library.
-
Live prototype
Authorization Tracker 2.0
Replaced a shared Excel workbook used by 200 people across 10 teams with a governed authorization platform. Includes a live prototype you can click through.
-
Live prototype
Club Coke
Multi-tier approval routing and legal contract execution for an enterprise iPad app used by field sales reps. Includes a live prototype.
-
Design system · Live library
Coca-Cola Consolidated Design System
Founded and chaired a Design Council spanning 5+ business units, and built the Digital Brand Guide component library it governed. Includes the live library.
-
Live prototype · Accessibility
Innov8 PSA Forecast
A self-directed five-screen prototype built with WAI-ARIA tabs, roving tabindex and full keyboard navigation, verified with automated tests.
-
3 live sites
Coca-Cola Consolidated Web Properties
The corporate site plus the Red Classic and ERS subsidiary sites, each restructured around the audiences it actually serves.






















