OLD WINE IN A NEW BOTTLE what I recall when encountered with jargon in the IT.
Gooooooooooooogled for the right lens, here is the essence I inferred.
Design Thinking focuses on solving complex problems in a highly user/human/people (empathy) centric way to deliver better product & services collaborating with multidisciplinary teams.
Hang On!!!
What were we doing thus far? Products were built for humans, right? is it fair to say we did not have them in mind? are we just coming up with another fancy name for what we were already doing? No offence intended please.
Now where is this stemming from?
Maybe be waterfall model kept most of the diverse team members disconnected from the BIG PICTURE. Those days (without doubts) boxed all of us to think only from the scope we were expose to. Now we have transitioned to Agile will it solve the problem?
Not really (in my opinion),
Unless there is a change in mind set. Most of us are still glued to our roles and want to have a say, thus often refrain from approaching the problem from multiple dimensions.
Hypocrisy at its best
Delivery team members are treated as order takers and not problem solvers, while every JD calls out, “We are looking for problem solving capabilities. Really?
Design Thinking in Action
Here is a very simple tool if you want to see Design Thinking in Action. Presentthe problem (with big picture) you are trying to solve, to all your team members (all functions) and “Go on Silent Mode “I mean (SHUT UP 😉) for a day or two and solicit thoughts.
You will see Design Thinking in actions. It costs nothing to try but lot to gain.
Most of us take pride in providing solutions along with problem statements.
This is not to question anybody’s solutioning capabilities, but to help your teams embrace, Design Thinking in easiest possible way. Interesting solutions come from unexpected quarter.
Coaching for Results is all about seeking solutions not providing one.
Cheers
Senthil Bellukutty