The holidays are approaching, and suddenly everyone’s scrambling to wrap up projects before taking a break. What should be a time for winding down and holiday parties becomes a sprint to the finish line, bringing a calendar full of meetings, shifting priorities, an overflowing inbox, and a voice in your head whispering, “just one last email before you log off…” 

That’s when mounting pressure gives way to the stark realization that you’re running out of time, and we start to hear a familiar phrase: 

“Let’s circle back on that next year.”

As the end-of-year crunch fast approaches, Atlassian partnered with YouGov to survey 6,000 knowledge workers across six countries (US, France, Germany, UK, India, Australia) to unpack the circle-back phenomenon.

🚨 Spoiler alert: On average, 1 in 5 projects (19%) will be pushed to 2025. One-third of those unfinished projects will be abandoned entirely in the new year.

Why do teams circle back?

The end-of-year scramble can be tough on everyone, and our research shows that “circling back” has become a collective coping mechanism. Sixty-eight percent of knowledge workers say at least some projects will go unfinished, with shifting priorities (34%) and unexpected challenges (32%) serving as the main reasons why. 

Avoiding burnout is a big motivator too, but one person’s blessing is another’s burden. While 18% of knowledge workers push projects back and pick them up in the new year to avoid year-end burnout, 22% say they avoid those kinds of delays to ensure a lighter January workload. 

Yet workers seem to be missing a bigger opportunity. What if instead of scrambling to complete a laundry list of tasks, we use this as an opportunity to evaluate what really matters?

Mark your calendars

We’re calling it: December 17 is World Circle Back Day! By mid-December, 71% of workers will either have all tasks wrapped up or push them into 2025.

Circling back or spinning wheels?

Shared understanding: finding the “why” behind the “what”

For many, the notion of “circling back” brings a deceptive feeling of relief. But pushing out projects – while an inevitable reality for some items in the December dash – might not result in the intended outcome. When it comes time to actually circle back, a mere 26% feel confident they can easily resume postponed projects in the new year.

Most workers have the best intentions for picking up their stalled projects, but it’s harder than it sounds. Who can remember an important action item shared verbally in a one-off meeting from last year? Or a small but mission-critical piece of client feedback in an email that’s now buried deep in your inbox?

Without documenting these decisions and touch points, teams work slow at best and ill-informed at worst, or end up running fast at the wrong priorities. And those tasks left on the back burner in December can quickly start to feel overwhelming in January, leading to delays – or worse, projects that drop entirely.

When important projects fall off the radar, it not only disrupts the flow of work, but also negatively impacts team trust and accountability. Suddenly your December dash turns into wasted output for the entire team.

Circling back(wards)

It’s hard to pick back up where you left off. Part of the problem is that workers tend to say they will circle back on EVERYTHING this time of year, instead of using it as an opportunity to get super clear on your team’s priorities and realistic about what does (or doesn’t) move the needle.

Some projects struggle to regain momentum after the holiday because they don’t have a big impact in the long run. These projects can feel tedious – we often call them “zombie projects” – technically “alive,” but failing to progress, draining resources and morale. The reality is that it might be time to scrap those zombie projects altogether. And that’s okay! The end of year is a great time to reevaluate your priorities, get clear on what matters, and come back prepared to make a meaningful impact with great focus (just make sure your team knows you’re scrapping it, too!).

So what about postponed projects that are mission-critical and worth circling back on? There are ways to set yourself up for success so your future self will thank you.

Disrupting the spin cycle

How to excel at asynchronous communication with your distributed team

A little time getting organized now can make a big difference in the new year. To pick up where you left off, teams need to document their important work, including up-to-date statuses and easy-to-find sources of truth with important context about each project.

These information sharing practices – often called asynchronous work – not only help you pick up where you left off, but make it easier to disconnect knowing your team has what they need to move work forward without you. This is especially useful during the holiday season, when mismatched PTO schedules, competing priorities, and fluctuating energy levels can make it tough to coordinate, risking delays or stalled progress. And no one wants to be on the receiving end of an angry ping asking where something is while on a holiday break.

what is asynchronous work?

Asynchronous work is teamwork that happens without needing everyone present, online, and available at the same time. Teammates can move work forward when it’s convenient for them, as long as the work is clearly documented, context is readily available, and there is clarity on expectations and deadlines.

Try these async work practices this circle-back season so your team can pick up right where it left off in 2025:

  • Capture context now for clarity post-holidays: Async work requires clearly documenting progress, decisions, and next steps in accessible formats like written documents, videos, or voice notes. Before you head out on PTO, publish a Confluence page (check out this OOO plan template) or record a Loom video that provides updates, suggested next steps, and context so team members can make progress while you’re out. Doing so means you can disconnect knowing you set your team – and your future self – up for success.
  • Time is of the essence, so think async first: When the pressure to complete projects mounts, it’s easy to default to scheduling a meeting. But meetings are time-consuming, and often not as productive as intended. Before scheduling a meeting (or accepting one!), think about what you’re really trying to accomplish. If it’s a status update, relaying information, or an FYI, keep it async and send your teammate a Loom instead.
  • If it’s not worth circling back on, scrap it now: Most people try to do too many things at once, which slows them down and lowers the quality of their work. Use this moment to let go of low-impact projects and focus on the work that truly matters. For tasks deemed circlebackable, reflect the new deadline on your planning pages, Jira tickets, and shared calendars so everyone is on the same page.
  • Be realistic about your calendar: As the year’s end approaches, timebox your calendar to make sure you have enough focus time to get your most important work done. Pick a few important things to see over the finish line (rather than trying make a little progress on everything).
pro tip

Record a “Loom to my 2025 self” to help jog your memory on where you left a certain project and suggest where to get started when you are logged back in.

New Year’s resolution: Work on what really matters

While this time of year can feel overwhelming, it’s also an opportunity for a fresh start. The beginning of the year is a great time to reevaluate your priorities, set new intentions, and get reenergized about your work.

If teams can change their mindset, they can turn the chaotic year-end rush and sluggish start to the new year into a seamless flow of highly effective teamwork. Breaking the circle-back cycle can be challenging, but the rewards – renewed focus, a smoother transition into the new year, and greater impact on team goals – are well worth it.

Happy circle-back season, to those who celebrate