Hot Tips is a collection of candid advice by and for product people.
Found a great new way to build your roadmap? Got an awesome design or research tool you can’t live without? Unearthed the holy grail of prioritisation techniques?
Tell the JAM community! Sharing a Hot Tip is the best, fastest way to pay it forward to +3,000 makers from all over Europe. Your daily grind might be their ‘aha moment’!
Think of it as a precious piece of advice you wish you had received when you started building products. It’s a short snippet of wisdom that helps you do things differently. With Hot Tips, we hope to show there’s no ‘one best way’ and it’s ok!
📖 Be as open as you can. Share your insider knowledge. Something people won’t have come across before. A Hot Tip reveals how you do things.
🎨 Show, don’t (just) tell! Talking about your roadmapping process? How about including a screenshot of the tool you use? There’s nothing like seeing your ‘behind-the-scenes’.
💌 Keep it short and personal. Aim for 200 words max, and word it like you’re helping a friend out.
Every week, we’ll curate the best Hot Tips and share them with the community.
You're in discovery and searching for the problems you need to solve. Who do you speak to? Where do you find your potential users? And what questions do you ask to get the insights you need?
Before you can run a great user interview, you need to establish your research goals. What do you need to learn about, and why? Look at your analytics, any past user research, and any knowledge about your customers from other teams around the business. What do you know about your customers already? Where are your knowledge gaps? Are there any assumptions you’re making that you haven’t tested yet?
I like to do this as a workshop. I ask my product team, plus representatives from other departments, to come armed with customer knowledge and data. We sketch a map of our customers’ journey, then add post its showing what we know, and what parts we have questions about. Doing this in a group helps us pool our knowledge and surface questions we might have missed.
After capturing all our questions, we group them into themes, look back at our product vision, and decide what big research questions we need to answer first to get there. For each, we ask, “What’s the best way to answer this?” Questions about customer attitudes or the ‘why’ behind something are best answered through exploratory interviews; questions about what people are doing are best answered through analytics; and questions about new features are best answered through lean prototypes and demand tests.
My best tips are all in the What Customers Want book, but essentially the most important questions are:
You don't need anything else except to write down what they say in a way that summarises what they are trying to increase, decrease, or feel.
Never, ever, ever, run 'focus groups'. They're a nightmare to coordinate, and one loud person will lead the opinions of everyone else.