Driving Transformational Change: Adopting the Product Operating Model

Impact
Intro

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.

Key Steps to Transformation

OKR workshop highlights:

  • Collaborative goal-setting: We focus on aligning our objectives with the company’s vision, fostering a sense of ownership and commitment among team members.
  • Creating buy-in and ownership: By involving everyone in the goal-setting process, we ensure that each team member feels a personal connection to the objectives, driving higher engagement and accountability.
  • Arguably the most impactful point - Leveraging team skills and knowledge: We harness the diverse skills and knowledge within our team, ensuring that every individual's expertise contributes to our collective success.

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 and Alignment with Strategy

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.

OKRs to drive impact

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:

  • Collaborative OKR workshops where every team member contributed to setting shared objectives, ensuring every team member's voice is heard and their insights are valued.
  • Emphasising measurable goals to ensure clarity and accountability.
  • Treating quarterly planning as a checkpoint rather than a deadline, allowing for reprioritisation and integration of ongoing work.
Empowered Product Teams

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.

Key Roles in Our Teams

Each role within our teams was designed to contribute to this empowered approach:

  • Product Managers: Leaders responsible for understanding customer needs, defining problems, and aligning the team’s work with the product strategy. They focus on delivering outcomes, not managing backlogs.
  • Product Designers: Create valuable, user-centered solutions by deeply understanding customer behavior and translating it into intuitive and impactful designs.
  • Engineers: Contribute from the very beginning of problem-solving, offering technical insights and collaborating on innovative solutions beyond implementation.
  • Engineering Leads: Provide technical direction and mentorship, ensuring the team’s solutions are scalable, efficient, and aligned with strategic goals.
Establishing a Clear Product Strategy

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:

  • Clear product strategy aligned with business objectives.
  • Transitioned roadmaps from feature requests to strategy-driven planning.
  • Introduced OKRs to provide clarity and focus for teams.
Cross-functional discovery and delivery process
Cross-Functional Discovery

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:

  • Early-stage collaboration to uncover and validate opportunities.
  • Rapid prototyping and user testing to de-risk development.
  • Iterative discovery to adapt to evolving insights.
Cross-functional discovery and delivery process
Cross-Functional Discovery

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:

  • Early-stage collaboration to uncover and validate opportunities.
  • Rapid prototyping and user testing to de-risk development.
  • Iterative discovery to adapt to evolving insights.

Continuous Integration and Deployment (CI/CD)

CI/CD has been a cornerstone of our delivery process from the start. Small, frequent releases allowed us to:

  • Deliver value quickly and consistently.
  • Gather real-time feedback to inform iterations.
  • Ensure high-quality releases with minimal manual effort through automation.

We continuously optimized our CI/CD pipelines, ensuring they supported high velocity and adaptability

Leveraging the Right Tools

To operationalize the product model, we implemented tools that enhanced transparency, collaboration, and data-driven decision-making:

  • Productboard: Centralized roadmaps and aligned priorities with user needs. This tool offers a wealth of insights to the product team, provided by clients and internal stakeholders.
  • Figma: We leveraged Figma for collaborative design work, enabling our designers and developers to work closely together in real-time.
  • Jira: Jira became our go-to tool for managing the delivery of features, providing visibility into our progress and dependencies.
  • Mixpanel: Delivered actionable insights into user behavior and feature performance.

Productboard
Figma
Jira
Mixpanel
Key takeaways
  • Empowerment drives innovation: Providing teams with the autonomy to operate within a structured framework encourages creativity and accountability.
  • Continuous improvement is crucial: An iterative approach to process enhancement, grounded in team feedback and market insights, ensures relevance and efficiency.
  • Data is a game changer: Implementing robust analytics tools empowers teams to make informed decisions, ultimately enhancing product success.
  • Alignment amplifies impact: A clear strategic direction ensures that all efforts are synergistically directed towards overarching company goals. OKRs are a powerful tool for aligning teams around common goals and ensuring everyone is moving in the same direction.

Let's connect

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.

Get in touch