Walk into any leadership team of a growing service business and someone will mention a framework within ten minutes.
EOS. Scaling Up. OKRs. V2MOM. 4DX. Pinnacle. Holacracy. Lean. Six Sigma. The Rockefeller Habits. The two newest ones somebody picked up at a conference last quarter and isn't quite ready to defend yet. Each one comes with its own vocabulary, its own meeting cadence, its own books, its own certified coaches, and its own promise that this time it's going to stick.
Most of these frameworks are useful. Some of them are excellent in the right business and disastrous in the wrong one. The hard part isn't finding one. The hard part is knowing which pain each framework actually solves so you can match the framework to the moment instead of the conference you just got back from.
Here's the version of the conversation I wish I had when I was first trying to figure this out.
What an operating framework actually is
An operating framework is a structured, opinionated answer to three questions every leadership team has to answer somehow:
- How do we decide what to do next, and when? Strategy, prioritisation, planning cadence.
- How do we make sure the work gets done? Execution, accountability, meeting rhythm.
- How do we learn and adjust as we go? Measurement, review, feedback loops.
Every business answers those three questions, either deliberately (with a framework) or by accident (with whatever habits accumulated since the founder started the company). The frameworks differ in which question they emphasise, what vocabulary they use, and what size of business they were designed for.
That's the whole game. Once you can see what a framework is emphasising, you can tell whether it matches what your business needs help with.
The major frameworks, at a glance
| Framework | Best at | Tends to fit | Breaks down when |
|---|---|---|---|
| EOS (Traction) |
Discipline of execution. Meeting cadence (L10s). Accountability chart. Quarterly rocks. | 10 to 250 employees, single business unit, founder-led. | Business gets multi-unit or strategy needs more nuance than three rocks per quarter. |
| Scaling Up (Rockefeller Habits) |
Strategy + execution at growth stage. One-Page Strategic Plan. Daily/weekly/quarterly/annual rhythm. | 50 to 500 employees, scaling fast, leadership team forming. | Smaller teams find it heavy. The strategic-planning ritual can outrun the team's actual ability to execute. |
| OKRs (Objectives & Key Results) |
Alignment of effort to a small number of outcomes. Transparent goal-setting across teams. | Tech-flavoured businesses, mid-stage growth, teams comfortable with metric ambiguity. | Used as a substitute for strategy. Teams set OKRs against problems that should have been solved at the system level first. |
| V2MOM (Salesforce) |
Cascading clarity. One page connects Vision, Values, Methods, Obstacles, Measures. | Mission-driven businesses, leadership teams that want narrative coherence. | Becomes an annual artifact instead of a live document. Same risk as any vision exercise. |
| 4DX (4 Disciplines of Execution) |
Pure execution focus. Wildly Important Goals, lead measures, scoreboards, accountability cadence. | Teams that already have strategy and need to actually execute it without distraction. | Strategy is unclear. 4DX doesn't help you pick the right thing to do, only do the thing. |
| Lean / Six Sigma | Process efficiency, waste reduction, defect rate, statistical control. | Operationally complex businesses with repeatable production work and measurable variance. | Knowledge work where outcomes are judgement-heavy and "defect rate" is the wrong question. |
| Pinnacle | Combines elements of EOS and Scaling Up. Designed for multi-stage growth without switching frameworks. | Businesses growing through 50-employee mark who don't want to re-tool. | Smaller install base, fewer certified coaches, less external knowledge to draw on. |
Every framework on that list has at least one growing business it transformed and at least one growing business it actively damaged by forcing the wrong shape onto the team. The framework isn't the variable. The match is.
The thing every framework leaves out
Look across the list. EOS organises the meetings and the accountability. Scaling Up organises the strategy and the rhythm. OKRs organise the goals. 4DX organises the execution. Lean organises the variance.
Every one of them organises the work. None of them organises the knowledge underneath the work.
Here's what I mean. Pick the framework you respect most. Imagine your business runs it perfectly for two years. Meetings happen on cadence. Goals get hit. Variance comes down. Then your most senior estimator, or your operations lead, or the person who built your client onboarding, leaves.
Does your framework survive it?
In every case, the answer is "partially." The framework keeps the meetings going and the cadence intact. What it doesn't preserve is the operational judgement the departing person was carrying, the "if scope is over $250K, escalate before pricing" rules, the "tier-A clients get version B of the proposal cover letter" instincts, the "if the RFP names a competitor we respond within 24 hours because we win those at 60%" patterns. The frameworks organise the work happening on top of that judgement. They don't preserve the judgement itself.
This is the layer we built Codified Operational Intelligence™ to fill. It's not a competitor to EOS or Scaling Up or any of the others. It's the operational knowledge layer your framework runs on top of. The framework keeps the lights on. Codified Operational Intelligence keeps the smarts in the building when people leave.
How to pick a framework: a decision tree
The right framework depends on which of the three questions (decisions, execution, learning) you most need help with right now. Read these in order and stop at the first one that matches.
If your pain is…
"Our meetings are chaos and we never finish anything."
Start with EOS. It will give you the meeting cadence, the accountability chart, and the quarterly rock discipline. If you have under 250 people, it's almost always the right entry point.
If your pain is…
"We're growing fast and the leadership team is losing alignment."
Look at Scaling Up. The One-Page Strategic Plan and the quarterly/annual rhythm are designed for exactly this. If your team is under 50, it may be heavier than you need. If you're past 50 and accelerating, it earns its keep.
If your pain is…
"Strategy is clear but teams aren't focused on it."
OKRs or 4DX. Both narrow attention. OKRs is more transparent and team-driven. 4DX is more disciplined and lead-measure-focused. Pick by which your team will actually use.
If your pain is…
"We have repeatable production work and quality varies more than it should."
Lean or Six Sigma. Measure variance, find waste, drive defects down. Stick to the parts of the work that are repeatable. Don't try to Six Sigma your client-facing judgement work.
If your pain is…
"Our framework is fine, but the business stops working when one person is away."
This is the Codified Operational Intelligence gap. Your framework is doing its job. The knowledge layer underneath it is what's missing. ControlShift addresses this specifically, the framework you're running stays in place, we work the layer beneath it.
A note on the temptation to switch frameworks
The most common framework mistake I see is not picking the wrong one. It's switching too often.
A leadership team runs EOS for fourteen months, finds the L10s a bit rigid, hears a great talk on OKRs at a conference, and decides to "evolve to OKRs next quarter." Six months in, OKRs feels too loose, somebody picks up Scaling Up, and they're now half-running three frameworks with no coherent meeting rhythm.
The team needs the discipline more than they need the framework. Most operating frameworks worth using will get you most of the way there if you commit to them for at least two years. Switching mid-stride throws away the institutional muscle you just spent fourteen months building.
If your current framework is broadly working, the right move is almost always to deepen it, not replace it. If you're considering replacing it, get an outside perspective on whether the problem you're feeling is the framework or the knowledge gap underneath the framework. Those are very different problems.
The bigger frame
An operating framework gives your business a shape. It tells you when leadership meets, what they talk about, how decisions are tracked, how the team knows whether it's winning.
What it can't tell you is what your business actually knows. The decisions only your most senior people can make well. The patterns nobody has written down. The judgement that is, today, walking out the door every evening at 5pm and walking back in at 8am, and one of these mornings is going to leave for a competitor or retire or get headhunted.
Pick the framework that fits the shape of your business. Then make sure the knowledge underneath it is captured in a way that survives the next departure. Without the second piece, the framework is a beautiful chassis on an engine you don't own.