On manufactured complexity, the Figma illusion, and the only UX metric that actually matters.
When I started my UX journey, I did what everyone does: I jumped straight into the interface.
I obsessed over Figma tutorials. Clean buttons. Minimal fintech layouts. Sleek and beautiful. I thought I was learning UX. Then I tried to go deeper, and hit a wall of jargon. User journeys. Cognitive load. Design thinking. Every new concept felt like a puzzle piece scattered across the floor.
The fog was real. And nobody seemed able to explain it simply.
When I actually started working in the digital product ecosystem—talking to developers, studying retention, mapping out a product’s lifecycle from idea to abandonment—the fog began to lift. But something still itched. There had to be a simpler explanation. One sentence that could hold everything I was learning together, without the buzzwords.
After wrestling with the reality of building software, I finally found it.
If a founder or a junior designer asks me today for the most honest explanation of what UX actually is, this is what I tell them:
We determine how one piece of data travels from its first entry point to its final endpoint.
That is it. No further explanation needed.
A user opens your product. They insert their first piece of data. True UX is having a bird’s-eye view of where that data will travel—every decision point, every friction moment, every server handoff—until the journey is complete.
From that single reality, everything else is built. The UI. The architecture. The retention loops. The error states.
It is the lighthouse question. Everything else navigates by it.
Why Nobody Tells You This First
The UX industry has a complexity problem—and it is not accidental.
Courses, certifications, and agency frameworks multiply because complexity justifies their price tags. The more opaque UX appears, the more valuable the people who claim to decode it seem.
But the practitioners who actually build good products don’t live in the frameworks. They live in the data flow.
This is the most expensive mistake founders make. They hire agencies to build “UX,” and they end up buying beautiful, static Figma screens that completely ignore how the actual data moves.
But this failure is not limited to tech startups. It is a universal management trap.
You see it in organizational design. A CEO pays a consulting firm to restructure the company. They get a beautiful, symmetrical org chart in a slide deck. But it completely ignores how an actual decision travels from a junior manager to final approval.
You see it in environmental design and public planning. A city builds a stunning, award-winning transit hub, but commuters still have to walk a quarter-mile in the rain because the bus drop-off doesn’t align with the train entrance.
They bought the scaffolding, but they missed the building. They bought the aesthetic of a solution without mapping the friction of the reality.
In the corporate world, we love to start meetings by asking: “What problem are we solving?”
It is a crucial question. But it is not the most important one.
The absolute most important thing in UX, operations, or business in general, is the final destination.
If you do not know the exact endpoint—and the brutal, unglamorous reality of how a user, an employee, or a piece of data actually travels to get there—your brilliant strategy is just a roadblock in disguise.
The next time your team presents a new software feature, a corporate restructuring, or a new public policy, stop looking at the aesthetics. Ask them the Lighthouse Question:
Where does the journey start?
Where is the final destination?
What exactly is happening in between to make it faster and less painful for the person on the other side?
If your team cannot answer that immediately, they aren’t designing a solution. They are just coloring in boxes.
Answer the question honestly, build the system around it, and watch the fog clear.