Always ask why

No offence to any Jims whom might be reading this.

Why, why and why.

Jim is not a reference to any of my colleagues in particular but rather a common trait that we display occasionally. (Even me, lol) Being closely connected to our end users, we often hear feedback in the form of feature requests. The easy way out is to take it at face value but that doesn’t make for a good product, does it?

In the early days of my current product team, there were times I felt like a human roadblock for our roadmap (hee hee, get it? 🙊). Nowadays, we have teammates reminding the users to tell us why when they request for a particular feature. From there, we dive into the root problem where its a whole other jungle and a story for another day.

That’s all folks!
If you liked the comic, do check out the one before here!