The part that
doesn't get automated.

I'm a Product Designer with 5+ years of experience building interfaces for complex, data-heavy products — most recently at Prescouter, where I design AI-driven UX for enterprise workflows. But I don't stop at the mockup. I design and vibe-code the front end, work closely with developers, PMs, and QA through to deployment, and ship through GitHub.

I care about how the work looks, but just as much about how it functions, how it scales, and whether it actually moves the business forward.

AI moves fast, but the people using what I build still need something that feels considered — clear, trustworthy, and built for how they actually work. That's the part that doesn't get automated.

AI isn't a gimmick I bolt on — it's built into how I work, every week: research and synthesis, copy exploration, wireframe exploration, dev support, QA, documentation, and process automation. It's there to speed up the parts of the process that should move faster, so I can spend more time on the parts that actually need judgment.

Every project is different, but the rhythm is usually the same: get clear, move fast, build properly, then tighten until it's ready for the real world.

(Nori approves of this message from his curled-up spot nearby)