Organizational Checkup: The 20-Question Score That Shows Where Your Business Is Actually Breaking

Hand your leadership team the twenty statements of the EOS Organizational Checkup, ask each person to score the company privately, and the numbers will not match. One leader rates the business a 78. Another, sitting in the same meetings and running the same company, lands at 52. The average of those two is a tidy 65, and the average is almost useless. The twenty-six-point spread between them is the real finding. It tells you the people at the top of the company do not agree on how healthy the company is, and that disagreement is usually the first thing worth fixing.

I run this exercise with nearly every leadership team I start with, because it is the fastest honest read I know of. Founders at $3M to $20M tend to carry a single gut-level verdict on the business: “we’re doing fine,” or “everything is on fire.” Neither is a diagnosis. Both are a mood. The Organizational Checkup converts the mood into a score you can act on, broken out by the specific parts of the operating system that are strong and the ones quietly dragging everything else down.

The reason it matters is simple. You cannot fix what you have not honestly measured, and most owners are measuring with an instrument they cannot trust: their own confidence. The checkup replaces confidence with evidence, and evidence is what tells you which fire to walk toward first.

What the Organizational Checkup Actually Measures

The Organizational Checkup is a twenty-statement diagnostic from Gino Wickman’s Traction that scores how strong your company is across the Six Key Components of a Business Operating System: Vision, People, Data, Issues, Process, and Traction. Each person rates each statement on a 1-to-5 scale, where 1 means the statement is almost never true of your company and 5 means it is consistently true. Add it up, convert to a percentage, and you get a single number out of 100 alongside a breakdown by component.

Statements read like plain truths a healthy company should be able to agree with: everyone in the organization is truly the right person in the right seat, we have a proven process for doing business and everyone follows it, we have a scorecard that gives us a weekly pulse on the business, we identify and solve issues promptly rather than letting them fester. You are not rating ambition. You are rating what is actually, reliably true today.

That distinction is the whole point. A low score is not a grade on your worth as a founder. It is a map. The components where you score a 2 are not character flaws, they are unbuilt systems, and systems can be built in a quarter once you know which ones are missing.

Why a Number Beats a Gut Feeling

Leaders are poor judges of their own organizations for the same reason they are poor judges of themselves. Organizational psychologist Tasha Eurich studied nearly 5,000 people and found that about 95 percent believe they are self-aware while only 10 to 15 percent actually are. The gap does not close because you are smart or experienced. It closes when you get structured outside input. The checkup is structured outside input, pulled from the handful of people who see the company from the inside at the altitude you do.

The cost of skipping that input shows up in execution. Research by Mankins and Steele, published in Harvard Business Review, found that companies on average deliver only 63 percent of the financial performance their strategies promise. The strategy is rarely the problem. The missing systems underneath it are. When a leadership team cannot name which component is weakest, it defaults to working on whatever is loudest that week, and the 37-point gap between promise and performance never closes because nobody ever agreed on where it was coming from.

There is also a growth case. A Gallup-validated study of 305 companies tracked over five years found that businesses running EOS with a professional implementer grew 2.8 times faster than a matched control group. You do not capture that kind of difference by trying harder. You capture it by installing the components the checkup measures, in the order the checkup tells you they are broken.

How to Run It So the Score Means Something

The mechanics matter more than most teams expect. Do not fill it out together in a conference room, because the loudest voice will anchor everyone else and you will lose the exact disagreement you are trying to surface. Have every member of the leadership team score the company independently, in private, before anyone sees another person’s answers. Then put the individual scores side by side.

Read the spread first. The statements where the team is tightly clustered, high or low, are settled questions. The statements where one person scored a 5 and another scored a 2 are where the real conversation lives. A wide range on a single statement signals a dissonance inside the organization: people are seeing different companies, which usually means information is not flowing or expectations were never made explicit. That gap is often more valuable to work on than the component with the lowest average.

Ninety.io, the software Ops Harmony builds these operating systems inside, turns this from a once-a-year worksheet into a standing discipline. It ships two assessments: a 33-question Baseline Assessment you take when you first adopt the system to set your starting line, and a 29-question Org Fitness Review you rerun every quarter to track movement. Both roll up to an Org Fitness Score and, because the modern Business Operating System expands the classic six components into nine competencies (Vision, Customer, Goals, People, Structure, Data, Meetings, Process, and Exit), you get a more granular read than the paper version. The tool matters less than the cadence. Score the same way, on a schedule, so you are comparing the company to itself over time instead of to a feeling.

📞 Book a Free 30-Minute Strategy Call

🚀 Try Ninety.io Free for 30 Days

Reading the Score: What 40, 70, and 85 Really Mean

A raw number out of 100 is only useful once you know the bands. The common reading runs like this: 20 to 34 percent means significant improvement is needed, 35 to 49 is average with real potential, 50 to 64 is above average with room to grow, 65 to 79 is well above average, and 80 to 100 is the target for a company that has installed the system well. EOS Worldwide frames 80 percent or stronger as the goal and is candid that most teams start well below it; one example company averaged 70 out of 100, which is a genuinely good score, not a failing one.

The trap is treating the number as a report card instead of a trend line. A company sitting at 55 that climbs four points a quarter is in far better shape than one parked at 72 for three years running. EOS Worldwide recommends taking the checkup roughly annually, before you start and every year thereafter, and the teams that get the most from it score more often than that, every quarter, so the trend is visible while there is still time to act on it.

The other number that matters is the one that moved. If People jumped from a 2.4 to a 3.8 because you finally put the right person in the operations seat, that is the win to name out loud. Progress on one weak component is what keeps a leadership team believing the work is worth it.

What I Watch For When a Team Scores Itself

The pattern I see most often is a company that scores itself strong on Vision and weak on Traction. Everyone agrees on where the business is going; nobody agrees it is actually getting there. That is the signature of a company that has done a planning offsite, written a nice set of goals, and then let them die in a shared drive by February. The fix is never more vision. It is the weekly execution rhythm underneath it.

A few years back I worked with a professional-services firm of about forty people where the founder was convinced the problem was Process. He wanted documented procedures for everything. When the leadership team ran the checkup independently, Process scored middling, around a 3, but Data came in at a 1.9 and the spread on the Data statements was enormous. Half the leaders thought they had a weekly pulse on the numbers; the other half had no idea what the current numbers even were. The real problem was not missing procedures. It was that the company was flying without a dashboard, and the founder had been about to spend a quarter building the wrong thing. We built a simple weekly scorecard first, and within two months the arguments about “how are we doing” stopped, because the answer was finally on one screen.

I learned to trust the spread over the average the hard way, long before Ops Harmony. Running network operations at a large telecom, I sat in reviews where senior leaders would nod along to a status that frontline managers knew was fiction. The number on the slide said green. The people doing the work would have scored it red. Whenever the room is too comfortable agreeing, the honest signal is hiding in the disagreement you are not inviting. An independent checkup forces that disagreement into the open, which is uncomfortable for exactly one meeting and clarifying for the rest of the year.

Signs You Are Overdue for a Checkup

You do not need a consultant to sense this. A few honest answers will tell you whether you are running the company on evidence or on vibes.

You could not confidently name, right now, which of the six components of your business is weakest, or your leadership team would each name a different one.
Your last three quarters of priorities were set by whatever was on fire that month, not by a deliberate read of where the business is thinnest.
Nobody on your team has ever scored the company independently; every assessment of “how we’re doing” happens out loud, in a room, with you in it.
You suspect two of your leaders see completely different companies, but you have never put a number on the gap.
It has been more than a year, or frankly ever, since you measured the health of the whole operating system rather than just the revenue line.

If two or three of those landed, you are not short on effort. You are short on an honest baseline, and you are almost certainly pouring energy into the component that feels urgent instead of the one that is actually holding you back.

Turning the Score Into Your Next Three Rocks

A score you file away changes nothing. The point of the checkup is to pick the fight. Run it with your leadership team this quarter, compare the independent scores, and find the single weakest component and the single widest spread. Those two findings become issues on your issues list, and you work them through the same discipline you use for every other problem: get to the root, decide, and assign an owner.

From there the lowest component usually converts into one or two of your quarterly Rocks, the ninety-day priorities that actually move it. If Data scored lowest, the Rock is a working weekly scorecard with live numbers, not a vague intention to “track more.” If Vision scored lowest, the Rock is a finished Vision/Traction Organizer the whole team can recite. Then you rescore next quarter and check whether the number moved. That loop, measure, pick the weakest link, build the system, rescore, is the entire operating discipline in miniature. The checkup is just the honest mirror that starts it.

Frequently Asked Questions

How is the Organizational Checkup different from a weekly scorecard? They answer different questions at different altitudes. A scorecard tracks a handful of leading numbers week to week so you catch trouble in days instead of quarters. The Organizational Checkup steps back once a quarter or once a year and rates the health of the whole operating system, all six components, so you know which systems to build next. One is your dashboard; the other is your annual physical.

Who should fill it out? Your leadership team, the people accountable for the major functions of the business, each scoring independently before you compare. You can widen it to the whole company with a tool like Ninety.io’s Org Fitness Review, which is designed for all teams, but the leadership team’s independent scores are where the most useful conversation starts.

What is a good first score? Lower than you would like, and that is normal. Plenty of solid companies start in the 40s or 50s. The target is 80 percent or stronger over time, but the number that matters on day one is not the score itself, it is that you now have an honest baseline to improve against. Four points of gain a quarter beats a high score that never moves.

📞 Book a Free 30-Minute Strategy Call

🚀 Try Ninety.io Free for 30 Days