Correctness Over Performance

It is usually only when we encounter a performance issue that we realize the need for improvement. While we all want our applications to be fast, we must explain why. As a user, I expect my inputs to produce valuable and meaningful output. Speed is a bonus. When inaccuracies are widespread, we need to fix the business rules to address the problem. To do this, we must first understand what the application supports and then identify and tackle the inaccuracy issue.

In most cases, correctness should take priority over performance. Instead of aiming for a fast feature from the beginning, we should focus on making it easy to change in the future. As the application’s code evolves, it will continue delivering value while clarifying where the slow code exists.

Effective time management requires identifying the actions that lead to long-term results. Measuring progress against short-term effects is a flawed strategy. Instead, we should focus on the process, not the outcome.

Impact mapping is a technique that can help us better understand how we can influence business outcomes. It goes beyond formal requirements documents by identifying the business’s desired impacts. For example, they may want to increase sales, market share, or engagement. With this information, we can play a more effective role in helping the business achieve its goals. It’s a collaborative exercise that helps build a shared vision for the product.

[¹]: Impact Mapping: Making a big impact with software products and projects

[²]: Time Management