I came here to write this, and also to say that on a software team, for example, where the problem is complex, no one person may have a well rounded enough or deep enough grasp of the problem, goals, limitations, etc. to come up with an optimal solution on their own. This is why we have businesses in the first place, to organize teams in a greater-than-the-sum-of-its-parts kind of way. A very basic example of this might be a UI designer coming up with a number of potential interface ideas for a particular problem users are experiencing, and an engineering choosing the design which will cost the least dev hours. Iterating on sketches of such potential solutions will almost certainly get to a better solution than the designer just making a choice their own favorite design and lobbing it over the wall to eng.Not to dismiss the psychological safety point the article makes, which i believe is very valid.
keithnz|4 years ago
fsloth|4 years ago
Brainstorming tries to achieve an unstructured creative session whereas engineering teams are trying to flesh out a structured plan to a complex problem.
Not all whiteboarding in a group is brainstorming. The former usually results in tremendous added value while with the latter I agree it's mostly pointless.
theIntuitionist|4 years ago
theIntuitionist|4 years ago