Traction by Gino Wickman is a business operating system that became the foundation for EOS (Entrepreneurial Operating System). It provides a structured framework for execution: rocks (90-day priorities), scorecards, level-10 meetings, issue lists, and vision-traction organizer. Businesses that implement it consistently produce better execution than those without it. What Traction is not: a financial diagnostic. It has no MMP calculation, no Layer Cake, no Working Capital Gap. Its scorecards measure what the leadership team decides to measure. Diagnostic depth depends entirely on what the leadership already knows to ask.
The Two Different Questions
Traction (Gino Wickman) answers: "Is the leadership team executing on the agreed priorities?"
The Aldebert Diagnostic answers: "Can the business fund MMP at its operating floor?"
Two different questions. Both matter. Confusing them is where owners lose time and money.
Side by Side
| Traction (Gino Wickman) | The Aldebert Diagnostic (RTO + MMP + Layer Cake) | |
|---|---|---|
| Primary job | Business operating system for execution | Financial diagnostic on business health |
| Core question | Are we executing our plan? | Can we fund MMP at our floor? |
| Framework focus | Rocks, scorecards, meetings, issues | MMP, Layer Cake, Working Capital Gap |
| Primary users | Leadership teams, integrators, visionaries | Owner-operators and their advisors |
| Cadence | Weekly level-10 meetings, quarterly rocks | Continuous diagnostic reading |
| Output | Execution accountability, agreed priorities | MMP, Layer Cake, Breakeven, written verdict |
| Diagnostic content | None built in; depends on leadership's chosen scorecards | Full Aldebert doctrine pre-built |
| Best use | Companies with execution gaps | Companies with diagnostic gaps |
What Traction (Gino Wickman) Does Well
Traction addresses a real problem well. Leadership teams that meet without structure produce vague accountability. Priorities drift. Issues get discussed but not resolved. Metrics are not tracked. Traction fixes this with a repeatable weekly and quarterly rhythm. Companies that implement it consistently see measurable improvement in execution discipline. The framework is portable across industries. The book, the coaching community, and the Wickman-affiliated implementers all support consistent adoption.
What the Aldebert Diagnostic Adds
Traction manages execution. It does not diagnose whether the plan being executed is financially sound. When a leadership team's rock is 'grow revenue by 25 percent,' Traction ensures the team executes on that rock. It does not ask whether 25 percent growth at Realized Gross Margin funds the working capital growth that comes with it, whether MMP restates upward as the rock is executed, or whether Layer Cake clears with the incremental hiring the rock implies. The Aldebert Diagnostic answers those questions. The leadership team then executes on rocks that have been diagnostically validated rather than aspirationally set.
The Rock Test
In Traction, quarterly rocks are the top 3 to 7 priorities for the leadership team. They are what has to get done in the next 90 days. Rocks that get executed produce forward motion. Rocks that get missed produce discussion and reset.
The framework provides no tool for testing whether a rock is financially sound before it is set. If the leadership sets a rock to 'launch a new service line,' Traction manages the execution. It does not ask whether the new service line's Layer Cake clears at the initial pricing, whether the ramp period consumes working capital the business cannot spare, or whether the sales team's incremental headcount to support it clears at the restated MMP.
The Aldebert Diagnostic runs those questions before the rock is set. Rocks then become financially validated priorities rather than motivated guesses. Execution against diagnosed rocks compounds. Execution against undiagnosed rocks sometimes wins and sometimes accelerates a hidden failure.
How They Work Together
Traction and Aldebert Diagnostic stack cleanly. Diagnostic sets which priorities are worth pursuing. Traction executes on those priorities with weekly accountability. The scorecard in Traction can include MMP coverage, Working Capital Gap, and Realized Gross Margin as measured leading indicators. The rocks become tied to specific diagnostic outcomes rather than to hope. This is how EOS implementations at more sophisticated businesses actually run.
Frequently Asked Questions
Is Traction the same as EOS?
Traction is the book. EOS (Entrepreneurial Operating System) is the certified implementation methodology built on Traction, delivered by trained implementers. Same core framework.
At what revenue does Traction make sense?
Anywhere from $500K to $50M+ can benefit. Below $500K, the leadership team is often just the owner, and the meeting cadence is less useful. Above $50M, enterprise-grade frameworks may fit better. Sweet spot is $2M to $25M.
Can Traction fix a diagnostic gap?
No. Traction manages execution. If the underlying business economics are broken, better execution of a broken model produces faster failure. Diagnose first, then execute.
What if my EOS implementer says my rocks are fine?
EOS implementers coach on execution and framework adoption. They are not typically trained on MMP or Working Capital diagnostics. Ask specifically whether they build financial diagnostics for the rock-setting process. Most do not.