"Great things are not done by impulse, but by a series of small things brought together." —Vincent Van Gogh
This excerpt is from The Art of Community. Building communities is vital today, whether it's to build a reliable support network, serve as a valuable source of new ideas, or provide a powerful marketing tool. In The Art of Community, you'll learn about the broad range of talents required to recruit, motivate, and manage community members. The book takes you through the stages of community, and covers topics ranging from software tools to conflict resolution skills.
"Rolling" was optimistic. Instead, I sat bumper-to-bumper in traffic with half of Southern England, all joined in curiosity about whether or not that film with Michael Douglas could become a reality on this cold English day.
This wasn't helping my nerves. As a fairly outgoing, angsty teen, nerves were not usually my bag, but tonight, I was dining on them.
You see, tonight was different. Tonight I was doing something unusual, something that had seemed like a great idea...when I wasn't running 30 minutes late, hammering my way down the motorway, with my Number Of The Beast cassette ritualistically sacrificed to the gods of hi-fi just for good measure.
Thankfully, the world's longest mechanical conga line decided to crank it up a notch. Before I knew it, I found myself on a street I had never been to, in a city I had never been to, about to head into a room full of people I had never met before, all united by one simple symbol... ...a penguin.
An hour before, that penguin had seemed so inviting and friendly. It was a symbol that encompassed everything about the movement it represented, a movement that came together in spirit and mind to build a system that drove a new generation of technology and freedom...a movement that celebrated this drive by forming user groups in unknown streets, in unknown cities, and with unknown people.
But as I stood there, doorbell already pressed, none of that was even close to my conscious thoughts. Instead, the brain of one Jonathan E J Bacon was battening down the hatches, preparing for ultimate, unparalleled discomfort as I walked into a place where I both did and didn't want to be at the same time.
Then, the door opened and a rather nice chap called Neil welcomed me into his home.
Community is a funny beast. Most people—the kind who watch talent shows on television and occasionally dip bread in oil in an expensive restaurant—don't understand people like Neil. Why on earth would this guy decide to open his home, free of charge, to a collection of strangers who met on the Internet? Why would he want to spend an evening drinking tea and making jokes about something called "emacs"? And why would he fund online resources like fliers, a mailing list, and a website from his own pocket, start a book-lending service for the group—and even shell out for tea and biscuits?
One person who really didn't seem to understand was Neil's wife. Somewhat bemused, and referring to us as his "Internet friends," Neil's significant other decided tonight was the night for visiting a long-lost (or possibly ignored) relative, rather than sticking around and faking interest.
But Neil is not unusual. At least, not in the Open Source, Free Software, Libre, and Free Culture world. There are many Neils all over the globe, organizing groups, setting up mailing lists, scheduling meetings, and coming together to share an ethos: the combined set of beliefs, customs, and sentiment that flows between like-minded people.
In the last 10 to 15 years, we have seen Free Culture in technology, art, and media explode into our consciousnesses. The entire machine is driven by people like Neil: people who volunteer themselves to the concepts of community and togetherness wrapped around such an ethos.
There are Neils outside the Free Culture world, too. They're in church groups, helping the poor and unfortunate; in Neighborhood Watch and Meals on Wheels campaigns, reaching out to those around them; and in public art installations, political groups, and craft fairs. They volunteer, perform, and share their opinions and creativity on anything from aerobics to knitting to yoga.
What intrigued me when I first walked into Neil's living room was the concept of a collaboration-driven ethos, although at the time I had no idea what those words meant. What that experience taught, and what that evening inspired in me, was an excitement about what is possible when you get a group of people together who share a common ethos and a commitment to furthering it.
In my world, that ethos has thus far been Free Culture, Free Software, digital rights, and breaking down the digital divide, but it can be as critical as solving world peace or as fanciful as sharing photos of kittens playing guitars on the Internet. The importance of community is not in the crusade, but in how you unify people to march forward together, side by side.
At its heart, The Art of Community is a distilled set of approaches and thoughts about how to build community. The book is a collection of experiences, observations, and thoughts from my career and elsewhere. My aim is to bring this grab bag of concepts and curiosities together into one consistent text.
However, it is important that we keep the book in perspective in the wider scheme of your growth as a community leader and organizer. You should mentally frame the content here as a foundation for your own ideas, but remember that practical experience is the real magic that we want to create, with theory merely the glittery jacket and spinning bow tie.
Community is fundamentally a soft science. Compare it with, for example, programming. If you want to write a computer software application, you write it in a programming language. These synthetic languages are vessels of logic. They live and breathe in a world where the answer to a question is either yes or no; there is no maybe. In a world where maybe does not exist, you can plan ahead for an answer. With community, the importance and diversity of the question is equally essential.
In this chapter we are going to be exploring the big-picture attributes that are present in every community. As such, this chapter is filled with a lot of high-level theory that is important to our journey.
It may be tempting to steam ahead and dig into the hands-on content in later chapters, but it is recommended that you read and understand all of the concepts in this chapter first.
This chapter was designed for tea and snacks. Go and grab some, curl up in a chair, and get ready to explore the social schematics of your community.
On February 26, 2004, three friends and I released the first episode of a new audio show called LugRadio (http://www.lugradio.org/). Although LugRadio will feature extensively in this book as a source of stories, all you really need to know about it right now is that (a) it was a loose and fun audio show (a podcast) about open source and free culture, (b) on that day it was entirely new, and (c) we had absolutely no idea what on earth we were doing. Radio personalities across the world were not exactly shaking in their boots.
Recorded in a very small room that I called a studio, but was actually a bedroom filled with second-hand recording equipment, LugRadio involved my three compadres and I opining into four precariously balanced microphones that fed into a computer. Episode 1 was around half an hour long, composed of bad jokes and a book review, and totally unpolished. At the time, it was just new and different. (Little did we know that four years later we would wrap up the show having achieved over two million downloads.) Anyway, enough of the selfcongratulatory back-patting and back to the story....
With the show out, we did what many of us in the open source world do—we set up forums, wikis, and channels, and tried to get people together around our new project. The forums went online first (http://forums.lugradio.org/), and people started joining.
The 22nd member was a guy called Ben Thorp, known as mrben on the forums. An Englishman living in Scotland, mrben was an open source enthusiast who stumbled onto the forums, listened to the show, and liked what he heard. For the four years that LugRadio lasted, mrben was there every single day: in total contributing over 3,000 posts; involving himself in the chat channel, the wiki, and the organization of the live events; running an episode download mirror; and much more. mrben was there every step of the way, loving every second of it.
The first question is—why? Why does a 30-something Engli-Scot decide to immerse himself so deeply in a group of people he has never met before? What is it that makes him want to spend time away from his friends and family to contribute to a radio show performed by four strangers in a different country? Why would he want to contribute to something with seemingly no financial, career, or other conventional benefit to him?
A cynic could argue that mrben is some kind of socially challenged nerd who can only communicate with other similarly socially inept nerds. Conventional wisdom sometimes argues that anyone who contributes their time freely to something that could not benefit them financially is weird. This was clearly not the case with Ben. He had a job, a wife, and a child. He went to church regularly. When I had the pleasure of socializing with him, I found him a fun, smart, and entertaining part of the group. In fact, at two of the live events, he was a guest in my home. Social deviation was clearly not the answer, or if it was, he hid it well.
The reason why Ben was so involved in LugRadio, why Neil ran the Linux User Group meeting, and why thousands of other community members around the world get together, comes down to one simple word: belonging.
By definition, a community is a collection of people (or animals) who interact together in the same environment. Community exists everywhere in nature. From people to penguins, from monkeys to meerkats, the vast majority of organisms exhibit some form of collective grouping. Grouping, however, is a touch simplistic as a means to describe community. It is not merely the group that generates community, but the interactions within it. These interactions, and the feeling of belonging that they produce, are generated from a distinctive kind of economy: a social economy.
At this point in our journey, it is clear that belonging is our goal. It is that nine-letter word that you should write out in large letters and stick on your office wall. It is that word that should be at the forefront of your inspiration behind building strong community. If there is no belonging, there is no community.
From the outset, though, belonging is an abstract concept. We all seemingly understand it, but many of us struggle to describe it in words. I identify belonging pragmatically: as the positive outcome of a positive social economy. In the same way that we judge a strong financial economy by prosperity, wealth, and a quality standard of living, belonging is the reward of a strong social economy.
An economy is a set of shared concepts and processes that grow and change in an effort to generate a form of capital. In a financial economy, participants put goods and services on the market to generate financial capital. The processes and techniques they use include measuring sales, strategic marketing, enabling ease of access, and so forth. A social economy is the same thing—but we are the product, and the capital is respect and trust. The processes and techniques here are different—open communications mediums, easy access to tools, etc.—but the basic principles are the same.
Stephen Walli, a prominent commentator on open source in business and review editor for The Art of Community, drew some interesting connections between the underlying concepts in a financial economy and how they apply to the open source social economy. He presented these thoughts in his piece entitled "Free and Open Source Software Developers Working for Free (Economics 101)" (http://stephesblog.blogs.com/my_weblog/2007/09/free-and-open-1.html):
"People value their skill sets differently in different contexts, but value them they do. I use writers as an example to explain this to nondevelopers: a technical or marcomm writer may spend 8 hours a day at their paid job, then spend their evenings and weekends teaching ESL classes at the local college, working on a newsletter for their local church/synagogue/neighborhood organization, helping a child with a school project, and writing a sonnet to their significant other (or the next great novel or screenplay). In every case they're using their writing skills; they're just valuing them differently in different contexts.
There's another way to look at it. Not every market involves exchanging money for goods and services. A gem of an economics book (Reinventing the Bazaar by John McMillan, 2002, p. 135) points out that well-designed markets, regardless of market type, have a number of things in common:
Let's look at well-run free and open source project communities in terms of such market dynamics.
- Information flows smoothly.
- People can be trusted to live up to their promises.
- Competition is fostered.
- Property rights are protected, but not overprotected.
- Damaging side effects on third parties are curtailed.
Individual projects behave as markets from one perspective, and code is currency, the medium of exchange. Just like all economic exchanges, the contributor offers something they value less (a fragment of code solving a particular need) for something they value more (the functioning software package in its entirety). Nobody is working for free in an economic sense."
- Information flows smoothly—transparency of community, process, code, policy, bugs, discussions.
- People can be trusted to live up to their promises—the project's license is a social contract. Its governance culture is well understood and supported.
- Competition is fostered—what fixes and features are accepted, and which ones don't make it.
- Property rights are protected, but not overprotected—code copyright management and licensing is handled properly in well-run projects.
- Damaging side effects on third parties are curtailed—the point here from the book is that WHEN real damage might be done to third parties, there are ways governments can involve themselves in the market to curtail such effects, whether by defining/enforcing property rights, taxes/ incentives, or policy/regulation. The community's license comes to mind.
Social capital is known by us all, but we know it by many different words: kudos, respect, goodwill, trust, celebrity, influence, supremacy, greatness, and leverage, to name a few.The first known use of the term "social capital" (referred to in Robert Putnam's Bowling Alone: The Collapse and Revival of American Community) was by L.J. Hanifan, a school supervisor in rural Virginia. Hanifan described social capital as "those tangible substances [that] count for most in the daily lives of people: namely goodwill, fellowship, sympathy, and social intercourse among the individuals and families who make up a social unit...". Social capital is the collective family of positive interactions between two or more people. When you affect someone positively, it builds your social capital. This could include being generous, helping someone, sympathizing over a problem, or something else. Hanifan identifies the opportunity behind social capital:
The individual is helpless socially, if left to himself.... If he comes into contact with his neighbor, and they with other neighbors, there will be an accumulation of social capital, which may immediately satisfy his social needs and which may bear a social potentiality sufficient to the substantial improvement of living conditions in the whole community. The community as a whole will benefit by the cooperation of all its parts, while the individual will find in his associations the advantages of the help, the sympathy, and the fellowship of his neighbors.
The meat in Hanifan's description is the opportunity for social capital to "bear a social potentiality sufficient to the substantial improvement of living conditions in the whole community." In essence, if a member of your community has a positive approach to another member, his social capital grows, which has a positive impact on that person and the community as a whole. It all sounds a lot like karma, and it is.
Of course, capital, whether monetary or social, is not the end game. People don't make money for the purposes of just having money: they make money because it allows them to do other things.
This is an important aspect of understanding where an economy starts and ends. Most folks riding the financial economy are not purely greedy numbers freaks who just want a big pot of money; most people who work with social capital are not merely air-kissing, hand-wavey, superficial animals who simply want to name-drop and be name-dropped in the interests of social acceptance. Of course, the greedy and the socially obsessed do exist, but it is important not to use them as a basis for judgment. The economy is not flawed; those people are flawed.
A final point: for an economy to work, every participant needs to believe in the economy. Belief is a critical component in how any group of people or animals functions. This can be belief in God, belief in values, or belief in a new future. Whatever the core belief is, the economy and the community can be successful only if everyone has faith in it.So let's have a quick recap:
In many ways, an economy is like a flowing river: it never stops, and the flow is critical to its success. Economies never stand still. Every day they change, adjusting to stimuli in the world that affects them. At the heart of how this movement works is communication.
Peter Bloch, a consultant on learning, makes an important foundational observation about communication in a social economy: "community is fundamentally an interdependent human system given form by the conversation it holds with itself." When I first heard that quote, I realized that the mechanism behind communication in a community is stories.
Stories are a medium in which we keep the river flowing. They are the vessels in which we not only express ideas ("I was taking the subway to work one day, and I saw this lady on there reading the paper, and it made me think xyz"), but also how we learn from past experiences ("there was one time when I saw David do xyz and I knew I had to adjust how I myself handle those situations in the future"). Furthermore, when the characters in the stories are people in a community, the stories are self-referencing and give the community a sense of reporting. Communities really feel like communities when there is a news wire, be it formalized or through the grapevine.
Not all stories are cut from the same cloth, though. Communities tend to exchange two very different kinds of story: tales and fables.
Tales are told for entertainment value and to share experiences. They are individual units of experience that are shared between people, and their primary value is in communicating a given person's experience and adding to the listener's repertoire of stories and experiences.
Fables are different. Fables are stories designed to illustrate an underlying message. The vast majority of us are exposed to fables as children, and these stories are passed down from generation to generation, each one extolling a moral message to the youth of the day.
Let us now take a step back to our earlier story about mrben joining the LugRadio community. This story was itself a tale that shared an experience that encased many of the concepts we have explored.
When mrben joined the LugRadio community, he identified with the ethos of the show. Then he began to engage with stories: first hearing them on the show itself, then getting them from the community, and finally sharing them himself. As mrben contributed more and more, his social capital started to rise—the community had a lot of respect for him and his opinions. He, in turn, had belief in the community and his own abilities. This objectivity in his storytelling and his general demeanor all contributed to his social capital. As he continued to be a part of the community, his sense of belonging developed. At this point, mrben was living and breathing LugRadio, its community, and its ethos.
The result of this process is a community member with a strong sense of loyalty. Some of the greatest examples of belonging and commitment to an ethos occur when the community is threatened. An interesting example of this was when we released Season 5 Episode 3 of the show and received a rather angry statement from a listener who was clearly agitated at the level of expertise on the show and the generally positive attitude toward Ubuntu (which all of the presenters used):
Nowadays I mostly stick to Dave Yates at lottalinuxlinks who is a genuine linux obsessive, Chess Griffin at linuxreality who maybe does stuff for noobs but is genuinely knowledgeable about Linux, and the guys at the linuxlinktechshow because they work with Linux and know what the f**k they're talking about.mrben, who had spent a few years in the community by now, responded to the criticism using stories to make his point:
I think you'll find that all of the presenters on LugRadio work with Linux on a daily basis. Whether or not they know wtf they're talking about is, of course, a matter of opinion. But the addition of Chris and Adam to the team, both of whom (IIRC) are professional Linux sysadmins, is an influx of knowledge on that side of things. Jono has a long history of working with Open Source and Linux within the community (bingo!) even if his technical knowledge is not at the same level. Aq is a Free software zealot, but is also experienced in web development and usability. I still think it's a good mix, personally.
The Ubuntu thing is an issue, admittedly. But then, LugRadio still reflects my experience of LUGs —the majority of people are talking about Ubuntu. It has become the mainstream desktop distro, and the benchmark that most people mark other distros against. But, IMHO, the recent shows haven't shown an overly Ubuntu slant. Look at this show—you've got an interview with Quim Gil, which is about Maemo, not Ubuntu, the finger of God, which is plain silliness, the software vendors and security issue, which applies across the board, and packaging, which was fairly Ubuntu specific, but could easily relate across to other Debian-based distros, and, as Chris said, he would've talked about RPM if it had been possible.
The "Ubuntu slant" is more about personal usage and experience, rather than a change in the show's direction (which was unashamedly Debian slanted before Ubuntu came out....)
In his three-paragraph response, mrben referred to 12 distinctive points and facts, citing many from existing online material. His response not only sought to convince the original poster of his error, but to demonstrate to the community that the poster was wrong, thus providing a sense of security. By using objective facts, he also spoke with the voice of the community, not just his own opinion. mrben's response was driven by belief in the community, formed by familiarity with stories, and legitimized by a wealth of social capital. Subtle, yet inspiring.
Although the underlying social economy infrastructure in community is compelling, it is important to remember that it is merely a structure designed to deliver a far more exhilarating prospect—opportunity. And with that, lets spin back in time first....
When I first learned about Linux, I was running a small bookshop in Milton Keynes, in Southern England, and living at home, having taken a year off before starting university. When Simon, the eldest of my two siblings, stayed in our house for a few weeks on his return from the USA, we frequently spent the evenings talking about computers and stand-up comedy.
On one of those evenings, while I was hurling abuse at my computer, Simon expressed surprise that I used a "Mickey Mouse Operating System." I was surprised myself. As far as I knew, Windows—Windows 98, at that—was all that existed. Simon told me about something called "Linux," which I could get for free, on the back of a book.
Armed with my 10% discount, I eagerly snagged a copy of Slackware Unleashed, and Simon set to installing Slackware 96 on my desktop computer. Two weeks later, having used guile, cunning, a soldering iron (literally), and maintaining the alignment of the planets, I actually got the thing to boot. As I gazed eagerly at the screen, ready to experience the next generation of operating system technology, I was confronted with:
It was not exactly Minority Report.
Simon, being the kind and sharing brother he was, wrote the username and password down on a piece of paper, stuck it to my screen, and promptly sodded off. The following day, he moved out. I was left with a login prompt, some nerves, and absolutely no idea of what to do. So I cracked open the book, threw on a Testament album, and started reading.
It was then that I read about the Free Software community: a worldwide collection of enthusiasts all connected by the Internet, sharing an ethos that software should be free while building a replacement to the Microsoft behemoth that frustrated so many. Piece by piece, this global army provided software alternatives, many of which improved on their commercial counterparts. Back then, Linux was in the dark ages of computing. It was all command-linedriven, devices rarely worked, and to do anything you needed to compile code. Still, this concept of a worldwide community sharing code absolutely fascinated me. I first smelled the sweet aroma of opportunity.
Although the reality of open source in 1998 was primitive, the potential within the community is what inspired me to stick with it. To be honest, I was pretty perturbed by the sheer complexity of it all. In those days it was insanely complicated to get a system up and running, and the innards of the operating system were on display for all to see. (These days, as Uncyclopedia [http://uncyclopedia.wikia.com/] so eloquently puts it, "Linux distros are so idiot-proof that you can put their install CDs into the floppy drive upside-down and it will still work" [slightly edited for a family audience].) Back then, we all knew that life with Linux was a lot harder than it needed to be, but the strong sense of underlying opportunity helped spark the imagination to put up with that complexity for the potential of a better future.
There is an important connection here in which imagination and opportunity are close friends. Imagination offers the mind a vision of how things could be. If there is a viable path toward this future, we build a sense of opportunity. If there is no viable path, we enter the world of fantasy.
Linux, and the possibility of it becoming a prominent operating system, was by no means a
fantasy. The rails were on the ground. The community just needed freely available tools and
communication channels to gather the materials, build the train, and put it on the track. In
the case of Linux, this manifested in three primary areas:
With an open community and publicly visible and accessible communication channels, anyone can join the community and meet hundreds of thousands of other community members just like them.Licensing of work
Every contribution to the Linux community is licensed in such a way that it benefits the entire community. The fair licensing of all contributions adds a strong sense of confidence to the security of the community.Open tools
Anyone with an Internet connection and a computer can contribute. All of the development tools and documentation are entirely free and open to access. This provides a low barrier to entry, and lets new users play with the technology.Although these elements were essential at the birth of Linux, it is not open communication, licensing, and tools that generate opportunity. These elements merely made it possible to build a world-class Free Software operating system. Opportunity is born in a sense of belief.
Belief is a critically important human function. Whether your belief is in an all-creating god, in a family member's ability to achieve something for herself, in a better future in your neighborhood, or in the reliability of a restaurant guide, belief is what gives us hope for the world around us. Belief can also make human beings surprisingly resilient in intensely difficult and uncomfortable situations.
One example of this is an incident that occurred a few years back. Every year, as part of LugRadio we host a face-to-face get-together called LugRadio Live (http://www.lugradio.org/ live/), which is a very different style of conference. We have worked hard to deliberately make the conference fundamentally a community event. Equality between commercial vendors and the community is a key attribute, and we deliberately set a low cover charge to keep it accessible. In addition to this, we have worked to produce a very informal and inclusive atmosphere, inspired largely from music events. (Many referred to
LugRadio Live as a "rock conference.") LugRadio Live has carved out something of a reputation for being different, and each of its participants has been very keen about advocating it and its formula. There was a strong sense of belief in the event—an event that was distinctively community-oriented and -driven, open to participation and available to all.
With LugRadio Live scheduled for July 22–23, 2006, everything was going to plan. The speakers and exhibitors were sourced, the schedule was in place, the social events were arranged, and the crew and community were ready. Everything was great until the evening of July 18, when I received news of an impending rail strike. The strike was planned for the full weekend of the event, with every rail link going down. The country would be completely inaccessible by train.
I have never experienced such anger and frustration. For around an hour, I transformed into an ultra-conservative right-wing anti-union crazy, and I stomped around the house, venting in the direction of my computer screen. We had spent six months of feverish planning and hard work, and this union decided that their problems were more important than anyone else's, and it was entirely reasonable to take the country down. I, for one, was not a happy bunny.
But, as my fellow organizers and I seethed on the phone, the community was already doing its thing. Forum threads appeared instantly to keep people up to date on the strike, blog entries were drafted, a nationwide car-sharing scheme kicked into play, and speakers and exhibitors were notified. While all of this was going on, I was on the phone tearing a strip out of both the union and the rail organization for their decision. Fortunately, the strike was called off a few days later.
What stunned me was just how mobilized the LugRadio community was. The community saw a threat to something they felt invested in, and reacted as a team to cover all the bases and try to limit the damage. Without any prodding from us, they made things happen. In a time of such panic and frustration, that community wrapped around each of the organizers like a comfort blanket. It was one of the most inspiring examples I have ever seen of a community coming together, driven by a belief in something we all shared.
Where belief gets exciting is when it is combined with that friend of ours from a few pages back: opportunity. Belief in a shared crusade—and a sense that the tools and opportunities are available to achieve that goal—is an intensely liberating feeling. People get a sense that they have control over their own destiny.
An example of this was the election of Barack Obama as President of the United States. Building up to his victory, the USA was facing difficult times. Led by a president who many lacked faith in and faced with a global economic crisis and a complex set of foreign affairs, the U.S. had a lot to deal with, including a growing sense of cynicism among its people. Many Americans had lost faith in politics and pride in their country. As Barack Obama stepped up as a candidate for the presidential election, he instilled a sense of belief and opportunity that inspired his followers.
When people feel that they can achieve a dream, it builds an incredible sense of liberation and a willingness to step up to the plate. People become very committed, very quickly. We saw this in droves throughout the presidential election. Thousands of people across the country took to the streets to tell the world about Obama.
Around that time I had kissed chilly England goodbye and relocated to sunny California. The Bay Area was a particularly fascinating place to be—people setting up tables, selling stickers, knocking on doors, and making phone calls. It seemed that one in three people on the street was wearing an Obama t-shirt.
Whether Obama was the right man for the job is the topic of a thousand other books, but he had the ability to define belief, opportunity, and liberation in a language that a nation could understand. His inspiration—and his army of passionate Obamaniacs—sealed his place in the oval office. This in itself was an incredible exercise in building, energizing, and inspiring community, and regardless of your political inclination, it was a stunning feat.
So far, we have explored some of the high-level concepts and architecture behind community and how it is structured. It is these concepts, such as social economy, belonging, belief, social capital, and communication, that help to draw the outline of the picture. We will use the rest of the book to color in the details.
Before we move on, though, we should spend some time profiling the artist holding this palette of colors. What are the skills required to draw the picture? What attributes will help us put the right colors in the right places? What do you need to build really great community?
Metaphor aside, community building is a genuine art form. Like any art, there are attributes and characteristics that define someone as an artist, but every artist has his own "special sauce" that makes him unique and different. Every one of you lucky enough to have your nose buried in this book will have yours. Although I talk about some common characteristics all community managers should have, always strive to find your own approach.
My wife and I often joke about how I respond when someone asks me what I do for a living. I used to describe my job as "managing a worldwide community of volunteers," which sounded rather accurate and complete to me. My wife was less impressed. She rightly nudged me andsuggested that made it sound like I manage a large online forum of very weird Japanese animation fans with a worrying obsession with tentacles. From that discussion onward, I have tried to summarize what we community mangers do in one sentence. The best I have come up with is:
I help to enable a worldwide collection of volunteers to work together to do things that make a difference to them.I know, it needs work. Send better suggestions to the usual address....
Twenty of those twenty-one words are really just filler around the word that I really think describes what we do: enable.
Our function as community leaders is to enable people to be the best they can in the community that they have chosen to be a part of. Our job is to help our community members achieve their greatest ambitions, and to help them work with other community members to realize not only their own personal goals, but the goals of the community itself.
For community leaders and managers, trust is a critical component in gaining the support and confidence of your community members. Earlier, we explored the example of Barack Obama stepping forward to enthuse a nation in turbulent times. Part of the reason why those times were turbulent was a significant lack of trust in President George W. Bush. When trust vanishes, words and promises lose their meaning. When trust is present, words and promises flourish in a world where they have purpose and potential.
Trust, though, is not something you can learn. You are either trusted or you are not. As my father-in-law said to my family one evening over dinner, "Live your life honestly—if you don't, you always have to remember to not be yourself." His words teach an important lesson: when trust is implicit in every step you take, you can always be confident in the transparency and openness of your actions. This is the most important aspect of community leadership, and of life itself.
Part of the reason why trust is so critical is that, as a community leader, you want to be emotionally close to everyone in your community. You want everyone in that community to think of you as an accessible, approachable, sensitive person, and trust is required for any of these roles. People will approach you for advice, for guidance, to discuss personal issues, to handle conflict, and more. Many of these situations will be complex, and will require a significant level of sensitivity and confidence.
But then again, some people will inspire you with their sense of responsibility, their ability to react to situations with grace and elegance, and their willingness to care for the community. As a community leader you will experience all sides of human nature, from strength and innovation to weakness and uncertainty. Whatever you hear from your community, you should endeavor to be the best listener that you can.
When you can demonstrate trust and the capability to listen, your community will develop respect for you. They will be there to listen to you, work with you, to stand side-by-side with you in your battles and become a large extended family that you can rely on.
This respect has an important function in reinforcing belief in your community. When community members have responsive positive interactions with community leaders, it makes the community feel more inclusive, which generates belief and, importantly, belonging.
Respect is a wonderful gift, and you should cherish it and protect it at all costs. Getting that respect back after you lose it is a near-impossible task.
The biggest risk that can face any community leader is excessive ego. Unfortunately, ego is something that plagues a lot of people who assume a form of leadership.
One rather fun side effect of an influential position is fame; people know who you are, they read your words, and they listen to your opinions. The growth of the Internet and online communities has made it easier than ever to bolster your ego. Google searches, social networking websites, news feeds, alerts, statistics tracking, and more make it easier than ever to find out how many people love (or loathe) you. While this may seem incredibly flattering at times, strive to get your audience in perspective. The world is a big place, and you have some incredible contributions to add to it, but always aim to strike a balance between valuing your contributions and disappearing up your own arse.
Unfortunately, I have seen ego claim too many victims. I have seen community leaders who have commanded incredible respect and adoration from their legions of fans, but have washed it away when they assume a sense of entitlement. In any community, entitlement is an enemy: it values the person over the contribution, creating unrealistic expectations about how people should be treated. People with this sense of entitlement typically identify the wider contributions of the community, but see their fame as a red carpet that others don't have access to. You can avoid the wrath of ego by always remembering that in your role as a community leader you are responsible to the team, not for the team.
One such example of this was a guy (who shall remain nameless) who got very involved in a large open source project. Although not a developer, he became a very public face in the project. He talked very loudly and very enthusiastically about the project and its work, and he actively participated on the mailing lists, discussion channels, and in blog conversations. His contributions were certainly valid: he acted as a champion and enthusiastic voice in the project, encouraging others and getting people pumped up.
As time went on, his name started to be mentioned more than the project. He started performing speaking engagements around the world, and his blog became filled with in-jokes shared with his well-respected, cool friends. He was very much part of the perceived "cool club," if there is such a thing in ultra-hardcore technology circles.
As his fame grew, so did his inbox. He clearly felt that other people, with "less important" tasks, should respond to the email, and the demands on his time were substantial. But he was also riddled with insecurity, and didn't want to loosen his grip on the project. Things stopped getting done. People started getting frustrated, but these frustrations were largely stifled by the community. No one really felt like they could speak out or criticize: if you spoke out, you sounded like the only voice who did not respect and appreciate the contributions of a "rock star." What a pickle.
Of course, this situation could not go on forever. People started to share their frustrations at conferences, in chat channels, and in other arenas. Before long, annoyance and disrespect had become public, and ego had claimed another victim.
The most frustrating part of this tale is that the guy in question was and still is a good guy. At no point did malice or ill will drive any of his decisions or actions. He simply got a little too big for his boots and lost track of how to manage his responsibilities.
I would like to pretend that these cases are rare, but unfortunately they are not. They happen every day, in a range of communities around the world, and you should always have this risk at the forefront of your mind: don't be that guy.
Theory has an important place in community leadership. Heck, I have just spent the last several sections talking about social capital, belonging, economy, belief, and other theoretical disposition. However, you will note that the hardcore theoretical content is confined to this chapter. The emphasis of our work should be in getting on the front lines and trying out ideas instead of burying our heads in a book. Sure, read and learn, but use reading and theory to help you decide where to focus your practical efforts. The most critical lesson here is that you should never replace practical experience with theory.
Part of the reason why I have filled this book with so many examples is that I believe that the most appropriate and effective form of teaching theory is sharing stories and experiences. I would much rather tell you a story about something that I experienced or heard than fill your mind with social science definitions and terms that would be enormously helpful in a game of Buzzword Bingo but of limited use on the ground.
Unfortunately, some folks have something of a love affair with theory. Many of these people write extensive blog entries, give very generic (although well-meaning) presentations, and often seem to think that their primary role is to impart knowledge to others and sound as wildly academic as possible. But there is no secret ingredient in growing community. What makes a great community leader is experience: trying new ideas and concepts and learning from the successes and mistakes.
Of course, theory does have its place: it can help us to see, analyze, and deconstruct the things that are in front of us. I have absolute respect for anyone who teaches others their art, but the teaching really needs to be secondary to getting out and being there with your community and helping to lead and inspire them. Use theory as a means to see the shapes in the chaos, but always ensure you focus your primary efforts on making the chaos less chaotic.
Your "secret sauce" is you. Your personality is the greatest asset that you have. Earlier we talked about how trust is the most critical component in being a great community leader. If you try and become someone who you are not, you will sacrifice that most important of traits. Be yourself. Identify your own traits, celebrate the good, and learn to improve the bad, but always be yourself; it will put you in good stead.
I learned this lesson when we started doing LugRadio. At the time I was a journalist: I wrote for around 12 magazines and also wrote a number of columns for various publications. As part of my work I would write my articles and features in a text editor, and then have plenty of time to edit, choose my words carefully, refine my language, and perfect my tone. I could perform plenty of research, ensure my citations were accurate, and pull from a worldwide library of quotes and stories that would illustrate my points effectively. In a nutshell, being a journalist allowed me to take my voice and ensure it was as refined as possible.
We then started doing LugRadio. From day one, LugRadio was set to be a shoot-from-the-hip, loose, opinionated social exploration of Free Software and Free Culture topics. There was no editing. There was no censorship of opinions. Every word that came out of our mouths was committed to history. It was ballsy, it was controversial, but importantly, it was us. It was the honesty of LugRadio that we were all so proud of.
Although my writing and journalistic work was honest and I never painted an inaccurate picture of my voice or viewpoints, the editing phase of writing added a little more sheen and more opportunity to remove any controversial aspects to my work. With LugRadio, every word that would flow out of my mouth into people's ears was much less formalized: it was me in my birthday suit, no holds barred.
For about two days I really worried about this. Was LugRadio going to affect my career as a journalist? Would people think less of me because of my participation in this hugely opinionated tech audio show? Was I closing off potential opportunities if people heard me for who I really am?
One evening, while at my karate training, sweating and performing second Kata, I decided I didn't care. I had always promised myself that I would be myself in my professional and personal life. I would never cover up my perspectives, my views, my interests, or my ambitions. I was always keen to be professional and respectful of the situations I was in, be they more formalized occasions or low-key social functions, but fundamentally the heart of my approach would be my own. This was the first test of that approach, and since then I have never looked back.
I believe that this commitment to being who you are is critical to being a great community leader. My father-in-law's statement—"Live your life honestly—if you don't, you always have to remember to not be yourself"—actually goes much deeper. Not only should we aspire to lead a good and principled life, but if we live it in a way that is honest to who we really are, we never need to worry about maintaining the illusion. My father-in-law has taken that approach, and so has my own father, and I have learned from them and have incredible respect for their methods.
If you take this approach in your work and manage to do a good job engaging and working with your community, you will never need to worry about trust, transparency, or respect; people will know that the words that come out of your mouth are your own, that your opinions are your own, and that your advice is your own.
This is particularly important when you are a professional community manager. When I started working for Canonical as the Ubuntu Community Manager, I expected people to worry that Canonical may be pulling the strings that made me dance. It has been very important to me that I demonstrate to any community I am involved in that my commitment to them is genuine, and I am as willing to stand up against the commercial sponsor as I am willing to stand up against the community. Trust and responsibility is a two-way street.
In this chapter we have grabbed a piece of paper and sketched out the primary outlines of community. We have discussed some of the high-level mechanisms of how a community works, explored why people build community, and analyzed what kind of attributes exist in great community leaders. The aim of this chapter was to build out an overview that we will delve into in more detail throughout the rest of this book.
The next step in our journey is to build a plan for our community. Although a community is a fairly organic collection of people and processes, we can architect a surprising amount of structure around it. This gives us an opportunity to more easily map out the road ahead.
I don't know about you, but I am ready to roll. Let's get to it....If you enjoyed this excerpt, buy a copy of The Art of Community.
Copyright © 2009 O'Reilly Media, Inc.