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.
Lead from a position of influence not authority. But how do you get there? And how do you get people on board and manage those different stakeholder expectations?
Over-communication is a one word answer here. A PM must ensure everyone is chummy like your family at a wedding party, including grandma and the vegan cousin Arlo.
Let’s break it down to three hippie principles.
Products change quickly. Make sure everyone is on the same page regarding decisions relevant to them.
A PM needs to be a people’s person. Clear communication is a prerequisite, but even more important is to speak with each stakeholder in their own language.
Explaining design restrictions to engineers is different from describing the benefits of new features to sales. One size doesn’t fit all. Grandma wants a steak, cousin Arlo a quinoa salad.
It can be easy to get full of yourself as a PM. You might start identifying as the owner of the product, and the one true “decision maker”.
You are not the product. You serve the product. You are a facilitator of effective creation.
Along with the product vision your mantra as a PM is “get over yourself”. Yup, no one said it would be easy.
If you are communicating up to C-level in an email, format it so it can be easily read on a mobile and put any vital information in the main text, rather than putting 'see attachment'.
If your exec team is anything like ours, they spend most of their time on their phone rather than at a desk or on a laptop, so may not easily be able to view slide decks and spreadsheets. Don't forget to check it's all good by emailing it to your mobile first!
If you have a clear message, it is impossible to over-communicate with business partners outside your direct team. Get your vision set, explain how you are going to get there, and what is happening next. Repeat. Over and over again. If they start to get bored of what you are saying, you know the message is being absorbed.
Most stakeholders tend to focus on business needs and goals.
So when you present ideas, don't get lost in design details and highlight how your product delivers on these goals first.
Show, don't tell! Use tools such as Abstract, Sketch and Invision to create working prototypes that demonstrate a realistic end product. Where possible, record and edit user tests to help them visualise how the product is being used (just don't make them too long!).
When communicating to people outside of your offices, make sure you take the time to explain things over a call. The enthusiasm you have for your product can get lost in an email or a prototype.
It all comes down to communication. Stakeholders are often removed from the product or design process. You're heads down, making hundreds of decisions every day. So it's your role to bring the right information to people... at the right time. Take a step back and ask yourself: what do they need to know and when? Sharing too much information with busy senior people can be counterproductive, so be selective.
In 'Articulating Design Decisions', Tom Greever says: "If we really expect to communicate effectively with our stakeholders, we need to use the same skills with them that we use in identifying with our users".
For example, you can write Stakeholder Stories. They follow the same format as your user stories but focus on the people you work with. Here are stories you might come up with:
Stakeholder stories can help you pinpoint people's motivations. With these in mind, it's easier to adapt your communication style and share information on what matters to them.