The four categories are the rational choice, the most likely to delight, the darling, and the long shot.
I want to learn more about these categories in detail
The four categories are the rational choice, the most likely to delight, the darling, and the long shot.
I want to learn more about these categories in detail
The Ideation room must have sufficient space for people to feel comfortable, but the atmosphere shouldn't be sterile, and team members shouldn't have to shout in order to be heard.
I wonder how this translates to a digital space rather than a physical one
This is really important and not something I would've thought about before, even though it sounds obvious, but not bringing those emotions into the room with you feels as important as not bringing biases with you
certain types of people might be more likely to be included than others, skewing results.
white, college educated, male, able-bodied, etc.
They help people move along with their lives without getting bogged down thinking about the meaning of every interaction or event.
I like that the article explains why we have biases when making cursory decisions and the cognitive reasons for why we have them before diving into how to fight against them
Doing so sometimes helps you to see significant patterns in the data clearly and derive breakthrough insights.
I really like the that stepping away and taking a break and looking at the coding process through fresh eyes is embedded into the step process.
Give each member a transcript or one field- or diary-study entry. Tell people to highlight anything they think is important.
I've never seen this before! It seems like it would be such a useful exercise in seeing what multiple people pick up on and the differences they notice based on background, prior experience, and personality
Read all your transcripts, field notes, and other data sources before analyzing them.
Curious about insights you might receive differently after processing the interview or interactions in the data you might have picked up on after the fact
Coding refers to the process of labeling segments of text with the appropriate codes.
I did this in my psychology lab! It makes sense that user research and psychology surveys would share a lot of commonalities
he analysis simply becomes a regurgitation of what participants’ may have said or done, without any analytical thinking applied to it.
this is so interesting! Something I've never thought about before
studies that are qualitative in nature generate data about behaviors or attitudes based on observing or hearing them directly, whereas in quantitative studies, the data about the behavior or attitudes in question are gathered indirectly, through a measurement or an instrument such as a survey or an analytics tool.
I've never heard this distinction made before and its really helpful
measure how well
What are questions we can ask to get the richest data/best results?
Do users understand how it works?How do users interact with your prototype?Can users find what they are looking for?Do the features look and feel right?
Does the design feel intuitive? Do you want to return to the space and to wander around? https://newpublic.substack.com/p/-from-street-cafes-to-sacred-sites
wireframes
"a simple diagram that represents the skeleton of a website or an application's user interface (UI) and core functionality."
While user research informs design, it doesn’t immediately provide solutions to problems.
This feels very important to note that theorizing and interviewing around the problem doesn't solve the pain point itself, and is just the beginning in the process of systematizing a framework for a solution
When you get your team on your side, it makes the process of building a product together with a smoother one where there is less room for conflicts and misunderstandings further down the line.
This is an interesting addition to the conversation about healthy conflict--also being able to mitigate that conflict
No ‘one size fits all’ approach
love this
What happens if you don’t do user research?
This question is so interesting! So excited to learn more
Before seeking new design solutions, we look for what is already working at the community level.
I love this point about acknowledging what is already working, and creating systems that protect it
We view change as emergent from an accountable, accessible, and collaborative process, rather than as a point at the end of a process.*
I really really love the phrasing of this--especially change as an accountable, accessible, and collaborative process. I think a lot of the time, the idea of iteration and prototyping seem tedious for organizations or exhausting, and this point speaks to how necessary this collaboration is, and how important it is to be understood by everyone involved, but most directly those in the community
the personal history and trauma of each actor must be considered while integrating healing practices within the process.
I really love this emphasis on design as a part of the process of healing, and understanding the experience of collective trauma within the community. I'd also love to explore here what could also be the potential conflict in having someone outside of the community design for it, i.e., what savior complex, etc.
sketching, storyboarding, wireframing, and construction/building.
Excited to learn more about this tools!
Testing and learning should continue throughout the lifecycle of the project.
I like the emphasis on this process being iterative, and emphasizing that community members might discover new use cases that you hadn't thought of or problems you hadn't foreseen, and being humble enough to step back and realize they know more in this particular area than you do
It’s not enough to build empathy - we also have to acknowledge what we know we don’t know (and what we don’t know, we don’t know).
This reminds me of what we were talking about yesterday with acknowledging young people may know more about specific technologies and, of course, more about their lived experience we do. It feels like it has so much more to do with creating something with the user and not just for them.
who is invited to decision-making tables
This is a huge point in that it touches on what feels like a true problem to solve within the design space--it's not just that community members voices, especially marginalized community members, is that they often aren't even present when decisions about the design are being made (ex: facial recognition software that can't read non-white faces)