Discover the interview of Tanya Donska:
How did you become designer?
I studied mechanical engineering, which had nothing to do with design. Spent my free time illustrating and working on game design projects because that’s what I actually wanted to do. Then someone invited me to start a company and said I should do UX design and creative direction instead. I said yes without really knowing what UX design was. Figured it out as I went. Turned out I was better at fixing interfaces than engineering bridges, so here we are.
How would you define your vision of design, your style?
I fix the boring parts nobody wants to touch. The feature that’s buried three clicks deep. The dashboard that takes twelve steps to do something simple. The onboarding flow losing users at step two for reasons nobody’s figured out yet.
Most of my projects aren’t portfolio material. They’re the unglamorous work of making products actually usable. Clean, functional, doesn’t fall apart when real users touch it. I like Scandinavian modernism – lots of space, good typography, nothing trying too hard.
If it works and people can use it without calling support, I did my job. If it looks good in a design award submission but confuses actual users, I failed.
For the future, what are your professional projects?
Staying small. Most studios want to scale – hire teams, build process, maximize capacity. I’m going the other direction. Keeping it just me, working embedded with product teams, no agency overhead.
Currently figuring out how to diagnose UX problems faster so I can spend less time auditing and more time fixing. Also writing more about what I actually see in products – the patterns that keep breaking, the mistakes teams keep making. Practical stuff, not design philosophy.
The goal isn’t to build a big studio. It’s to be known as the person who fixes what’s actually broken, not the person who redesigns things that were working fine.
What do you like the most in your job?.
Finding the thing everyone’s just accepted as broken. Support explaining the same feature location to users every day. Product team knowing something’s wrong but not sure what. Engineers saying “yeah, we know that flow is weird, but nobody’s prioritized fixing it.”
Then I fix it and the numbers actually change. Adoption goes up. Support tickets go down. Users stop getting stuck.
Also: no daily standups. No Slack check-ins. No meetings about whether we need a meeting. I work async with most clients, which means I can actually think instead of performing productivity. That’s probably the best part, honestly.
