4 ms·
The irony ... in order to solve for the stakeholder’s assumed problem statement, the advice was to avoid assumptions...all assumptions, I assume, except the ass
by cgio 7y ago
The irony ... in order to solve for the stakeholder’s assumed problem statement, the advice was to avoid assumptions...all assumptions, I assume, except the assumptions of the report.
From the article
> They prototyped and tested solutions to municipal problems. Finally, in collaboration with the Blue Ribbon Committee, the IDEO team published a report. It aimed to address the problem—an absence of “competitiveness” for new business and talent—that Mayor Braddy had diagnosed.
And further down the article from the report itself:
> (“Instead of assuming,” for instance, “that the right answer to dealing with trees cut as a result of development is a policy to limit the amount of trees that can be cut, why not ask the question, ‘How can we maintain a desirable degree of shade and tree coverage as part of Gainesville’s overall design?’”)
- meristem 7y agoFrom a human factors engineering POV, this is straight usability research. Instead of assumptions, use observations and interviews— then form problem statements. Instead of a single solution, form ‘how’ statements about intent. In Product Management parlance: speak in terms of problems, not solutions. The design cycle then moves to create product/refine product.
- cgio 7y agoDon’t disagree. It reads like they didn’t eat their dog food though.