Product designer. Ten years of making software feel like it was meant for someone.
I’m Jhoko — a product designer with over a decade on software that people use because their job requires it, not because it is fun. Payroll, HR, compliance: the category where a confusing screen costs someone a real afternoon.
That constraint shapes how I work. I spend most of my time on flows, edge cases and the design system underneath, because consistency is what makes a large product learnable. The remaining time goes to brand and film, which is where the same ideas have to survive being seen for three seconds instead of used for three years.
I work end to end — problem framing through to the tokens engineering ships against — and I am comfortable being the person who names things, sets the bar, and reviews other people’s work to it.
What I do
- Product design
- End to end: the problem, the flows, the screens, and the unglamorous states everyone forgets until QA.
- Design systems
- Tokens, components and naming a designer and an engineer can both reach for without a meeting.
- Brand and campaign
- Identity, motion and the film that has to hold up on a billboard and a phone.
- Design direction
- Setting the bar on a team, reviewing the work, and keeping ten screens by four people looking like one product.
How I work
- Ship the boring states
- Empty, loading, error and permission-denied are most of the real experience. They get designed here, not left to defaults.
- Name things properly
- Half of a system’s value is in what the tokens and components are called. Bad names cost a team years.
- Show it in place
- Nothing is approved on an artboard. Work gets reviewed at the size and distance it is actually read from.