If you’re a designer or developer, you probably know that trying to make your project perfect can extend the time it takes to complete a project up to several times. There’s always one last element you want to improve quickly before posting it. But I think Perfection is equal to fascism.

It’s a bold statement, I know. But look around you. Is there at least one defective object in your house or garage?

Your car? You have to refuel it and sometimes it breaks down – not perfect. Your computer? It breaks and crashes, and your hard drive dies before you can back up your data – not perfect. Bread? It gets too old – not perfect. Glasses? Glass is vulnerable – far from perfect. So what’s the conclusion?

Why design without a design faucet is like composing

Why design without a design faucet is like composing

We had a great time at the Kars4Kids design department recently when our supervisor said, and I quote … Read more

Perfection hurts development

Nothing around us is perfect. There is always at least one thing that can be improved. If everyone leads their product to perfection before it is released to the public, then we would have nothing! Not even electricity or a bike.

Since everything around you isn’t perfect, don’t you want to own them? Would you prefer until someone leads them to perfection before they let you get them? Probably not.

Therefore, when working on your project, always take the failures of others as a reference – be creative, but don’t try to be perfect.

Why is perfection harmful?

Because it does not favor the achievement of goals when starting work, planning must always achieve some real goals. It can be something as obvious as increasing sales or unusual, like raising awareness at a water kick boxing center.

However, they should be goals you need to focus on, and whenever you want to do something new, you should ask yourself, “bring this thing closer to me?”

perfection-damaging development

And now the fun part. The pursuit of perfection will not bring you closer to your goals. On the other hand – invention the simplest possible solution does. That’s right – the most straightforward and reliable, not the best. At one early stage of a project, you can’t be 100% sure which solution is best.

Because how do you know this when you haven’t even started it? Only market feedback (real users) can give you genuine ideas for your website and how to improve it usability. This feedback is an improvement you need to focus on. not what you thought was best for them.

This is a blatant truth (unfortunately). You never know what people want or need, so working on a complex solution that may not be needed is a waste of time. That’s why you have to start with a solution that allows you to achieve your goals in the simplest way possible. And one more thing you should know:

Perfection often goes unnoticed.

Unfortunately, all this extra time you have spent striving for perfection can go unnoticed and priceless. There is a reason why the project recipient doesn’t even notice the extra effort.

And it’s simply because they didn’t see the previous version of the project, so they have nothing to refer to and compare. The only thing they notice and criticize are the basic functions and elements.

Working on the details (small fragments of your graphic design) will rob you of most of your time. It’s one little thing that constantly accelerates you or some other function that you think is neat and convenient.

So, before you understand it, the project completion time has been extended several times. Do you want to spend 60% of your working time improving details and only 40% achieving goals?

try perfect design

If you are freelancer, you can be sure that each customer is 100 times more grateful for a simple, easy-to-use, and understandable project to achieve goals than a beautiful work of art that looks good but doesn’t bring extra money in their pockets.

Rejecting perfection is far from giving up a good project.

As I’ve said before, in the project / product / design creation phase, you can’t be sure what the perfect solution is, so the whole idea of ​​implementing it is doomed from the start.

When you’re working on something, the only way you can judge perfection is by your own subjective motives – One person’s flesh is another person’s poison.

The most important rule of design: You are not your customer or visitor. Therefore, you cannot judge what you are planning just by your own opinions and assumptions.

You create a much better website without being perfect.

It’s simple (and true). If you don’t try to make every detail complete and instead focus on the most important key elements, these key parts are not only clearly visible in the final solution, but you also finish the job earlier.

So by hiding perfection in your pocket, you have a lot more productive and produces much better results.

Here are the benefits that can be achieved by forgetting perfection and creating a simple version of the website instead:

  1. The site can be launched earlier.
  2. The site can make money / get exposure sooner.
  3. Visitor feedback arrives earlier.
  4. Because of the early feedback, you improve the website by focusing on the things brought up by visitors (except things that you thought were great).
creating websites

The main conclusion here (although it sounds strange) is that a a simple solution is better than a complete solution. “Ok, but how can this approach be implemented?”

Divide the tasks into two groups: “Important” and “Information”.

The important ones are important, like achieving goals, building basic functions, etc.), and the details are just, well, just the details.

The details are time consuming. Therefore, you need to skip them and come back to them later, in one of the next steps of the job (or don’t go back to them at all). So what do I mean “later”? When is the best time to go back to the details?

Work iteratively

I mean, just keep up with me – Once you’ve divided the tasks into two groups, you should try to focus only on the important tasks on the first repeat and try to complete them in the easiest way possible. At the end of this iteration, you have a website ready to launch (SCRUMtype approach). You can start another if you want.

In this iteration, you can try to improve on the previous version. (Get ideas for improvement from customer / visitor feedback.) After the second iteration, you have an improved version of the website.

If you want to keep working and constantly improve your website, you can start the third iteration and then the following. This is the right time to go back to things you have classified as “details” at the beginning of the job, but you may as well understand that these “details” are completely unnecessary based on the reaction of visitors / customers (a very common thing).

work iteratively

This is the real strength of the iterative approach. During each step of the job, you have a complete website that is ready to launch, and you can continually improve it. This is a much better situation compared to working with a closed room for ten years, trying to make it perfect without feedback from the world.

A repetitive approach is also much safer. What is a better scenario – Do you realize that your idea is part of you know what and there is no demand in the market after a month of work, or you implement it after ten years of work?

Side note onlyA: Because of this approach, I was able to complete my master’s degree a few months before my colleagues did. I focused on the most important thing in each chapter, did it as soon as possible, and left all the details for later reference.

If I had wanted to do every perfect chapter from the beginning, I probably wouldn’t have finished it until today. In addition, more than two years have passed since I defended my M.Sc.

Work quickly and efficiently.

This is a general-purpose tip and can be put into practice when working on a client’s project as well as working on your own website. These are the only important things right now: fast work and fast results. It’s time to adjust.

Always try to produce quick results (focus on achieving your goals) by providing the simplest possible solution, not the “perfect” solution according to your own subjective opinion. Remember – you don’t have to be perfect. “Good enough” is good enough.

One more thing – What experiences do you have with projects where you have tried to provide a complete solution?


Please enter your comment!
Please enter your name here