Leading Product Edition 10
We made it! 10 is a nice number. Thanks for reading.
Happy Spring. For the tenth edition of Leading Product I present 10 product things. Curation is fun.
🤝🏿 This awesome thread about finding a director of product at Honeycomb, by Megan Gleason.
🌟 This back and forth thread on finding the North Star.
And Ibrahim Bashir’s take:
🆘 Helping with meaning.
🧩 John Cutler’s three product strategy puzzles post on LinkedIn.
💰 How do products happen, and get funded? Check out Chapter 3 of The Turning Point: A Novel About Agile Architects Building a Digital Foundation by Stephanie Ramsay, Kees van den Brink, and Sylvain Marie (The Open Group Press).
N.B. Rather than confine teams to rigid ways of working, standards unlock agility. 🤔
💸 Selling Nextsale - Indiehackers. Martech. Nicely done.
😂 This billboard ad campaign from odoo. You know immediately who it’s for. It caught my eye the other day in Toronto.
🤯 Sharing with everyone 4 mindmaps of key takeaways from “The Epic Guide to Agile” Came across this a while ago via HackerNews, a great amount of effort for something super practical.
🔮 How to Future-Proof Your Product Management Skills - Gartner
🧵 This thread about understanding an organization’s product bearing, by Shreyes Doshi. BTW I’ve always taken issue with the term “product-led” - doesn’t / shouldn’t that just mean customer-led…?
Data Mesh From an Engineering Perspective
An excellent scroll if you work with data intensive applications, or run data-as-a-service product(s).
The data as a product principle projects a product thinking philosophy onto analytical data. This principle means that there are consumers for the data beyond the domain. The domain team is responsible for satisfying the needs of other domains by providing high-quality data. Basically, domain data should be treated as any other public API.
Thanks for reading and getting this thing to ten.