Problem discovery skills for software developers and designers.

Why should you care?

1. A problem well-stated is a problem half-solved.

2. Finding problems is an analytical-emotional dance.

3. It is analytical for obvious reasons.

4. It is emotional because one has to first, work on oneself, then with others.

5. Failure to perform this analytical-emotional dance leads first to internal team dysfunctions, only later, to product failures, lost investments, lost customers, stretched time-to-value and time-to-market.

A glimpse of the journey you will take. Click to zoom in.

Hi, my name is Shehjar.

In 2009, I was having lunch with an investor visiting our development team at Gluster. “What should we focus on?”, I remember asking the investor. He replied, “Keep solving customer pain points.” A little confused, I sneaked out from lunch that day mulling just one question. Sure, I’d been solving customer pain points everyday as a software developer,  but how do I find customer pain points?

For over a decade since, my search for answers to this question took me on a journey of discovery. Whatever I’ve learned, now I bring to you in a structured format.