UX doesn't need prophets. It needs practitioners

UX doesn’t need prophets. It needs practitioners.

Our field loves to deify gurus, between Don Norman, and IDEO founders. Their names get treated like scripture.

They’re not liars - their theory is still solid, they wouldn’t be successful otherwise.

What’s missing is proximity.
I can’t help but feel they’re detached from the reality of day-to-day design work - the grind of junior designers, the messy constraints inside agencies, the compromises between design and dev.

They’ve built names big enough that they can afford to stay at the 30,000-foot level.

That’s privilege, not practice. It’s not representative of the grit of real design work.

The problem is when business schools and corporations keep recycling these voices as the canon of innovation. Theory is not reality, and innovation happens in reality.

For example, a theory-heavy workshop can make everyone feel smart for two hours. The team maps personas, writes sticky notes, circles a few themes, and leaves with the language of customer centricity. Then Monday comes, the developer says the flow cannot work with the current API, the account manager says the client already promised the feature, and the junior designer has to make the compromise look intentional.

That is where practice lives.

Practice is knowing when a beautiful journey map is hiding an operational constraint. Practice is noticing that the user problem is really a sales promise, a support burden, or a decision nobody wants to own. Practice is being able to say, “This sounds good in the framework, but it will fail in the handoff.”

That kind of judgment rarely comes from keynote distance. It comes from shipping, negotiating, documenting, watching users struggle, and dealing with the consequences when the elegant theory meets a messy organization.

If design and innovation want to evolve, we need fewer prophets on pedestals, and more practitioners whose work is grounded in outcomes, constraints, and consequences.