Organizational strategy, in three stops
I chose Org Strategy, Uplift, and Handoff to show how domain ownership, engineering governance, and human review changed the way teams built, including where buy-in stayed partial.
Start here. There was no UX function at Arcos before I built the credibility, the team, and the process to make one exist.
Arcos, IncArcos had no UX function before I arrived. Credibility, a team that owned its domains, and a delivery model that freed time for shaping are what made design a necessary voice in what gets built, not just how it looks.
This is the honest version: a cross-functional headcount argument made with no direct authority, and a governance model that’s still earning buy-in, not one that landed cleanly on day one.
TVH Parts Co.How moving design system engineers under UX ownership, then co-designing governance with an engineering advocate, turned a neglected component library into shared infrastructure across four brand tech teams.
I changed the delivery model so designers validated generated specs and engineering reviewed UX-authored code. Three Arcos Control Tower cycles showed the early result; the formal review and merge process was still uncodified when I left.
Arcos, IncHow restructuring the design-to-dev pipeline at Arcos cut kickoff time from two weeks to three days: one shared design language for UX, engineering, and AI.
More finished work
Reconstruction. · Mark 1 · early vision, created by me Reconstruction. · Mark 2 · prototype, created by me Arcos Control Tower: From Concept to Testable Prototype
I created Mark 1, my early vision of the Command Center, and Mark 2, the testable prototype. These public reconstructions show both with fictional data; the near-final Mark 3 in the study was built in three versions by two senior designers and me.
Legacy Files grid, recreated Risk inbox · later design BetterCloud Secure: From File Grid to Risk Inbox
I led the sprints and usability work behind the risk inbox’s list and inline actions, building on research I synthesized with BetterCloud’s Business Intelligence team. Allison Kim, a senior product designer, designed the charts. Parts reached beta; a backend caching issue held up the full release before the project was shelved.
Mark 1: one person (Rodeo build) Mark 2.1: the whole crew Timecards: From One Person to the Whole Crew
I built Mark 1, the prototype linemen and foremen tested at the Linemen’s Rodeo. When they showed that the crew lead enters everyone’s time, crew entry became the start of Mark 2. The first screen is the Rodeo build; the second is Mark 2.1, the crew-entry build I made at Arcos after the Rodeo. These are original captures, separate from the public Mark 2 demo I reconstructed after leaving. Fictional names, before production code was written.
Earlier design: eShop Neo Redesign: Innovatis TVH Uplift: From eShop Neo to Innovatis
Two PDP design-file exports. I contributed low/mid-fidelity specs/details tabs alongside Geoffrey Van Meirhaeghe and Suzan, who finalized both displayed screens. I made the composite. Innovatis and cross-brand work remained in progress at my October 2024 departure; this comparison does not establish a customer release.
Guidance: warning means pending or review required Example: The Harmony Chip Intent example shows the same work-order statuses in light and dark themes. Harmony: One Intent, Two Themes
Harmony was intended to carry design intent to designers, engineers and AI coding agents. Harmony’s chip guidance maps color to semantic intent; warning means pending or review required. The Harmony Chip Intent example shows the same work-order statuses in light and dark themes.
