25 years of growing this method
Product & service design teams rarely get that sense of actually making things better for people. They feel trapped in endless cycles. Leaders wonder why the solutions don’t capture the market. Is it the method? Yes! Defining “user needs” from the lens of the solution is circular. It grazes the surface of knowledge you need. Quick data analysis invites bias. You need dimension instead of an “average user.” Problem space research lets you leap out of these traps.
My role is to provide the richest understanding of the people’s purposes and inner thinking, so that your discussion, decisions, and design can be based on a more accurate, inclusive foundation.
Supporting humans is more important than creating tools
Generating respect, dignity, and a sense of making progress in community with others–those are what lives are made of. And those are what get crushed in the rush to push technology forward. Those are what get crushed by the zeal for mega payouts. I’m a technologist, but not a solution-ist. I’m a systems person who loves that we can do so much with the internet and these tiny computers we carry around. But most apps feel harmful to me. The tool I reach for most often is deep listening. I’m one of those people molding our methods to a more human shape. I’m spreading the idea of paying attention to people. I’m helping you support humans, rather than simply create tools.
I give practitioners and leaders powerful mindsets and awareness. Depending on their own context, developers, product owners, designers, researchers, and leaders can adjust these mindsets and awareness to best work within their organization. This adjustment gives people the confidence that they need to lead, push, or pull their org into a more ethical, person-supporting frame of mind.
A method for supporting humans
Are you wondering how I came up with mental model diagrams, opportunity maps, and thinking styles? Find out about the genesis of the method
Research for ethical product design
We can’t go on solving things only based on our own thin understanding. Even if we have diverse teams (which is sadly rare), our ideas are based on our own experiences. Who speaks for everyone else out there who may think differently? It’s time to bring ethics to bear, in particular futures research (also called opportunity, foundational, or exploratory research).
It’s time to
- examine the risk of your assumptions
- create knowledge properly
- understand how confidence in data is achieved in the social sciences
“Woke” in the Technology Workplace
Right now in the technology world, broad representation of cultures, histories, and values among teams is rare. We’re working on improving this, actively seeking the people who have been excluded from chances others have access to.
Credits
- Website design & logo: Yousef Kazerooni
- Photos on page headings: Laurie B Photography
- Photo on Home page: Guillaume Coquoz
- Site coding: David Rodrigues
- App coding: Jorrit Poelen
Harness the power of deep understanding
When paired with big data trends, solution space research, design thinking, JTBD, lean UX, and agile methods, opportunity maps allow organizations to hold a wealth of data in one place. Thinking styles let you activate better support for far many more people.
You can make solutions that truly support different people as opposed to an “average” one-size-fits-all attempt. You can help your organizations realize they’ve not invested enough in understanding the problem space.
For the past two decades I have provided organizations with the knowledge to face the future with confidence and excitement that they can truly see people and support many different perspectives.
Advocate & Create Trust
Though at first daunting, it’s possible to help stakeholders shed years of assumptions, and trust the value of problem space research.
We are a solutions culture. Our first impulse is to come up with ways to fix things. Dropping this impulse for a moment, taking time to listen deeply, is the way to develop trust. With stakeholders, this means learning how they think, building your understanding of their concerns, and making them feel heard. Over time, you will have built their trust, which they will extend to you.
You can also develop trusting relationships with your peers at work. You can develop trust with customers. And best of all, you can develop trust with people who you’d never thought of before. With all this trust, with this deep knowledge, you can then turn on your fixing-things ideas.
Indi’s Bio
Indi is a researcher who coaches, writes, and teaches about inclusive product strategy. Her work is rooted in the problem space where the focus is on people, not users. Indi pioneered opportunity maps, mental model diagrams, and thinking styles. Her way of approaching the problem allows teams to truly pay attention to people, without letting cognitive bias and assumptions creep in. Indi has written two books, Practical Empathy and Mental Models. Her next book, Assumptions Aside, will cover thinking styles. She builds knowledge and community via a series of live online advanced courses about the importance of pushing the boundaries of your perspective. She was one of the founders of Adaptive Path, the pioneering UX agency. You can follow her on Twitter @indiyoung and access many resources on her website indiyoung.com as well as at medium.com/inclusive-software.
Indi’s Accomplishments
- Indi has spoken at 40+ conferences globally
- 2018: Indi begins building a series of live online training about listening skills, synthesis, creating mental model diagrams & thinking-style segments
- 2016: Indi narrated Practical Empathy for Audible
- 2015: Indi’s second book, Practical Empathy, was released
- 2008: Indi begins offering workshops to organizations
- 2008: Indi’s book Mental Models was published as the first Rosenfeld Media book, introducing the problem space research method to a wider audience
- 2006: Indi returns to freelance consulting, doing research studies for many clients
- 2001: Indi was a founding partner of Adaptive Path, the pioneering UX agency responsible for knowledge sharing via many channels
- 1996: Indi briefly works as a UX designer for Ikonic, and introduces problem space research to the directors, developers, and PMs there
- 1992: Indi begins freelance work, starting with apps in the PenPoint tablet (early handwriting recognition), and continuing through the Dot Com era
- 1989: Indi moves into interaction design, in Unix, during the Motif vs XToolkit+ competition
- 1987: Indi begins her career as a software engineer
- 1987: Indi starts her masters in Computer science at CSU Fort Collins, then quits because she wanted to push interaction design forward. (This was before any UX programs existed!)
- 1987: Indi gets her degree in Computer Science from Cal Poly San Luis Obispo