What Designers Actually Do

Good design is evidence based. That might surprise people who think design is mostly gut feeling and aesthetics, but it’s true. Evidence comes from everywhere. Usability testing. Research. Defined design standards. Trends in the field. Accessibility guidelines. Real users doing real things with real products and hitting real walls.

When I tell people what I do for a living, I don’t say I’m a product designer, UX designer, or UI designer. Those titles mean nothing to those outside of tech. I say I design phone apps and websites. Everyone knows what those are. Everyone has used one that’s frustrated them, confused them, or made them feel stupid for not figuring it out right away. That frustration is a design failure. My job is to prevent it.

But here’s what that job actually looks like from the inside, the part that doesn’t make it into the title or the job description.

It looks like running a usability test and watching someone hesitate on a screen for three seconds before tapping the wrong thing, knowing that three second pause means the design hierarchy is off, not the user. It looks like pushing back on a stakeholder who wants a feature added because a competitor has it, and explaining that just because it exists elsewhere doesn’t mean it belongs here. It looks like spending an afternoon on a single button. Not its color. Not its label. Its placement, its size, its relationship to everything around it, and whether a user with low vision or limited motor control can actually use it.

Being a designer is iteration. Again, again, always iterating. The first design is almost never the best one. Not because the first idea is bad, but because design is a process of refinement that requires feedback, testing, critique, and the humility to start over when the evidence says to. Good design takes time. It takes effort. It takes other people telling you something isn’t working and you choosing to hear them instead of putting the blinders on.

That last part is the invisible skill nobody talks about in job descriptions. Designers work in one of the most subjective fields that exists. There is no black and white correct solution. No compiler that tells you the layout is wrong. No error message when the onboarding flow is technically functional but emotionally exhausting. The feedback is human, which means it’s messy, contradictory, and sometimes painful. Learning to be confident in your work without being married to it, to care deeply about whether a design is right while staying genuinely open to being wrong, is something that takes years to develop and never fully stops being difficult.

The subjectiveness is one of the leading causes of burnout in design and other creative fields. Designers tend to be empaths. We truly care about doing our work well. We want our designs to look good, but we also want them to work for real people, in real moments, and on real devices. That level of investment is what makes good design possible. It’s also what makes the job exhausting in a way that’s hard to explain to people outside it.

AI can generate a UI in seconds. It can produce ten variations of a layout before your coffee cools. What it cannot do is watch a user hesitate and know what that hesitation means. It cannot feel the tension between what a stakeholder wants and what a user needs and navigate that conversation with both honesty and professionalism. It cannot sit with the discomfort of not knowing if a design is right as is or still needs some iteration.

That’s not making things pretty. That’s the job.