make meaning, not noise.
serbia, belgrade & new york
7:50:40
CEST
Design Process
Creative Career
16.6.2025

What I’ve learned after 50+ projects and what still get wrong

You'd think that after more than fifty projects things would start to feel predictable. That there would be a perfect process, complete confidence, and a reliable formula for solving every problem. In reality, the opposite has happened. The more projects I complete, the more I realize how little design is about certainty. Every industry behaves differently. Every client sees the world through a different lens. Every project introduces constraints that didn't exist before. What worked perfectly six months ago can feel completely irrelevant today. Experience doesn't eliminate uncertainty. It simply changes your relationship with it.

When I look back at the last few years, I don't think about awards, launches, or metrics first. I think about the lessons that kept repeating themselves across completely different projects. Some took years to understand. Others I learned quickly and then somehow forgot again. Even now, I continue to make many of the same mistakes. The difference is that I notice them sooner. This isn't a list of rules or universal truths. It's simply a collection of observations that became impossible to ignore after spending years designing websites, brands, and digital experiences.

Simplicity Is Much Harder Than Complexity

Early in my career, I associated complexity with skill. More interactions, more visual layers, more animations, more ideas competing for attention. Complexity felt impressive because it was visible. Simplicity felt easy because it looked effortless. Years later, I've come to understand that simplicity is usually the harder path. Removing something is often more difficult than adding it. It requires clarity and forces you to decide what truly matters. Every element must justify its existence. Every interaction must serve a purpose.

Even now, I regularly catch myself overcomplicating layouts, interactions, or entire concepts before eventually returning to a simpler solution. The best projects rarely feel simple during the process. They become simple through the process. What appears obvious in the final result is often the outcome of countless decisions, revisions, and discarded ideas. Simplicity isn't the absence of effort. It's the result of it.

Clients Rarely Need More Options

One of the biggest mistakes I made early on was believing that more concepts created more value. If one direction was good, surely five directions would be better. The reality is that options often create uncertainty rather than confidence. Most clients are not looking for endless possibilities. They are looking for guidance. They want someone who can evaluate a problem, make informed decisions, and explain why a particular direction deserves to exist.

Over time, I began presenting fewer concepts and spending more energy explaining the thinking behind them. Design is not simply the act of creating visuals. It is the act of reducing ambiguity. Clients hire designers for perspective as much as execution, and the longer I work, the more I realize that confidence often matters more than quantity. Presenting fewer directions forces better thinking, stronger reasoning, and clearer communication. It also creates something that many creative people struggle with: commitment.

Process Matters More Than Inspiration

For a long time I waited for inspiration far more than I should have. A strong idea felt like the beginning of a good project. If the idea wasn't there immediately, it felt like something was wrong. Today I trust process far more than inspiration. Research, references, exploration, testing, and iteration may not sound particularly exciting, but they consistently produce stronger outcomes than waiting for the perfect idea to arrive.

Some of my favorite projects started with uncertainty rather than confidence. The direction only became clear after exploring multiple dead ends. Looking back, inspiration rarely appeared before the work began. More often, it appeared somewhere in the middle of it. The process exists to help navigate uncertainty. Most mistakes happen when I convince myself that experience allows me to skip steps. It never does. Every time I ignore the process because I think I already know the answer, the project eventually reminds me why the process exists in the first place.

The More You Learn, The More You Realize You Don't Know

Perhaps the biggest lesson has been understanding how much remains unknown. There is always a better way to present an idea, a more efficient workflow, a new technology worth exploring, or a perspective that challenges existing assumptions. The industry changes constantly, which means expertise is never permanent. What feels advanced today eventually becomes standard. What feels impossible eventually becomes accessible.

Even after years of work, I still research basic things, experiment with new approaches, and make mistakes. The difference is that those mistakes no longer feel like evidence of incompetence. They feel like part of the process. The best designers I know tend to share a similar mindset. They remain curious long after they have achieved recognition because curiosity is what keeps growth moving forward. The moment you believe you have figured everything out is usually the moment progress begins to slow down.

Still Learning

If there is one conclusion I've reached after fifty projects, it's that design is less about finding answers and more about asking better questions. Every project is a conversation between business goals, user needs, creative ambition, technical limitations, and personal taste. None of those variables remain fixed for very long, which is why there is no perfect formula waiting to be discovered. The challenge is not learning a system that works forever. The challenge is staying adaptable enough to continue learning as the industry evolves.

I'm still changing my mind. Still discovering mistakes in projects I once considered finished. Still finding better solutions months after launch. In some ways that can be frustrating, but it is also what keeps the work interesting. The moment everything feels solved is usually the moment growth stops. Looking back, that may be the most valuable lesson of all. After fifty projects, I haven't found certainty. I've simply become more comfortable working without it.

What I’ve learned after 50+ projects and what still get wrong