
Open to lead, staff, or senior roles
↳ by asking the right questions first, then prototyping the answer with AI.

Michelle Park, lead product designer for both the tools businesses run on and the apps their customers use. I lead the design and set up the process, design system, and team behind it.
Open to lead, staff, or senior roles · Dallas, remote, or hybrid
Our CEO asked us to use AI to move faster. I led a plan to do it inside our design system, with a sandbox where PMs prototyped on a copy of production.
How money moves through a new self-storage platform, from the front desk to the tenant portal: payments, billing, and move-outs.
Turned an eight-variable formula into a page car dealers could understand and act on.
Rent increases, leads research, promotions, and how the design team worked.
A certification and pricing platform, Cadillac test drive booking, and the myCadillac app in Europe.
Transfers, the rent increase flows we tested, the leads Kanban board, and more settings and dashboards.
If that's not you, let's talk →
I work closely with PMs and developers. Now that prototypes are code, design, product, and engineering work in the same place, so how we work together matters even more.
Once our PMs started prototyping in Claude Code, we worked in two ways. PMs still talked to customers and the field, then prototyped what they heard. I set how design and product worked from there. For a simple feature, design reviewed the prototype and brought it up to our standards before it went to developers. For a complex one, their prototype was the starting point. We iterated together and showed versions to customers, and I ran the user testing so we asked the right questions.
When a question touches how something gets built, I set up time with the PM and the developer together, so feasibility shapes the design early. Developers go deep once the requirements and technical specs are set. At Monument, prototypes were code: we merged them into the sandbox in GitHub, and developers reviewed the branch and built it with their own code.
I treat it as a discussion. I ask why, and what they're seeing. If their reasoning holds up, I change course. More often, the questions get us to a better answer together. When we're still stuck, I go back to what customers told us. Research is neutral ground.
Good designers want to be proved wrong.
That's why I ask for critique early, while it can still change the work.
I'm curious about why people make the choices they do. My best work started with a question nobody had asked yet, like why some facilities printed their promotions to keep at the desk.
I listen before I decide, and I want to hear the opposing view. I learned that in fine art critiques, and again at Illustria, where I went from sales to founding the client services team. I changed how the agency priced its work, and average deal size grew 125%. I also led the research behind a client's rebrand, after which their revenue grew 200%. That's where I learned that bringing stakeholders along is part of the job. Psychology is what pulled me into UX.
Research doesn't have to be a big study to be useful. One of my most useful findings came from a usability test I added to interviews I was already running. I bring the same care to the screens, because spacing and type shape how software feels more than people expect. I get designs in front of users early so the details get fixed while there's still time.




Tell me about the role, or the problem you're working on. You can also email me at [email protected].