Free software, by its nature, attracts self-driven people who like to be involved in diverse and challenging projects. I know, I am one of those people. I work with those people, I hang out with those people. But there’s a danger, when you’re a self-driven, motivated person, of over-committing to too many projects, and burning out.
Free software projects are places where burnout can happen, moreso than other places. The bazaar style model is fertile ground for burnout. There are always new projects starting up, always exciting things going on. New projects always need volunteers and, with a limited number of contributors available, it’s unlikely that a project will turn down someone who has the requisite skills and who is enthusiastic. This is particularly a danger when a contributor first comes to the project. You want to make a big impact, are super-excited, and think that the best way to become enmeshed in the community is to do everything.
This is exacerbated by the global, highly networked, nature of the project. There are no fixed hours during which work is done. People are always online working. People who enjoy their work and who are prone to working anyway, work all of the time, at all times of the day.
Throughout my years on the project, through my own experience, and through observing other people, I’ve seen that path that people go down that leads them to burning out, and walked that path myself.
I’m no stranger to overcommitting. As well as finishing off a book about the history of the WordPress project, I help out with docs, am involved with a number of large WordCamps, developer.WordPress.org, and a feature plugin. I also speak at WordCamps and meetups, and do my best to be available to if any contributors need help. At the recent working days at the community summit, I spent two days hopping from meeting to meeting with disparate groups of people.
I do, however, try to stop myself from taking on any more, particularly since I’m working on a mammoth project. Every time I feel myself jumping forward to volunteer, I pull myself back. And when I fail to do so, I am lucky that I have a colleague who I can pass stuff on to when I realise that I’ve taken on way too much (thanks Sam!).
Whose responsibility is it?
Dealing with contributor burnout is a difficult challenge. Only the contributor knows exactly how many projects they have committed themselves to. And since we operate in a bazaar, everyone is able to volunteer and have a voice wherever they want. But when you’re full of energy and ready to make a big impact in a project, it had be hard to forsee what could happen in the future. It’s so easy to volunteer for everything that comes along that sounds interesting or that could raise your profile.
As a project, we have an interest in ensuring that contributors don’t burn out. For one thing, we have a responsibility to individuals’ good mental health. Experiencing burnout is extremely traumatic and have a long-lasting impact on the contributor’s personal and professional life. Beyond that, we have a responsibility as a project to attract and retain contributors who will have a long-term positive impact on the project.
Signs of burnout
Earlier this year I was working on a particularly challenging section of the WordPress book. I was getting stressed out. I didn’t want to be thinking about it. My work was piling up and I couldn’t see the end of it. A close friend pinged me on Skype to call me out on something I’d said on Twitter that was particularly terse and cold. My response was to launch into a tirade and tell him to “fuck the fuck off.”
Day to day, this is not how I deal with things. And when I had calmed down from my rage, I realised that, even though my reasoning for rebuking him had been fine, the way I had gone about it was totally irrational and out of character.
This is one of the clearest signs that someone is burnt out, or approaching burnout: when normally rational people deal with problems in irrational ways. I’ve seen it happen in many meetings – someone who you’ve been working with for a long time deals with an issue in a way that’s totally out of character. They are terse, they snap, and get into arguments.
The other way to detect burnout is less obvious. Someone just disappears. They’ve been really active and all of a sudden they’re not around so much. Some people don’t get angry, they just withdraw. In these cases it’s hard to know what’s going on inside somebody’s head. You may have a general sense of apathy towards your work and life, find it difficult to get work done, and be unable to concentrate.
As a project, we shouldn’t just be thinking about burnout when it happens, but how we can prevent it from happening in the first place. How do we prevent people from getting so stressed out that they end up breaking down? How do we nurture our contributors so that they grow into their roles, rather than rushing in and burning out?
What you can do
- think about the area in which you can have the most impact and focus on that doggedly. Tackling one problem will have greater impact on the project than trying to do a million things at once.
- have interests other than WordPress (or whatever Free Software project you’re involved with). You need down time to think about other things, then you can return to the project with fresh eyes.
- having other interests also helps with your sense of identity. If your sense of identity and self-worth comes only from the project, then if you do crash and burn it’ll make it ten times worse.
- make time every day to do something that you love, whether that’s writing code, writing, painting, drawing, spending time with your family, running, or whatever. When you’re prevented from doing the things you love you’ll feel resentment, which can contribute to burnout.
- if you think you’re becoming overstretched, talk to someone. There are lots of people who want to help. It’s better for one project to fail than to lose and damage a contributor.
- take care of your health. Eat properly, exercise, get out of the house every day.
What we can do
- be aware of the signs of burnout and talk to contributors who are having problems.
- ensure that no one spreads themselves too thinly.
- create a collaborative culture, one where individual and heroic feats of coding, writing, or organisation, are given less weight than participation in a team effort.
- disseminate knowledge to ensure that no one is a single point of failure. This puts too much mental pressure on contributors and makes the project structure fragile.
- make it clear that it’s okay for a person to step down from a project, that someone else can be found to take on the work.
- if a contributor is struggling with one project, help them to find another one that they can get excited about.
- create good workflows that help people get work done, rather than making it difficult for contributors.
- stay on top of communication. Being stuck behind roadblocks that you can do nothing about is incredibly stressful and frustrating.