

A predictable thing happens when a leadership team starts running on a real quarterly cadence.
At first, it feels great. There is motion everywhere. Rocks defined. Meetings humming. Everyone reporting progress and saying they are on it.
Then the quarter ends.
And when you actually look at what shipped, what is fully done and embedded, it is thinner than it should be.
Not because the team is weak. Not because they do not care. Because they tried to do too many meaningful things at once.
Why I Say 13 Weeks Instead of “a Quarter”
I rarely talk about “a quarter.”
A quarter sounds big. It feels abstract. It gives you room to drift.
Thirteen weeks is different.
When you say 13 weeks, every week matters. Every day counts. When 13 weeks suddenly becomes five because two slipped and a few were chaotic, you feel the tension immediately.
Thirteen weeks forces reality. A quarter allows storytelling.
That distinction matters, because execution lives in weeks and days, not in calendar labels.
Want to learn how to level up your team’s execution? Check out the replay of our Strategic Execution Masterclass here.
The Lie of Capacity
Here is the pattern I see constantly: If someone takes on two genuinely big priorities in a 13-week window, they usually finish one. The other drifts. It gets to 60 percent. It becomes “in progress.” It quietly rolls forward.
That’s not laziness. It’s reality.
Real work expands. Dependencies show up. Customers escalate. Complexity intrudes. What looked clean in planning turns messy in execution.
Thirteen weeks exposes wishful capacity. It forces you to confront what you can actually finish, not what you hope you can juggle.
“I’m Only Getting Four Things Done a Year”
At some point, a strong leader looks at the math and feels underwhelmed.
Four meaningful initiatives per year. That sounds small. Especially if you are wired to produce.
Then you zoom out.
If you have six leaders and each completes four high impact initiatives per year, that is 24 significant moves across the business. Not tasks. Not activity. Structural movement.
The mistake is evaluating output individually instead of systemically.
You do not win as a CEO by stacking heroic effort. You win by increasing the throughput of the organization.
Quantity Versus Quality
This is where most teams get tripped up.
Quantity feels productive because it is visible. You can point at a long list. You can report motion. You can check boxes and feel good about momentum.
Quality is harder because it forces tradeoffs.
Quality asks a different question. Not “What can we get done?” but “What will have the greatest long-term impact?”
Quantity is short term satisfaction. Quality is long term leverage.
Most teams default to quantity unless someone holds the line on quality. That someone is usually the CEO.
Why Technical Teams Struggle More
If you lead a technical organization, this tension is amplified.
Technicians are rewarded for throughput. Solve the job. Clear the queue. Move to the next one. The dopamine hit comes from visible progress.
I totally understand. I spent a good chunk of my career thinking that way.
When you ask a technical leader to pick one major priority for 13 weeks, it sounds irresponsible. There are too many fires. Too many jobs.
But that thinking confuses activity with impact.
The goal is not less work. The goal is work that permanently improves the system.
The Leverage Test
In a recent session, a divisional leader reframed this perfectly.
He asked, what is the thing that saves every technician five minutes on every job for the rest of the year?
Five minutes sounds small.
Let’s do the math.
If the average job is an hour and each technician runs six jobs a day, that is 30 minutes saved per technician per day. If you have 20 technicians, that is 10 hours saved every single day. That is more than a full technician recovered from a single improvement that shaved five minutes off each job.
That is what leverage looks like.
Not another initiative layered on top. A fix that compounds daily.
When you start thinking this way, the quarter stops being about activity and starts being about capacity creation.
One, Maybe Two, Right Things
This is where leadership discipline matters.
For most leaders, the right number in a 13-week window is one meaningful Rock. Possibly two, if they are truly independent and you have proven you can finish both without cannibalizing time and attention.
Three only works if they are genuinely smaller and do not compete for the same resources.
Beyond that, you are back in the quantity trap.
One finished, high leverage initiative shifts trajectory. Two can move the needle meaningfully. Four half-built efforts dilute focus and create drag.
It is not about lowering ambition. It is about finishing what matters.
Strategic Cascade
The right Rock should not originate at the individual level.
It should cascade.
The organization sets clear quarterly priorities that support the annual objectives. Divisions align to those. Functions align to the division. Individual Rocks align to the function.
When that cascade is tight, trade-offs get easier because everyone understands what they are protecting.
When cascade is loose or nonexistent, teams default to local optimization. They pick what feels urgent inside their silo instead of what advances the business.
If your cascade is still maturing, use a simple filter. If this Rock finishes, does the business meaningfully improve, or just this department?
Departmental relief is useful. System level movement is strategic.
The Real Shift
If your team feels busy but progress feels light, do not push for more effort.
Cut the list. Tighten the cascade. Choose the one, maybe two, initiatives that will have the greatest long term impact and actually finish them.
Four properly cascaded, high leverage moves per leader per year compounds faster than a hundred half done initiatives.
Busy feels productive in the moment.
Finished leverage changes the business.
