December arrives, and suddenly everything feels urgent. Projects that have been progressing steadily for months now “must” be completed by December 31st. Teams work unsustainably to hit arbitrary year-end targets.
We know intellectually that January 1st is just another day. Nothing fundamental changes when the calendar flips. Yet we feel compelled to close everything out, to finish strong, to start the new year with a clean slate.
If you’re a leader feeling this pressure right now—or worse, creating it for your team—it’s worth pausing to ask: How much of this urgency is real, and how much have we manufactured?
The December Deadline Delusion
Year-end has become an artificial finish line for goals, projects, and initiatives, regardless of whether there’s any operational reason for that timing. This happens even in organizations that don’t have fiscal year-end pressures tied to the calendar year.
The pattern is so normalized that we rarely question it. Of course we finish projects by year-end. Of course we assess progress against annual goals in December. That’s just how it works. Except it doesn’t have to work that way.
These are organizational and cultural choices that we can examine and potentially change.
For nonprofit leaders, this gets complicated. You’re balancing board reporting expectations, annual funding cycles, and performance measurement systems. These aren’t imaginary constraints, but even under these real pressures, there’s often more flexibility than we assume.
Real Urgency vs. Manufactured Urgency
Not all year-end pressure is manufactured. The key is learning to distinguish between real urgency and urgency we’ve created through our own assumptions.
What Actually Can’t Wait
Some deadlines have real consequences. External commitments with genuine time constraints matter, like contracted deliverables, funder reports, and regulatory requirements. Year-end giving in nonprofits is real, and the tax deadline creates genuine urgency. If your fiscal year ends on December 31st, certain financial processes must be completed on that timeline.
These are externally driven deadlines where missing them creates genuine operational, financial, or relational consequences.
What Probably Can Wait
Then there’s everything else that we treat as urgent but probably isn’t. This includes internal project milestones that aren’t tied to any external commitments. We set annual goals simply because we work in annual cycles, even though rigid timeframes often create more problems than they solve for complex, adaptive work. Performance review cycles fall into this category too, as they’re organizational choices we’ve made, not natural laws. Sometimes we push to complete goals primarily to prove we accomplished what we said we would, serving optics rather than impact. The desire to start the new year with a “clean slate” is entirely psychological rather than operational.
The test is simple: Ask yourself honestly, “What actually happens if this extends to January?” If the real answer is “nothing except it feels incomplete” or “my board will ask why it’s not done,” that’s manufactured urgency.
Why We Manufacture December Urgency
Understanding why we create false urgency helps us challenge it more effectively.
Humans crave completion. The calendar year-end triggers this desire for closure. This is normal psychology, but it’s a preference, not an operational necessity.
Performance measurement systems create real pressure to show completion by December 31st, but these systems are organizational choices. If they’re creating urgency that undermines quality and sustainability, the problem isn’t your execution; it’s the measurement system.
Most of us absorbed messages from hierarchical environments about “finishing strong” and proving value through visible year-end achievements. In Organizing for Impact, I write about this corporate conditioning: patterns and beliefs we’ve internalized that often work against creating adaptive organizations. Year-end urgency is a perfect example. We’ve been conditioned to believe annual cycles and year-end completion are simply “how work works.” They’re not, however, inevitable. They’re inherited conventions we can question.
Sometimes urgency comes from a leader’s own discomfort with uncertainty. Creating urgency can feel like taking action. When we channel that discomfort into manufacturing urgency for our teams, though, we’re managing our own anxiety at their expense.
One of the most common manifestations of this is the phrase, “We’ve always closed out projects by year-end.” Nobody remembers why. These inherited patterns are powerful precisely because they’re invisible.
The Real Cost of False Urgency
Manufactured urgency costs more than we acknowledge.
Teams work unsustainably in December, then arrive in January exhausted. They need weeks just to recover. You’ve eroded long-term organizational capacity for short-term completion satisfaction.
Work done under intense time pressure is generally of lower quality. People make mistakes, skip important steps, produce something “done” that isn’t actually good. Often, it needs revision in January anyway.
When teams realize urgency was manufactured, they trust leadership less. This creates a boy-who-cried-wolf effect. When genuine urgency arises, it’s harder to mobilize people.
Rush mode prevents reflection and strategic thinking. You sacrifice thoughtful Q1 planning and learning, which include exactly the conversations that would make the next year more effective.
When leaders drive false urgency, they teach teams that constant urgency is normal, that sustainable pace isn’t realistic, and that sacrificing well-being for completion is expected. The next generation of leaders inherits these assumptions unless someone interrupts the cycle.
How to Identify What Can Actually Wait
Here’s a practical framework:
Make everything visible. List everything that “must” be done by December 31st.
Question each item:
- What external commitment or consequence is tied to this deadline?
- Who outside our organization is depending on this specific timing?
- What operational problem occurs if this extends to January?
- Is this tied to the fiscal year-end, or any regulatory requirements or contracts?
- Am I driving this urgency, or is it externally driven?
Sort into categories:
- Actually urgent (real external consequences)
- Strategically important but not time-sensitive
- Organizationally convenient but not necessary
- Psychological closure but no operational need
Make explicit decisions. Commit to completing the actually urgent items. Explicitly decide to extend strategically important items into Q1. Communicate these decisions clearly. Don’t let things drift.
This takes courage. It means potentially disappointing board expectations, reporting incomplete goals, and tolerating discomfort, but it models that you value quality over optics, sustainability over arbitrary completion, and people over performance theater.
What to Do with Goals That Can Wait
Communicate clearly. Explicitly announce extensions: “We’re extending this into Q1. Here’s why, here’s the new timeline.” Frame it as a strategic choice, not failure.
Reset expectations. Have potentially uncomfortable conversations with your board, your team, and yourself. These conversations require vulnerability and courage. They also build trust.
Use December differently. Reflect on what worked and didn’t this year. Plan Q1 thoughtfully. Create space for strategic thinking. Allow for rest and recovery. This isn’t wasted time; it’s essential for maintaining a sustainable pace.
Document for next year. Note which goals weren’t genuinely year-end urgent. Question whether some goals need to be annual at all. Maybe your organization would benefit from shorter, iterative planning cycles that enable greater adaptation.
A Different Way of Working
Traditional organizational approaches operate on predictable, linear cycles: set annual goals, execute, assess completion at year-end, repeat. This works for predictable, stable environments.
Most mission-driven work, however, happens in complex, changing conditions. Rigid annual cycles with year-end urgency don’t serve this work well.
In Organizing for Impact, I explore adaptive, iterative approaches. Instead of long planning cycles with artificial completion points, use shorter cycles with built-in learning and adjustment. Have a vision that spans years, but plan in quarters instead. Use continuous sensing and responding rather than trying to predict and control. Build systems where goals evolve as you learn.
These approaches don’t eliminate accountability. They recognize that forcing everything into annual cycles with December deadlines often creates more problems than it solves. When you organize around shorter cycles with regular adaptation points, you don’t get the same year-end urgency buildup.
This is part of moving from hierarchical organizing toward more distributed, adaptive approaches. It requires questioning inherited assumptions and having the courage to try different patterns.
The Self-Awareness Work
Challenging year-end urgency requires examining your own patterns.
What drives your need for completion? How does your anxiety create urgency for your team? What are you trying to prove with year-end achievements? Where did you inherit these patterns?
This self-awareness work may not be comfortable, but it’s essential leadership development. You can’t lead adaptively and sustainably if you’re unconsciously driven by unexamined patterns and anxieties.
It takes courage to challenge these patterns: to question conventional practices that everyone assumes are necessary, to fall short of what others expect of you, to look like you didn’t “finish” everything, to trust that January continuation is often better, to push back on performance measurement systems that create false urgency.
Most importantly, this courage models that it’s safe to question urgency, that critical thinking matters more than blind adherence to convention, and that people’s wellbeing and work quality matter more than arbitrary completion.
Starting the Conversation
You don’t have to overhaul everything at once.
This week: Audit your year-end goals. Identify at least one thing that can wait. Have a conversation with your team about it. Give them permission to question urgency, too.
Before December: Get clear on what’s truly time-sensitive versus what you’ve been assuming. Communicate explicitly about what will extend. Reset expectations.
For next year: Question your annual goal cycles. Consider shorter, more iterative planning approaches. Build sustainability and learning into your planning from the start.
You have more power than you think to challenge year-end urgency. Your team is likely feeling the same pressure and waiting for permission to question it.
The goals that can wait aren’t failures. They’re opportunities to model sustainable leadership, strategic thinking, and the courage to challenge inherited patterns that don’t serve your mission or your people. So, to summarize, just start with one goal, name it as something that can wait, and notice what happens when you create that space.
Leave a Reply