Short answer: choose for the failure you actually have, not the framework with the best book. Most companies do it the other way round and lose a year finding out.
There are four different failures hiding under the phrase "we need alignment," and they do not share a cure. Name yours first. The rest of this article tells you which system fits which failure, where each one leaves you exposed, and the one question most frameworks go quiet on.
Who this is for
Companies of roughly 20 to 250 people. Big enough that alignment genuinely breaks, small enough that nobody is staffed full time to fix it. If you have a corporate improvement department, you have options this article does not cover.
Step one: name the actual failure
"We need alignment" is a symptom. Underneath it sits one of four problems, and they need different tools.
- Focus. Too many priorities and none of them moving. Ask five people the top three priorities and you get five different answers.
- Rhythm. Meetings that end without decisions. Work that gets done twice because nobody owns it.
- Measurement. You find out the score too late to act on it. Problems arrive as damage control.
- Cascade. Strategy is clear at the top and invisible three levels down.
Most companies have two or three of these running at once. Start with the one that costs you the most.
OKR: Objectives and Key Results
Developed at Intel under Andy Grove, popularised by John Doerr and adopted widely at Google. An Objective is the qualitative ambition. Key Results are the handful of numbers that prove you got there. Usually run quarterly.
Strongest at:
- Narrowing attention. It is the sharpest tool available for cutting twenty priorities down to three.
- Transparency. Goals are public, which kills a lot of quiet duplication.
- Stretch. Built to make targets uncomfortable on purpose.
Where it leaves you exposed:
- It tells you what to aim at. It does not tell you who owns it.
- It says almost nothing about engagement, recognition or culture.
- It has no built-in answer for what happens when a goal slips mid-quarter.
Best for: a focus problem. If your team is capable and busy but pointed in five directions, start here.
EOS: the Entrepreneurial Operating System
From Gino Wickman's book Traction. Six components: Vision, People, Data, Issues, Process and Traction. In practice it shows up as quarterly Rocks, a weekly Level 10 meeting, a Scorecard and an Accountability Chart.
Strongest at:
- Operating rhythm. The weekly meeting structure is the best part of it and works immediately.
- Ownership. The Accountability Chart forces the uncomfortable conversation about who actually owns what.
- Small and mid-sized companies. It was designed for exactly this size and it shows.
Where it leaves you exposed:
- Lighter on sophisticated measurement than Balanced Scorecard.
- Prescriptive. You largely take it as designed or not at all.
- Recognition is not built in.
Best for: a rhythm problem. If your meetings end without decisions and nothing has a clear owner, this is your tool.
Balanced Scorecard
Robert Kaplan and David Norton, early 1990s. Measures across four perspectives: Financial, Customer, Internal Process, and Learning and Growth. Usually paired with a strategy map linking cause to effect.
Strongest at:
- Measurement rigour. Nothing else on this list comes close.
- Forcing you to look past financial metrics to the things that produce them.
- Making strategy legible to a board.
Where it leaves you exposed:
- Heavy. Genuinely heavy, both to build and to maintain.
- It frequently degrades into a reporting exercise nobody reads.
- Slow cadence. It is not built for a fast quarter.
Best for: a measurement problem. If you cannot see the score until it is too late, this is the rigorous option, provided somebody will actually maintain it.
Hoshin Kanri
Policy deployment, out of Japanese quality management and the lean tradition. Uses catchball, a back and forth negotiation of goals between levels, and often an X-matrix to map objectives to initiatives, metrics and owners.
Strongest at:
- Cascading strategy from the top of the company to the floor. Better than anything else here.
- Separating breakthrough objectives from business as usual.
- Two-way negotiation, so goals arrive with buy-in rather than as instructions.
Where it leaves you exposed:
- It assumes a mature improvement culture you may not have yet.
- The X-matrix intimidates people and stalls adoption.
- Hard to start from a standing position.
Best for: a cascade problem, in an organization that already has discipline.
The question most frameworks go quiet on
What happens when a goal slips?
Not if. When. Halfway through the quarter, one of your key results is clearly not going to land. What does your system do?
If the honest answer is "we discuss it at the next quarterly," you do not have a system problem. You have an absence of system problem, and no framework on this list fixes that by itself. The framework is the easy part. The discipline of running it on a Tuesday in a busy month is the whole job.
Where CHAMPION fits, honestly
I built CHAMPION™ because across 25 years inside ExxonMobil, Shell, CNRL, TC Energy and Enbridge, on portfolios up to $14 billion, I kept needing all four at once and kept assembling them by hand.
It puts seven tests on every goal before it counts: Challenging, Achievable, Measurable, Purpose-driven, Inclusive, Organized, Nurturing. It adds six defined roles, a live weekly scoreboard, guardrail metrics so a team cannot win the score by breaking something expensive, and recognition inside the cycle rather than bolted on at the end. It asks 2 to 3 hours per person per month.
The honest limitation: it is one system to learn, and if you only have one of the four failures, it is more than you need. I would rather tell you that here than on a call.
How to choose: the short version
- Focus problem, too many priorities: start with OKR.
- Rhythm problem, meetings without decisions: look at EOS.
- Measurement problem, you see the score too late: Balanced Scorecard, if someone will maintain it.
- Cascade problem, strategy stops at the second floor: Hoshin Kanri, if your culture is ready.
- All four at once, and nobody on staff to assemble them: that is the gap CHAMPION was built for.
Whichever you pick, the test is the same six months later. Can five people on your team name the top priority without checking? If not, the system did not take.
Frequently asked questions
Which goal-setting framework is best?
None of them, in the abstract. The best framework is the one matched to your specific failure. OKR for focus, EOS for rhythm, Balanced Scorecard for measurement, Hoshin for cascade.
Can you combine OKR and EOS?
Yes, and many companies do. EOS gives you the weekly rhythm and accountability chart, OKR gives you sharper quarterly targets. The risk is two vocabularies for the same thing, which confuses people. Pick one name per concept.
How long before a goal system shows results?
One full cycle, so a quarter at minimum. Anyone promising faster is selling you the setup, not the outcome.
How much time does this take from my people?
CHAMPION™ asks 2 to 3 hours per person per month. EOS runs roughly 90 minutes weekly for the leadership team. Balanced Scorecard is heavier and depends entirely on your reporting burden.
Do we need software?
No. Every system here can be run on a spreadsheet and a wall. Software helps once the discipline exists. It never creates the discipline.
What is the most common reason these fail?
Nothing holds the goals up after week one. The launch is easy and well attended. The eighth weekly check in a busy month is where systems actually die.
One thing to do this week
Ask five people on your team what the company is trying to achieve this quarter. Write down the answers without correcting anyone.
If you get one answer, you do not need any of this. If you get five, you now know which of the four failures you have.
If you want the structured version, the CHAMPION Readiness Score is 17 questions and about four minutes, and your score appears the moment you finish.