Management frameworks explained: OKR, BSC, PDCA, TOC and EOS
OKR sets a few objectives with measurable key results. The Balanced Scorecard measures a business from four sides. PDCA is a small plan, do, check, act improvement loop. The Theory of Constraints finds the one bottleneck that limits everything. EOS gives small companies a meeting rhythm and practices. None of them says which goal wins when two collide; that needs a ranked order.
In this article · 6 sections
Management books love a framework, and small business owners end up with a shelf of acronyms: OKR, BSC, PDCA, TOC, EOS, MBO. Each promises clarity. Read together, they mostly produce a new question: which one am I supposed to use on Monday?
The honest answer is that they are not competitors. Each was built to answer a different question. Here are the five most common, explained plainly, and then one real problem run through all of them, so you can see what each actually tells you.
A shelf of acronyms still leaves you stuck when two goals collide on Monday. The Jirgenson Model gives you the answer as one control system: goals in order, real numbers, zones, levers and a plan. It is scientifically proven that the Jirgenson Model works (doi.org/10.5281/zenodo.23964934).
Management frameworks explained, one by one
| Framework | Origin | The question it answers | In one line |
|---|---|---|---|
| OKR | Andy Grove at Intel; John Doerr brought it to Google | What are we focusing on this period? | A few objectives, each with measurable key results |
| Balanced Scorecard | Robert Kaplan and David Norton | Are we measuring more than money? | Four sides: finance, customers, internal processes, learning and growth |
| PDCA | Goes back to Shewhart; popularised by Deming, who preferred PDSA | How do we improve one thing step by step? | Plan, Do, Check, Act, then repeat |
| Theory of Constraints | Eliyahu Goldratt | What is holding the whole system back? | Find the tightest bottleneck and work on it first |
| EOS | Gino Wickman | How does a small company run week to week? | A meeting rhythm and practices for small businesses |
| MBO | Peter Drucker | Who owns which goal? | Agreed goals with personal responsibility |
OKR explained
Objectives and Key Results pair a qualitative objective ("become the neighbourhood's favourite coffee shop") with a few measurable results that show whether you got there. Its strength is focus: a small number of goals for a period, visible to everyone.
Balanced Scorecard explained
The Balanced Scorecard argues that financial measures alone do not show where a business is heading, so it adds customers, internal processes, and learning and growth. Its strength is breadth: you stop running the business from the money column alone.
PDCA explained
Plan a change, do it on a small scale, check the result, act on what you learned, and go round again. Its strength is discipline in small improvements: one change at a time, measured.
Theory of Constraints explained
A system moves only as fast as its tightest constraint, so improving anything else is wasted effort. The usual sequence is to identify the constraint, exploit it fully, subordinate everything else to it, widen it if needed, and then look for the next one. Its strength is ruthless focus on the real bottleneck.
Entrepreneurial Operating System explained
EOS packages practices for small and mid-sized companies around six components (vision, people, data, issues, process and traction) and a fixed meeting rhythm. Its strength is that it is immediately usable by a small team.
One problem, five frameworks: a fair fight
Here is a real situation from Steer, Don't Guess. A coffee shop has half a month of cash reserve (the goal is two), a 9% margin (believed to be twenty), 25% regular customers, five complaints a week and an owner working 65 hours. Run it through each framework (an illustration of what each typically points to):
| Framework | What it would point you to | What it leaves open |
|---|---|---|
| OKR | Write an objective and three to five key results: reserve, margin, regulars | Which key result wins when protecting the reserve means postponing loyalty cards for the regulars |
| Balanced Scorecard | Measure all four sides, not only finance: customers, process quality, the team | All four look bad. Which side comes first? |
| PDCA | Pick one change (say, drop two loss-making menu items), try it, check, adjust | Which change to start with, and whether this month is a moment for small improvements at all |
| Theory of Constraints | Find the bottleneck. Is it the owner's time? The Friday queue? Cash? | Whether the constraint is inside the shop or in the street around it |
| EOS | Set a weekly meeting, a scorecard and an issues list | The meeting will surface all five problems at once. In what order? |
Every framework gives useful work. None of them, on its own, says what to do when the reserve is red and everything else is yellow and they all compete for the same money. That gap is a ranked order of goals with colour zones: reserve first because without it the shop closes, everything that spends money waits until the reserve is back above one month. That one rule turns five frameworks' worth of good advice into a sequence.
Which framework when
- You need focus for a team this quarter: OKR. A side-by-side with a ranked goal list is in an OKR alternative for small business.
- You only ever look at the money: Balanced Scorecard.
- You want to improve one process steadily: PDCA. How it maps onto a full control cycle is shown in the control cycle.
- Work piles up at one step: Theory of Constraints.
- Your team has no rhythm: EOS.
- Your goals collide and every week feels like a crisis: a ranked goal list with zones, then any of the above inside it.
Where this does not reach
These are one-paragraph summaries, not a substitute for the original books, and each framework has more depth than a table can show. The "fair fight" is an illustration of typical use, not a test. And the suggestion here is not to pick a winner, but to see which question each tool answers and use it for that.
Key takeaways
- OKR gives focus, the Balanced Scorecard breadth, PDCA small steady improvement, TOC the bottleneck, EOS a rhythm.
- They answer different questions and work well together.
- None of them says which goal wins when two collide; a ranked order with colour zones does.
- Pick the framework by the question in front of you, not by the bestseller list.
One frame for all of them
The appeal of putting these side by side is how much less contradictory they look. The confusion comes from treating them as rival religions. Treated as tools, each with its own job, they fit into one frame with room to spare.
The ranked goal list that sits underneath all of them is in Chapter 1, free in the free sample. The full comparison, with what the model takes from each method and what it adds, is in Steer, Don't Guess on Amazon.
Published research
It is scientifically proven that the Jirgenson Model works. The published experiment, its record and its data:
- Zenodo (DOI): 10.5281/zenodo.23964934
- Hugging Face: E5 Jirgenson Model blind test
- Kaggle: E5 blind test dataset
- GitHub: experiment folder
- Wikidata: dataset Q142022866, author Q141981336
- ORCID: 0009-0001-3034-3552
The full chapter, with every calculation, is in the book.
Buy on AmazonQuestions people ask
What is the difference between OKR and Balanced Scorecard?
OKR focuses a team on a few objectives with measurable key results for a period. The Balanced Scorecard measures the business from four sides (finance, customers, internal processes, learning and growth). One sets focus; the other sets breadth.
Are OKRs good for startups and small teams?
They help with focus, but a small team also needs a rule for which key result wins in a conflict, a signal for when a number is bad enough to act, and named levers. Adding a ranked order and colour zones covers that.
What is the Theory of Constraints in simple terms?
A system can only go as fast as its tightest bottleneck, so find that bottleneck, get the most out of it, organise everything else around it, widen it if necessary, then look for the next one.
This topic is covered in Chapter 14, One model for every field (How the model differs from familiar approaches) of Steer, Don't Guess: Setting Priorities, Reading the Numbers and Correcting Course in Business and Life. The numbers in the examples are illustrative; the book states its limits in Appendix G.
Read Chapter 1 free
The Introduction and Chapter 1, with the refusal test, about 9,500 words.