Hoshin Kanri (policy deployment)
Picks a few breakthrough priorities and deploys them through bidirectional catchball dialogue, an X matrix linking objectives to owners, and monthly plan do check act reviews that turn strategy deployment into a disciplined, recurring learning cycle.
Yoji Akao and Japanese TQM practitioners, 1960s
The origin of the framework, as the directory records it. The mark grades the origin, not this page.
Umbrex, Hoshin Kanri (policy deployment)
The directory entry this score was read from. Umbrex is a consultancy network; its summary is the reference, not a primary source.
Scored against the twelve cells, it loads three: Strategy, Learning, and Coordination. The other nine it leaves to you. None of Composition, Evidence, or Mastery is among them, which is the usual result in this directory: the questions an agent in the loop raises first are the ones the literature answers least.
The library already carries it as Hoshin kanri, and that entry holds the full sources and the cells in detail.
This is not a summary of the framework. Umbrex has one; the link under Sources goes there.
Where on the evolution curve does each capability sit, and does that dictate build, buy, or let go?
How does tacit judgment become reusable, and who owns the loop that has to close?
What synchronizes the work when there is no room and half the team is not a person?