I created the Product Management Playbook to show my clients the steps and responsibilities involved in product development.
I’ve been talking about this playbook for a while. It’s part of my latest book, and I’ve been updating it as I collect feedback.
I believe I’ve reached a fairly complete version. And it all starts with Vision.
The first step is having clarity about Vision, which is a description of what we want to build. It’s where we want to take our product and why we should get there. It’s our destination and the motivation that drives us to reach it.
The person responsible for creating the Vision is the company’s founder, with input from leadership and the teams.
Once the Vision is defined, the destination we want to reach, the next step is to define the strategy, which describes how we’ll get there, and the team structure, which describes who will build that path. This is defined by leadership, together with the founder, and with input from the teams.
With clarity on vision and strategy, teams define the objectives and metrics that show those objectives have been achieved (OKRs), identify the strategic bets to reach those objectives (Roadmap), and begin running experiments that guide the building of solutions (Discovery and Delivery), solutions that solve customers’ problems while generating results for the company. Leadership and the founder provide significant input, but the teams are the ones responsible for this part.
Daily discovery and delivery will generate many learnings that should feed into monthly roadmap reviews, quarterly OKR reviews, and annual strategy reviews. During the strategy review, it may also be worth revisiting the vision and team structure, though these shouldn’t change on a yearly basis.
Capturing these learnings in practice requires discipline and clear rituals. Day to day, this can be as simple as logging tested hypotheses and their results in a shared repository. In monthly roadmap reviews, the key question is: what did we learn that changes our bets? In quarterly OKR reviews: do the outcomes we’re pursuing still make sense? And in the annual strategy review: what have the market, our customers, and the data told us that we should take into account? Without these rituals, learning stays in people’s heads, and walks out the door when they do.
With this, we have a complete playbook that brings together all the necessary tools, responsibilities, and review cycles to build products with a real chance of success.
More than a set of artifacts, the playbook is a way to align the entire organization around a common direction — from the vision the founder defines to the experiments teams run every day.
When each layer understands its role and the review cycles are working, strategy stops being a document and starts driving real decisions.
In practice, though, one of the biggest challenges I see in organizations is exactly this: the strategy exists, but it never reaches the product. That’s what Paulo Caroli and I will be discussing in the masterclass below.
In this 3-hour masterclass, Paulo Caroli and I will present a practical model to connect product vision, strategy, OKRs, and discovery to the real work of product teams.
The goal is to understand how to translate strategic direction into real product decisions.
The Masterclass will be in Portuguese.
More information and registration:
I’ve been helping companies and their leaders (CPOs, heads of product, CTOs, CEOs, tech founders, and heads of digital transformation) bridge the gap between business and technology through workshops, coaching, and advisory services on product management and digital transformation.
At Gyaco, we believe in the power of conversations to spark reflection and learning. That’s why we have “Product in Focus” (Produto em Pauta in Portuguese), a podcast that explores the world of product management from different angles:
Available on YouTube and Spotify. Recorded in Portuguese, with English subtitles on YouTube.
Do you work with digital products? Do you want to know more about managing a digital product to increase its chances of success, solve its user’s problems, and achieve the company objectives? Check out my Digital Product Management books, where I share what I learned during my 30+ years of experience in creating and managing digital products:
