Hoshin Kanri for COOs: close the gap between strategy and Linear

Strategy lives in slides; execution lives in Linear or Jira. Between the two sits a translation layer — usually you, the COO, rebuilding a status deck every month from sprint boards, chat threads and memory. The symptoms are always the same:

• Projects in the execution tool that nobody can trace to a strategic objective — shadow work that consumes real capacity.
• Strategic initiatives with no execution project behind them — strategy theater that looks green until the quarterly review.
• Status meetings that spend their time collecting status instead of arbitrating, because the data was never fresh in one place.

Hoshin Kanri draws a hard boundary. The X-Matrix holds the why and the what: objectives, initiatives, KPI targets, correlations, reviews, decisions. Your execution tool keeps the how: issues, sprints, assignments, daily tracking. The bridge is one field — each initiative carries an external_ref pointing to its execution project.

There is deliberately no task management, no Gantt chart and no duplication of issues in the matrix. Anything that would require your teams to maintain the same information in two tools is a design error the platform refuses to make — because that duplication is exactly what kills strategy tools by March.

Connect Claude (or Cursor) to the Hoshin Kanri MCP server next to your Linear or Jira MCP — OAuth, about two minutes each. Then the built-in weekly_sync prompt runs the loop every Monday:

• Reads the initiatives in the South quadrant and their external_ref links.
• Pulls progress and blockers from each linked project through the execution tool's own MCP.
• Updates initiative statuses in the matrix — the strategy is now as fresh as the sprint board.
• Flags drift in both directions: execution projects mapping to no initiative, initiatives linked to nothing.
• Drafts the weekly review agenda: off-track KPIs, blocked initiatives, decisions pending.

The West quadrant holds the KPIs, and each one is correlated to the objectives and initiatives it is supposed to prove. That correlation is what turns a dashboard tour into a review: the question is never "what does this number say?" but "which strategic bet does this number confirm or refute?".

The completeness score audits the indicator set itself — including the leading/lagging balance. An operations dashboard that only contains lagging indicators tells you where you failed after the fact; the score pushes you to instrument the leading signals while there is still time to act.

Replaced: the Sunday-evening status deck, the meeting that collects status instead of deciding, the quarterly surprise where an initiative turns out to have been dead for two months, and the role of human middleware between strategy and execution.

Not replaced: your project management tool (Linear, Jira, Asana keep the how), your BI stack (measurement data and time series stay where they are). Hoshin Kanri holds the strategy layer and stays linked to both.