“We know exactly what our users need.”
“Our product solves a problem we have.”
“My sister told me she’d definitely pay for my app.”
“Why do people sign up, then not use our product?”
In many conversations I have had with startup founders and product owners in the past year, I heard very confident individuals who ask themselves great questions about their users. I learned they are answering these questions in unreliable and invalid ways. Most people who are involved in product development don’t do any user research. When they think they do, they are doing it wrong.
Many product developers skip user research completely because they perceive it as a burden, something that is only suitable for academia, costs a lot of money, takes a lot of time, and requires hiring a costly consultant. Others, affected by the Lean Startup movement, think user research means A/B testing.
Lean User Research is going to change these perceptions.
I’m excited to announce a book which will provide knowledge, tools, and techniques for running basic research people can complete quickly on their own. It is not going to be about the “right”, robust, heavy research methods, but about small-scale, good-enough practices for better informing design and product decisions.
The book is targeted at:
- People involved in product development – designers, developers, engineers, product managers, startup founders, entrepreneurs, and intrapreneurs.
- C-level executives who wish their organizations improve how they learn from users or customers.
- Newcomers to the UX world.
- International audiences who struggle with reliable, accessible resources about lean user research techniques.
The book will introduce 9 questions people who participate in product development ask about their audience. Each book chapter will provide step-by-step instructions on how to answer a question with lean user research techniques.
The book will be published in 2015. Until then, I will share snippets and other relevant materials on this website. Please join me in this exciting journey. I can’t wait to hear about your expectations and, later on, feedback.
Leave a Reply