The week-three problem
Most organizations we work with end their quarterly planning feeling pretty confident. They’ve aligned backlogs, mapped dependencies, refined and approved OKRs at multiple levels. And then it all starts to fall apart around week three.
The goals are still there. The plan technically still exists. But new requests have shown up. Dependencies are delayed or have changed. Teams are quietly renegotiating what’s “really possible.” And no one quite names what changed.
Some organizations are good at pivoting to the current reality. By the end of the quarter, the original plan feels like a quaint artifact of history, if it’s referenced at all.
Others double down on execution. To hit the original commitments, they ignore new opportunities, flood the system with change orders, and ask for overtime and “being a dedicated team player.” If it mostly works, the quarter ends in celebration of heroic delivery. If it doesn’t, the conclusion is that planning failed to capture enough detail, and the solution is to plan even harder next time.
It doesn’t have to be this way. We’ve helped teams across a wide range of organizations design quarterly planning that holds up past week three. Below are three things that make the difference.
What’s really going on
What we’ve learned is that the week-three problem isn’t usually caused by insufficient planning detail, poor execution, or a lack of rigor. It’s caused by a planning approach that treats all work as if it behaves the same way.
Quarterly planning breaks down when we plan Complex work as if it were Complicated, lock in commitments before we’ve done enough sense-making, and then fail to revisit those commitments as reality changes.
Teams that avoid this don’t plan more. They plan differently. They make three deliberate shifts that help quarterly planning hold up once the work actually begins.
Shift 1: Start with shared understanding, not commitments
Quarterly planning usually fails before any goals are written.
Teams jump straight into backlogs, timelines, and dependencies before they’ve made sense of the current state. They begin mapping out solutions and tactics before aligning on purpose, the problems to solve, important constraints, and the Cynefin domain of the work.
Shared understanding doesn’t mean agreement on every detail. It means teams can see the system clearly enough to make coordinated decisions. Why this work matters now. What’s known. What isn’t. Where cause and effect are reasonably stable, and where learning is still required.
Cynefin and CAPED (Complexity-Aware Planning, Estimation, and Delivery) give teams language and structure for this distinction. Before committing, teams need to see which work is Ordered and which is genuinely Complex. Some initiatives are ready for Analytical Planning. Others still need Active Planning and sense-making.
When teams skip this step, they create confident plans built on hidden assumptions. By week three, those assumptions surface as surprises.
When teams start with shared understanding, planning gets lighter. Commitments become more realistic. And coordination becomes easier instead of more fragile.
Shift 2: Match goals to the domain of the work
A lot of quarterly planning falls apart because teams write goals that the work itself can’t support.
During planning, everything gets translated into outcomes and commitments. That works well for Clear and Complicated work, where cause and effect are reasonably stable and teams can influence results in a predictable way.
It breaks down for Complex work.
When teams commit to specific outcomes before they understand the problem or solution, goals stop guiding decisions. They turn into pressure. By week three, teams are either quietly redefining success or working around the goals altogether.
The fix isn’t better goal writing. It’s using different goal types for different kinds of work.
For Clear and Complicated work, commitments make sense. Health metrics and operational targets work well in the Clear domain. Outcome-focused goals like OKRs make sense in the Complicated domain.
For Complex work, goals should be framed around learning. Clear hypotheses. The next experiments to run. What the team expects to learn before making stronger commitments.
This is a core component of CAPED. We don’t pretend exploration and delivery are the same thing. And we don’t leave predictable work so vague that no one knows what success looks like.
When goals match the domain of the work, teams don’t feel stuck defending commitments that no longer make sense. They can adjust responsibly as they learn, without treating every change as a failure.
That helps keep quarterly goals relevant past week three.
Shift 3: Keep goals relevant during the quarter
Once the planning meetings are over, it’s easy to set the goals aside and focus on execution. Execution matters, but we planned for a reason. If we disconnect the work from the goals it’s meant to serve, by week three we may as well have skipped planning altogether. We lose an important ongoing ability to connect day-to-day work to meaningful outcomes.
To avoid this, treat quarterly goals as a living part of the system, not a planning artifact. Make progress toward those goals visible in a way that fits the domain of the work.
Regularly communicate about:
- What progress are we making toward the goal?
- What have we learned?
- Given what we now know, what makes sense to do next?
How this shows up depends on the work.
For Clear work, visibility usually means tracking a small set of health metrics and noticing meaningful changes.
For Complicated work, it means reviewing progress toward outcomes (KPIs and KRs) and understanding what’s driving that progress.
For Complex work, it means sharing hypotheses, experiments, and what’s being learned from them.
This keeps the work of the quarter connected to the outcomes everyone aligned on at the outset, instead of letting goals fade into the background.
Bringing it all together
The week-three problem isn’t a failure of discipline or commitment. It’s a signal that quarterly planning wasn’t designed to be complexity-aware.
When teams start with shared understanding, match goals to the domain of the work, and keep those goals relevant throughout the quarter, planning stops being a one-time event. It becomes a way of steering work as conditions change.
Done well, quarterly planning doesn’t eliminate surprises. It makes them manageable. Teams stay aligned on outcomes, adjust responsibly as they learn, and end the quarter with a clearer sense of what actually moved the work forward.
Week three stops being a crisis. It becomes just another check-in on progress toward outcomes that matter.
Go deeper
- CAPED Certification. Interested in learning more about working complexity first to get early value, learning, and risk-mitigation for your high-stakes initiatives? Join us for our upcoming CAPED Consultant Certification workshop where we dive deep into how to make this way of working stick in an organization.
- Contact us. If your organization is interested in a complexity-aware approach to quarterly planning that supports real progress, consider bringing in a skilled facilitator to help you create more clarity and alignment. Contact us for more information.
Last updated