In this guide
Key Takeaways
- →Hoshin and OKRs are not competitors. They work at different altitudes, on different clocks, and most organizations get the most from running both.
- →The pattern that works: hoshin at the top, OKRs underneath, with key results contributing upward.
- →Two conflicts come up reliably: commitment versus aspiration, and bottom-up versus negotiated. Both are settled by labelling and by catchball.
- →Team key results written as outcomes make natural adoption measures, which is what exposes outcome lag in the first quarter rather than the fourth.
- →Two tools means someone reconciles them every month. Buying hoshin software and OKR software separately buys that monthly job along with the licenses.
- →The test that settles it: when a team key result moves, how many systems does that number pass through before the hoshin review sees it?
“Hoshin or OKRs?” is usually the wrong question. The two work at different altitudes and on different clocks. The real question is how to connect them so a team’s key result and the breakthrough it serves aren’t reported in two places.
A false choice
Organizations evaluating hoshin kanri often already run OKRs, or are considering them, and the comparison gets framed as a contest. OKR advocates point to speed, simplicity and team engagement. Hoshin advocates point to focus, explicit correlations and the discipline of catchball.
Both sides are describing real strengths. They’re also describing tools built for different jobs. Hoshin kanri is a deployment system for a few multi-year breakthroughs. OKRs are a goal-setting format that works especially well for teams over a quarter. Many organizations get the most from running both, with a clear line between them.
Different altitudes, different clocks
| Hoshin kanri | OKRs | |
|---|---|---|
| Horizon | Multi-year breakthroughs, annual objectives | Usually quarterly, sometimes annual |
| Altitude | Leadership, divisions, sites | Functions, teams, sometimes individuals |
| Number | A few breakthroughs; a focused set of priorities | A few objectives per team, many across the organization |
| Distinctive device | X-matrix correlations; catchball | Measurable key results; frequent check-ins |
| Target style | Commitments negotiated through catchball | Often a mix of committed and aspirational |
A division of labor that works
The pattern that works well in practice runs hoshin at the top and OKRs underneath.
- Leadership sets breakthrough and annual objectives on the X-matrix, with priorities, KPIs and correlations.
- Each annual priority is carried into the quarter as one or more team OKRs. The team owns the objective; its key results describe the change the priority needs.
- Those key results contribute directly to the hoshin objective above them, so progress flows up without anyone re-entering it.
This has a useful side effect. Team key results are usually written as outcomes, which makes them natural adoption measures for hoshin priorities. A priority measured by “centers opened” becomes, at team level, a key result measured by “contract attach rate in new territories”. That’s exactly the kind of measure that exposes outcome lag early.
Where they conflict
Two tensions come up reliably.
Commitment vs aspiration
OKR practice often encourages stretch goals where hitting 70% counts as success. Hoshin commitments, negotiated through catchball, are meant to be met. Mixed carelessly, nobody knows which kind of target they’re looking at. The fix is to label it: key results that roll into hoshin objectives are committed; team-level aspirational OKRs that don’t roll up can stretch.
Bottom-up vs negotiated
OKRs often emphasize teams setting their own objectives. Hoshin emphasizes negotiated alignment with the level above. The two meet at catchball: the team proposes its OKRs in response to the hoshin priority, and the negotiation settles them.
Hoshin decides what must change. OKRs decide how each team will change it this quarter. The trouble starts when the two are written in different places.
Why they belong on one data model
When hoshin lives in one tool and OKRs in another, the connection between them is maintained by hand. Every month, someone matches team key results to the hoshin priorities they serve and re-enters progress. The connection weakens with each renamed objective and reorganized team, until the two systems describe different plans.
On one data model, the connection is the record itself. A key result checked in by a team lead updates the hoshin objective it contributes to, which updates the correlations on the X-matrix. Nobody reconciles anything.
A worked example: one priority, three team OKRs
An illustrative hoshin priority, “launch multi-year service contracts”, is graded primary against services share of sales. In Q1 it’s carried by three teams.
| Team | Objective | Key results | Weight on the priority |
|---|---|---|---|
| Commercial | Launch the multi-year contract model | Legal approval by 31 March; pricing approved by finance | 40% |
| Service sales | Sell the new contracts in pilot regions | 30% attach rate on new equipment in pilot regions; 40 contracts signed | 40% |
| Finance | Make the contracts reportable | Revenue recognition policy agreed; contracts visible in monthly services report | 20% |
Illustrative. Key results labelled as commitments because they roll into a hoshin objective.
Each team owns its OKR and checks in on it weekly or monthly. The key results contribute to the hoshin priority with the weights shown, so the priority’s progress on the X-matrix reflects real team outcomes rather than a milestone tick. The service sales attach-rate key result doubles as the priority’s adoption measure: if contracts launch on time but attach rate stays low, the matrix shows outcome lag in the first quarter, not the fourth.
What running two tools actually costs
The reconciliation described above is not a small job, and it is the part of the decision that never appears on either quote. It is worth pricing before a shortlist forms, because it changes which route is cheaper.
| What the route requires | Hoshin tool plus separate OKR software | One platform |
|---|---|---|
| Subscriptions | Two, with two renewal dates and two uplifts | One |
| Matching key results to priorities | By hand, monthly, by someone senior enough to judge it | The contribution is the record; no matching step exists |
| When a team is reorganized | The mapping breaks silently and is rebuilt | The link moves with the objective |
| Weighting a priority across teams | A spreadsheet beside both tools | Weights sit on the contribution itself |
| Check-in cadence | Two cadences, two sets of reminders, two adoption problems | One |
| What the review sees | Whatever was reconciled before the meeting | What owners checked in |
Price the route, not the two licenses.
Most OKR software is excellent at the job it was built for: quarterly team goals, check-ins, and keeping a few hundred people pointed in the same direction. Very little of it was built to carry a weighted contribution up into a multi-year breakthrough, because that is a hoshin problem rather than an OKR one. That is not a criticism of the category; it is a scoping question to settle early, because the gap only becomes visible in month two, after both subscriptions are signed. It is also the question that separates OKR tracking software, which is built to keep quarterly goals moving, from OKR management software bought to run a whole goal system.
One question settles most of it, and it is worth asking every vendor on both shortlists: when a team’s key result moves, how many systems does that number pass through before the hoshin review sees it? If the honest answer is more than one, you are buying the monthly reconciliation along with the licenses. Purpose-built hoshin kanri tools vs strategy execution platforms works through the same arithmetic across all three methods, and what drives the cost of hoshin kanri software covers how to total it.
Hoshin and OKRs in Profit.co
Profit.co runs OKRs and hoshin kanri on the same data model. On the X-matrix, each objective shows its contributing key results with their weightings, owners and statuses, and the bowler chart covers objectives and key results together. More on the hoshin kanri software overview.
Both sit in the Essentials plan alongside Balanced Scorecard and Strategy Roadmap, so adding OKRs beneath an existing hoshin program is a configuration question rather than a second purchase, and the same is true in reverse if the OKR program came first. If a board scorecard follows later, that is the same subscription too, rather than balanced scorecard software bought as a third system. The 30-day free trial is long enough to load one hoshin priority with the team OKRs that carry it and watch a check-in roll up, which is the behavior the whole decision rests on.
Free Product Demo
Connect your OKRs to your X-matrix
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
Often both. Hoshin works best for leadership, division and site-level breakthroughs; OKRs work best for team-level quarterly outcomes that carry hoshin priorities into weekly work.
Each annual hoshin priority is carried into the quarter as one or more team OKRs, and their key results contribute to the hoshin objective above them.
On target style, because OKRs often use stretch goals while hoshin targets are negotiated commitments, and on direction, because OKRs often emphasize bottom-up setting while hoshin emphasizes negotiated alignment through catchball.
Only if hoshin stops above team level. If teams set quarterly goals, those goals and the hoshin priorities they serve either share a data model or get reconciled by hand every month, which is a recurring cost neither quote shows.
Carry a weighted contribution from a key result up to a hoshin objective, keep the link when teams reorganize, and run one check-in cadence across both. Most OKR software tools were not built for the first of those.
Yes, if they are labelled. Key results that roll into a hoshin objective are commitments and are meant to be met. Team OKRs that do not roll up can stretch, and nobody should have to guess which is which.
