Feeling the Grip? Traction Promises Relief
If you are a business owner or leader in a growing company, you have likely felt "the grip" - that moment when the business that was supposed to set you free starts to feel like a prison. Growth stalls, people issues multiply, and you are driving with the emergency brake on.
Enter Gino Wickman's Traction: Get a Grip on Your Business. The book has become the Bible for small to mid-sized businesses looking to scale because it replaces mystique with a practical operating system.
In this deep dive, we will unpack the genius of the Entrepreneurial Operating System (EOS®), explain why self-implementation so often backfires, and show how MonsterOps keeps EOS® traction without the friction.
Part 1: The Book Experience
Traction is not a memoir; it is a manual. The prose is dry, utilitarian, and obsessed with the "how." There is no fluff, only instruction.
That dryness is a strength. Wickman writes for the frustrated entrepreneur who does not have time for theory. Every page is a checklist for regaining control.
The Core Premise: Operating System, Not Another Product
Every business faces the same frustrations: lack of control, people issues, profit woes, and hitting the glass ceiling. The solution is not a new product or a new market; it is a better operating system.
Vision: Make the V/TO a Living Document
Most companies have a mission statement on the wall, but no one knows what it means. EOS® forces you to answer eight questions in the Vision/Traction Organizer (V/TO).
- Core Values: The timeless guiding principles.
- Core Focus: What you are best at (your "hedgehog").
- 10-Year Target: The long-term, audacious goal.
- Marketing Strategy: Your target market and differentiators.
- 3-Year Picture: What the company looks like in 3 years.
- 1-Year Plan: The specific goals for this year.
- Rocks: The 3 to 7 most important priorities for the next 90 days.
- Issues List: The obstacles standing in your way.
Why it works: it forces everyone to row in the same direction.
People: Right People, Right Seats
This is the hardest pill to swallow. Wickman uses a simple quadrant to classify your team.
- Right Person, Right Seat: Ideal - fits the culture and masters the role.
- Right Person, Wrong Seat: Great fit, wrong role - move them.
- Wrong Person, Right Seat: Hits the numbers but hurts the culture - remove them.
- Wrong Person, Wrong Seat: Why are they still here?
The accountability chart makes ownership explicit. It is different from an org chart because it is based on functions and outcomes, not titles and ego.
Data: Run the Business on Numbers
Stop running the business on feelings. Run it on data.
- Scorecard: A weekly report with 5 to 15 leading metrics.
- Leading vs. Lagging: Focus on activity-based numbers you can influence.
- Everyone has a number: each person owns one measurable metric.
Issues: IDS (Identify, Discuss, Solve)
In most companies, problems are either hidden or endlessly debated. EOS® pushes you to IDS until the issue is gone for good.
- Identify the real root cause.
- Discuss it openly.
- Solve it and assign an owner.
Process: Document the 20/80
You cannot scale chaos. Document the core way you do business.
- The 20/80 Rule: Capture the 20% of processes that drive 80% of results.
- Followed by All: Once documented, everyone follows the same playbook.
Traction: Rocks and Meeting Pulse
Vision without traction is hallucination. This component brings the vision to the ground.
- Rocks: 90-day priorities. If everything is important, nothing is.
- Meeting Pulse: The heartbeat of the organization (including the Level 10 Meeting).
The Level 10 Meeting (L10)
A strict, 90-minute weekly meeting for the leadership team. The agenda is fixed:
- Good News: 5 minutes.
- Scorecard Review: 5 minutes.
- Rock Review: 5 minutes (on track/off track only).
- Customer/Employee Headlines: 5 minutes.
- To-Do List: 5 minutes (reviewing last week's tasks).
- IDS (Identify, Discuss, Solve): 60 minutes.
- Conclude: 5 minutes.
Part 3: The Implementation Trap
After reading Traction, you feel energized. The concepts are simple and the path is clear. It is tempting to start self-implementing on Monday.
This is where trouble begins. The concepts are simple; human psychology is not. Discipline and honesty are hard to maintain while also running the company.
Why Self-Implementing is a Nightmare
Because the book is a manual, it does not account for the emotional nuance of your team. When you roll out the accountability chart, people get defensive. When you enforce the scorecard, some feel micromanaged.
Without an external facilitator, the Integrator often becomes the bad cop, nagging everyone to update Rocks or fill out the scorecard. The system meant to liberate you starts to feel like a chore.
The Fragmentation of Truth
Self-implementing also creates a logistical nightmare. Traction was written before the SaaS boom, so teams default to a jumble of files and apps:
- Vision/VTO: A dusty PDF no one opens.
- Rocks: A whiteboard or buried Trello/Asana tasks.
- Scorecard: A fragile Excel file that breaks when someone adds a row.
- Issues List: A Slack channel or running Google Doc.
- Processes: Scattered across Drive, Notion, and email.
This fragmentation kills momentum. You spend more time managing tools than managing the business.
Part 4: The Tooling Dilemma
To fix the fragmentation, businesses reach for one of three software categories. Here is why most of them fail EOS® teams.
1. Project Management Tools (Asana, Monday, ClickUp)
Great for tasks, weak for EOS®.
- They blur the line between a Rock (90-day goal) and a to-do (7-day task).
- They struggle to visualize the V/TO or the accountability chart.
- Result: The vision disappears and teams get stuck in the weeds.
2. Spreadsheets (Excel, Google Sheets)
Flexible but passive. They wait for humans to keep them alive.
- Manual entry invites broken formulas and stale data.
- No ownership or history to track accountability.
- Result: The scorecard is a chore filled out 5 minutes before the meeting.
3. Pure EOS® Software (Traction Tools, Ninety.io)
Built for EOS® purists, but often too rigid.
- Rigidity: Hard to adapt agendas or scorecards to your reality.
- Siloed: Teams log in once a week, then ignore it for six days.
- Result: It feels like an extra tool instead of the main operating system.
Part 5: The Solution - Why MonsterOps Wins
If you want EOS® discipline without rigidity or chaos, there is a gap in the market. MonsterOps fills it.
How MonsterOps Solves It
- The living V/TO: updates to Rocks reflect in the vision automatically.
- Unified workflow: link daily to-dos directly to quarterly Rocks.
- Automated scorecard: integrations and trend visuals flag issues early.
- Customizable meeting pulses: keep Level 10 discipline while tailoring agendas for each team.
- People and accountability: dynamic accountability charts tied to scorecard numbers.
With MonsterOps, the software acts as your Implementer. You get discipline without the handcuffs of rigid, legacy EOS® platforms.
The Verdict
Self-implementing with MonsterOps gives you the structure to keep EOS® alive, without the admin drag of spreadsheets or the rigidity of older tools.
Conclusion: Get a Grip, But Get the Right Gloves
Traction is a masterpiece of business simplification. The V/TO, Rocks, and the Level 10 Meeting change companies, but reading the book is the easy part.
The hard part is keeping the system alive week after week. A shared spreadsheet or scattered docs will not save you. They will slow you down.
Combine Wickman's timeless concepts with a flexible platform like MonsterOps to build an operating system that drives you forward instead of holding you back.
Summary of Key Takeaways
How each EOS® component breaks in self-implementation and how MonsterOps fixes it.
| EOS® Component | The Concept | The Self-Implementation Pitfall | The MonsterOps Solution |
|---|---|---|---|
| Vision | The V/TO (Vision/Traction Organizer). | Becomes a "shelf-ware" document nobody reads. | A live, interactive dashboard visible daily. |
| People | Right People, Right Seats. | Accountability charts are static PDF files. | Dynamic charts linked to performance metrics. |
| Data | Scorecard (5-15 leading metrics). | Manual entry in Excel; broken formulas; lagging data. | Automated tracking; visual trend analysis. |
| Issues | IDS (Identify, Discuss, Solve). | Issues lost in Slack/Email; never truly solved. | Centralized repository; tracks history of solutions. |
| Process | Documenting the 20/80. | Documents scattered in Drive/Dropbox. | Centralized wiki linked to specific roles/seats. |
| Traction | Rocks & L10 Meetings. | Meetings go off-track; Rocks are forgotten until day 89. | Guided meeting agendas; daily progress tracking on Rocks. |