Hi both
Good stuff 
First, let me add to the Eames-video with this short by clothing designer Ken Sakata and his conversation with Claire Waight Keller creative director at UNIQLO. Where they discuss the importance of ârestrictionsâ (what Eames calls constraints): Ken Sakata (@frontofficeco): "How do you design with limited time or money? With Clare Waight Keller, creative director of Uniqlo"
Secondly itâs really hard to distinguish between needs and wants. But very importantly: they are not interchangeable concepts. People are motivated by their needs, but want/use tools to achieve them (that is why we call them âusersâ).
A need emerges in a given situation. âSituationsâ are an important concept because a). itâs a vastly better way to frame why people are doing what they are doing, and b). it broadens our perspective when we are looking for âconstraintsâ and influences that have an effect on what people want, what success looks like and how we can get them there.
Given the two frameworks above I would offer a challenge and a simple question:
Do we want to help people make sense of something or categorize something?
What this means is that if we are trying to make sense of something we let the data lead the way and help us find and shape the framework = âdata precedes frameworkâ (Dave Snowden)
While if we are trying to categorize something we create the framework and then ask people to fill in the data = framework precedes data
Iâm personally much more focused on helping organizations make sense of emerging markets, compared to categorizing and solve complicated problems.