Product Management Insights

Writing software, especially prototypes, is becoming cheaper. This will lead to increased demand for people who can decide what to build. AI Product Management has a bright future! Software is often written by teams that comprise Product Managers (PMs), who decide what to build (such as what features to implement for what users) and Software Developers, who write the code to build the product. Economics shows that when two goods are complements — such as cars (with internal-combustion engines) and gasoline — falling prices in one leads to higher demand for the other. For example, as cars became cheaper, more people bought them, which led to increased demand for gas. Something similar will happen in software. Given a clear specification for what to build, AI is making the building itself much faster and cheaper. This will significantly increase demand for people who can come up with clear specs for valuable things to build. This is why I’m excited about the future of Product Management, the discipline of developing and managing software products. I’m especially excited about the future of AI Product Management, the discipline of developing and managing AI software products. Many companies have an Engineer:PM ratio of, say, 6:1. (The ratio varies widely by company and industry, and anywhere from 4:1 to 10:1 is typical.) As coding becomes more efficient, teams will need more product management work (as well as design work) as a fraction of the total workforce. Perhaps engineers will step in to do some of this work, but if it remains the purview of specialized Product Managers, then the demand for these roles will grow. This change in the composition of software development teams is not yet moving forward at full speed. One major force slowing this shift, particularly in AI Product Management, is that Software Engineers, being technical, are understanding and embracing AI much faster than Product Managers. Even today, most companies have difficulty finding people who know how to develop products and also understand AI, and I expect this shortage to grow. Further, AI Product Management requires a different set of skills than traditional software Product Management. It requires: - Technical proficiency in AI. PMs need to understand what products might be technically feasible to build. They also need to understand the lifecycle of AI projects, such as data collection, building, then monitoring, and maintenance of AI models. - Iterative development. Because AI development is much more iterative than traditional software and requires more course corrections along the way, PMs need be able to manage such a process. - Data proficiency. AI products often learn from data, and they can be designed to generate richer forms of data than traditional software. - ... [Reached length limit; full text: https://lnkd.in/geQBWz6s ]

As head of our product organization at Chase, I often think about how and what we’re delivering to customers, but I recently reflected on the vital role of product managers. While some may view it as merely administrative, in my opinion this couldn't be further from the truth. Product managers are the driving force behind strategy and exceptional experiences, whether for external customers or internal users. Our role demands a deep connection to both the product and its users. Three essential qualities we all have: Customer Obsession: Go beyond empathy by diving into data and insights to understand user behavior, pain points, and opportunities. Decisions should be data-driven, ensuring the product evolves with user needs. Strategic Leadership: Product managers must define and drive the product vision, setting strategies that align with company goals. This involves fostering alignment across cross-functional teams and building strong relationships with stakeholders to ensure everyone is working toward a shared vision. Accountability: Own the outcomes, whether good or bad. Exceptional product managers embrace challenges, learn from mistakes, and continuously iterate to improve. They step into gray areas, connecting the dots to drive cohesive and successful outcomes. This role is strategic and high-impact, requiring us to lead with intention, push boundaries, and always advocate for the user. #productmanagers #productdevelopment

Most tech companies break out product management and product marketing into two separate roles: Product management defines the product and gets it built. Product marketing wires the messaging- the facts you want to communicate to customers- and gets the product sold. But from my experience that's a grievous mistake. Those are, and should aways be, one job. There should be no separation between what the product will be and how it will be explained- the story has to be utterly cohesive from the beginning. Your messaging is your product. The story you're telling shapes the thing you're making. I learned story telling from Steve Jobs. I learned product management from Greg Joswiak. Joz, a fellow Wolverine, Michigander, and overall great person, has been at Apple since he left Ann Arbor in 1986 and has run product marketing for decades. And his superpower- the superpower of every truly great product manager- is empathy. He doesn't just understand the customer. He becomes the customer. He can shake off his deep, geeky knowledge of the product and use it like a beginner, like a regular person. You'd be surprised how many product managers skip that hugely necessary step- listening to their customers, gaining insights, empathizing with their needs, then actually using the product in the real world. But for Joz, it's the only way. So when Joz stepped into the world with his next-gen iPod to test it out, he fiddled with it like a beginner. He set aside all the tech specs- except one: battery life. We created typical customer personas, then walked through the moments in their life when they used their iPods- while jogging, at parties, in the car. And we showed Steve that even if the number engineering gave us was twelve hours, those twelve hours actually lasted most people all week long. The numbers were empty without customers, the facts meaningless without context. And, that's why product management has to own the messaging. The spec shows the features, the details of how a product will work, but the messaging predicts people's concerns and finds way to mitigate them. It answers the question, "Why will customers care?" And that question has to be answered long before anyone gets to work. - BUILD Chapter 5.5 The Point of PMs

A PM at Google asked me how I managed 30+ stakeholders. 'More meetings?' Wrong. Here's the RACI framework that cut my meeting load by 60% while increasing influence. 1/ 𝙍𝙚𝙨𝙥𝙤𝙣𝙨𝙞𝙗𝙡𝙚 𝙫𝙨 𝘼𝙘𝙘𝙤𝙪𝙣𝙩𝙖𝙗𝙡𝙚 Most PMs drown because they invite everyone who's "interested." Instead, split your stakeholders into: - R: People doing the work - A: People accountable for success 2/ 𝙏𝙝𝙚 𝘾𝙤𝙣𝙨𝙪𝙡𝙩𝙖𝙩𝙞𝙤𝙣 𝙏𝙧𝙖𝙥 Stop asking for approval from everyone. Create two clear buckets: - C: Must consult before decisions - I: Just keep informed of progress 3/ 𝘿𝙤𝙘𝙪𝙢𝙚𝙣𝙩 > 𝙈𝙚𝙚𝙩𝙞𝙣𝙜 For "Informed" stakeholders, switch to documented updates. They'll actually retain more than in another recurring meeting. 4/ 𝙏𝙝𝙚 𝙈𝙖𝙜𝙞𝙘 𝙋𝙝𝙧𝙖𝙨𝙚 "𝗜𝗳 𝘆𝗼𝘂'𝗿𝗲 𝗻𝗼𝘁 𝗱𝗶𝗿𝗲𝗰𝘁𝗹𝘆 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗹𝗲, 𝗽𝗹𝗲𝗮𝘀𝗲 𝗳𝗼𝗿𝘄𝗮𝗿𝗱 𝘁𝗵𝗶𝘀 𝘁𝗼 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗽𝗲𝗿𝘀𝗼𝗻. 𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗶𝗻 𝗮𝗱𝘃𝗮𝗻𝗰𝗲." Use this in every email. Watch the right people emerge. 5/ 𝘼𝙥𝙥𝙧𝙤𝙫𝙖𝙡 𝘼𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚 Build your approval flows around your R&A stakeholders only. Everyone else gets strategic updates. --- This isn't about excluding people. It's about respecting everyone's time while maintaining momentum. If you found this framework helpful for managing stakeholders: 1. Follow Alex Rechevskiy for more actionable frameworks on product leadership and time management 2. Bookmark and retweet to save these tactics and help other PMs streamline their stakeholder management

I am constantly thinking about how to foster innovation in my product organization. Building teams that are experts at execution is the easy part—when there’s a clear problem, product orgs are great at coming up with smart solutions. But it’s impossible to optimize your way into innovation. You can’t only rely on incremental improvement to keep growing. You need to come up with new problem spaces, rather than just finding better solutions to the same old problems. So, how do we come up with those new spaces? Here are a few things I’m trying at Duolingo: 1. Innovation needs a high-energy environment, and a slow process will kill a great idea. So I always ask myself: Can we remove some of the organizational barriers here? Do managers from seven different teams really need to say yes on every project? Seeking consensus across the company—rather than just keeping everyone informed—can be a major deterrent to innovation. 2. Similarly, beware of defaulting to “following up.” If product meetings are on a weekly cadence, every time you do this, you are allocating seven days to a task that might only need two. We try to avoid this and promote a sense of urgency, which is essential for innovative ideas to turn into successes. 3. Figure out the right incentive. Most product orgs reward team members whose ideas have measurable business impact, which works in most contexts. But once you’ve found product-market fit, it is often easiest to generate impact through smaller wins. So, naturally, if your org tends to only reward impact, you have effectively incentivized constant optimization of existing features instead of innovation. In the short term things will look great, but over time your product becomes stale. I try to show my teams that we value and reward bigger ideas. If someone sticks their neck out on a new concept, we should highlight that—even if it didn’t pan out. Big swings should be celebrated, even if we didn’t win, because there are valuable learnings there. 4. Look for innovative thinkers with a history of zero-to-one feature work. There are lots of amazing product managers out there, but not many focus on new problem domains. If a PM has created something new from scratch and done it well, that’s a good sign. An even better sign: if they show excitement about and gravitate toward that kind of work. If that sounds like you—if you’re a product manager who wants to think big picture and try out big ideas in a fast-paced environment with a stellar mission—we want you on our team. We’re hiring a Director of Product Management: https://lnkd.in/dQnWqmDZ #productthoughts #innovation #productmanagement #zerotoone

My 8 years of product lessons in one post: 1. There are only two criteria for product success: Whether it solve a user problem well? Whether it help business move forward? 2. Users will only use the product if it solves problems in their lives, or addresses a desire, better than the alternatives. 3. Business will move forward if it increases market share, or revenue, or builds competitive advantage. 4. User Empathy is the no.1 skill you need as a product manager. 5. Your team is the most important factor in your success. Fortunately, there are ways to learn to motivate and align people. 6. Almost no product can satisfy all kinds of customers. Learn to separate noise from signals during user research and analysis. 7. A product manager who doesn't talk to their users frequently, ends up becoming just a feature manager. 8. On Stakeholder management: Involve leaders early. Get people to work on their ideas. Stand up for your team. Create a culture of meritocracy and quick feedback. 9. Always decide on metrics before you start working on the feature. It's easy to fall for fundamental attributer error later. 10. The quality of your mental health will reflect in the quality of your product. Working long hours all the time isn't sustainable. 11. Always prioritize and filter before execution. 12. Execution is an important skill, but shouldn't be the only skill that you have. Combine execution with strategy and see yourself grow. 13. Asking the right questions is 90% of product discovery, and the rest 10% is structuring and analyzing your findings. 14. Cracking a PM interview and doing a PM job well are two different things. That's a sad reality. 15. It's possible to move from ANY DOMAIN to product management, but it's not easy. 16. Do not be a slave of tools. Tools change, and your expertise improves. 17. Reflect often - The feature only fails if it fails to achieve metrics and you didn't learn anything from it. 18. It's difficult to explain your job, even to your team. 19. All roadmaps change. 20. Build relationships, and solid proof of work. This is probably not your last job or company. Fellow PMs, What have been your key learnings in your career? I am taking a Free Masterclass on Product Management this Saturday, register here: https://lnkd.in/gkx3ueyM #productmanagement #learnings

Vlad Loktev taught me more about product management than anyone else I've ever worked with, and is responsible for the biggest inflection in my PM career. Vlad spent 10 years at Airbnb where he started as an IC PM and quickly advanced to lead product, and then GM the entire Airbnb homes business, managing over 1,000 people and reporting directly to CEO Brian Chesky. He recently left Airbnb and joined Index Ventures as their newest partner. Prior to Airbnb, Vlad spent a year at Zynga, where he helped grow Words with Friends to over 14 million daily active users. In our conversation, we discuss: 🔸 Insight into Brian Chesky’s leadership style 🔸 Why success as a PM is all about impact, impact, impact 🔸 Why chaos can be good 🔸 Why as a leader it’s OK to let some fires burn 🔸 Why you should learn to “poke the bear” 🔸 Balancing product release speed with quality 🔸 Lessons on prioritization, decision-making, and organizational design 🔸 Advice for founders on building company culture 🔸 Much more Listen now 👇 - YouTube: https://lnkd.in/gMrECh5z - Spotify: https://lnkd.in/gG8yRXh2 - Apple: https://lnkd.in/g8rKdAjm Some key takeaways: 1. Relentlessly focus on impact. Start by identifying the highest priorities for your organization or team. Each day, ask yourself: What are the most critical tasks or projects that align with these priorities? Ensure your efforts are directly contributing to these goals. 2. Don’t be afraid to “poke the bear”: When you have a strong opinion or concern, don’t shy away from voicing it, even if it challenges the status quo. Poking the bear means confronting difficult issues constructively and openly, which can drive meaningful change and improvements. 3. Lead with curiosity and dial down advocacy: When entering a conversation or meeting, start by asking open-ended questions to understand others’ perspectives fully. This approach shows respect for differing opinions and helps you gather important information. Only after you have actively listened and absorbed the other viewpoints should you advocate for your own perspective. 4. Let some fires burn. You can’t address everything at once, and if you feel a need to do so, that’s a sign you don’t understand what’s most important for your business. You need to be explicit with yourself and your team about what the priorities are and what you’re willing to let burn in service of them. Aligning on this in advance will help you resist the urge to put out fires as they start. 5. Two tools to help you calm your mind: a. The serenity prayer: “Grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.” b. The shit bucket: Designate a specific place, like a physical trash can or a digital file, as your ‘shit bucket’ for frustrations and issues you can’t change.

The role of product management, especially for AI-based products, is changing a lot. Interestingly, a significant number of products are becoming "AI-based" products. You'll often see requests for a stronger technical background alongside traditional PM skills. It's not enough to just know the market and users anymore; product managers now need to understand things like algorithms, data pipelines, and machine learning. This isn't a small change; it's a real shift in what's required. It’s not about knowledge of a toll but the technology. I'm seeing this trend firsthand. Look at product manager job descriptions, and "understanding or working knowledge of AI" is becoming standard. We're also seeing more data scientists and AI engineers moving into product management. This isn't just a career switch; it's a sign that technical knowledge is crucial for building good AI products. For people without this background, it's a big challenge, requiring a lot of learning and a willingness to try new things. Being able to explain complex technical ideas in a way that users understand is now a must-have skill. The key to AI product management is balancing big ideas with what's actually possible. Without understanding AI's strengths and limitations, product managers can easily get swayed by marketing hype or struggle to create realistic roadmaps. It's the difference between a dream and a practical vision. Equally important is building strong communication with engineering teams, not just for technical alignment but for building trust. Don't believe the idea that you don't need technical skills in PM. This trend is only going to get stronger. It's better to adapt and learn than to struggle later. #ExperienceFromTheField #WrittenByHuman

One critical skill of great Product Managers is that they can take an immense amount of information and make sense out of it to find a path forward. Your job isn’t just to get the data, it’s to create action out of that data. But this is where many people get paralyzed. For product managers who struggle with this, I find tools like Affinity mapping extremely helpful to help organize your thoughts. Affinity Mapping is a basic facilitation and collaboration tool, but it’s extremely powerful. Put simply, it’s a practical way to sort through different pieces of data, group them into common themes, and discover valuable insights. Whether you're dealing with complicated user research or trying to get everyone on the same page, this method helps you focus and find your way forward. Here's how to run an Affinity Mapping session that's not just productive, but also a bit of fun: 1️⃣ Gather Your Data: Start with all the raw data you have – post-its from brainstorming, customer feedback, interview notes, you name it. Get it all on the table. Literally. 2️⃣ Invite the Right People: Bring together a diverse group from your team. Yes, diversity! You want different perspectives – designers, developers, marketers, and especially those who are often quiet but have brilliant thoughts simmering under the surface. 🧠 3️⃣ Create a Safe Space: Before diving in, set the stage for open collaboration. Remind everyone that every idea is valuable and we're here to discover, not judge. This is about finding patterns, not picking favorites. 4️⃣ Sort and Cluster: Now, get sticky! Start placing related ideas together. Don't overthink it. Go with your gut. You'll see themes start to emerge as you cluster similar thoughts. It's like a puzzle where the picture becomes clearer with each piece. 🧩 5️⃣ Label the Themes: Once you have your clusters, give each one a name that captures the essence of the ideas within it. These labels will be your guideposts for action later on. 6️⃣ Reflect and Discuss: Take a step back. What do you see? Any surprises? Discuss as a group and make sure everyone's voice is heard. This is where the magic happens – insights start to bubble up to the surface. 7️⃣ Prioritize and Act: Finally, decide what's most important. Which themes align with your goals? Which insights are game-changers? Make a plan to act on these priorities. Affinity mapping is not just about organizing thoughts; it's about unlocking the collective wisdom of your team. It's a powerful way to build consensus and ensure everyone's voice is heard. So, next time you're grappling with data overload, grab some sticky notes and start mapping! What else have you used to help organize your thoughts and data? #ProductManagement #UserResearch #Collaboration #AffinityMapping