EOS Rocks: Why Your Team Says "On Track" Until It's Too Late

Leadership teams often mistake silence for actual progress. This complacency leads to a culture where critical objectives are neglected until they become emergencies. Genuine accountability requires more than just a glance at a status report.

So, you are sitting there in your weekly Level 10 meeting, and you are watching the clock as the "Rocks" section begins. One by one, your department heads look you right in the eye, and they say those two magic words: "On track."

It gives you a sense of relief, check the little box, and you can move on to the next item. But what you don't know is that you're likely being lied to — not because your team is dishonest, but because your whole process is shallow.

Research indicates that nearly 60% of business goals reported as "on track" at the mid-quarter mark ultimately fail to meet their deadline.

When you simply accept a three-second update on some project that actually defines your company's quarterly success, you are basically choosing comfort over real results.

How Rocks Get Reviewed in L10 Meetings (And Why 30 Seconds Isn't Enough)

The L10 meeting is designed for speed, but speed without depth is simply a quick way to go in the wrong direction. You take 30 seconds to review a Rock that could involve costs of $20,000 for a software or 100 hours of labor from staff. This is a huge mistake.

When you only inquire if a Rock is "on track," you are asking for an opinion instead of seeking evidence.

You need to shift your way of assessing from "Is it okay?" to "Show me the proof." A person with experience understands that if you are not examining a tangible deliverable like a draft, a signed contract, or a coded feature, you do not really know the status.

If your marketing lead claims that the "New Lead Generation Funnel" is on track in Week 4 but has not even completed the wireframe, they are already falling behind. You need to compel a deeper examination.

Table 1: What "On Track" usually means vs what it should mean

What Most L10s Accept	What Real Status Tracking Looks Like
Verbal "on track" with no proof	Tangible deliverable shown (draft, contract, code)
30-second review per Rock	3 minutes for high-stakes Rocks
Owner's gut feeling	Specific milestones with dates
Status only at the meeting	Updated continuously between meetings
Binary green or red	Velocity tracked week over week

If a Rock carries high stakes, spend 3 minutes on it instead of just 30 seconds. Ask what was accomplished yesterday and what tasks are starting tomorrow. If the response is unclear, then the Rock is at risk.

The Binary Trap: "On Track" vs "Off Track" Hides the Real Story

You are in a binary trap; the project is either green or it is red. The EOS standard was meant to keep things simple, but it has become a haven for procrastination — a place where teams can hide behind a green light at the expense of actually getting anything done.

You've seen it all too often before: a Rock has gone "On Track" for 8 solid weeks, and then in Week 10, suddenly off track. The reality is that the project wasn't failing in week 10; it was dying in week 3, but the binary system allowed the team to ignore all the warning signs and act like everything was ok.

You need to realize that "on track" is just a feeling — it's subjective, and "progress" is what really matters: cold, hard facts. Your team will only be in the "green" zone as long as they have a magic solution to "catch up" over the weekend (which rarely materializes in a fast-growth environment).

What you need are some decent milestones and deadlines to keep people on their toes. If you can't break a Rock project down into at least 3 clear checkpoints, the whole "on track/off track" system is a joke.

False Green: When a Rock Looks Fine But the Hard Work Hasn't Started

It's likely your team is falling into the trap of "False Green" reporting — and most leaders don't even notice until it's too late.

This occurs when people naturally start with the easy, administrative tasks of a Rock first, because they feel like they are doing something productive, and the task can be checked off.

They set up a shared drive, schedule the kick-off meeting, send a couple of emails to the key stakeholders — and hey, they're doing something. 25% done, they think. "On Track," they report.

But the reality is that the hard part — the technical integration that requires expertise, the difficult hiring decision that requires judgement, the data analysis that requires time — has not even begun.

As a leader, the most important question you can ask in these situations is not "what are they doing?" but "when is the heaviest lifting on this Rock supposed to take place?"

Table 2: False Green vs Real Progress signals

Activity Reported	False Green Signal	Real Progress Signal
New product launch	Kickoff meeting scheduled, shared drive set up	First feature shipped to test users
Lead generation funnel	Wireframe ideas brainstormed	Wireframe approved, copy drafted, page live
Hiring a department head	JD posted, recruiter engaged	Final round interviews scheduled
Software integration	Vendor calls completed, NDA signed	API connection tested in staging
Data analysis project	Data sources identified, access requested	Cleaned dataset, first insights documented

 If the most difficult part of the Rock is scheduled to happen in the last three weeks of the quarter, that Rock is not "On Track" — it is already late, regardless of what the status report says. This is not pessimism, but rather a fact of project life.

The final 20% of any significant project will take up about 50% of the time and effort. Things get more complicated, unforeseen challenges emerge, and progress slows just when you need to accelerate.

So, if your team isn't in the thick of it by Week 6, that comforting green light is not a sign of good health; it's an illusion. Don't wait until the last three weeks of the quarter to see through it.

Why 70-80% Completion Rate Feels Like Success But Isn't

You may be tempted to be "nice" and settle for 80% completion rate at the end of the quarter. You say, "They did a good job, and we are close."

In the world of EOS and high-level execution, 80% Rocks are 0% investments. If you build 80% of a bridge, you can't drive across it. If you complete 80% of a new client onboarding manual, the new employees are still confused.

If you reward 80% as a "win", you are encouraging your employees to quit when the going gets tough. You are rewarding failure. You have already spent the payroll and the mental energy; by failing to cross the finish line, you have wasted those resources.

A Rock is a 90-day promise of a product. Anything less is a lie to the company. You have to hold the line that "Done is Done" and "Almost" is an expensive failure.

The Week 3-to-Week 9 Dead Zone Where Rocks Silently Die

Every quarter has a deadly period that most leaders don't anticipate, and it is called the "Dead Zone."

Quarters have a predictable rhythm — your team starts strong and motivated in weeks 1 and 2, and then struggles to put out fires in the last-minute scramble of weeks 10 to 12.

But it is the long, slow middle — weeks 3 to 9 — that does the most damage. The inbox fills up, the customers complain, and one "emergency" after another distracts your team from the things that matter.

This relentless activity is not obvious. It just consumes your long-term goals.

Table 3: The 12-week quarterly rhythm — where Rocks actually live or die

Quarter Phase	Weeks	What Usually Happens	What You Should Watch For
Kickoff	1–2	High energy, planning, optimism	Are milestones written and dated?
Dead Zone (Early)	3–5	Daily fires distract from Rocks	First signs of "on track" without proof
Dead Zone (Late)	6–9	Silent stagnation, no real progress	Velocity has slowed or stopped
Final Scramble	10–12	Panic mode, last-minute push	Realization that Rock is actually 40% done

The danger of this period is that the rot is invisible. Over time, your team's focus shifts from growing the business to surviving the day. When you ask about the Rock in your L10 meeting, you will hear "On Track" — spoken with just enough conviction to be believed. But the reality is that they have not worked on that Rock since last week.

They are not sharing progress; they are guessing and hoping. This is why the Dead Zone is the time to be alert, not complacent. If you are not seeing real progress week after week in this middle period, you are setting yourself up for a Week 12 surprise — the kind where everyone is shocked by the outcome.

The adage is true here: what gets measured gets managed. If you're not measuring progress in the middle of the quarter, you are not managing.

What Velocity Tracking Would Catch That Your L10 Review Misses

You are missing an important indicator, which is Velocity. Your L10 review tells you where the team is, but velocity tells you if they are moving fast enough to finish on time.

For instance, if a Rock has 10 distinct steps and only one step has been done in the last 14 days, it is not moving fast enough. Even if the status is "On Track," the numbers tell you it won't be done on time.

Instead, look for what I call "movement indicators." Ask your team, "What has changed about this Rock since Tuesday?"

If they can't tell you something that has changed, then there is no progress. You don't need a fancy spreadsheet to do this — you just need to stop accepting progress reports that don't show real progress.

If progress stutters or stops, move the Rock to the "Issues" list. Don't wait until it turns red, because by then it will be too late for the quarter. You want to catch it early, when there is still time to do something about it.