I practiced Design Thinking at IDEO for 10 years, and I can assure you it's not "one size fits all." And you can onboard an intern or a client CEO in days, without requiring them to internalize a very abstract system for decomposing problems.

▲

gond 4 hours ago | parent [-]

>I practiced Design Thinking at IDEO for 10 years

That may possibly explain your motivation but even ten years do not make it right, nor the speed of teaching.

You are saying it yourself: internalising the very abstract system for decomposing and adapting it has a value of its own you cannot replicate by pre-solving it. The spinning-off of Design Thinking only accomplished further segmentation of a space which was already too fractured and was a disservice to the field.

I don’t think we will approach a consensus here, and that’s fine.

	▲	turnsout 4 hours ago \| parent [-]
		It's always valuable to have a generalizable skill. But design is fundamentally a craft; an applied art. It's problem-solving. And like any craft, there are tools and techniques that are tried and true. You could approach woodworking with a ground-up Systems Thinking approach, but would you turn down the advice of a carpenter with 30 years of experience? Technically all you need to understand woodworking is a physics textbook and maybe an organic chemistry textbook. My guess is you're a software developer (as I am), and in my opinion the fatal flaw of our group is the incorrect belief that we could do anything or solve any problem by simply decomposing it into smaller and smaller components. The thing is, for a big enough problem, there are an almost infinite number of ways to break it down and then build it back up. In optimization terms, complex projects are highly nonlinear problems, so you may be able to understand what the inputs are, but it sometimes takes wisdom and experience to tune the parameters.