Migration guide
Running Hoshin Kanri alongside Primer
Catchball, the X-matrix, and annual breakthroughs, encoded in Primer's schema, not a spreadsheet.
Respecting the system you already run
Hoshin Kanri came out of Toyota, earned its place through decades of lean practice, and is arguably the most disciplined policy-deployment system in modern management. If your team runs Hoshin, you have invested real time in the catchball ritual and the X-matrix discipline, this guide is not asking you to throw either away. It shows how Primer's schema already carries the concepts you use, so the X-matrix stops living in a spreadsheet and starts living in a model designed for it.
Translating Hoshin Kanri concepts into Primer
The lean community will recognize every row, this is one of the smoothest conceptual fits of any framework in the catalog.
| Source concept | Primer equivalent | Translation note |
|---|---|---|
| Breakthrough objective (Hoshin) | strategic goal | Typically 3–5 per organization, annual. Primer's strategic typing fits exactly. |
| Annual improvement priority | child goal with per metric cadence = 'annual' | Rolls up to a breakthrough via typed goal dependencies. |
| Catchball (negotiation) | the resolution workflow (draft, aligned, leader accepted, superior accepted, committed) | The single closest one-to-one match between any external framework and Primer's internals. |
| X-matrix cascade | cascaded goal plus typed dependency links | The four quadrants of the X-matrix become typed dependency links. |
| Annual / 90-day review | per metric cadence + snapshot locking on the cycle | Locked snapshots match the lean principle of freezing the plan to expose variance. |
Three ways to try Primer alongside what you already run
None of these ask you to give anything up. Pick the lowest cost option you can get away with. Your own data will tell you what fits.
Path 1: Concurrent
Run Primer concurrently
Keep your X-matrix spreadsheet. For one Hoshin cycle, mirror the breakthrough objectives and annual improvement priorities into Primer as goals, and let Primer record each catchball round as a the resolution workflow transition. Compare the catchball history at year-end: the spreadsheet version almost always loses some rounds; Primer preserves all of them.
Path 2: Combine
Combine inside Primer
Replace the spreadsheet X-matrix with Primer's goal dependency view. Every breakthrough, every annual priority, and every cascaded subordinate goal lives in one queryable place, and the catchball negotiation is captured as first-class data instead of Excel comments.
Path 3: A/B test
A/B test one breakthrough
Pick the breakthrough whose catchball usually drags the longest and run it through Primer's resolution workflow while the others stay in the spreadsheet. Ask the team which felt faster.
What Primer contributes beyond the standard Hoshin practice
Hoshin's vocabulary is already rich. Primer's value is in the schema underneath, so the vocabulary stops being enforced by discipline alone.
Typed dependency graph
Typed relationships (blocks, informs, supports) encode the four X matrix quadrants. Your strategy map is a query, not a slide.
Complete catchball history
Every resolution transition is logged in the audit log with who, when, and why. The round-by-round catchball conversation becomes an audit trail leadership can walk years later.
Five-tier rubric for annual scoring
Hoshin typically uses red/yellow/green at review time. Primer's alarm / concern / content / effective / optimized gives reviewers more resolution without adding meetings.
Snapshot-locked baseline
Once the cycle is committed, targets freeze. Lean teams already believe in this discipline; Primer enforces it in the schema rather than relying on culture.
Per-level cadence
Breakthroughs can be annual while the cascaded subordinate goals are quarterly. Primer carries both on the same graph without confusing either. Most X-matrix spreadsheets cannot.
Customization suggestions, code you may want to modify
Hoshin shops tend to be deeply invested in the X-matrix layout. Here are the customizations that make Primer feel like a native Hoshin tool.
X-matrix rendering component
Build an the X matrix view that reads the four categories of typed goal dependencies and renders them as the classic four-quadrant X. Heavy UI work, but the payoff is immediate recognition.
Catchball round counter
Add a derived count on each goal showing how many draft → aligned cycles it took to reach commitment. Surface it in the review view, it becomes a health metric of the practice itself.
Annual Hoshin report template
A PDF route that renders the year-end catchball history and tier scoring in the standard Hoshin report shape lean auditors expect.
Relabel resolution states in Japanese
If your team uses the Japanese Hoshin vocabulary, update the ja.json locale for the resolution workflow state names. Purely a copy change.
90-day review page
A dedicated review route that groups goals by their cascaded ancestor so the Hoshin facilitator can walk top-down through every breakthrough in a single session.
You bought a perpetual source license. Every part of Primer is yours to change. These are suggestions, not requirements.
Let your team discover what fits
Hoshin practitioners usually recognize Primer as a native home for the practice within an hour. Run one cycle and see whether the catchball history alone justifies the switch.
Try it on one breakthrough
Pick a breakthrough whose catchball always drags. Put it into Primer's resolution workflow and see how it lands.