@John238 Thanks for your comments and views -- appreciate your taking time to share them.
While each of your points may be valid, there is an underlying problem when taking them as a whole, in my view. The basic reality is that coordinating a team (including project participants, technical resources, and business stakeholders) is the key challenge for achieving success. Design thinking offers an approach to align all the players while maintaining a discerning view toward various assumptions and goals.
Projects fail because participants are self-serving, try to game the system for their own gain, are confused and inexperienced, and so on. While no system can completely stop this behavior, especially on large projects, design thinking at least makes a serious effort. In my experience, serious attempts to align participants will pay dividends.
On the other hand, if no one involved in the project really cares about the outcome, then why bother to fix anything? In that case, the entire project becomes little more than a political shooting match where everyone is out for themselves. While it's easy to find examples of those projects, I am personally more interested in folks who are trying to do the right thing.
Although you are correct in suggesting that design thinking is not a panacea to solve all problems, it does offer a genuine step in the right direction. Design thinking offers a worthwhile view that is highly consistent with my own perspective on IT success and failure. That's why I invited Chirag to write this post.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
