While Objectives and Key Results (OKRs) have become a well-known framework for helping organizations achieve measurable goals, many organizations struggle to connect those goals to their day-to-day operations. In my experience as an organizational coach, I have observed that although leadership teams often define ambitious OKRs, the execution frequently falls short because teams cannot clearly translate these strategic goals into operational activities.

To address this challenge, I helped organizations complement OKRs with the Hoshin Kanri framework. By integrating these two approaches, organizations were able to bridge the gap between strategy and daily execution. While each framework serves a distinct purpose, together they create a powerful system for strategic alignment, focus, and adaptability.

---

Understanding OKRs

OKRs were popularized in Silicon Valley, particularly by companies such as Intel and later Google. The framework is based on two primary components:

• Objective: A qualitative statement describing what an organization wants to achieve.
• Key Results: Measurable outcomes used to track progress toward the objective.

Example

Objective: Improve customer experience

Key Results:

• Increase Net Promoter Score (NPS) from 45 to 60
• Reduce response time from 24 hours to 6 hours
• Achieve a 95% customer satisfaction score

OKRs provide clarity and focus. However, many organizations struggle to translate these results into specific operational actions across teams and departments.

---

The Role of Hoshin Kanri

Hoshin Kanri originated in Japanese quality management practices and is widely associated with Lean management. Its primary purpose is to ensure that long-term strategic objectives are aligned with daily operations.

The framework typically uses a strategic planning matrix that includes the following key components:

1. What – Breakthrough Objectives Long-term strategic goals (typically 3–5 years).
2. How Far – Annual Objectives High-level goals to be achieved within the current year.
3. How – Strategic Initiatives or Projects Specific initiatives required to achieve the objectives.
4. How Much – Metrics or KPIs Quantitative measures used to track progress and performance.
5. Who – Ownership and Accountability Clear assignment of responsibilities across teams and individuals.

This structure makes Hoshin Kanri particularly effective for translating strategy into coordinated action across the organization.

---

Real-World Example: Cybersecurity Transformation

In one engagement, I supported a client undergoing a cybersecurity transformation initiative focused on increasing the use of artificial intelligence in daily operations. While the leadership team had defined strong OKRs at the CIO level, the Chief Security Officer (CSO) and their team struggled to translate these strategic goals into actionable plans and identify the necessary cross-departmental collaboration.

To address this challenge, I worked with the CSO and their architect team to translate the CIO’s OKRs into the Hoshin Kanri framework.

The first step was building the “What” quadrant, which aligns closely with the Objectives component of OKRs. This helped clarify the strategic direction and ensured that the cybersecurity team’s goals directly supported the CIO’s priorities.

Next, we used the Key Results from the OKRs to define the “How Far” quadrant, establishing measurable annual progress targets.

The following phase involved collaboration between architects and development teams to determine the technical feasibility and implementation requirements. This process proved to be a pivotal moment for the team. For the first time, they clearly understood—early in the year—what would be required to meet the CIO’s expectations.

After this realization, we conducted a pressure test of the expected outcomes, aligning the OKR Key Results with the Hoshin “How Much” metrics. When discrepancies emerged between expected outcomes and realistic capabilities, it became essential to communicate back to the CIO early in the planning cycle to recalibrate expectations.

The “How Much” metrics also enabled development teams to reassess their architectural approach and ensure that their solutions would deliver sufficient impact.

Finally, the “Who” component helped identify the people and skills required to execute the initiatives successfully. This step proved especially valuable because it revealed resource gaps and clarified responsibilities across teams.

---

Conclusion

Combining OKRs with Hoshin Kanri provides organizations with a structured way to translate strategic objectives into operational reality. OKRs define what success looks like, while Hoshin Kanri clarifies how the organization will achieve it and who is responsible.

When used together, these frameworks help organizations:

• Align strategy with daily operations
• Improve cross-functional collaboration
• Identify feasibility constraints early
• Strengthen accountability and execution

If you or your organization wants to learn more about how integrating OKRs with Hoshin Kanri can significantly improve the organization’s ability to turn strategy into measurable outcomes feel free to reach out to me.