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.
When do you choose 1:1 meetings as opposed to team meetings? What's their role, and how do you make sure they achieve the intended result?
First, take the individual out of the day-to-day. Find a quiet corner and sit down with a coffee. Remove the person (and the conversation) from the immediate work environment. This is about them.
Second, start with them. A simple How are you doing? is a great starting point and gives you valuable information about how they're feeling and what may be bothering them. Be prepared for this to not just be about work.
Only then get onto tasks. What's going well? What's going wrong?. Get updates on any actions from your previous catch-up.
Your role here is to support and enable. How can I help? is a super simple, but effective question to ask. Wrap-up by summarising next steps and actions — both for them and for you.
One-on-ones might seem like a waste of time. After the product mission and vision are defined, shouldn't people “just know” what to do?
No. It’s your role to keep the product machine rolling.
You’re like the ball bearings that make the wheels turn. You need to make sure each wheel—each person—is operating in an efficient way. You remove unnecessary friction, provide enough support and oil to prevent breakdowns.
One-to-one meetings take a lot of time. But, in several cases they are worth it—they bring exponential returns. Here are three top goals of your one-on-ones and key principles to employ in each.
Set specific goals for each team member to make it easier for them to take pride in their achievements.
Accountability. Strong accountability culture is one of the characteristics that makes your team antifragile. But, different people respond better to different forms of accountability. Some prefer to set OKRs, others use Habit RPG, others want be measured by specific metrics—for example time taken to resolve a customer support ticket. Find out what works for each person.
Autonomy. While deliverables are important, you don’t want to micromanage. Make it clear where you leave your team members autonomy to experiment. Showing trust this way will lead to creative solutions and greater job satisfaction.
Keep track of team's performance.