How to Empower Product Teams for Product-Led Growth

I’ve seen so many leaders pour all their energy into features, metrics, and launches, while forgetting that the quality of those outcomes is only as strong as the team behind them. And this is a struggle that many new product leaders face. You can have the most brilliant roadmap in place, but if: Your PM and engineers are not aligned, Designers don’t feel empowered to ask the hard questions, Sales doesn’t have a seat at the table, Then trust me, 𝗲𝘃𝗲𝗻 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 𝘄𝗶𝗹𝗹 𝗰𝗼𝗹𝗹𝗮𝗽𝘀𝗲 𝘂𝗻𝗱𝗲𝗿 𝗶𝘁𝘀 𝗼𝘄𝗻 𝘄𝗲𝗶𝗴𝗵𝘁. So what does it mean to actually build your team as your first product? It means treating the team with the same rigour you’d treat a product: 𝗗𝗶𝘀𝗰𝗼𝘃𝗲𝗿𝘆: Do you understand what motivates and blocks them? 𝗗𝗲𝘀𝗶𝗴𝗻: Have you created clear interfaces between roles? 𝗜𝘁𝗲𝗿𝗮𝘁𝗶𝗼𝗻: Are you continuously tuning your rituals, tools, and norms? 𝗠𝗲𝘁𝗿𝗶𝗰𝘀: Do you track not just velocity, but alignment, trust, and ownership? Once you start looking at your team with this lens, your processes will automatically flow way better! #productleadership #startup #techstartup

Your engineers should annoy your PMs (I say this now as a product leader). As a senior product manager, I launched a new onboarding flow that boosted trial conversions by 25%. I was riding high on success…and then an engineer on my team suggested removing an extra step. Sure, it would further reduce cognitive load and drive even more conversions, but I was so in love with the design of the onboarding flow that I got annoyed. I pushed back—despite clear data! In the end, that engineer (rightfully) sidestepped me, ran the experiment, and proved me wrong. My self-indulgence almost cost our team another win. Now, as a product leader, I can see that customer- and data-centric engineers who help define product are a product manager’s gold mine. They enable PMs to scale out of the day-to-day and drive more impact across the organization. Leading tech companies and high-growth startups already encourage engineers to act like PMs. With AI making customer, competitor, and market insights more accessible, product-centric engineering will soon be standard everywhere. Product leaders, here’s how to embrace and empower these cross-functional teams: 1️⃣ Foster a culture where engineers, designers, and customer success teams don’t just share ideas, but actively shape product definitions. This allows PMs to act like air traffic controllers rather than pilots, guiding multiple “flights” simultaneously so more initiatives can land successfully. 2️⃣ Provide the right tools broadly—including direct access to customer feedback and data—so every role can make informed recommendations. 3️⃣ Encourage PMs to delegate and scale beyond their core responsibilities, taking on broader, more cross-functional work while peers step up with product insights. Your PMs and your organization as a whole will benefit. How have you encouraged your PMs to scale themselves? #productmanagement #productleadership

Most product teams aren’t empowered. They’re over-responsibilized. “You’re the product manager, you decide.” “Drive outcomes.” “Be bold.” “You’re accountable.” Sounds empowering, right? But let’s be honest: it often isn’t. It’s responsibility without influence. Autonomy without access. Pressure without protection. With a background in sociology and systems theory, I see this as more than just a leadership gap. It’s a systemic contradiction: a misalignment baked into the way many organizations are structured. Leadership assigns accountability but doesn’t provide the actual levers to deliver on it. They expect ownership, but keep control of budgets, roadmaps, and access to customers. They say “outcomes over outputs,” but reward feature delivery and roadmap velocity. Empowerment isn’t a mindset. It’s a system. And it starts at the top. A real system of empowerment means: 🔑 Teams have built-in access to users, not ad-hoc permission 📊 They influence how data is interpreted and used and don’t just consume dashboards 🧭 They shape problems collaboratively instead of executing pre-scoped plans 🧠 Leadership provides context, clears blockers, and shares decision-making instead of delegating goals It also means empowered product managers. Not just delivery owners, but strategic leaders with a seat at the table. The kind of PMs who shape the system around them, not just survive within it. When those conditions aren’t in place, responsibility turns into exposure. If your team can’t say no, talk to users, or challenge the plan then you haven’t empowered them. You’ve just exposed them and the organization pays the price. The cost isn’t just morale. It’s execution speed, product quality, and innovation. Empowered teams aren't born. They’re built with intention and structure. If leaders don’t enable that, they’re not empowering. They’re just outsourcing the blame.

“You fixed the product team.” Not exactly. Six months into a new product leadership role, someone said this to me. And while I appreciated the compliment, the truth is more nuanced. When I joined, the product development culture was a mess: ➤ Leadership was frustrated that nothing ever seemed to get done. ➤ Engineers were frustrated—they wrote code that never shipped. ➤ Product managers lacked autonomy—unable to dig into customer problems or solve them. There was no clear process to align on priorities. Product had little voice in what should be worked on, and top-down projects were often decided behind closed doors—only to change week to week. With no space for proper discovery, pressure fell on engineering to deliver against unclear, shifting expectations. Tension between product and engineering grew. But the right people were there: 👉 Product Managers who were customer-centric and solutions-oriented 👉 Engineers who cared deeply about building great software 👉 Leadership that understood the importance of prioritization and tradeoffs So no—I didn’t fix the team. I created the conditions for them to thrive. ✅ Transparency & Trust: Introduced a clear, transparent planning process with regular roadmap check-ins so leadership could align and understand progress. ✅ Product Empowerment: Gave PMs problems to solve—not prescriptive solutions—so they could do meaningful discovery on the best approach. ✅ Engineering Partnership: Brought engineering into the process early to set realistic expectations and surface platform needs. The talent was always there. They just needed clarity, trust, and runway.

Head of Product, this is your secret weapon: Curiosity. Stepping into a role as Head of Product in an organization where field experts and clients have historically driven product decisions can be daunting. So how do you add value and empower your team in such an environment? Start by bridging gaps in domain knowledge. Encourage your product managers to shadow field experts. This allows them to see the real-world application of products and understand user challenges firsthand. Your PMs should be asking "What do our clients do with our products? What problems are they trying to solve?" Fostering curiosity in your team is key. A great product manager doesn't have to walk in the door with extensive domain expertise. But they should be hungry to learn and understand (if that's missing, you might not have the right fit for your product team). But how can you drive curiosity? Start by developing processes. Encourage the team to conduct user research and set up programs where they can interact directly with customers. Before kicking off projects, make customer interviews a regular part of the discovery phase. Also, consider pairing PMs with a field expert mentor for continuous learning. Don’t forget to lead by example. Learn the domain alongside your team if needed. Your role is to create the structure that facilitates learning and knowledge-sharing, ensuring your product managers engage with users and field experts regularly. Ultimately, the drive to understand and solve user problems is what makes a product manager successful. As a leader, your focus should be on fostering this mindset and setting the stage for continuous learning. That's how you add value and ensure your team can effectively build products that resonate with your users. Are you fostering curiosity in your teams? How? Let’s share techniques in the comments.

🚀 Many product leaders dream of transforming their product org. But let’s be honest — it’s tough. In my last post, I shared four archetypes of product organizations. Did you see your team in the chart? If so, your next question might be: How do we evolve? Here are a few concrete moves to increase autonomy and maturity — no matter where you start: 🔴 From Feature-Driven → Output-Focused ✅ Set clear product goals instead of feature lists ✅ Start small discovery loops (even with just 1% of your time) ✅ Get PMs closer to users and data 🟡 From Output-Focused → Empowered ✅ Shift from “what to build” to “which problem to solve” ✅ Invest in product skills: coaching, mentoring, shadowing ✅ Align PM, Design, and Eng around outcomes—not deliverables 🟢 From Empowered → Mission-Based ✅ Organize teams around customer journeys or lifecycle stages ✅ Give teams full ownership: problem, solution, and success metrics ✅ Use portfolio reviews for alignment—not control 💡 This is a journey, not a checklist. Change often happens team by team, wave by wave. And depending on your org’s size, you may need to bring stakeholders or managers along for the ride. 🏁 But here's the thing: If you don’t start now — when will you? 🔍 Even a small step can create momentum: Which move is most urgent for your org right now? And what would it take to unlock it?