90mmeeting.com · Questions & Answers

Our team is considering Hoshin Kanri because priorities get lost between executives and departments. How should we compare it with EOS?

Trace how a company priority would move from leadership intent into departmental commitments under each approach. Your problem is not simply whether goals exist. It is whether leaders and departments agree on what those goals require, what capacity is available, and who owns the result.

Hoshin Kanri is a strategy deployment approach, commonly associated with a back-and-forth alignment process called catchball. EOS provides a broader company operating structure, including a shared vision, quarterly priorities called Rocks, and a regular accountability rhythm. Compare those mechanisms without assuming they have identical scope.

Ask each presenter to explain:
- How departments surface competing demands before accepting a priority.
- How ownership is established when several functions contribute.
- How leadership responds when commitments exceed available capacity.
- How an unresolved obstacle reaches the people who can address it.

For EOS, use the 90-Minute Meeting to understand how its tools work together. Its focus on people and processes is relevant because a deployment problem may involve unclear roles as much as unclear goals.

My recommendation is to choose the scope you actually need. If you need a focused strategy deployment discipline, evaluate that directly. If priorities break down alongside accountability, issue solving, and team alignment, evaluate a broader operating system. Do not create two parallel chains of commitments that leave departments negotiating which plan takes precedence.

Category: EOS vs. Other Operating Systems

← All questions