How I work
The process hasn't changed: discovery, flows, prototypes, user testing, collaboration, all just happening a lot faster these days.
What is also evolving is everything around it. I prototype in code with agents now, and only reach for Figma when the project needs it.
This makes for fewer handoffs between the thinking, the design and the building, which can only be a good thing.
Some steps elongate, some get skipped. But the process itself is ever-present: frame the problem, conceptualise, validate, prototype, ship.
Design process
Problem, users, constraints, what success looks like. I sit with the PM, engineer, or founder until we agree on what we're actually solving. Output is a shared brief everyone can point at later.
The terminal is where I clarify intent, draft the PRD, and pressure test my own assumptions. Risks, edge cases, unknowns all surface early through research, while it's still cheap to change direction.
User tests, quick prototypes, self-serve research. I'd rather learn I'm wrong in a day than ship confidently into the dark. What comes back reshapes the output.
AI builds, I guide structure, behavior, and UX quality. Most design decisions happen in the working software because this is where the nuances show up.
When the org requires it: alignment with the existing design system, handoff documentation, the works. When I'm shipping directly, the code is already the source of truth. Figma is a tool, not a required step.
Design QA, usability tests, final tweaks in code, release. I stay close through launch and iteration. A ship date isn't the end of the work.
Why this matters
The main focus is shipped software. But the prompts, patterns, and skills I build along the way are always shared, written down so the next person can use them.