Hot Tips is a constantly growing, curated collection of candid advice by and for product people.
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.
Contributing a Hot Tip it the fastest way to reach 3,000+ makers from all over Europe. Your daily grind might be their ‘aha moment’!
1. Write your Tip following the guidelines below.👇
2. Submit the Tip through Typeform.
3. Wait patiently! The Tip will undergo some scrutiny by our Hot Tip Catcher, who will then decide whether to publish it (we may tweak the content for clarity).
4. Watch out! Every week we’ll pick the best Hot Tips and share them with the community in the JAM newsletter. Look out for yours! 👀
Your Tip can belong to one of the three categories.
📖 Be as open as you can: share 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 better than 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.
🔧 Share tools: offer readers an opportunity to explore the topic. Link to at least one helpful ebook or article that helped you in the past.
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.