Gunjan Doshi

I do assessments on the resources and capabilities of product development organizations. Usually, I follow the following 3 steps

1. GAP analysis, followed by
2. Root-cause analysis and then
3. Suggest core recommendations.

Nowadays, as a result of practicing Appreciative Inquiry, I get lot of insights that I would have usually missed. I have not completely given up the old approach but am trying to apply the best of both worlds.

For example, at a recent client assessment, I asked a QA analyst, “tell me of the time when things just clicked and you were very happy”. The answer I received was simple but filled with wisdom.

“when code is working as expected, that is hurray for me. Other days are struggle“.

It was again a reminder that all practices and processes are just a means to an end but not the end.

We then centered our discussion on this quote and talked more about practices that worked during those times. We then touched on how and why we had digressed away and how we could come back to the roots. Other benefit of appreciative inquiry is that it also keeps the discussion positive and engaging.

I was first referred to Appreciative Inquiry by Cynthia Andres and Kent Beck. It seems like an art at first but you really start enjoying it - the moreyou practice it.

Tags: No Comments