Traction: Get a Grip on Your Business

By Gino Wickman

12 min read

Why does it matter? Because the chaos in your business isn't bad luck — it's a missing system.

You've hired better people. You've rebranded. You've brought in a consultant, read the book they recommended, tried the framework from that conference. And for about six weeks, something shifted — then the old gravity pulled everything back. Here's what nobody told you: the problem was never the initiatives. It was that you were stacking fixes on top of a business with no operating system underneath them. No common language, no shared rhythm, no structural logic holding the pieces together. Gino Wickman's argument is blunt — most companies under fifty million in revenue aren't failing from lack of ambition or talent. They're failing from chaos dressed up as busyness. EOS gives you six interlocking disciplines that, applied consistently, stop the founder from being the system. Read this and you'll have the vocabulary to finally diagnose what's actually broken — because it's almost never what you think it is.

You're Not Uniquely Broken — You're Just Running Without a System

Most entrepreneurs living inside chaos aren't doing something wrong — they're doing exactly what almost every founder does. Gino Wickman has worked hands-on with over a hundred and twenty leadership teams, and he's catalogued the same five breakdowns every time: the founder can't control their time or their company, the people around them won't align, profit stays thin, growth hits a wall, and every attempted fix fails to stick. If you nodded at two or three of those, you're not uniquely broken. You're in the majority. Wickman's figure — drawn from that same body of client work — is blunt: most organizations run below fifty percent of their potential, and the ones that survive often do so in spite of themselves, not because of anything deliberate.

The actual problem isn't effort or intelligence or strategy. It's that most founders are running a complex organization without any coherent operating system underneath it. Wickman shows what this looks like in practice: two capable leaders on the same team, one calling something an 'objective,' the other calling it an 'action item,' both assuming they're aligned. They're not. That invisible friction — duplicated across every meeting, every department, every hire — compounds into the exact symptoms you've been blaming on your industry, your market, or your people. The chaos isn't the disease. It's the symptom of missing structure.

That reframe matters because it changes what you do next. A character flaw is hard to fix. A missing system can be installed. Wickman's argument, stripped down: predictable problems have learnable solutions, and the five frustrations you've been living with are just the most common ways an unmanaged organization announces itself.

The Thing Keeping Your Business Small Is You

Imagine an entrepreneur dangling from a cliff — not at the top, not at the bottom, just suspended. A voice from above tells him the only way to safety is to let go. He looks up and asks: 'Is there anybody else up there?' That hesitation is not cowardice. It's the most natural thing in the world. The vine is the only thing that's kept him alive this long. Of course he doesn't want to release it.

Wickman uses this image to name something founders rarely say out loud: the thing keeping your business small is your grip on it. The 80-hour weeks, the hand in every department, the final say on every decision — these aren't signs of dedication. They're a structural ceiling. One person can only make so many calls, catch so many fires, approve so many invoices. At a certain size, the founder's control stops being the engine and starts being the bottleneck.

The exit from this trap isn't working harder. Wickman identifies five abilities required to break through: simplify the organization so it doesn't depend on one person's institutional memory; delegate responsibilities to people who are genuinely better at them than you are (and that last clause is where most founders quietly stop reading); predict short and long-term so the company has direction rather than just momentum; systemize the core processes so the work gets done the same way whether you're watching or not; and structure the organization so accountability is built into the chart rather than managed personally by you.

Notice what's not on that list: hustle, vision, passion. Those got you here. These five are what get you through. The founder who insists on staying chef, head waiter, and dishwasher isn't running a restaurant — they're running a one-person show with staff watching. Letting go of the vine isn't an act of surrender. It's the only move that actually works.

A Vision Locked in Your Head Is Not a Strategy

Rich Broder and Todd Sachse ran a successful real estate management company. Then a stranger walked in with an offer: buy an industrial building, lease it back to him, and become partners in an engine powder-coating business. Customers were already lined up. On paper, it looked like a million dollars. Eighteen months and three hundred thousand dollars later, they shut it down. They never should have opened it — and the question that would have killed the deal on day one is the simplest one: what business are we actually in? Real estate management and industrial coatings share nothing: no customers, no expertise, no operational overlap. A written core focus would have answered that question before anyone got on a plane. The company now has a name for deals like that one — CCT, after Capital Coating Technologies — and whenever something shiny catches someone's eye, that's what they call it.

The CCT trap isn't a story about greed or stupidity. It's what happens when a leadership team has no explicit core focus. When you haven't written down exactly what business you're in and why, every opportunity that crosses your desk gets evaluated against nothing. It looks good because you have no filter.

A vision that lives only in the founder's head can't govern decisions made by anyone else, and it can't protect you from your own distraction. Wickman's tool for solving this is a two-page document called the Vision/Traction Organizer, built around eight questions a leadership team answers together. Most teams have never formally answered all eight — and the ones that sting the most are the ones that sound obvious: What is our core focus? What does this company look like in three years, specifically? What are we going to finish this quarter, and who owns it? The point isn't the document. Until five people in a room have argued through those questions and written down the same answers, they don't actually share a vision. They share a general feeling about where things might be headed, which is a different thing entirely.

And even once it's written, it has to be repeated. Wickman is specific about the number: seven. Not because the message changes — because belief takes repetition, and the first three deliveries are just paying the skepticism tax. The leader's job isn't to say it once and move on. It's to say it again, and again, until the message stops being an announcement and starts being the air everyone breathes.

'Good People' Is Not a People Strategy

Every leader who credits their success to 'surrounding myself with good people' is saying something true and almost completely useless. The phrase sounds meaningful until you try to act on it. Wickman's framework makes it mechanical: right people means they share your core values, right seat means they're operating inside their genuine strengths. Both have to be true simultaneously, or you have a problem.

The People Analyzer handles the first half. List your core values across the top of a grid, put names down the side, rate each person plus, plus-minus, or minus for each value. Set a minimum bar — Wickman recommends no minuses, no more than two plus-minuses for a five-value company — and anyone below it gets a structured conversation and thirty days to change, twice. If they haven't moved by the third conversation, they go. Here's where it gets uncomfortable: when you run this on someone you genuinely like, someone who's been around for years, and they come out with two minuses, the tool has done its job. You no longer have a judgment call. You have a result. Most people, once the standard is explicit, either rise to it or self-select out.

The seat question runs through three filters — does this person get the role, want the role, and have the actual capacity to execute it — and a single no on any of them ends the conversation.

The single most consequential seat in most organizations is the Integrator: the person who runs day-to-day operations, manages the leadership team, and translates ideas into execution. Wickman draws a sharp line between this and the Visionary role, typically the founder, who generates ideas, tends major relationships, and sets cultural direction. These two functions require completely opposite wiring, and when one person tries to do both, neither gets done well.

Bruce and Dan at Asphalt Specialists, a $40M paving company, were co-running everything — and running it badly, into their first unprofitable year in company history. Working through the Accountability Chart forced a recognition neither had made explicit: Bruce was a Visionary, Dan was an Integrator. Once they separated into those distinct roles, the company had its most profitable year on record, during the worst construction downturn the region had seen in two decades. The business didn't change. The structure did.

Wickman's observation across client teams: when you finally remove the person who shouldn't be there, the discomfort is real but brief — about thirty-six hours. Everything before that moment is the actual cost. Stop paying it.

Your P&L Is Already Out of Date — Here's What to Track Instead

Rudolph Giuliani walked into City Hall in 1994 inheriting a city that had normalized its own chaos. The NYPD's standard measurement system tracked arrests made and response times — both reasonable things to count, both useless for stopping crime. By the time those numbers appeared in a quarterly report, the pattern had already shifted. You weren't reading the city; you were reading its obituary.

Giuliani replaced that system with CompStat: daily and weekly crime-activity data, broken down by precinct, visible to commanders in near real time. The shift sounds small. The results were not. Over eight years, murders fell almost seventy percent. Overall crime dropped by roughly the same margin. The difference between the old system and the new one wasn't more resources or tougher policies. It was the difference between trailing indicators and leading ones. Trailing indicators tell you what already happened. Leading indicators tell you what's about to happen — and give you time to intervene.

Your business has the same problem the NYPD had: you're measuring the wrong things at the wrong interval. Your profit and loss statement is a trailing indicator. By the time it shows declining revenue, the problem is months old. The sales pipeline dried up in Q1; the P&L reflects it in Q3. You're not reading your business — you're reading its recent past.

Wickman's answer is a Scorecard: five to fifteen weekly activity-based numbers, each owned by one specific person on your leadership team. Not the person who enters the data — the person accountable for the result. Sales leads generated, appointments scheduled, customer satisfaction ratings, accounts receivable aging. Consider what 'sales leads generated' tells you that revenue doesn't: revenue shows you what closed last month; leads show you what's coming next month, while you still have time to do something about it. These are the CompStat numbers for your business — the pattern while you can still redeploy resources, fix the process, or address the problem before it lands in the P&L.

The practical discipline is simple. Track thirteen weeks at a glance — because a full quarter of data is the minimum needed to distinguish a blip from a pattern. Flag any number that misses its target in red. Review it every week without exception. After a few months, patterns emerge, and patterns are predictive. You stop reacting to last quarter's bad news and start steering toward next quarter's results. That's the actual job.

The Real Problem Is Almost Never the Problem You're Arguing About

What if the recurring fight on your leadership team — about communication, about accountability, about that one department that never delivers — isn't actually about any of those things? Wickman's answer is almost certainly yes. The stated problem is almost never the real problem. It's a symptom, and teams that keep arguing about symptoms never run out of material.

The discipline he proposes is called IDS: Identify, Discuss, Solve. The sequence matters, and most teams violate it immediately by skipping straight to Discuss. The Identify step is where the real work happens — peeling back the stated issue until you reach the root.

Here's what that looks like. A warehouse manager named John has been complaining that his customers are unreasonable for expecting two-day delivery. The team takes this at face value and starts debating whether the expectation is fair. Push a layer deeper: is the communication with customers the problem? Push again: is the process broken? One more layer: the two-day window is entirely reasonable, and every other warehouse in the industry manages it. The real issue is that John lacks the capacity to run the function. John is in the wrong seat. The customer complaint was never about the customer. Once that's clear, the solution is obvious — and it takes about three minutes to decide.

Notice what happened: the Discuss and Solve steps collapsed once the Identify step was done accurately. Most teams do it backwards. They spend an hour debating a symptom, reach an inconclusive "let's revisit this," and schedule a follow-up meeting to have the same argument again. That's not dysfunction. That's the predictable result of skipping step one.

Wickman also gives you a rule for the moment after IDS surfaces what the problem actually is: you have exactly three options — live with it, change it, or end it. If you won't change it and you won't end it, agree to live with it and stop bringing it up. Most teams quietly choose a fourth option that isn't on the list: complain indefinitely while doing none of the three. That's not a strategy. That's just noise.

The Unglamorous Mechanics That Separate Vision from Results

Picture a glass cylinder sitting on a table, surrounded by rocks, gravel, sand, and a glass of water. Most people pour the water in first — the small, ambient stuff — then the sand, then the gravel, and finally discover the rocks don't fit. That's not a time management problem. That's a sequencing problem. Wickman borrows this image from Stephen Covey to make a point that sounds obvious and is almost universally ignored: if you don't put the big priorities in first, they will never fit.

That's the logic behind Rocks. Every quarter, the leadership team identifies three to seven outcomes that have a clear deadline and a single owner — not goals you're working toward, but things that will either be done or not done by the end of the quarter. When two people own a Rock, no one does. Eighty percent completion is the target, and it's enough to build something great. The 90-day window isn't arbitrary — Wickman observed across hundreds of leadership teams that humans reliably lose focus around that interval. Fighting it is futile. Building the rhythm around it is the whole point.

Rocks without a meeting structure are just a list that fades. The Level 10 Meeting closes that gap. Ninety minutes, same day, same time, every week, non-negotiable. The agenda runs in fixed order: a quick personal check-in — one word on how you're walking in — then a quick pass through the Scorecard, Rock status, and last week's to-dos, roughly thirty minutes of reporting. Then sixty full minutes of IDS: identifying, discussing, and solving the week's most pressing issues. One meeting, one sheet of paper, no minutes required. The rigid structure isn't bureaucratic; it's what keeps the best part of the meeting — the problem-solving — from getting crowded out by catching up.

Most leaders can describe where they want to go with real conviction. Almost none have a designed system for getting there. Rocks tell everyone what matters most this quarter. The Level 10 Meeting confirms, every seven days, whether you're still moving toward it. Neither is glamorous. Both are exactly what separates organizations that execute from ones that just intend to. Closing the distance between that description and Tuesday is the whole job.

The Business That Doesn't Need You

Here's the closing most founders won't want to hear: every tool in this system — the Vision, the Scorecard, the Rocks, the meetings, the right people in the right seats — points at one destination. A business that runs when you're not there. Not because you've given up, but because you've actually finished building something. Most founders treat their indispensability as proof of their value. It's actually proof of an incomplete job. The founder still white-knuckling that vine isn't heroic — they're just afraid to find out what's underneath them. And here's what Wickman's hundred-plus leadership teams keep discovering: once they let go, there's ground. Solid, built ground. The business doesn't collapse without your daily grip. It finally gets to stand on its own — which is what you said you wanted when you started it.