Why don't you need the perfect solution
Perfectionism is a sweet killer. He killed more nerves, relationships, and projects than a kitchen knife, a Kalashnikov assault rifle, and your customer together.
In this article I will explain why you do not need the perfect solution.
Absolute does not even alcohol. And if there was, then what?
Attempting to reach the mythical 100% costs catastrophically expensive and does not bring anything but broken deadlines and jambs wherever possible.
According to The Standish Group , 50% of the functionality is almost never used, 30% is rare, and only 20% of the functionality is used frequently.
')
Scientifically, this is called Pareto's Law : 20% of the effort brings 80% of the result.
In most cases, 80% of the result is enough. Do not overpay and take risks. Do well what you really need.
An effective solution is not necessarily the right solution. This is the right decision that the team supports.
You can be infinitely right, but what is the use of it, if at the end of the day the performer does everything in his own way?
Dr. Robert Zawacki expressed it with the formula
ED (effective desicion) - an effective solution,
RD (right desicion) is the right decision
CD (commitment to decision) - the level of commitment to this decision.
The train will not stop at “train, wait, one, two,” and the team will not invest in a solution that they don’t believe in just because you are the boss.
If you want a result, get team support.
Have you heard of “Well, what is difficult for you? Are we already discussing longer? ” In English, this is called gold plating. As a result, a small refinement takes more time than expected, and the output turns out that now nothing works at all.
According to PMI , in 2018, 52% of the projects suffered from the spread of content and uncontrolled changes. Tellingly, champion companies suffer from it much less often than lagging ones: 33% versus 69%.
It is impossible to improve what is not working yet. Make a working product, and only then engage in its improvement.
And never forget: Done is better than perfect.
In this article I will explain why you do not need the perfect solution.
You don't have to pee at 100
Absolute does not even alcohol. And if there was, then what?
Attempting to reach the mythical 100% costs catastrophically expensive and does not bring anything but broken deadlines and jambs wherever possible.
According to The Standish Group , 50% of the functionality is almost never used, 30% is rare, and only 20% of the functionality is used frequently.
')
Scientifically, this is called Pareto's Law : 20% of the effort brings 80% of the result.
In most cases, 80% of the result is enough. Do not overpay and take risks. Do well what you really need.
Don't decide for everyone
An effective solution is not necessarily the right solution. This is the right decision that the team supports.
You can be infinitely right, but what is the use of it, if at the end of the day the performer does everything in his own way?
Dr. Robert Zawacki expressed it with the formula
Where
ED (effective desicion) - an effective solution,
RD (right desicion) is the right decision
CD (commitment to decision) - the level of commitment to this decision.
The train will not stop at “train, wait, one, two,” and the team will not invest in a solution that they don’t believe in just because you are the boss.
If you want a result, get team support.
The road to hell is paved with good intentions.
Have you heard of “Well, what is difficult for you? Are we already discussing longer? ” In English, this is called gold plating. As a result, a small refinement takes more time than expected, and the output turns out that now nothing works at all.
According to PMI , in 2018, 52% of the projects suffered from the spread of content and uncontrolled changes. Tellingly, champion companies suffer from it much less often than lagging ones: 33% versus 69%.
It is impossible to improve what is not working yet. Make a working product, and only then engage in its improvement.
How to get a good solution
- Decompose the product / requirements.
Understand what you want to get at the exit and do not leave room for unhealthy fantasies. - Prioritize between components. For example, the Moscow method is suitable for this.
Vital components are assigned the value Must.
Components without which you can live, although I would not want to, Should.
Give the hotel to the Could.
The rest is Would or Won't. While you can forget about them. - First, make the components MUST.
A working product is better than a promise of a miracle.
The rest will do when you do the work. - Do not grab for all the brilliant ideas on how to do even better. Each must be carefully weighed.
Learn to say No / Not Today / I will think. If someone's Wishlist works, he will be a hero. If you screw up the whole project, you will be extreme. - Do all this with the team and attract the customer.
If you do not want to fill up the project, considering yourself an unrecognized poet.
And never forget: Done is better than perfect.
Source: https://habr.com/ru/post/460275/
All Articles