What you want is not what you need

Recently, one of my friends was planning to buy a car. I asked him, "What do you want to buy?" and he replied, "A BMW." I thought it was a great choice and inquired about his plans for the car. He said, "I'll use it for driving, mainly to my office, then for shopping at D-mart (think of it as Tesco), and also for occasional trips to Lonavla for a long drive (imagine Hastings, Britain, connected to M25)."

I admired his plan, but I couldn't help but point out some practical considerations. The BMW model he was interested in gives 8 to 9 km/l, and considering the traffic in Hinjewadi (though it may not be as chaotic as London, where most people use the tube or train), he would likely get around 4 to 5 km/l. This means he'd be spending 1000 INR daily on his commute.

Additionally, the BMW's boot space isn't substantial enough to accommodate all his groceries and monthly shopping in one go; multiple rounds would be necessary.

Moreover, since his parents accompany him on trips to Lonavla, the 5-seater BMW, with its limited back seat capacity for 2 adults and 1 kid, may not be the most practical choice.

This lesson extends seamlessly into the realm of software development. Often, we may be drawn to the latest technologies or programming languages because they are popular or personally comfortable. However, just as my friend needed a car that suited his lifestyle, software development choices should be driven by project requirements rather than personal preferences. In the business world, a similar pattern emerges.

Traders may initially desire numerous features in a trading system, but a crucial step is to delve into the "why" behind each requirement. Understanding the underlying needs ensures that the solution is tailored to address actual challenges, leading to a more efficient and effective outcome.

Reflecting on a past project, our team initially leaned towards rewriting a trading system in C++, the familiar territory. However, a series of"why" questions led us to the realization that Java was a more suitable language for a fresh development approach. Stepping out of our comfort zone ultimately resulted in a successful trading system that we are proud of.

In essence, whether it's choosing a car, selecting technologies for software development, or meeting business requirements, the key takeaway is clear: what you want is not always what you need. Aligning choices with genuine needs ensures practical, efficient, and successful outcomes in any endeavor. #DecisionMaking #SoftwareDevelopment #BusinessStrategy