3 ms·
Yeah... an acid test for these things is often, "what are you telling me not to do?" In my encounters with design thinking, the controversial "don't" has actua
by evrydayhustling 8y ago
Yeah... an acid test for these things is often, "what are you telling me not to do?"
In my encounters with design thinking, the controversial "don't" has actually been frequent, iterative release. For some folks, design thinking is a defense of a "measure twice, cut once" waterfall-y approach to product development.
That might make a lot of sense for some things, like physical consumer products, where a ton of branding and manufacturing go into each release. I think it's a bad idea for most software, where the ease of distribution means that you can learn from your market much more dynamically.
- AndyNemmity 8y agoThe times I've been a part of it, it's been in time boxed proof of concept situations where you're outlining a customer's desire, and then coming up with solutions for it, then delivering on them with an iterative process. It's worked out better than any other process I've been apart of, but it may just be some other factor than it's value. The companies that were open and interested in using it, were often... of a generally higher quality of talent, and perhaps better outcomes is natural no matter what process is used.