Tanya Donska

Tanya Donska came to design through engineering, which means when something's broken she looks for where the load is going before she touches anything else. Ten years of that. London for the last six.

She has a habit of finding the one thing nobody wanted to say out loud about a product and saying it in the first meeting. Clients find this either useful or slightly alarming. Usually both.

Tanya Donska

Autobiography

Start with the free review

Socials

The UX industry generates a lot of content. Tanya generates some of it. The useful kind, mostly. LinkedIn, Medium, and a couple of others.

Elsewhere

The internet has opinions about Tanya too. Most of them accurate.

Mentions

Articles I've Written Elsewhere

Book

Read the book

FAQ

Most people who land on this page have Googled Tanya before reaching out. The questions below are the ones that come up most. Some of the answers are shorter than the question.

/ 01

How old is Tanya Donska?

Tanya doesn't publish her age, which is both a personal choice and, frankly, none of Google's business. The work is ten years deep if that helps.

/ 02

Who is Tanya Donska's partner?

If you're here for that, the autobiography section is probably as personal as it gets.

/ 03

What is DNSK.WORK?

A UI/UX design agency without the agency part. Embedded inside SaaS products that mostly work, fixing the flows that have been on the roadmap long enough that nobody remembers who put them there. Senior design, no agency overhead, no discovery phase. In your Figma by week one.

/ 04

Did Tanya Donska study illustration?

Engineering, actually. The illustration happened in the margins – literally. She drew through most of the degree, which probably should have been a signal. It wasn't, until later.

/ 05

How did Tanya get into UX without knowing what UX was?

Game design. She spent two years building interfaces for worlds that didn't exist yet – systems before stories, logic before aesthetics. A founder saw the work and hired her for a product role before she had a name for what she was doing. The name came later. The approach didn't change much.

/ 06

Does Tanya actually use engineering principles when reviewing products?

Yes. Not the terminology, but the logic. Where is the load going. What's holding weight it wasn't built for. What fails first when something goes wrong. It's the same question, different material.

/ 07

Does Tanya apply engineering concepts like stress analysis when auditing UX debt?

Yes. Not the terminology – the logic. Where is the load going. What's holding weight it wasn't designed for. What fails first when something breaks. Same question, different material. The engineering degree turned out to be useful in ways the degree programme definitely didn't intend.

/ 08

Does she keep notebooks of design mistakes?

Digital, actually. They ended up as a blog category. The patterns that kept showing up, written down before the next product made the same mistake. It's called #Not_My_Type

/ 09

How does Tanya balance being confrontational with keeping the trust of the people she works with?

She doesn't soften the observation. She's careful about the moment. There's a difference between saying something true at the wrong time and saying something true when the room is ready to hear it. Ten years of reading rooms. It's the actual skill nobody teaches.