I Built Something Beautiful That Nobody Could Use

Before I understood design, I thought it meant making things look good on Dribbble.

I was interning at a company doing frontend work — HTML, CSS, JavaScript. It was stressful. I didn’t like it. Then I saw my mentor design an e-commerce mobile app for shoes. The colors were perfect. The typography was perfect. Everything worked together so well that you just wanted to sit down, listen, and absorb when he talked about it. I knew immediately: this is what I want to do.

So I switched to design.

And then I built something that taught me everything.

The Hospital That Couldn’t Use What I Built

My first real project was a hospital management system. I was obsessed with making it beautiful. I pulled inspiration from Dribbble, looked at what other designers were doing, and built screens that looked polished and professional. I wanted to prove I was learning. I wanted to show I could design.

What I didn’t do was talk to the hospital.

I never asked them how they actually worked. I never watched a nurse navigate their current system. I never sat with the admin staff to understand what frustrated them. I just... designed screens. Beautiful screens. Completely disconnected from reality.

At the end, they couldn’t use it.

And that’s when I understood something that changed everything: anything beautiful that doesn’t work is useless.

The Thing Most Junior Designers Get Wrong

A lot of young designers want to prove a point. They want to show they’re improving. They want colleagues to be impressed. And look — that impulse isn’t bad. But here’s what’s missing:

They don’t do due diligence. They don’t research. They don’t look at how similar products actually work. They don’t study the winners — the products that are actually solving the problem people have.

Instead, they build in a vacuum and hope it’s beautiful enough to matter.

My mentor taught me something simple: look for products that are winning, not failing. Study them. Understand how they work. See what their UX actually does. Then bring those ideas into your own thinking.

That’s not copying. That’s learning from reality.

What I’d Tell My Younger Self

If I could go back to that hospital project, I’d tell myself one thing: Do your due diligence. Talk to the people who are going to use what you build. Understand their actual workflow. See how similar systems work in the real world — especially the ones that people actually want to use. Then design from that understanding, not from what looks good.

Because a beautiful hospital system that doesn’t work doesn’t help anyone. It just sits there. Unused. A reminder that you designed for yourself, not for the problem.

The best design I’ve ever made didn’t start with “How can this look amazing?” It started with “How does this actually need to work?”

Beauty comes after that. Always.

If you're learning design, I’ll be writing about this stuff regularly. Subscribe and come along.