Products of Music (@productsofmusic) header
Products of Music (@productsofmusic) profile picture

Get the full story on what makes a great music technology product, with 1 to 1 conversations from leading voices and rising stars.

London, UK
Joined April 2023
Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)Photo by Products of Music (@productsofmusic)
Products of Music retweeted
This has gotta be on one of my favorite podcasts I've ever participated in. Adam had some really great questions and we covered a lot of ground that I've never gotten into before. Thx for the great convo @productsofmusic! youtu.be/pTKX8kSsQsw?si=p3xJ…
2
6
1,412
Products of Music retweeted
Code your Dream Project with AI Use tools like: - Cursor to code complex projects. - bolt, lovable to code websites, micro SaaS. - v0 lovable to code frontend screens Step by Step Guide to code your first software with AI: (Bookmark this for future use)
28
104
4
968
132,568
Products of Music retweeted
Sharing my secret sauce for producing great #podcast audio here: youtu.be/A5JTZ6DdorU?si=UO3r…
1
1
3
63
Products of Music retweeted
A lot of non-technical product managers and marketers use software like Google Analytics or Appsflyer that collect data and shows basic dashboards to make decisions. Unfortunately, this data ends up siloed because all the various SaaS tools companies use don't talk to each other. I spoke with @adamjwakeling about this problem and how we built @datawisp to solve it.
1
6
12
716
Products of Music retweeted
As a PM, your main goal is maximizing customer value. But many a few know how to prioritize ideas with ease. There are two popular ways of doing this. Here's everything you need to know: (1/17)
2
27
1
208
41,062
Products of Music retweeted
I started my career in #magazine publishing, and I love this concept of 'finishability'. I think it is one of the key unique differentiators that separates it from a typical web experience, or the endless scroll approach of social media platforms.
1
1
3
96
Products of Music retweeted
Why is a motivated product team crucial? If you're interested in learning about the benefits of motivated product teams, be sure to check out our blog post on this topic bit.ly/3SgjnWQ #productmanagement #productmanagers
1
3
786
Products of Music retweeted
How do you do move activation? Break it down in to setup, aha, and habit: Here's what those mean. • Setup: Users setup the feature so they can use it • Aha: Users achieve the magic moment • Habit: Users make the magic moment a habit Let's contextualize that with the Facebook example. • Setup: Upload contacts • Aha: 1 friend in 7 days • Habit: 7 friends in 10 days Activation is then the the measurement of the rate of users the product team can get to these setup, aha, and habit metrics over a certain timeframe. -- Activation is Hard! Activation is one of the hardest things to move in product. Numerous product teams have floundered in moving the metric. If we could all suddenly just get users to do what we want, we wouldn’t need activation teams, after all. 3 factors make activation harder than many other product problems: 1. Your typical constraint is the core product functionality remaining the same 2. It’s role in retention means that it has an outsized “Eye of Sauron” 3. As more people use a technique, its effectiveness is diminished; and, most the techniques are not rocket science -- That's why breaking it into steps and moving those steps is generally the preferred approach.
4
17
1
104
17,074
Products of Music retweeted
Everyone in your company has an different opinion on how your product grows. And it's a problem. I know - this doesn't seem like the worst thing in the world. Everyone has their own view of how the product grows, and they help spin that part of the flywheel, right? Not so fast: -- The problem this creates is disagreement on what to fund. What seems like a straightforward initiative to one person may make absolutely no sense in someone else's mental model. -- Take the example of spending more on marketing. Your marketer may see awesome AARRR metrics, great LTV/CAC, fast payback period... and conclude we should spend more. On the other hand, your PM, focused on setup, aha, and habit rates might find that totally irrelevant. And your CEO, focused on sales-led growth and retention, may find it a small driver of the sales motion. As a result, no one agrees, and the spend isn't funded. Your marketer thinks everyone else is an idiot but continues on, ready to "disagree and commit." Is this really the ideal scenario? -- Or - take the example of product experiments to improve aha rates. Your PM sees the leverage easily in their mental concept: increase aha rates, increase retention, and make revenue go up exponentially. On the other hand, your engineer, focused on latency and response rates, may not see it as important at all. And your designer, focused on the easiest to use product, has no ideas why you would inject dark patterns and modals into the product. The result is no one can agree on what to build. Your PM gets pushes forward what they think - but behind closed doors, not everyone agrees. It's not ideal. -- So what's the answer? Build a quantitative growth model. A detailed quantitative model can give the different parties in the company a holistic view of what actually drives growth. This makes debates over what to build much simpler. Instead of ships sailing past each other in the ocean, you can have a reasoned debate on what will drive growth.
3
16
66
28,246
Products of Music retweeted
"They drew on outside experiences and analogies to interrupt their inclination toward a previous solution that may no longer work. Their skill was in avoiding the same old patterns... With ill-defined challenges and few rigid rules, range can be a life hack." David Epstein, Range
1
3
127
Products of Music retweeted
Be careful. Most "products" are, in fact, projects. 9 red flags (and how it should work): 1. Large PRD: You start an initiative by documenting everything. 2. Feature factory: You implement the requirements. "Why" is irrelevant. 3. Waterfall: All the requirements are collected in the "initial phase." 4. Gantt roadmap: A time-based, feature-based roadmap. 5. No discovery: No need to validate ideas before implementing them. 6. No designer: There is no Product Designer on the team. 7. No analytics: You have no idea how people use your product. 8. Customer in charge: Powerful customer(s) make all the decisions. 9. No strategy: You try to maximize sales by satisfying all customers and grasping every opportunity. - Here is a better way: 1. Your cross-functional team is empowered to solve the problems. 2. PM, Product Designer, and Lead Engineer perform Product Discovery together. Continuously. 3. You have an outcome-based roadmap. Preferably Now-Next-Later. 4. If you commit to a date, you do it rarely and only after the discovery. Never commit too early. 5. Manage the value, usability, feasibility, and viability risks by experimenting. 6. Test the riskiest assumptions before the implementation. 7. Choosing, instrumenting, and tracking the right metrics is key. 8. Ship incrementally, measure the outcomes, and learn from it. 9. Tradeoffs are essential. What you do, but also what you don't. Respect your market and the unique value proposition. - And if your product hasn't been launched yet: 1. Discover the market and define a unique value proposition, business model, initial vision, and strategy. 2. Test your idea with minimal effort. Before the implementation. 3. Define the go-to-market strategy and validate key assumptions. 4. You can't rely on product analytics. Talk to the customers and collect data from experiments. 5. The Product Trio performs the Initial Product Discovery, just like in Continuous Product Discovery. You need a Product Designer and Lead Engineer. 6. Once you ship, leverage product analytics and apply Continuous Product Discovery. - Hope that helps. What are your thoughts? ----- P.S. If you liked this, subscribe to my newsletter to get 1 actionable tip for PMs every Saturday. The link is under my profile: @PawelHuryn
7
48
1
269
40,252
Products of Music retweeted
YouTube is a free university for PMs. But it's tough to cut through the noise. Top 9 PM channels you'd be crazy to miss: 🧵
1
23
2
176
29,309
Products of Music retweeted
What do people think of jump cuts while watching someone talk on YouTube? (particularly on longer form video podcasts) #videoediting
67%I can't stand them
0%I don't mind/like them
33%I am indifferent to them
0%What's a jump cut?
3 votes • Final results
1
1
4
112
Products of Music retweeted
It's now common to see 100+ PMs applying for a single position. According to Glassdoor: - Corporate job postings typically receive 250 resumes - From these, only 4-6 candidates get an interview invitation Recently, I re-evaluated my career path. In just the second week, I received 13 interview invitations (9 from job postings, 4 from my network) and canceled 80% of the processes. And ultimately accepted a Senior PM position in a company I loved. Here are 7 techniques everyone should know: 1. Network to explore the hidden job market According to TheBalance, 60% of job opportunities aren't posted online but are found through networking. If you don't want to post on social media, try this: - Research and follow potential future companies - Find and follow their employees on LinkedIn - Engage with their posts and comments - After building rapport, invite them to connect 2. Be proactive. Don’t be afraid of rejection. Relying just on standard application forms and procedures is a mistake. After sending your application, contact the hiring team and let them know you applied. Ask questions that demonstrate you've done research and are interested in this position. They might consider your application faster. Reach out to them again after 2-3 days and ask whether they have any questions. “You are happy to answer them.” 3. Strive for feedback Often, rejections come without feedback. Unless you seek it. Acknowledge the decision, express gratitude, and: - Politely ask about areas for improvement - If no response, a couple of reminders could help While it pushes your comfort boundaries, learning from rejections is crucial. 4. ATS optimize resume According to TopResume, 75% of resumes are rejected before a human can see them, primarily due to the use of an applicant tracking system (ATS). I validated my resume with ResumeReworded until it received a score of 100/100 (I'm not affiliated with any of the companies from this post). 5. Write a cover letter. It's not optional. Not attaching a cover letter sends a strong, negative signal. The more personal, honest, and based on research the cover letter is, the better. It should prove your experience and demonstrate your passion, curiosity, and genuine interest. 6. Optimize your LinkedIn profile According to TopResume, 54 percent of employers have rejected candidates based on their social media profiles. Adjust your headline and about sections. Align your experience with bullet points from your resume. If you don't have a high-quality headshot photo, check @aragon_ai 7. (Advanced) A/B test your resume I tested my resume by sending links with analytics enabled instead of PDFs. Key insights: - The professional summary and initial 2-3 jobs are crucial - Contrary to belief, people do read the resume's second page - Contrary to belief, certificates do matter Hope that helps. P.S. You can read more about those techniques by reading my new Substack post. The link is under my profile: @PawelHuryn
3
16
143
34,295
Products of Music retweeted
Some of my favourite #ProductManagement books so far. What are some of your recommendations? Book Details below ⬇️
2
5
30
1,291
Products of Music retweeted
Prototypes are the most powerful way to validate product ideas. Here's a complete breakdown of 10 ways to validate your prototypes + save yourself from wasting weeks of time:
1
18
134
12,090
Products of Music retweeted
Many companies are on the escalator from PLG -> PLS -> Enterprise Sales. Is it possible to go in reverse? I don't think so. @ElenaVerna, @far33d and I discuss. This is from the latest episode of Unsolicited Feedback where we break down product strategies and give outside critiques. Full episode in the thread. My opinion is no, it's not possible to go Enterprise -> PLS -> PLG. There are a few reasons for this: ➕➖Adding Is Much Easier Than Simplifying➕➖ When you start in the enterprise you spend more of your limited resources serving the buyer vs the end user. This inherently adds complexity to the product. It is much harder to go from a complex product to a simple product vs starting with a simple product and adding to it over time. ✂️💵Cutting Prices Is Harder Than Raising Prices ✂️💵 To move down market and enable PLG you have to build cheaper versions of your product. The problem is that internal struggles always result. What if the cheaper product cannibalizes the more expensive version? How do I comp salespeople on this? etc, etc. The internal friction tends to be too much. 🧬 Company DNA 🧬 Starting in the enterprise you build a very specific operating cadence and DNA around the sales cycles of enterprise deals. This flows through everything including how you ship products. The shipping cadence, risk tolerance, and focus areas of enterprise products are very different. @ElenaVerna provides a couple of possible exceptions to the above in the clip.
3
1
1
13
3,103
Products of Music retweeted
It’s easy as a PM to only focus on the upside. But you'll notice: more experienced PMs actually spend more time on the downside. The reason is simple: The more time you’ve spent in Product Management, the more times you’ve been burned. The team releases “the” feature that was supposed to change everything for the product - and everything remains the same. When you reach this stage, product management becomes less about figuring out what new feature could deliver great value, and more about de-risking the choices you have made to deliver the needed impact. -- To do this systematically, I recommend considering Marty Cagan's classical 4 Risks. 𝟭. 𝗩𝗮𝗹𝘂𝗲 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗦𝗼𝘂𝗹 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 Remember Juicero? They built a $400 Wi-Fi-enabled juicer, only to discover that their value proposition wasn’t compelling. Customers could just as easily squeeze the juice packs with their hands. A hard lesson in value risk. Value Risk asks whether customers care enough to open their wallets or devote their time. It’s the soul of your product. If you can’t be match how much they value their money or time, you’re toast. 𝟮. 𝗨𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗨𝘀𝗲𝗿’𝘀 𝗟𝗲𝗻𝘀 Usability Risk isn't about if customers find value; it's about whether they can even get to that value. Can they navigate your product without wanting to throw their device out the window? Google Glass failed not because of value but usability. People didn’t want to wear something perceived as geeky, or that invaded privacy. Google Glass was a usability nightmare that never got its day in the sun. 𝟯. 𝗙𝗲𝗮𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗔𝗿𝘁 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗼𝘀𝘀𝗶𝗯𝗹𝗲 Feasibility Risk takes a different angle. It's not about the market or the user; it's about you. Can you and your team actually build what you’ve dreamed up? Theranos promised the moon but couldn't deliver. It claimed its technology could run extensive tests with a single drop of blood. The reality? It was scientifically impossible with their tech. They ignored feasibility risk and paid the price. 𝟰. 𝗩𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗠𝘂𝗹𝘁𝗶-𝗗𝗶𝗺𝗲𝗻𝘀𝗶𝗼𝗻𝗮𝗹 𝗖𝗵𝗲𝘀𝘀 𝗚𝗮𝗺𝗲 (Business) Viability Risk is the "grandmaster" of risks. It asks: Does this product make sense within the broader context of your business? Take Kodak for example. They actually invented the digital camera but failed to adapt their business model to this disruptive technology. They held back due to fear it would cannibalize their film business. -- This systematic approach is the best way I have found to help de-risk big launches. How do you like to de-risk?
13
59
6
356
79,575
Products of Music retweeted
Many PMs struggle to explain the difference between Vision, Strategy, Objectives, and Roadmap. But those are extremely simple concepts. Let's tackle them one by one: 1. Product Vision (Why) Product Vision is the long-term aspiration of your product. It motivates your team to wake up every morning and go to work. For example, “Send humans to the Moon” or “Help tour operators focus on doing what they love.” Effective vision needs to be inspiring and emotional. It becomes much more memorable when it speaks to people's hearts. My favorite example is the JFK Moon speech: youtu.be/th5A6ZQ28pE?si=YWCc… 2. Product Strategy (Where & How) Strategy is not a plan, a goal, or a set of actions. It's a cohesive set of choices that you believe will allow you to win (achieve your Vision) at the playing field of your choice: - market and its constraints (e.g., geography) - value proposition - relative costs - tradeoffs - growth The strategy should pass the “can’t / won’t test” so that competitors can't copy it without sacrificing their existing businesses. A fantastic, short video by Prof. Roger Martin: youtu.be/iuYlGRnC7J8?si=UCcD… The Product Strategy Canvas (no email, no paywall): lnkd.in/d3w3QUwV 3. Objectives (What) I encourage you to use the OKR framework. It's a simple, incredibly effective approach for setting, monitoring, and achieving your goals. While following the SMART goals principle (Specific, Measurable, Achievable, Relevant, and Time-Bound), OKRs add an additional, inspirational aspect to the Objective. I recently described how to start with OKRs in a free post: nitter.gq/PawelHuryn/statu… 4. Product Roadmap (So What & When) Product Roadmap is a communication tool that allows you to align everyone in the organization. It creates focus on what’s important right now. It should also explain the reasoning behind it. In 3 Ways to Create 10X Better Product Roadmaps, I emphasized that it's extremely important to: - Focus on outcomes, not features - Do not commit too soon - Shorten the planning horizon My favorite format is the Now-Next-Later. Free article (no email, no paywall): lnkd.in/dRKgaJzb More information: - Vision, Mission, and Purpose are often confused, and everyone interprets them differently. I use a single term. An article by Prof. Roger Martin: rogermartin.medium.com/the-m… - Some say that Vision is part of Strategy. It makes sense, as Strategy is an integrated set of choices. And you develop them together. But that’s not the most common opinion. So, during interviews, keep it simple. Hope that helps. What are your thoughts? - P.S. If you liked this, consider joining a community of 32,000+ product professionals. Get one actionable tip for PMs every Saturday: lnkd.in/djnfdris
OKRs are a simple, incredibly effective approach for setting, monitoring, and achieving your goals. But they are commonly misunderstood. How to start? 1. Empowered teams OKRs work only with a culture of empowerment. In companies with a dysfunctional organizational culture, OKRs might become another tool to impose control over employees. 2. Vision and strategy Before defining your first OKR, it's essential to establish a vision and strategy. While the vision provides a long-term "Why," the OKR motivates and guides a team in the short term, typically over a quarter, defining: - Why it's important. - What we need to achieve. - How we will measure we succeeded. 3. Start with just one team First, get one team to try OKRs before the whole company jumps in. This team should be cross-functional, able to reach their goals without relying on others. After a few months, celebrate what they've achieved. Hopefully, this will get other teams excited about OKRs. 4. Select just one OKR Start with a single OKR for the entire company without cascading it down. This simplifies the implementation and allows you to identify teams that need more coaching. This is particularly effective in smaller companies. 5. Start from initiatives focused on the outputs For example, if you're adding a new search feature, think backward. Ask yourself: What’s the goal of this initiative? How would we measure that we succeeded? This helps you turn the task into an OKR and start thinking and making decisions based on data. 6. Keep things simple Don't expect to figure out everything from the start. Test ideas, learn from them, and get better over time. Based on Radical Focus by @cwodtke ----- P.S. In the free part of my latest newsletter (1,351 words), I described: 1. Two Approaches to OKRs 2. Why Do We Need OKRs? 3. What Exactly Are OKRs? 3.1 Prerequisites 3.2 How to create Objectives? 3.3 How to create Key Results? And in the premium part (2,440 words), we deep-dive into the OKRs: 4. OKRs: A Quarter Step-by-Step: 4.1 How to start? 4.2 During the quarter + my advice 4.3 Closing the quarter 5. OKRs: Best Practices and Common Mistakes 6. OKRs: Advanced Techniques 6.1 OKRs and Scrum 6.2 OKRs and Product Roadmap 6.3 OKRs and Continuous Product Discovery 6.4 Extending the traditional OKRs 6.5 OKRs vs. alternatives Hope that helps. You can keep learning here: lnkd.in/dQmrs_3G
4
118
4
593
53,667