The first version of your growth engine is just the beginning. In this section, we'll explore how PLX can help you continuously improve through small bets, fast feedback, and the use of quarterly OKRs to drive long-term growth.
So far, we've focused on creating the first version of your product growth engine using the PLX canvas to identify the necessary building blocks. Now that you've built your product growth engine, it's time to focus on continuous improvement.
Continuous improvement begins with a clear picture of where your growth engine is working—and where it isn't. That's the role of funnel analytics.
Funnels help you track how users progress through the key stages of PLX (i.e., Evaluate, Activate, Adopt, Expand, and Advocate) and pinpoint where drop-offs occur. Each stage is tied to a specific user action, and the funnel makes these transitions measurable.
A well-instrumented funnel answers questions like:
This isn't just about optimization. It's about focus. If a change doesn't improve funnel performance, it's not a priority.
Most analytics platforms support funnel tracking—but not all support easy comparison over time. If you're using Google Analytics (GA4), for example, you'll likely need to pair it with Looker Studio to get a clearer view of performance trends.
By connecting GA4 events to Looker, you can build charts that:
For example, a new onboarding flow might improve the Activate rate by 15% in Q2 compared to Q1. But that increase could just as easily be driven by a new marketing campaign—or even the action of a key competitor. It's your job as a product designer to figure out what changed and why, so you can take the right next step.
Typically, continuous improvement involves making incremental changes based on analytics and stakeholder feedback. But I suggest a slightly different approach for PLX: a quarterly process layered atop your existing continuous improvement workflow. Here's how it works:
Many teams use OKRs (Objectives and Key Results), which focus on outcomes rather than outputs. For example:
Note: In typical OKR fashion, the objective is achieved if 70% or more of the KRs are completed before the end of the quarter.
The focus on outcomes over outputs is essential. In the planning meeting, we concentrate on the "what" and "why"—determining what deserves our attention in the next three months. Since you can't do everything, prioritisation is key.
The "how" is left to the team—not because it's less important, but because discovering how to, for example, "Improve Expand KPI from X% to Y%" involves trial and error and experimentation.
Tip: It's also crucial to distinguish between KPIs to improve and those to maintain. While it might be tempting to improve all metrics at once, lasting change requires focus. It's wise to target one or two KPIs for improvement while ensuring that others remain stable.
→ FOR MORE, SEE "OKR COACHING MODEL" BY ANDREAS HOLMEROnce you've agreed on your quarterly OKRs, it's time to focus on the "how." This is a great time to revisit the PLX Canvas. You can plug new ideas into an Impact/Effort Matrix to prioritise which solutions to try first.
Three months isn't a lot of time. You might get lucky and have your first experiment achieve your quarterly OKR. But more likely, you'll need to test a few different things before finding something that works. The faster you move, the more solutions you can test.
Tip: Each idea or solution is a hypothesis, and you need your cohort charts to prove they work. So, make small bets with fast feedback, and pivot if your first hypothesis fails to deliver the expected result. Ship often and early.