I swear by the Pareto principle as a universal duality that applies to almost anything. Got this image from Contactme.com where it shows the different applications of the principle in business.
I wish to extend this further by saying that engineering, especially Software Engineering’s Agile Methodology, uses this principle. The first 20% of the specs you develop first should cover 80% of the value of the project to the end-user already. The initial efforts, which are usually the most coordinated, should take care of the main problem being addressed. If you manage project priorities this way, it makes sure that the customer gets results early and feels the value of the project early on. The key takeaway here is knowing what the customer believes is of most value and correlate this to what your team believes is the most important. This is easy to say but is a very tricky balancing act every single time.
Take it one level down, to engineering design, and the same rule applies. The ideal model, the jump-off point in any engineering design, takes care of 80% of the solution. Executing the ideal model will take 20% of the effort. The remaining 80% of the effort solves the 20% of the non-idealities.
This also roughly applies in the statistics of design. Most of the problems that might arise have less than 20% chance of happening. However, engineers use 80% of the effort in mitigating these potential failures. So better make sure your team does not get lost in the details and forget the relative value of the particular task in the big picture. Sometimes, it’s unwise to spend too much resources in solving a pesky problem that has much less than 20% chance of happening. Especially if this is delaying launch.
