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.
Many teams are built around these core roles and all need to have their seat at the table. But how do you ensure the relationship thrives? Do you take a specific approach?
I know it sounds simple stupid, but believe me, it actually works. In my experience, involving the whole team in discussing the problem and doing a quick brainstorm about possible solutions in the early inception phase helps a lot.
This could be treated as a nice little project kickoff where everyone gets familiar with the team's focus and the next challenge coming.
On my team at Government Digital Service, we have 'fika' each afternoon. It's Swedish for 'a coffee and cake break'. We take 15 minutes to chill out as a team, connect with each other, and clear our heads for the final onslaught of the day. We have a hard rule that no one talks shop during fika; instead, we chat about life outside work and what we like getting up to, our interests and qualities.
When you're working on tough stories or complicated infrastructure, empathy and patience are paramount. Fika helps propagate that.It's caused us to gel more as a team, brought us much closer together and means we see the humans behind the job roles – as if we were a family.
Don't have meetings for meetings sake, but do make sure your team communicate. All too often I have worked in teams where a direct question to another team member would have resolved an issue a lot quicker than the individual trying to resolve problems in isolation - your team are there to help, make the most of the extra brain power. You should never be made to feel like you are asking a stupid question, especially if you are seeking the advice of another discipline. In my experience the best teams are ones that will take the time to involve the right people at the right time.
Morning stand ups are important, they involve the whole team and help identify who is working on what and identify the top level issues that need to be addressed. I cannot recommend these enough, but make sure they are short. Longer conversations should take place between the relevant people after the stand up.