Product thinking for designers

Early in my career I thought my job was to make things look good. I was proud of clean layouts and nice type, and I would defend a pixel like my life depended on it. None of that was wrong exactly. It was just not the whole job, and it took me a while to see that.

The shift happened when I started asking a different question at the start of a project. Not what should this look like, but what is this actually for, and how will we know if it worked.

Design in service of a problem

A screen is not the goal. It is a tool for solving a problem someone has, inside a business that has its own goals. When I hold both of those in my head at once, the design decisions get easier, because I finally have something real to measure them against.

If I cannot explain how a design helps the user do their job and helps the business at the same time, I usually do not understand the problem well enough yet. That is a useful signal. It sends me back to talk to people instead of pushing pixels.

Beauty that does nothing is decoration

I still care deeply about craft. But I have learned that beauty which does not move anything is just decoration. The most satisfying work I have done was not always the prettiest. It was the work that quietly removed a support burden, or lifted a number that mattered, or made a hard task feel simple.

This is why I like working close to product and engineering. They keep me honest. They ask why, and they ask what happens next, and a good designer should be asking the same things first.

How this shows up day to day

I prototype early, because a rough working thing teaches me more than a perfect argument. I try to measure whatever I can, because opinions start a conversation and data ends it. And I collaborate constantly, because the best ideas rarely arrive fully formed from one person.

Product thinking did not make me less of a designer. It made me a better one. The craft matters more when it is pointed at the right problem.