Why design leaders don't need to be industry experts

Every technical industry builds products for itself. Crypto is the sharpest example I know. Products designed by experts, built by experts, reviewed by experts. Then the industry wonders why normal people bounce off them.

The cause is simple. Expertise creates blind spots. Once you know what a term means, you stop seeing it. Once a flow makes sense to you, you stop noticing what it demands from someone new. Knowledge only moves in one direction. You can't experience your own product as a stranger, no matter how hard you try.

The outsider's advantage

When I took over design at a crypto company, I wasn't a crypto native. I treated that as an asset, because it was one.

In my first weeks I could feel every point where the product assumed knowledge I didn't have. Every unexplained term, every step that only made sense if you already knew the ending. That's the exact experience of the users this industry keeps failing to win, and I was getting it first-hand, on payroll. No research budget buys that.

Put the gap to work

In a company full of experts, not knowing is the one thing nobody else can do. So I used it deliberately.

I became the test user for every flow we reviewed. If I couldn't follow it, we treated that as a bug, not a training issue. My questions doubled as a jargon detector for interface copy. And in debates about what users would understand, I didn't have to guess. I was the evidence in the room.

Hidden, a knowledge gap is a weakness. Deployed, it's the sharpest research tool in the building.

Fresh eyes expire

The catch is that the advantage has a shelf life. Every week you understand more and see less. So you have to work it deliberately.

Write everything down before it evaporates. Every confusion in the first weeks is a finding. Once you learn the answer, you will never feel that confusion again, and your notes become the only record of what a new user actually experiences. Mine turned into a backlog of fixes no insider had flagged.

Use the product before you read the docs. Documentation teaches you the insider's mental model. The product shows you the one users are stuck with.

Ask the obvious questions in rooms full of experts. Users can't ask anyone. You can. Any answer that takes ten minutes to explain is a design problem, not a user problem.

Learn the domain, keep the seat

None of this is a case for staying ignorant. You need real fluency, and quickly. Credibility with technical founders depends on it, and you can't fix what you don't understand. I went deep on the domain within months, and the job needed it.

The trick is what you protect while you learn. Your role is to hold the user's seat at the table, and the record of your own early confusion is the proof of what that seat sees. Learn like an insider. Advocate like an outsider.

Hire for the thing that takes years

Domain knowledge takes months to build. Design judgment takes years. When companies insist their design leader comes from inside the industry, they're selecting for the cheap skill and filtering out the expensive one.

The industries with the worst usability need outside eyes the most. If everyone in the room shares the same knowledge, nobody in the room can see the product.