No process is ever the same, and that’s completely fine

I’ve never been the kind of person who follows one set recipe when I design. And the longer I do this, the more confident I get that you don’t really need one.

There are tons of fancy models out there for how you’re supposed to work. But for me, it rarely starts that way. I often jump straight into something concrete. A button. A form module. An idea I need to get out before I lose it. Then I build the rest around that.

Sometimes I start in the middle. Sometimes at the very end. I work like that because that’s how my mind works. Not because it’s random or poorly planned, but because I rarely run into two projects that are truly alike. It doesn’t make sense to pretend everything can fit into the same mold every time.

When I try to follow a streamlined process from A to Z, I lose a bit of energy. I start caring more about doing things “right” than solving what’s actually in front of me. I begin thinking about what will look good in a case study instead of what works for the user.

So this is just a small reminder — to myself, and maybe to you too: it’s okay to take things as they come. It’s not laziness. It’s not bad UX. It’s just a different way of thinking.

What matters most is that what we make works. Not that the process looked good on a whiteboard.