Product in Practice: Stepping Into Your First Product Leadership Role—What to Expect

New product leaders often struggle with the shift from doing discovery and delivery themselves to leading teams and stakeholders. Two leaders from the Continuous Discovery Habits community share how they handled this transition. Trevor Acy faced pressure from leadership to speed up discovery and learned to separate genuinely risky bets from low-risk changes that can be built quickly, while still protecting time for learning. Iryna Melnyk used an opportunity solution tree to treat her team as a product, making invisible operational work visible and celebrated. The piece matters because product leadership is under-documented, and it shows how continuous discovery habits can be applied to stakeholder trust, team growth, and focus.

01Key takeaways

• Separate risky bets that need assumption testing from low-risk, reversible changes that can be shipped quickly.
• Map the specific obstacles behind vague pressure to move faster, then tackle the largest one first.
• Build stakeholder trust by first pursuing the results leaders care about before trying to change how things work.
• Understand how your business makes money so you can connect product outcomes to business outcomes.
• Treat your team or organization as a product and use an opportunity solution tree to set focus areas.
• Make invisible operational work visible and celebrate it, and avoid trying to change too many things at once.

02Key sections

The shift into product leadership

New leaders move from hands-on discovery and delivery toward strategy and team responsibility, which can feel isolating. The article frames this as a major change in role.

Trevor Acy and the speed-versus-learning tension

Leadership wanted faster discovery, so Trevor mapped the obstacles to speed and asked the community how to decide when to test assumptions versus simply build. The guidance was that discovery reduces risk, and low-risk, reversible choices don't need full testing.

Building trust and results

Trevor shared the community's guidance with leadership and used rising metrics as evidence, which built trust in the process and gave the team permission to try bolder ideas.

Iryna Melnyk and the team-as-product approach

Iryna reframed her role by treating her teams as her product, using an opportunity solution tree with the outcome that teams are set up to win.

Making invisible work visible

Iryna found the platform team's operational work was underappreciated, so the team made that work visible in quarterly plans and planned to showcase it at an all-hands.

Key leadership lessons

Both leaders stress building stakeholder trust by caring about their priorities, understanding the business, growing team members rather than doing their work, and focusing on a few priorities at once.

03From the post

“Stepping into your first product leadership role is a major change. As an individual contributor, you’re focusing on your own projects and progress, but as a leader you are now responsible for the team (or teams) that report up to you. You may find yourself less involved in the”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.