IS Why? Enough.

We launch a lot of products. I am using the term “product” to highlight any tool feature that serves someone. It could be for 100+ users or millions of users. We are always taught that we should be asking “Why?” The more we work on any project , the more evident it becomes that just asking “Why?” is not enough .

Along with asking “Why?” We also need to challenge the response to “Why?” Is the answer to Why correct, is the context correct. How are we going to measure if the answer to Why was correct? Is the question asked timebound ? Will it be relevant in 6 months or 2 years , or ever. I know I am getting philosophical, but let’s take an example

Let’s assume a project/feature request is picked up:

“Systems should be scaled to support X orders in a given region y”, this sounds like an interesting project and seems to have good enough engineering complexity, but have the following questions been considered?

.

Related posts:

We started returning to the office, hitting the gyms, having lunch at restaurants, and being ecstatic about having drinks in-person with colleagues again. Distancing, masks, take-out only, and then…

I had roughly three competing dream jobs when I was younger: actor (by which I mean world-famous movie star, of course), author (by which I mean world-famous novelist, of course) and zookeeper. Can…

The black presence before the 20th century in Europe: There is a danger in asking twentieth-century inquiries of prior occasions since the present