More Right or Less Wrong?

Are we trying to get things more right or less wrong?

I believe there is a fundamental mindset shift between these two approaches: a) We’re doing X well today. We think we have an idea of how to improve X tomorrow. b) We know we’re doing X somehow wrong today. We can’t wait to discover the data that will help us do X less wrong tomorrow.

The first approach is built on pride. It assumes we are mostly right and only need refinement. It consolidates bias.

The second approach is humble. It admits we might be off course and welcomes the learning process.

In software development, the second stance is much more effective. It helps avoid waste and the dangerous trap of right-the-first-time thinking.

Instead of aiming for an illusion of perfection, it fosters an agile, tech-debt-aware operating model. We know we might be building this feature wrong. Let’s ship, measure, learn, and adapt so the next iteration is (hopefully) less wrong.

Software products evolve through continuous discovery, not continuous imagination.

Originally posted on LinkedIn