Krisna Wiyana
There isn't a fast version.
Product Designer · Indonesia

Design is being generated in seconds. I still take the long way.

I'm Krisna Wiyana, a SaaS and product designer who spends real time with a problem before I let a single pixel near it. Nine years, forty-plus shipped products, zero shortcuts.

Scroll or press ↓, there's no rush
Why slow

Anyone can prompt a layout into existence now. That was never the hard part of design.

The hard part is sitting with a business long enough to know which screen actually needs to exist, what a user will trust on sight, and where a single decision saves six months of rework. AI can fill a canvas. It can't sit in that discomfort with you.

So I do the unglamorous part first: the questions, the flows, the wrong draftsReal example: for Primal Race I built three full landing-page concepts before picking one. The two we killed weren't bad, they just weren't load-bearing for the actual goal, race-day registrations, not "looks impressive.", before anything gets fast or pretty. What comes out the other side isn't faster. It's correct, and it stays correct after launchAcross 40+ shipped products, the ones that needed a redesign within a year were almost always the ones rushed through discovery, not the ones with weaker visual polish..

9+ yrs in product design 40+ products shipped -30% design-to-dev time 1B+ IDR GMV growth at Agriaku
How it actually goes

Four stages, no skipping ahead.

  1. 01

    Listen longer than feels efficient

    Stakeholder calls, support tickets, half-finished specs: I read all of it before I open Figma, because the brief is rarely the real problem.

  2. 02

    Map the whole flow, not the pretty screen

    Wireframes and user flows for the entire journey, so the "exciting" screen isn't built on a structure that collapses three steps later.

  3. 03

    Design in drafts you'll actually argue with

    Rough, revisable concepts shared early, not a polished reveal, so we find the real disagreements while they're still cheap to fix.

  4. 04

    Hand off something engineers don't have to guess at

    Developer-ready files, states, and edge cases documented, so the slow front-end work doesn't turn into a slow build, too.

Intermission

Halfway through. Take one slow breath.

The next cards will still be here in eight seconds. Nothing on this page is in a hurry — you don't have to be either.

Selected work

Five projects, looked at slowly.

Drag sideways to browse all five →

Most of these are under NDA, so you get wireframe sketches instead of screenshots. The numbers are real.

"Design simply, think deeply, impact greatly." That's the line I keep coming back to, and the closest thing I have to a personal brief.
What I take on

A short list, on purpose.

UI/UX Design SaaS, Mobile & Web App Design Dashboards & Admin Panels High-Converting Landing Pages Design Systems & Component Libraries Wireframing & Prototyping User Research & Usability Testing Cross-Functional Collaboration Rapid Iteration & Delivery Figma
Not a fit if you want something "made pretty" with no users, goals, or timeline behind it. That's a different job, and not one I'm good at.
Get in touch

If you're building something worth getting right, I have the time for it.

East Java, Indonesia. Working with teams across Indonesia, the US, and Singapore.

Start a conversation
Colophon · for the patient

You went through the whole deck. So here's how it was actually made.

14 drafts, 6 days. Three typography passes, two full rewrites of the hero line, and one intro animation that nearly didn't survive.

1 feature killed. A contact form. It felt faster, but it said less than a plain link.

0 templates. Built with AI, but not generated by it. Every section here went through real reasoning and research before it earned its place — the tool was fast, the thinking wasn't.

2 typefaces. Fraunces for the things that deserve attention. Inter for everything else.

Thanks for taking the long way. — Krisna