How to Build EOS Scorecards

Show Notes: Inside the 90™ Episode #30

This episode starts with a simple admission: scorecards are one of the most powerful tools in EOS, and one of the most misunderstood.

Jami and Andrew dig into why that happens. The issue is rarely that leaders do not believe in data. It is that they try to build the perfect scorecard before they have a usable one.

And in EOS, that mindset gets in the way.

A scorecard is not supposed to be a flawless reporting system on day one. It is supposed to be a practical weekly tool that helps a team see the health of the business, spot issues early, and create accountability around what matters most.

The core truth: scorecards should simplify the business, not complicate it

One of the clearest takeaways in the conversation is that teams often overcomplicate scorecards before they even get started.

They ask:

• What are the perfect KPIs?
• What should be automated?
• How do we make this dashboard look polished?
• What if we do not have the data yet?

But the better starting point is simpler:

Start with the major functions of the business and identify two to three key measurables in each one.

That means looking at the natural flow of the organization:

• marketing creates demand
• sales converts demand into customers
• operations delivers the work
• finance tracks the money

From there, the first scorecard begins to take shape.

Not perfect. Just useful.

That is the point.

Start with the accountability chart, then build the scorecard

The episode ties scorecards directly back to EOS structure.

Once the accountability chart is clear and the major functions of the business are defined, the next question becomes:

What are the few weekly measurables that tell us whether each function is healthy?

That gives teams a simple and practical place to begin.

Instead of trying to build a complete business intelligence system, you build an early scorecard around the seats and functions that already exist.

That first version may be rough. It may involve manual reporting. It may expose gaps in your systems. That is not failure. That is exactly what it is supposed to do.

If you cannot get the data, that is not a blocker. It is an issue.

A strong EOS theme runs through this conversation: if you cannot get the number, do not stall out. Put it on the issues list.

That mindset matters because it keeps scorecards from becoming theoretical.

Too many teams stop at:

• “We should probably track this”
• “But we do not have the system”
• “So we will wait until later”

The better move is:

• identify the number
• try to report it
• if you cannot, drop it down as an issue
• solve it over time

In other words, the scorecard does not need to wait for the business to be perfectly instrumented.

In many cases, the scorecard is what reveals which systems need to be built next.

Do not automate what you are not already doing manually

This is one of the most practical points in the episode.

There is a natural temptation to jump straight to dashboards, automation, and slick reporting. But that often happens before the team has even confirmed that it is measuring the right things.

The advice here is simple:

Do not automate anything you are not already doing manually.

If the first version of the scorecard lives across a few spreadsheets and requires manual collection, that is fine. Manual is often the fastest way to test whether a measurable is actually useful.

Automation should come after clarity, not before it.

EOS scorecards are meant to trigger better decisions

A scorecard is not just a reporting sheet. It is a trigger.

That is where a lot of teams miss the point.

The conversation makes two important distinctions here:

1. Leaders should prepare the scorecard before the L10

If you own the number, you should already understand what it says before the meeting starts.

That means:

• reporting it accurately
• analyzing it ahead of time
• bringing the right issue if something is off track

2. Repeated red numbers should create action

If a measurable is red for multiple weeks, the team should not normalize it. It should become an issue worth discussing and solving.

The scorecard is the business dashboard. Its value is not that it shows color. Its value is that it tells the team where attention is needed.

A bloated scorecard loses its power

Another reason scorecards break down: they start tracking too much.

When a scorecard gets overloaded with numbers that are interesting but not essential, teams stop using it the way EOS intends.

That is when the real health signals get buried.

The episode makes the case for fighting for simplicity:

• not every metric belongs on the scorecard
• not every point of analysis should be reviewed weekly
• only a handful of numbers really need leadership attention

A great scorecard is not impressive because it is detailed.
It is powerful because it is clear.

Everyone has a number, but not all numbers belong on the leadership scorecard

As EOS gets rolled out deeper into the business, scorecards become more structured.

At first, the leadership team may track an entire function at a high level. But over time, those numbers should move down into departmental scorecards, where the individuals closest to the work own them directly.

That is how EOS creates the idea that everybody has a number.

It does not mean the leadership scorecard gets bigger forever.
It means the organization gets more aligned as each team builds its own scorecard and reports into the larger system.

The result:

• cleaner leadership visibility
• clearer team accountability
• less confusion about who owns what

Sometimes the solve is simply tracking the issue

One of the best examples in the episode comes from account service.

The team was short-staffed, and while work was still getting delivered, client communication was starting to feel reactive. So they introduced a new measurable:

How many times did a client ask for an update this week?

That one number created visibility. And because it created visibility, it changed behavior.

Everyone became more aware of the need to communicate proactively. Over time, the metric dropped back to zero.

That is an important lesson:

Sometimes the solution to a recurring problem is not a major strategic initiative.
Sometimes the solution is putting the right thing on the scorecard and watching it weekly.

Scorecards, Rocks, and To-Dos each play a different role

The episode does a good job separating three EOS tools that often get blurred together.

Scorecards

The weekly numbers that tell you if the business is staying on track.

Rocks

The major priorities that must get done by the end of the quarter.

To-Dos

The action items being completed week to week.

That distinction matters because it helps teams decide where something belongs.

If it is a weekly behavior or process condition, it may belong on the scorecard.
If it is a quarterly priority, it is probably a Rock.
If it is a next action, it belongs in To-Dos.

That kind of compartmentalization is what makes EOS workable instead of messy.

The best scorecard metrics are often simpler than leaders expect

A recurring theme in this conversation is that many leaders think scorecards need highly sophisticated measurements when often the best ones are simple.

Some of the examples discussed:

• was the checklist followed: yes or no
• was the phone answered within two rings
• was the truck loaded in 45 minutes
• were there zero incidents
• did the customer leave a positive Google review

Those kinds of measurables work because they are:

• clear
• behavior-linked
• visible
• easy to understand
• directly tied to outcomes

Simple does not mean shallow.
Simple means usable.

Good scorecards create alignment because they make winning obvious

One of the strongest illustrations in the episode is a moving company team with just three measurables:

• load the truck in 45 minutes
• zero incidents
• positive Google review

If that team hits those three numbers, they know they won.

That kind of clarity does something powerful inside a business:

• it reduces ambiguity
• it improves engagement
• it helps teams self-correct
• it makes accountability feel fair instead of arbitrary

This is especially important for field teams or operational roles where employees can otherwise feel disconnected from the broader business.

A scorecard turns “do your job” into “here’s what success looks like.”

The “napkin test” is the best way to know if your scorecard is working

The story they use near the end is a great one.

Imagine you are on vacation. You are offered an extra week in paradise. Someone walks up and hands you a napkin with six to eight numbers on it.

No context. No conversation. Just the numbers.

Would you know whether the business is healthy enough for you to stay?

That is the standard.

A strong leadership scorecard should be simple enough and meaningful enough that, at a glance, you can understand the condition of the business.

Data cuts through opinion and creates focus

The conversation closes on a point that feels especially relevant for growth-stage teams:

If all you have are opinions, the loudest voice can win.
If you have the right scorecard, the data helps the team focus on reality.

That is why A players tend to want this system. They want clarity. They want accountability. They want to know what winning looks like.

And that is why resistance to scorecards is often revealing. When someone consistently overcomplicates the numbers, avoids reporting, or pushes everything into vague analysis, it may not just be a systems problem. It may be a commitment problem.

Final takeaway: do not overthink the scorecard, strengthen it every week

The clearest takeaway from the episode is this:

Do not overthink the scorecard in the beginning.

Build a simple version. Use it weekly. Let issues strengthen it over time.

If you cannot access a number, that becomes an issue.
If a recurring problem shows up, maybe it belongs on the scorecard.
If the scorecard is bloated, simplify it.
If it is helping the team focus and act, it is working.

That is the real power of EOS scorecards.

Not perfection.
Not polished dashboards.
Just a practical tool that helps the business stay aligned, accountable, and on track one week at a time.