Jana Gonsenicova

I map the rules before I draw the screen: what can happen, what happens next, and where those states collide. The interface comes after the logic.

I don't explore in isolation. I bring developers in right during exploration and pull in PMs and customer-facing teams when their context can change the answer. When something is easier to understand in code, I build it there.

Not a Figma approximation — it runs in the production codebase and the team's own design system, with the loading, empty, error and edge states in place. I use AI tooling, MCPs and skills to work directly in the codebase; everything I open goes through the same review as anyone else's. Some of it merges directly; the rest engineers build from and cite in their own pull requests.

The method follows the question: production usage, surveys, interviews, usability testing, churn data. When the evidence disagrees with my solution, the solution changes.