Randy Fay is doing a session at DrupalCon on Burnout:
We have an incredible group of people who invest deeply in our common project. Some significant portion of this group is near burnout at any given time, and we've lost important contributors, some famously, as a result of this.
The more general problem is: How can we help our contributors to manage their work so they don't get so close to burnout? How can we help people find (or regain) balance while dealing with the technical and social problems of contributing to our great project?
- Begin a concentrated initiative to grow and keep our contributors, and to keep them happy.
- Make this a goal a key project responsibility.
He just posted a blog post, on defining burnout and signs of it, this week as well.
Burnout among community leaders is real and damaging, not just to those who are burnt out, but the greater community who rely on these people. I have seen friends burn out, and I have been teetering on the brink of full on burnout for a while. Now I'm going to be blatantly honest about why I think it happens and what we could do about it. Please take my complaints as fodder for improving, and not slights on the community!
I think that personally, and as Co-lead of Docs, my increasing burnout can be attributed to a few factors:
- Work. Of course, I have my non-volunteer work to do as well, and that takes precedence over my volunteer position. Work has been really busy for the last year, and that's taken away a lot of the time and energy I was previously dedicating to Docs and core.
- Life. General stuff going on in life has also distracted me from working on Docs. It's a fact of life that personal factors will come into play, good or bad. Last year when I was sick a lot, I actually had more time at home on my own to be online.
- Health. I have chronic health problems and my energy levels fluctuate wildly from week to week. Some weeks I can keep up, others I can't. But the issue queue doesn't care about my health!
- Lack of community support. Let's face it, docs can be the ugly duckling of development work. Lots of people write code and don't put docs online for it, or update code and don't update docs. There are a TON of docs. There are a TON of redundant docs. There are a TON of missing docs. It's a real beast, and the amount of material to write, format, and maintain is hugely disproportionate to the amount of time the community puts into docs. Which brings me to...
- Lack of resources. There are not many people who write and maintain the docs, and this group is often transient, moving onto development, or working in short bursts. That is not helpful in keeping up on the amount of work to be done. This could be a fulltime paid job, and there is virtually no funding for docs. Managing people is a big job, I think I actually got way more done for docs before becoming Co-lead as none of my time goes to writing docs now, it all goes to managing the issue queue and responding to questions/requests, leaving no time to do more overarching tasks.
- It's often a thankless job. Sure other avid contributors are often extremely thankful for the work the Docs Team does. But sometimes I feel like the project's documentation is taken for granted, and there is a tone of entitlement to good documentation (contrib maintainers surely see this as well). Issues in the queue complaining about the state of the docs or demanding documentation on a particular topic are disheartening - I see the same thing in the queues for popular contrib projects. Maintaining the docs is like treading quicksand, and it's a losing battle with the current resources.
- Expectations. I can't even imagine doing the job of Docs Lead on my own! OMG. I have no idea how Addi survived it as long as she did. This position is not realistic! Even with Jennifer managing docs infra and API docs, and me just managing the online docs, it's a hefty job. It's not enough. We have a few a few topic coordinators listed, but we really need more, as well as team members who can help with docs for the ever growing library of contrib, and help maintain the docs queues. Additionally, this is an under-resourced volunteer position and people need to adjust their expectations accordingly. For me, the expectation that I will attend a DrupalCon, and submit sessions, as well as lead the docs sprint is even a large one. My health doesn't often allow me to even attend full days of the conference, nevermind those added responsibilities.
- Give some, want more. It seems when someone volunteers to give some of their time and energy to the community, there is always a want for more. I understand that it's a compliment that the community thinks a volunteer does good work. But it's important not to overburden people who already have huge responsibilities. I've been learning the hard way to say no more, but as much as I appreciate being given additional opportunities, don't care for any kind of "oh, you're missing out" attitude when I turn down opportunities that would take up even more of my time/energy/finances.
Maybe I'm not cut out for this! But maybe "this" just needs to change for all leaders in the community... Enough about what is going wrong, what can be done to improve?!
- More, smaller leadership positions. The community and amount of docs and code we maintain is constantly growing. Co-leads and more coordinators are essential for the continued health and sanity of our contributors. Topic coordinators in docs, and things like the Views bug squad are good starts, but we need more people helping, and we need to work on enabling them to be more self sufficient so they're not always waiting on feedback. (If you want to be a topic coordinator for docs, let me know! More are listed on g.d.o.)
- Respect the time of community leaders. If someone doesn't respond immediately, don't get angry. If a leader needs to take a break, for instance going on hiatus for a couple months, respect that. We are doing our best. That said...
- We need to accommodate time off! Leads shouldn't have to be on duty 365 days a year. Every person in a leadership position that is fairly critical should have either a co-lead and/or an understudy. Someone who can help out and when needed take over for a while. Just the existence of this structure would take a lot of pressure of leaders to not have to be available all the time.
- More people need to help. I know, this is an ongoing issue for open source projects. But we need to get more Drupal users and community members to participate, especially in some of the less popular tasks. They still need to be done! Maybe we need a marketing campaign of some sort? Some people, like me, even enjoy these kinds of tasks, so we should also...
- Revere "gruntwork"! Things like support and documentation aren't just gruntwork - they are really important tasks for all levels of community members. They shouldn't just be looked at as a stepping stone to development work. Support and Docs Team members should be nurtured just like developers are, and given the same respect so that they aren't perceived as lesser positions in the community. Not saying everyone has this attitude, but it's important, especially as the community grows to recognize these tasks as critical parts of the ecosystem.
- Funding for docs? I don't know if it's realistic to get funding for documentation work. It sounds like it'd be possible for a huge infra project, but isn't so much for day to day needs. Not sure how to get more help with our infra from the larger community so that we can help our processes become more efficient.
- Reset expectations. When interacting with anyone in a major leadership position, remember how much we are responsible for. Try not to be impatient with us, or demanding of our time. Don't put pressure on leaders to contribute more. We're volunteering to help, but that doesn't mean we are solely responsible. Which reminds me, we need to find a way to...
- Make contributors more self-sufficient. Documenting how to help doesn't seem to be enough. I would love to see a more structured mentorship system in place that would take some of the weight off of the shoulders of people already in leadership positions. There are many community members who could answer simple questions and help onboard new contributors. And yet it always tends to be the already overburdened leaders who take this on.
- Rethink things. Finally, I think that we could really rethink some of the more burdensome parts of the community task list. For instance the documentation. Should Docs Team really be responsible for this massive amount of community contributed docs? Should we just manage some "official" core docs and end user tutorials? Maybe there are other approaches that would work better with the growing community. Open to suggestions!
Preventing Volunteer Burnout
And now, some tips from our dear friend, the internet, for preventing volunteer burnout:
In my experience, burnout can happen for a number of reasons: the work I’m doing isn’t challenging, the work I’m doing has little meaning, I’m not learning anything new, I’m doing something I’m not passionate about, or the workload I’m shouldering is overwhelming. - Tom Johnson, 'Avoiding Burnout as a Technical Writer'
Moderation is key...aying no is difficult, especially if you think your answer is going to disappoint someone. But it's necessary since spreading yourself too thin can be a bad thing for you and the recipient(s) of your volunteer efforts. It's best to be sensible about your time so that you're able to maintain the energy and desire to honor the commitments you make. - John Barrymore, 'How Volunteer Burnout Works'
As the saying goes, "if you want something done, ask a busy person." ...in Canada. Interestingly, a small minority of volunteers accounted for the bulk of the hours. The top 25% of volunteers accounted for 78% of total hours of volunteer support... If they do not get the balance they will get burnt out...The problem is that we do not notice the burnout coming until it is too late and what you are left with is either a very unhappy volunteer or a great volunteer who quits.
- Connect to purpose
- Create an achievable position description
- Give volunteers holidays
- Set guidelines at the start
- Create an environment that is welcoming
- Thank volunteers
Slideshare, takes a while to load - the slides are pretty self-explanatory...
In my volunteer management work, I see and hear about volunteer burnout. Volunteer 'burnout' was the term coined years ago to mean asking those faithful volunteers to do more and more to the extent that they actually burned out, left the organization, and likely stopped volunteering altogether. This was likely the beginning of serious recruitment issues: instead of recruiting new volunteers, those who could be depended on were asked for more 'time'.
"Volunteers who are committed continue to be asked to give more time. We are also expected to give more money to the causes we volunteer for. We are also expected to sell more, promote more, and show up at fundraisers." - Donna Lockhart, 'Volunteer Fatigue: What impact on the future of volunteerism?'
Finally, a great post from my favourite Project Management author, Michael Lopp, on bordom and burnout (not directly related to volunteering): 'Bored People Quit'. I think this is also important because doing repetitive tasks and being constantly overburdened can also be boring - it strips away the creativity that keeps people engaged. We need to try and make sure that smart, engaged contributors have that creative time so they don't get bored!