The cost of producing UI has collapsed. What used to
take a week of Figma now takes an afternoon in Cursor
with Claude Code. That changes where the value sits —
less in production, more in deciding what's worth
producing in the first place. So that's where I spend my
time: framing the problem, choosing the direction, then
building the prototype myself rather than describing it.
In practice that looks like this: I start with the
outcome and the constraints, sketch the shape of the
solution, then move into a coded prototype early —
usually Vue or React inside an existing design system,
deployed to a branch URL that stakeholders can actually
use. That's how the day-to-day work at Defrr and
Galvanized Pukeko gets shipped. The property-platform
design challenge above — buyer and seller side — was
built the same way, end to end.
I've spent the last year deliberately closing the
technical gap that used to sit between designers and
engineers. IBM's AI Product Manager Professional
Certificate and four Generative AI courses through IBM
SkillsBuild covered the model and product fundamentals;
Google Cloud's Conversational AI on Vertex AI and
Dialogflow CX gave me hands-on experience designing for
agent behaviour; LinkedIn Learning's AI Product Ideation
track filled in the discovery side. Combined with
shipping production code at Defrr and Galvanized Pukeko,
it means I can discuss trade-offs with engineers as a
peer, not hand off a static file and wait.
The constant across all of it is taste. AI
gives you a starting point. Whether it ships as
something coherent or something generic — that's still a
human call.