The Rock has been “almost done” for three weeks.
The owner says it’s at 80%, same as last Tuesday, same as the Tuesday before that. Somebody says they’ll follow up after the meeting. Nobody follows up. Next week it’s still 80%, and now there are four weeks left in the quarter.
If you run a leadership team, you have sat in that meeting.
Most teams respond to that gap by adding check-ins. Then the calendar fills up, one person becomes the full-time follow-up department, and everyone starts describing the company as micromanaged.
EOS handles it differently. EOS accountability comes out of the system itself, as a byproduct of how the week is structured. Below is how the five tools work together, where the whole thing usually breaks, and what to do when it does.
We ran our last company on EOS and sold it. We know the distance between a beautiful Accountability Chart and a Rock that actually lands on time.
What accountability means in EOS In EOS, accountability comes from a system of five tools. The Accountability Chart gives every seat one owner, Rocks set 90-day priorities, the Scorecard makes weekly progress visible, To-Dos capture seven-day commitments, and the Level 10 Meeting reviews all four every week.
That structure does something specific: it removes the ambiguity people hide in.
When two people share a function, work falls between them. When a number has no name attached, a bad month becomes a discussion instead of an owner’s problem. When a commitment lives in someone’s notebook, it disappears. EOS assigns one person to every seat, every number, and every commitment, then puts all of it in front of the team once a week.
The scale of the ambiguity problem is worth sitting with. Gallup’s July 2026 engagement report found that 49% of employees strongly agree they know what’s expected of them at work — down from a peak of 61% in 2015. Half the workforce is guessing.
Accountability in this framing is a design problem you solve on purpose. That’s the good news — design is something you control.
Each tool answers one question the others can’t:
Accountability Chart — who owns this?Rocks — what matters most for the next 90 days?Scorecard — are we on track this week?To-Dos — what did we commit to in the next seven days?Level 10 Meeting — where do we look at all of it together?The Accountability Chart: one owner per seat The chart maps the functions your business needs, then puts exactly one name on each. It answers who owns what, which is a different question than who reports to whom.
McKinsey’s research backs up why this comes first. Their July 2025 analysis of organizational health found that organizations with strong role clarity are over twice as likely to hold employees accountable, and nearly five times more likely to be organizationally healthy. Clarity comes upstream of accountability. You can’t hold someone to a responsibility they were never clearly given.
If you’re building or fixing your chart, we wrote a full walkthrough on how to build an EOS Accountability Chart that works . For this post, treat the chart as week zero — necessary, and nowhere near sufficient.
Rocks: ninety days of priorities Rocks turn the annual plan into three or four things each person will actually finish this quarter. Every Rock has one owner and a done-or-not-done definition.
The 90-day window is doing real work here. Gallup’s 2024 research on performance management found that 56% of employees formally review their goals with a manager once a year or less. The same study found that employees with quarterly progress checks are 90% more likely to be engaged and more than twice as likely to see the process as fair.
An annual goal gives you one moment of truth. A quarterly Rock gives you four, and each one is close enough to course-correct.
Scorecard: numbers everyone can see The Scorecard is five to fifteen weekly numbers, each with a target and one owner. Red or green, every week, in front of everybody.
This is the tool that converts good intentions into information. Ian Groves, managing director of Start Tech, described what it did for his team:
“Actually, more often than not, everybody within an organization wants to know whether they’ve done a good week’s work. They want to know what defines a good week for them as an individual. Having the weekly meetings and the scorecard help them tap into this natural impulse. Good people aspire to beat what they’ve agreed to in their scorecard.” — Ian Groves, Managing Director, Start Tech (read the full story )
Getting the metrics right takes a few passes. We put together seven questions for building a Scorecard that drives action if yours currently tracks things nobody acts on.
To-Dos: seven-day commitments To-Dos are the small stuff — call the vendor, send the draft, pull the numbers. Seven days, one owner, done or not done.
They look trivial next to Rocks. They’re the highest-frequency accountability signal you have. A To-Do that carries over three weeks running tells you something important long before a Rock goes red.
Level 10 Meeting: the weekly review The L10 is the 90-minute meeting where all four of the above get looked at, in the same order, every week. Scorecard, Rocks, To-Dos, then issues.
The fixed agenda is the point. Nobody has to decide whether to bring up the stalled Rock, because the agenda brings it up. If your L10s have drifted into status updates, we catalogued ten reasons L10 meetings go sideways .
Why the weekly loop beats the chart Almost everything written about EOS accountability stops at the Accountability Chart. Design the structure, name the owners, and accountability follows.
Structure solves week zero. Week eleven is a different problem.
By week eleven the chart hasn’t changed. The Rock is at 40%. Two To-Dos have quietly carried over four times. One Scorecard number has been red so long the team stopped reacting to it. No org design prevents that. A loop that runs every seven days does.
Watch how the tools hand off to each other:
Rocks set what matters for the quarter The Scorecard shows whether this week supported those Rocks The L10 surfaces the gap between the two To-Dos close the gap in the next seven days The chart tells you exactly whose name goes on each of those The loop’s real advantage is speed of feedback. A missed commitment shows up in seven days instead of at a quarterly review, which is early enough that fixing it is still a small conversation.
This is the part that tends to fall apart in spreadsheets. When the Scorecard lives in a tab that someone updates the morning of the L10, it becomes a report about the past. Nobody looks at it on a Wednesday, when looking at it might change a decision.
We built Strety’s Scorecard to update as work happens, so red shows up the day it goes red. To-Dos sync out to Microsoft To Do, Outlook, Teams, Google Tasks and Asana. Commitments land in the tools people already have open. Paige Longmore, marketing director at 31st Street Capital, sits in eight to ten meetings a week across five companies:
“Managing all those to-dos and rocks was a real headache before Strety. Now, with everything integrated into one place through Outlook’s To Do list, I’ve become a lot more efficient!” — Paige Longmore, Marketing Director, 31st Street Capital (read the full story )
Accountability without the micromanaging Check-ins feel like micromanaging for a structural reason: they put a manager between a person and the truth about their own work. The manager asks, the person reports, and the manager decides whether to believe the report.
A Scorecard removes the manager from that loop. The number is red or it’s green. The owner sees it at the same moment everyone else does, which means the conversation starts from shared facts.
Two things change once that’s in place.
Peer accountability takes over. In a weekly L10, your Rock status isn’t a private matter between you and your boss. Everyone at the table sees it. Georg Dauterman, president of Valiant Technology, put it plainly:
“You have to face the music every week if you didn’t do your work. If you properly set the accountability up, I think that people tend to just do their work better and then the expectations are clearer.” — Georg Dauterman, President, Valiant Technology (read the full story )
That pressure comes from the room. It also lands lighter, because it arrives alongside seven other people reporting their own numbers. We went deeper on this in why peer accountability is the secret to scaling with EOS .
The manager’s job changes. When the system reports status, you stop spending the week collecting it. The question shifts from “where are you on this?” to “what’s in the way?” — which is the question people actually want their leader asking.
When accountability breaks down The system will tell you something is wrong. It won’t tell you what to do about it, and the diagnosis matters, because these four failures need four different responses.
A To-Do that carries over twice is usually a scoping problem. It was never a seven-day task. Break it down or make it a Rock milestone. Treating it as a discipline problem when it’s a sizing problem teaches your team that To-Dos are aspirational.
A Rock at 40% in week nine is an L10 failure. Somebody knew in week four. The issue never got raised, or it got raised and never made it to the issues list. Start by fixing the meeting.
A chronically red number with a disengaged owner is a seat conversation. When someone stops reacting to their own red number, the number stopped feeling like theirs. Ask whether they get it, want it, and have the capacity to do it.
Repeated misses across quarters mean the seat needs a fresh look. Two quarters of missed Rocks with clear expectations and no blockers is a fit question. Run the People Analyzer, have the honest conversation, and stop hoping the next quarter is different.
Jill AlJundi, integrator and VP at Pendello Solutions, described why EOS makes these conversations happen at all:
“The level of accountability and clear ownership that is forced through that EOS process, especially in a small company where people wear multiple hats, is invaluable.” — Jill AlJundi, Integrator and VP (COO), Pendello Solutions (read the full story )
Time for some marketing here 🙂 — the reason we built People tools alongside the EOS tools in Strety is that this last category kept sending us into a second system. Your quarterly conversations, People Analyzer scores and 1:1 notes belong next to the Rocks and Scorecard they’re about.
Three mistakes we see most Building the chart and stopping there. The most common one by a wide margin. Teams spend two offsites perfecting the Accountability Chart, hang it in the conference room, and change nothing about how Tuesday works. The chart names owners. The weekly cadence is what holds them.
Adding activity instead of ownership. More status meetings, another dashboard, a Friday recap email. Each one adds work and moves accountability further from the person doing the work. If a new ritual doesn’t put a name on something, it’s overhead.
Letting the Scorecard go stale. A number updated the morning of the L10 is a historical record. It can’t change a decision, because the week it describes is already over. Weekly numbers need to be current enough that someone can act on them mid-week.
Frequently asked questions How does EOS create accountability? Through five tools working together — the Accountability Chart assigns one owner per seat, Rocks set 90-day priorities, the Scorecard makes weekly progress visible, To-Dos capture seven-day commitments, and the Level 10 Meeting reviews all four every week.
How do you hold your team accountable without micromanaging? Make the work visible so the check-in becomes unnecessary. When Rocks, numbers and To-Dos sit on a shared scorecard reviewed weekly, the team sees what’s off track before anyone has to ask.
What causes a lack of accountability in a team? Usually unclear ownership. When two people share a function or no name is attached to a number, there’s nobody for the work to land on.
Is accountability the same as the Accountability Chart? No. The chart is where accountability starts, by naming one owner per seat. It holds because of the weekly cadence that follows.
How long before accountability sticks after starting EOS? Most teams feel the cadence take hold within one or two 90-day cycles, because the Scorecard and L10 surface missed commitments every week rather than at review time.
What do you do when someone consistently misses commitments? Move it from a task conversation to a seat conversation, and ask whether the person gets it, wants it, and has capacity for it. Repeated misses across quarters are usually a fit question.
Can you run EOS accountability in a spreadsheet? You can start there, and plenty of teams do. It breaks down when the Scorecard only gets updated the morning of the L10, because then nobody sees a red number during the week it could still be fixed.
Who is accountable for accountability in EOS? The Integrator owns the day-to-day cadence — running the L10 and keeping Rocks and To-Dos current — while each seat owner is accountable for their own numbers and commitments.
Where to start this week Accountability comes from clear ownership plus weekly visibility. Five tools, one loop, running every seven days.
Find the weakest link in your loop and fix that one thing. If your Scorecard is stale, make the numbers current before you touch anything else. If Rocks are vague, tighten the definition of done. If the L10 has become a status meeting, put the agenda back in order. Adding a meeting to solve any of these makes it worse.
We built Strety because we were running this loop across a scorecard spreadsheet, a project tool and a meeting doc, and losing the thread between L10s. It’s the software we needed when we were running on EOS ourselves.
Try Strety free for 30 days — no credit card required. Or if the meeting is your weak link, start with our complete guide to the Level 10 Meeting .
