When I stepped into leading Root’s product management function, my mission was clear: to evolve our product processes for greater impact. The goal was ambitious yet focused: transforming a lean team of product managers, designers, and engineers into a high-impact organisation to outperform competitors, create meaningful differentiation, and deliver exceptional solutions to customer problems.
At the heart of this transformation were empowered teams and the Product Operating Model, inspired by the Silicon Valley Product Group. This approach was anchored by a clear product strategy, measurable goals using Objectives and Key Results (OKRs), and new ways of working that prioritized delivering impactful outcomes over outputs.
Through targeted changes in discovery, delivery, and goal-setting, we unlocked the potential of our product and engineering teams. We treated our way of working like a product itself—continuously refining and improving it to adapt to evolving needs and opportunities. In fact, we’re iterating on these processes even as you read this.
OKR workshop highlights:
These workshops have become a cornerstone of our quarterly planning, driving alignment and ensuring our teams are equipped to deliver impactful outcomes.
Read my Substack blog: How to boost team impact with collaborative OKRs
Our Culture
At Root, we fostered a culture of collaboration, accountability, and continuous learning. Teams were given autonomy to experiment, learn from failure, and iterate on their solutions. Transparency and trust were key pillars, enabling cross-functional teams to operate with clarity and confidence.
Team topology was closely tied to our product strategy. Each team had a clear purpose that directly supported overarching goals, ensuring alignment and focus. We iterated on team structures to balance specialization with flexibility, adapting to changing needs and priorities.
Teams operated with defined principles, such as prioritizing customer impact, leveraging data for decision-making, and collaborating early and often. This clarity allowed teams to stay aligned while maintaining autonomy over their work.
We started by introducing the OKR framework to set clear, measurable objectives for our product and engineering teams. This involved working closely with team leads to define ambitious yet achievable goals and key results that aligned with our company's strategic priorities. The OKRs were reviewed quarterly, allowing us to adapt to market changes and new insights.
Our OKRs aligned team objectives with company goals. Quarterly planning allowed teams to focus on solving complex problems while remaining agile enough to adjust as needed.
Key practices included:
Empowered product teams are given ownership over the problems they solve rather than the features they build. They are aligned with clear strategic objectives and are trusted to collaborate across disciplines to define and deliver solutions. These teams are outcome-focused, creative, and deeply engaged in the process of solving customer problems.
Each role within our teams was designed to contribute to this empowered approach:
The first step was to define a clear product strategy in collaboration with our CEO and senior leaders. This strategy became the foundation for all decisions, enabling us to keep our eyes on the prize, say no to distractions, and maintain hyper-focus. It also became an essential tool for stakeholder management, ensuring alignment across the business.
Moving to the product operating model required a shift in how roadmaps were driven. No longer dictated by stakeholder requests, our roadmaps were guided by the product strategy, informed by insights from stakeholders, customers, and market research. This approach provided teams with a clear north star, ensuring alignment with both customer needs and business goals.
OKRs became the tool we used to align our teams with this strategy, providing clear, measurable goals for achieving our vision.
Practical changes:
We implemented a cross-functional discovery process that brought together product managers, designers, engineers, and stakeholders early in the problem-solving phase. This collaboration ensured solutions were feasible, desirable, and aligned with business objectives. The same teams carried projects through delivery, enabling a seamless transition.
Key Aspects:
We implemented a cross-functional discovery process that brought together product managers, designers, engineers, and stakeholders early in the problem-solving phase. This collaboration ensured solutions were feasible, desirable, and aligned with business objectives. The same teams carried projects through delivery, enabling a seamless transition.
Key Aspects:
CI/CD has been a cornerstone of our delivery process from the start. Small, frequent releases allowed us to:
We continuously optimized our CI/CD pipelines, ensuring they supported high velocity and adaptability
To operationalize the product model, we implemented tools that enhanced transparency, collaboration, and data-driven decision-making:
Feel free to contact me anytime if you'd like to chat about work or side project opportunities, or just connect. I am always keen to have new conversations about all things product.