{"id":25368,"date":"2022-12-22T17:06:19","date_gmt":"2022-12-22T17:06:19","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/22\/why-and-how-we-close-buffer-for-the-last-week-of-the-year\/"},"modified":"2022-12-22T17:06:19","modified_gmt":"2022-12-22T17:06:19","slug":"why-and-how-we-close-buffer-for-the-last-week-of-the-year","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/22\/why-and-how-we-close-buffer-for-the-last-week-of-the-year\/","title":{"rendered":"Why and How We Close Buffer For The Last Week Of The Year"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

I\u2019ve been fortunate that we’ve closed down for the last week of the year for the last seven years that I\u2019ve been at Buffer. We kicked off this at the end of 2016<\/a> and have kept up every year since then.<\/p>\n

Closing down for the last week of the year is an opportunity to pause and recharge. It\u2019s like a reset, except across the whole company. I love telling people about this practice at Buffer because they have so many questions about how we continue to operate while closing down for a week.<\/p>\n

As we work with many small businesses and creators who can sometimes struggle with working over the holidays, it feels especially important to share how we\u2019re going about this.<\/p>\n

So in this post, I\u2019ll cover what it means to close down for a week as a business whose customers are always using it, why we do it, and specifically how our largest teams manage this time off while still caring for our product and our customers.<\/p>\n

Let\u2019s dive in!<\/p>\n

What does it mean to close down for a week?<\/h2>\n

At the end of every year, we close down for the year’s final week. The exact definition of \u201cclosed down\u201d varies from company to company \u2013 some businesses will completely shut down operations while others will only close particular sections of their business.<\/p>\n

This gives everyone at the company some extra time to rest, and it creates an environment where no one is worried about missing out on projects or updates while they\u2019re offline because we\u2019re all offline. We\u2019ve done this sort of thing before, closing down for an extra long weekend in the summer, and it\u2019s always been refreshing for our team.<\/p>\n

When I say that we\u2019re closed, that means that most of the company is off (I\u2019ll elaborate in the next section), we aren\u2019t releasing new features or changing our product at all, we aren\u2019t publishing new blog posts, and it is intentionally a time of rest.<\/p>\n

In our business, creating tools for small businesses and creators building a brand online, this time of year is also reliably slow. So unlike some other industries that may pick up over the holidays, we can lean into rest by closing the company during a naturally slower period.<\/p>\n

What does this look like in practice?<\/h2>\n

For most teams at Buffer, closing for the holidays means a full disconnect. Our two largest teams, Engineering and Customer Advocacy have to create systems where we can still serve our customers and ensure Buffer is operational while also making space for additional rest. So here\u2019s how Engineering and Advocacy tackle the week off.<\/p>\n

How our Advocacy team handles a week closed <\/strong><\/p>\n

Our Advocacy team is a group of absolute pros who are taking care of our customers. This year, they\u2019ve helped solve over 60,000 customer support requests with an average first response time of just three hours.<\/p>\n

Over the years that we have been closing, they have figured out the right balance to ensure we can still help customers while also giving our Advocates that extra rest.<\/p>\n

To start, we take steps to make this period visible to our customers. They post a clear message stating that we\u2019re shut down for the holidays in all the main channels where we communicate with customers. Those include a banner for people who are in Buffer, an auto-reply to customer support email, a pinned tweet on our account, and several other places.<\/p>\n

This year, the message reads:<\/p>\n

The Buffer team is observing a company shut down between December 24 and January 1.<\/em><\/strong>
We are still responding to customer support emails and messages but will take longer than usual to reply. We\u2019ll get back to you as quickly as we can. Happy Holidays!<\/em><\/p>\n

For Advocates, we ask that each person on the team works one full day or two half days in that period. We have 21 people on the Advocacy team, and we\u2019ll have two or more people online most days. We don\u2019t always have people on December 24th or 25th, or January 1st, and we\u2019re okay with that.<\/p>\n

The team has in place a clear schedule, expectations when people are online with how to prioritize their work and get back to customers, and guidelines for emergencies. (We have those guidelines in place all the time, but it\u2019s always good to review ahead of the holidays.)<\/p>\n

How our Engineering team handles a week closed<\/strong><\/p>\n

Similar to Advocacy, for our engineers, we need to have some coverage of engineers who are on call in case something happens.<\/p>\n

For Engineering, their break looks different because they are on call, meaning they are available if something breaks, rather than fully online during this time. That means that the load of being on call can be spread among fewer people because the likelihood of them needing to be online is lower.<\/p>\n

The way that the on-call schedule works is that there are several specialized or senior members of the team who are immediately placed in all of the on-call spots. Then we ask for volunteers from the rest of the engineering team to be on-call throughout the week.<\/p>\n

In addition to having folks on call, we also do a code freeze before the end of the year. This simply means we stop shipping new code and making changes to Buffer. The goal of this is to increase our confidence that things will go smoothly for the engineers on-call and our Advocacy team.<\/p>\n

A few questions from our community about closing down for a week<\/strong><\/p>\n

We reached out on social media to see what questions people had about closing down for a week, and we got a few good questions. Here\u2019s our response: <\/p>\n

Do clients find this frustrating or ever complain?<\/strong><\/p>\n

We haven\u2019t heard major complaints or frustration about this in the past, and if ever things have not gone as planned, we\u2019ve adjusted our plan for the following year. We make sure to be very transparent that we\u2019re taking this time off across our communication channels. We still have our Advocacy team spending some time online and can reply to anything urgent.<\/p>\n

Did this impact your bottom line at all?<\/strong><\/p>\n

No, we intentionally choose a slow time for us to be closed. So it\u2019s the right time to take a break without any major impact. In addition, since the Advocacy team is still monitoring for urgent customer requests and the Engineering team is on call, we can still jump on any issues that pop up, and our customers still have support.<\/p>\n

I\u2019d love to know about the benefits your company has seen and how it positively impacts employees!<\/strong><\/p>\n

The biggest benefit we\u2019ve seen from closing down for the holidays is that our team is more rested and refreshed. It\u2019s a unique opportunity for everyone at Buffer to take a break, rather than it happening in spots throughout the year. It means the energy levels in the first few weeks of the year are always really high for us. Taking this week off for all of us at once also gives us a greater opportunity to relax because no one needs to think about projects that are moving forward without them or missing out on team communication. After all, we\u2019re all offline. This is great for us as a team, which translates into being great for our product and our customers.<\/p>\n

Do you take breaks from work or your business, and if so, what\u2019s your approach? We\u2019d love to hear from you on Twitter<\/a> or Discord<\/a>.<\/p>\n