The "design thinking is dead" narrative is everywhere (as always), but we're missing something fundamental about how this framework actually works. Real design thinking means moving fluidly between observational research with actual users, visual sense-making that helps teams process complex information, and iterative design that responds to what you learn. It's about building organizational capacity for user-centered problem-solving, not checking boxes on a predetermined path. So how do you actually apply this cyclical mindset? Our Design Thinking Study Guide breaks down each phase (Empathize, Define, Ideate, Prototype, Test, Implement) with practical advice. From empathy mapping that builds genuine team alignment on user understanding to ideation methodologies that expand your solution space, plus prototyping approaches like the Goldilocks Principle that generate honest user reactions. The framework isn't dead—but the application of it is often misunderstood. Dive deeper into design thinking: https://bit.ly/3THktvc Or join one of our instructors in a hands-on live online course to better integrate the design thinking mindset into your UX work: https://bit.ly/47GWLoE #DesignThinking #UXDesign #UserResearch #NNG #NNGroup #ProductDesign
Thank you for such a thoughtful and comprehensive article! I completely agree — design thinking can’t really be “dead.” It’s a fundamental mindset and process behind creating any meaningful product or solution. Perhaps what people mean is that we should move beyond treating it as a set of checkboxes and start embracing it as a true way of thinking.
Much needed look at the fundamentals of Design. In the age of AI, Design Thinking is more relevant than ever with its human centered approach. Core principles will remain the same while AI augments this.
Great article, I saved to my bookmarks. (even I'm not a product designer) Thank you very much, Kelsey !
Utah Valley University•2K followers
5moAgree, and the UX community is to blame for the misapplication of the design paradigm and the havoc it has wreaked on our community. I always go back to my Rapid Prototyping Model I created during my graduate degree as it took off from the cascade model commonly used at that time and built an early version of Agile, which is also misapplied often, too. This model above is still missing two items in the process that I had in my model from 1998...Define with Stake Holders is well before the cycle begins, and at the end of the cycle, there needs to be a release of the product showing a termination of tasks for product deployment. Once released, though, the intermediary between Release and Define, brings the product life cycle to a new state of versioning. This example is not complete and reiterates the problem.