The Role of the CPO

To be an effective intermediate PM, you must understand the world of your Chief Product Officer (CPO). The CPO is responsible for the Product Portfolio and the high-level Strategic Intent. They care about how all products work as a system to provide value — not the details of any single feature.

When you walk into a CPO's office talking about tickets and timelines, you're speaking the wrong language.

Breaking the "Order Taker" Cycle

Many mid-level PMs fall into the "Waiter" archetype — simply taking orders from stakeholders and passing them to engineering. This creates a Product Death Cycle: you build features because customers say they are missing, but no one uses the product because the core problem was never diagnosed.

The cycle looks like this: 1. Customers complain features are missing 2. PM adds those features to the roadmap 3. Features ship — adoption doesn't move 4. Customers complain more features are missing

To break this cycle, stop taking feature requests at face value. Start diagnosing the underlying problem.

Communicating with Outcomes

When "managing up," stop reporting on "Percentage Complete." Instead, communicate in the cadence of the strategy levels:

Vision (5–10 years): Where are we going? This is the CPO's language.

Strategic Intent (Yearly): What business challenges are in our way? This is where you connect your work to company goals.

Product Initiatives (Quarterly): Which problems will we solve to address the challenges? This is your primary operating layer.

Options (Monthly/Daily): What are the different ways we can solve those problems? This is the experimentation and delivery layer.

When you frame your updates in this hierarchy, leadership immediately understands how your work connects to their priorities.

Living Roadmaps

Roadmaps should not be static Gantt charts that promise specific features on specific dates. A "Fixer" maintains a Living Roadmap that explains strategy and current stages of uncertainty rather than just release dates.

A living roadmap answers: *"What problem are we solving, what are we learning, and how confident are we in our current direction?"*

Immediate Takeaway: Next time a senior stakeholder asks for a specific feature, don't say "yes" or "no." Say: *"Help me understand which of our current Strategic Intents this helps us achieve, and what problem it solves for the customer that our current Options don't."*