Every organization has (to a greater or lesser extent) a mission or vision, from which strategic goals emerge. These goals are then often translated into portfolio plans or initiatives. As a Product Owner, it's essential to understand how your product goals contribute to these. This prevents you from developing fantastic features that don't align with the broader business objectives.
For instance, if management wants to 'grow in the Asian market,' a product goal could be: "Add multilingual support and local payment methods." This clearly shows how your backlog items serve the overarching strategy.
OKR is a well-known framework for achieving alignment:
By formulating team-level OKRs derived from higher business goals, you create a clear link between your daily backlog activities and the overall strategy.
In lean environments, Hoshin Kanri (or X-matrix) is sometimes used to 'break down' the strategy across the entire organization into departmental and team priorities. This 'X-matrix' shows the breakthrough objectives the organization has and what measurable actions each team can take. As a PO, you look at the themes that align with your product domain and prioritize backlog items that contribute to them (e.g., cost reduction items if one of the Hoshin goals is 'Operational costs -20%').
Alignment isn't just a top-down process; it works both ways. As a PO, you might find that a strategic goal doesn't align with customer needs or is based on unrealistic assumptions. In an Agile environment, it's crucial for the team and the PO to provide feedback to management, for example: "We've noticed this market need isn't as strong as anticipated; consider pivoting." This prevents teams from holding onto an outdated plan for too long.
During sprint reviews, stakeholder updates, or product demos, you can regularly refer to the company strategy: "This new module contributes to our goal of becoming the market leader in segment X," or "This performance improvement supports the Hoshin Kanri goal of reducing operational costs by 20%." This helps stakeholders and team members keep the bigger picture in mind.
Without alignment, each team might be doing incredibly innovative things, but collectively, they deliver less value. By explicitly linking product goals to organizational goals, there's a greater chance that the final product will deliver the ROI the company expects.
Whether you work with OKR’s, Hoshin Kanri or another methodology: the most important thing is to have a clear line connecting the organizational strategy to your product goals and backlog. As a Product Owner, this enables you to explain the 'why' behind your prioritization and ensure your team delivers value not only in short-term sprints but also in the long term. And don't forget the feedback loop: if the market or customer needs differ from what management anticipated, feed that information back so the strategy remains agile—just like the product itself.
.svg){kind=icon}
.svg)
