TL;DR: Q2 planning falls apart for most SMBs around weeks 5 to 7. It doesn’t happen because the plan was bad or that the team isn’t good at what they do. Because the cadence to keep the plan alive doesn’t exist. The priority with the least emotional urgency quietly stops being a priority. A new urgent problem takes its place. By June, the team’s focus has faded and the Q2 plan is a vague memory. The fix is a 15-minute weekly rhythm that catches drift while it’s still a one-week problem.
It’s the beginning of May – you Q2 plan is four or five weeks old today. Can you name the three priorities you committed to at kickoff? Without looking?
The founders I work with usually can’t. That’s not a memory problem. That’s what happens when the plan lives in a doc buried on your hard drive somewhere and the week gets determined by what shows up in your inbox.
What’s happening to most Q2 plans right now? Three things, in sequence. The priority with the least emotional urgency quietly stops being a priority. A new urgent problem moves to the top of the stack. By week 6 or 7, the original Q2 planning work is more vague memory than roadmap. Catching it takes a 15-minute weekly rhythm, and the teams I work with rarely have one in place yet.
Why Q2 Planning Drifts Differently Than Q1 Planning
Q1 has an advantage Q2 never gets. The year is new. Energy is high. Everyone remembers what was agreed to in January because January was two weeks ago. The plan stays warm without much effort.
By Q2, the novelty is gone. Leadership has moved to the next thing. The team is running on muscle memory from Q1, but the targets have changed. That gap is invisible from week to week.
Everyone is working hard. Progress is happening. It just isn’t progress against what you said you cared about in April. Q1 has its own version of this drift and we covered the early-warning signs in that piece. Q2 is structurally worse: same drift mechanics, less attention, fewer fresh eyes catching the slide.
The Specific Failures Showing Up Right Now
Four weeks into Q2, here’s what’s quietly starting to go wrong:
- The priority that became optional. You set three priorities. One of them is getting “when we have time” energy from the team. That’s priority death by erosion, not by decision.
- The update that didn’t happen. The person who owns the most important number for Q2 hasn’t given you a real number since week one. You’d know this if you asked. You’re not asking.
- The decision made by inertia. A meeting happened. A direction was chosen. It was not the direction your Q2 plan assumed. Nobody has said that out loud yet.
- The calendar that filled in. Your Q2 planning session assumed a certain amount of deep strategic work. Your calendar now has three new recurring meetings that weren’t in the plan.
Any one of these, caught now, is a 15-minute conversation. Left alone until mid-June, each one becomes a quarter-reset.
How Do You Catch Q2 Planning Drift Before May Erases It?
The gap isn’t strategy. You had a strategy.
The gap is the cadence that turns the strategy into the first thing you’re working on Wednesday morning. Research from Harvard Business Review on goal-setting consistently lands on the same point: teams that recalibrate frequently outperform teams that hold the original plan past the point where it still makes sense. Q2 planning that survives May is Q2 planning with a weekly check-in attached.
Status meetings won’t do it. Status meetings tell you what happened. They don’t catch drift. They confirm it, slowly, over six weeks.
What catches drift is a structured check-in that asks three questions each week, per priority:
- From what, to what? The metric your priority is moving. Last week’s value to this week’s. “Activation: 34% → 38%.” Not “we launched the new flow.”
- What’s blocking this? Not “what might become a problem.” What is actively stuck and needs a decision or a hand-off.
- What are we doing about it before next week? A captured decision, not a documented status.
If the answer to all three is “nothing,” you’ve found a priority that’s already dead. Revive it or officially reassign the time. Either beats the drift.
Want a structured 15-minute check-in template to run this in your team? Download the OKR check-in template and use it for your next weekly sync.
Why Q2 Planning Falls Apart Without a Weekly Cadence
Asana’s Anatomy of Work research found that knowledge workers spend nearly 60% of their day on coordination overhead. A team that doesn’t have a clear weekly signal of “what matters most this week” defaults to whatever’s loudest. The Q2 plan you wrote in April becomes background noise.
That isn’t a discipline issue. It’s a signal issue. The plan didn’t fail. The plan never made it into the operating cadence. Without that bridge, every week becomes a fresh negotiation between what’s urgent and what’s important. Urgent wins. The Q2 plan loses, quietly.
A weekly check-in is the cheapest bridge. 15 minutes. Three questions. One captured decision. Done well, it’s the difference between a Q2 that closes on plan and a Q2 you spend July re-planning.
Why We’re Building OKR Leader
I’ve watched SMBs make the same Q2 mistake for years. Great plan in April. Dissolved plan by June. Reset in July.
The tools available to fix this are either built for Google-scale orgs (too much overhead) or they’re a spreadsheet (too little structure). Neither holds a 20-person team’s attention through May.
OKR Leader is the third option. Structured enough to protect the quarter. Light enough that a small team actually uses it. Built around the 15-minute weekly check-in that turns the Q2 planning doc into the first thing you’re working on Wednesday morning.
We’re in early access right now. Not a waitlist. Actual access, limited seats. If you want to see whether a structured weekly rhythm could protect the quarter you just started, tell us about your team and we’ll send an invite.
Four weeks into Q2 is the right time to install this. Eight weeks in is too late to save the quarter. Today is the second-best day.
Frequently Asked Questions
When does Q2 planning typically start to drift?
Most Q2 plans start to drift around weeks 4 to 6. The first three weeks coast on April momentum and quarterly kickoff energy. By week 4, the new urgent problems start arriving. By week 7, the priority with the least emotional urgency has quietly become “when we have time.” The drift is rarely a single dramatic event. It’s a slow erosion of attention, week by week.
How is Q2 planning different from Q1 planning?
Particularly for organizations that have their fiscal year line up with the calendar year, Q1 planning gets the structural advantage of a fresh year. Energy is high, leadership is engaged, the targets feel new. Q2 inherits the muscle memory of Q1 without the same fresh attention. The plan changes (or should), the cadence often doesn’t, and the team runs on outdated context. Q2 is where the real test of operating discipline shows up.
What’s the minimum cadence needed to keep Q2 planning on track?
Weekly. 15 minutes per team. Three questions: what’s actually moving on each priority, what’s blocked, and what decision needs to happen before next week. Bi-weekly is the absolute minimum and only for teams with cycles longer than a quarter. Monthly is too long. You find out about drift after it’s compounded into a quarter-reset.
Can Q2 planning be saved if it’s already drifted?
Yes, if you catch it by week 6 or 7. The fix isn’t a re-plan. It’s installing the weekly cadence and using it to either restore the original priorities or officially deprioritize them. The deprioritization is the part that typically gets skipped, and skipping it is exactly why drift compounds. Either bring the priority back or let it go. Both are honest. The dishonest option is “still on track” while the work isn’t happening.
