Blue Oxen’s 4th Anniversary

A few weeks ago, about 50 friends and colleagues — including co-founder Chris Dent, visiting from Seattle — joined us at Chris Messina and Tara Hunt‘s gorgeous new office in San Francisco, Citizen Space, to help celebrate Blue Oxen Associates‘ 4th anniversary. Thanks to all who came and to all who sent well-wishes. Thanks especially to Chris and Tara for being such great, generous hosts, and thanks to Tara Anderson for handling all of the logistics. Pictures are up on Flickr, and there’s a funny video of some late night, after-party silliness as well.    (LLX)

Of course, being a Blue Oxen event, there had to be a “group exercise.” This year, Kaliya Hamlin led us through an incredibly moving one. She asked all of us to take a moment and write down a meaningful thing that happened to us this past year. She then asked us to write down something we hope will happen next year. Everyone then posted them on the whiteboard for all to see and share.    (LLY)

A few people signed their notes, but most of them left theirs anonymous. Some notes were easy to identify, but most still leave me wondering who wrote them. Some notes were business-related. Many were deeply personal. Some notes were knee slappers. Others were heart-wrenching. People wrote about relationships, both good and bad. They wrote about losing family members and about surviving cancer. They expressed both despair and hope.    (LLZ)

What the exercise did was raise the group consciousness. I knew almost everyone in the room, most of them well, and over the past year, I interacted regularly with many of them. Yet this simple exercise surfaced many things about the people in my community I didn’t know. It changed the way I looked at everyone in the room, and it reminded all of us of our humanity.    (LM0)

Great group exercises not only surface interesting content, but also elicit surprising behavior. Jonas Luster started the process by drawing connections between cards of people he thought should connect. I don’t know how many people connected through the wall, but I know some did.    (LM1)

Due to the hustle and bustle of being the host of the party, I didn’t have a chance to contribute my own meaningful moments to the wall, so I thought I’d rectify that here. My list is long. Most of my moments consist of late-night conversations with friends and colleagues over dinner, over drinks, and over the phone, covering everything from concrete topical challenges to philosophical ramblings to general silliness. Just thinking about many of these moments brings a smile to my face.    (LM2)

If I had to sum up all of the meaningful moments from the past year into one sentence, it would be this:    (LM3)

I’m grateful that my relationships with many of my work colleagues have evolved into true friendships.    (LM4)

I’m a firm believer in professionalism, which often translates into a wall between myself and my colleagues. It’s my personal manifestation of the Intimacy Gradient, and my wall is probably a bit higher than others. Nevertheless, I do let down my guard over time. It’s never planned. It’s just something that happens organically over time, a natural deepening of trust past a personal threshold. When it happens, it’s always incredibly enriching. It happened a lot this past year.    (LM5)

I am so grateful to have such high-quality and supportive people in my life. It makes me all the more motivated to chase my dreams, to continue to learn and improve, and to contribute as much as I can to this world. I’ve discovered something that’s special and important, and I’m not even close to fully understanding it. I’m going to work my butt off until I do, and I’m going to share what I learn as widely as possible.    (LM6)

WikiMania 2006: Quick Hits and Final Thoughts

I really enjoyed Wikimania, but it felt distinctly different than last year. A big part of it was personal. The conference was held in Cambridge, my home for four years, so the location itself was familiar and uninteresting. I was only there for three days, whereas last year I came early for Hacking Days, where I had a chance to get to know people better at my leisure. I also had much more on my mind, whereas last year, I was fully present the whole time — morning, noon, and night.    (L0E)

Part of it was the conference itself. It wasn’t as international as last year, but it was still quite good — one out of four attendees were from outside of the States. There were also more visitors, folks new to Wikis who came to see what this stuff was all about. Several of these people were fairly high-level, described by Jason Calacanis as “folks who ride on the back of builders.”    (L0F)

The same held true for RecentChangesCamp earlier this year, except the spirit was quite different. There, the visitors were eager to learn and to participate, and the community embraced them. Here, many visitors stayed at arm’s length, choosing to observe from afar rather than immerse themselves in this wonderful community. At Wikimania last year, a different group of us would go out every night, laughing, sharing stories, mixing with other groups. This year, there were more clusters, more silos. I saw people — especially the visitors — sticking with the folks they knew, rather than mixing with others.    (L0G)

That is not our community’s way, and I found it mildly distressful. To some extent, it’s the price of success — especially true in the case of Wikipedia — and the result of the culture that those not acclimated to Wikis bring to the table. To a large extent, process is at fault. I find it fascinating that a community schooled in self-organization and the value of emergence continues to organize top-down gatherings. If it’s not careful, Wikimania may eventually go the way of Linux World, Comdex, and many other conferences that began as a wonderful, generative community gathering and eventually became a meeting place for fast-talking salespeople.    (L0H)

Despite my standing in the Wiki community, I’m an outsider to Wikipedia, and I only have three ways of encouraging a shift in how Wikimania operates. The first and best way is to become active in the community and in the planning of the next conference. In an alternative world, this would have already happened, but the reality is that it’s not likely. The second and worst way is to preach to the folks in the community, which I’ve been doing. I find this distasteful. It’s my personality to effect change, not to talk about it.    (L0I)

The third way is to create a space where people can learn for themselves and to catalyze that learning as much as possible. This, in a nutshell, is the purpose of Blue Oxen Associates. I’ve had some success in this area. The FLOSS Usability Sprints exposed some folks to effective collaborative processes, including one of the original Bar Camp organizers. I was then able to point to Bar Camp as a model for the RecentChangesCamp organizers, who wanted to bring Open Space to the Wiki community. Both the usability sprints and Bar Camp helped spawn DCamp, the Bar Camp for the usability community. Our “Tools for Catalyzing Collaboration” workshops have inspired a number of people to pursue similar event models.    (L0J)

In addition to helping the tech community learn about face-to-face collaborative processes, I’ve also helped other communities — from Planetwork to the World Economic Forum — learn how online collaborative spaces can complement physical ones.    (L0K)

All of this is just the start. I have bigger and better things in the works. More importantly, the meme is starting to spread. I’ve helped initiate some of this, but there are many other sparks, and others are starting to fan the flames. We will learn how to collaborate more effectively. But it will take time.    (L0L)

I’m sounding a bit ominous, and it’s an exaggeration of how I actually feel. As I said before, all in all, Wikimania was wonderful. When you bring great people together and get out of the way, great things happen. Even if there are minor obstacles, great people will find a way around them. This has held true not just for the participants at Wikimania, but for the organizers. I am amazed at the efforts, commitment, and passion of Samuel Klein, Phoebe Ayers, Delphine Menard, and the many, many others who worked ridiculously hard to make this conference happen. The whole community deserves tremendous praise. I hope it continues to do what it does well, while unabashedly exploring ways to improve.    (L0M)

One goal that the Wikimania organizers should have for next year is improving conference Wiki usage among the participants. Effective self-documentation via Wiki is a staple of Blue Oxen‘s processes, and we’ve managed to influence many others about it, including Bar Camp and the Aspiration events. But the best Wiki usage at an event I’ve ever seen was at RecentChangesCamp. The community was already steeped in Wiki culture, and the process encouraged self-documentation. The fact that neither Wikimania nor WikiSym has seen effective conference-wide usage of Wikis is an indicator that something is blocking the community’s natural instincts. It’s also a lost opportunity, as those who attend the conference seeking to learn about Wikis miss out on the chance to experience them first-hand.    (L0N)

Quick Hits    (L0O)

  • I was amazed at the number of speakers who exclaimed how honored they were to be there. Some of them were merely experiencing the euphoria of speaking at a gathering of their peers for the first time. Others were hardened veterans of the speaking circuit, including Yochai Benkler and David Weinberger. Yochai even interrupted his traditional two months beach getaway to speak at the conference.    (L0P)
  • Speaking of David Weinberger, I saw him talk for the first time, and now I know what the fuss is about. He’s a wonderful speaker — self-deprecating, sharp wit, great sense of humor, and very thoughtful. He did a Monty Python-like parody of Lawrence Lessig‘s presentation-style that had the entire audience rolling with laughter, and he managed to slip in references to Hegel and Heidegger without sounding pretentious. But I had two beefs with his talk. (Boy, I’m just Mr. Negativity today.) First, he disputed the notion that knowledge is just in people’s head, citing all the knowledge associated with the artifacts that surround us. I understand the point he was trying to make, but I didn’t like how he made it. Artifacts are not knowledge. I generally find myself taking the exact opposite stance as Weinberger — emphasizing that knowledge is in our heads, because it stresses the human element we so often forget when we think about our relationship to knowledge. Second, he made a hypothesis about Wikipedia editing behavior that practically everybody in the room knew was wrong. He admitted that he was speculating, and gracefully acknowledged his error when informed of it, but he never should have made that mistake in the first place. There were many people he could have simply asked before making such a claim.    (L0Q)
  • The best talk from someone I had never heard of was by Seth Anthony, who spoke about Wikipedia editing patterns. See Ross Mayfield‘s notes for a summary.    (L0R)
  • Fernanda Viegas and Martin Wattenberg, the IBM researchers who created History Flow, gave an outstanding talk where they demonstrated some new visualizations of Wiki usage. Some of those visualizations are available in my Flickr collection. I particularly found their visualizations of user behavior interesting, because of past suggestions that such visualizations could be a powerful way to help casual readers determine reputations. The biggest obstacle (besides the computing power required to generate these visualizations)? Privacy. Even though these visualizations were based on public data, that does not automatically make it okay to make those visualizations available. Witness AOL’s recent fiasco (and read Tom Maddox‘s commentary).    (L0S)
  • I caught up with Denny Vrandecic towards the end of the conference, and I’m glad I did. He gave me an in-depth demo of Semantic MediaWiki, which he had first proposed (but had not coded) at last year’s Wikimania. The notion of encoding link types in Wikis is not new, but up until I saw the Semantic Mediawiki, the best implementation I had seen was Evan Prodromou‘s WikiTravel. I think the Semantic Mediawiki is a better approach. It’s less expressive than WikiTravel, but more likely to be widely adopted. I plan on experimenting with it and incorporating some of its capabilities into my own Wikis.    (L0T)

Yochai Benkler and Rishab Aiyer Ghosh at WikiMania 2006

On Saturday morning, I had the pleasure of attending talks given by two very important contributors to my field. About a year and a half ago, shortly after I first met Katrin Verclas, Katrin started telling me, “You’ve got to read Yochai Benkler.” I’m pretty sure that she ended 90 percent of our subsequent conversations with, “You really should read Benkler.” When Benkler came out with his book, Wealth of Networks earlier this year, everybody else in the world seemed to echoed Katrin’s advice.    (KYH)

I knew that Benkler was speaking this weekend, so I finally downloaded his book and started reading it on the plane. Unfortunately, I only got through the first chapter. You can imagine how lame I felt when I found myself having dinner with him on Friday night. Fortunately, Benkler himself gave a thirty minute synopsis of his book on Saturday morning.    (KYI)

(As an aside, Benkler unintentionally scored some major geek points, when his laptop revealed that he runs Linux with KDE. There are a lot of outsiders commentating on Open Source these days, but most of them do not actually run Linux themselves.)    (KYJ)

Benkler’s thesis is that technology has enabled unprecedented forms of large-scale cooperative production, what he calls “commons-based peer production.” Think Wikipedia, think Open Source, think Mash Ups, etc. According to Benkler, these non-market activities are no longer on the periphery, but form the very core of economic life for the most advanced societies.    (KYK)

Technology is largely responsible for our ability to behave this way, but only partially responsible for the authority to behave this way. The latter is a cultural phenomenon that has been catalyzed by the technology, but is not entirely causal.    (KYL)

The question is, is this behavior an outlier, or is it economically sustainable? Benkler didn’t talk a lot about this — this is why I need to read the book — but he did cite numbers such as IBM’s revenues from Linux-related services, which far outpaces its revenues from IP licensing. (This alone is not evidence; smaller Open Source companies like MySQL are making significant revenue from dual licensing, a lesser known fact of life for many Open Source companies.)    (KYM)

Benkler touched a bit on the importance of humanization in commons-based peer production, which he said is the focus of his current research. He also cited the reemergence of a new folk culture in society today, something that Lawrence Lessig also talks about.    (KYN)

There was a minor hullabaloo between Jason Calacanis and Benkler during Q&A. (See Andy Carvin‘s description, plus some background and commentary. It was entertaining, but low on any real controversy. Benkler acknowledged that the interface between market and nonmarket interaction is not well understood right now. There are good examples of how paying people kills the community dynamics, but the patterns are not necessarily discernible yet. However, Rishab Aiyer Ghosh, who spoke after Benkler — made it crystal clear that those citing numbers about how a small number of people are responsible for a large percentage of work are missing the point. If you pay for 75 percent of the work, you end up with a three legged chair, which is worthless.    (KYO)

Ghosh has done some of the best quantitative analysis on Open Source communities, and he’s been doing it for a while. The Blue Oxen report on open source communities was heavily based on work that Rishab had done.    (KYP)

Ghosh kicked off his talk by talking about James Watt‘s exploitation of the patent system, and argued that Watt’s significantly slowed innovation with the steam engine and thus was partially responsible for delaying the Industrial Revolution.    (KYQ)

(I didn’t find Ghosh’s argument particularly compelling or relevant, but it was a good story. Patents give folks monopolies, and monopolies are bad for markets. We know that already. But patents are also supposed to incentivize innovation. Ghosh was insinuating through his story that patents were not a strong motivator for innovation in this particular case, but I have trouble believing that. Christoph Friedrich Von Braun wrote an excellent, but dense book, The Innovation War (1997), where he explained how difficult it was to correlate patents to innovation, either for or against. And von Braun barely touched on software, which adds even more complexity to the question.)    (KYR)

Ghosh then went on to talk about FLOSS developer motivation and described his value-flow and cooking pot analogy for how markets can sustain this type of behavior. He also pointed out that the collaboration is not new, but the scale is.    (KYS)

Ghosh continues to do good research, much of which is hosted at FLOSS World.    (KYT)

BlogHer 2006: Thoughts from an Observer of Observers

I was bummed that I couldn’t make the BlogHer conference this year. Last year, I had project commitments up the wazoo, but I made some time to meet up with Nancy White at the conference site, whom I had never met face-to-face. We sat at a table outside of the Santa Clara Convention Center and embarked on a fascinating conversation. As we talked, more and more folks — all women — saw us, said hello, and joined us, further enriching the conversation. A few hours later, I had to rip myself away from that table to make it to my next meeting, and I swore that I would attend the following year.    (KVL)

Well, I didn’t. I was in Staunton, Virginia for the 1Society team retreat. I was even more disappointed after having met Elisa Camahort, Lisa Stone, and Jory Des Jardins at the June Collaboration SIG meeting.    (KVM)

Fortunately, as you might expect, folks blogged about the conference. Here are some of my thoughts on their thoughts.    (KVN)

Welcome Neighbors    (KVO)

Nancy White shared this gem from Caterina Fake:    (KVP)

A lot of online community building is like you are the host of the party. If you show up and don’t know anybody and no one takes your coat and shows you around, you are going to leave. The feminine touch there really matters. That is how we greeted people at flickr. Creating a culture in an online community is incredibly important. What’s ok in a fantasy football league is different than what we wanted to cultivate on flickr. Then those become the practices of the flickr. Everyone starts greeting people., Get the ball rolling. You want people engaged, feel strongly enough so they are the community police.    (KVQ)

It’s another instance of the Welcome Neighbors pattern!    (KVR)

Christine Herron    (KVS)

Christine deserves her own category, because I’ve been relying more and more on her blog for her excellent summaries of other gatherings. We haven’t actually met, although she blogged one of my talks way back when.    (KVT)

Christine wrote about community design and evolution and the importance of constant engagement:    (KVU)

Even the most intelligent design will miss the mark, if community members are not involved in setting purpose and norms. This implies that a healthy community will bake in “continuous listening,” and its purpose and norms will evolve over time. It’s noteworthy that many communities develop spontaneously, rather than according to plan.    (KVV)

Listening was an ongoing theme in a lot of the BlogHer summaries.    (KVW)

On communities and continuous learning:    (KVX)

Susannah Gardner, the author of Buzz Marketing with Blogs, has become the center of a blog newbie community. As a case study, this serves as a model for most of the folks in the room. Gardner quirkily revealed that “My community is inherently flawed.” Most people coming to her community come to learn, but once they’ve learned what they need, they leave. This also means that the community is constantly renewing itself and forming new relationships to each other — that over the long term, no longer require Gardner’s bridge for sustained connection.    (KVY)

Finally, Christine blogged about a session on identity that actually had something to do with identity!    (KVZ)

A powerful and relevant final thought on this issue comes from Amartya Sen, a Nobel-nominated economist and the co-author of Identity and Violence — we all have multiple identities, but when we marry ourself to just one, violence happens. When this nugget was shared, the bubbling room fell into a thoughtful, silent pause. Would the world be a better place if more and more of its peoples participated in sharing identity?    (KW0)

Conversations and Conferences    (KW1)

Tom Maddox also wrote about the prevalence of listening at the conference:    (KW2)

Because the usual male-female ratio was inverted at Blogher, male display was almost entirely absent, replaced by friendly, open conversation. The prevailing atmosphere — the oxygen — was friendliness, openness, inclusiveness.    (KW3)

It’s not that Blogher was perfectly organized and run — if you want to see a list of complaints, just look at the Technorati-tagged blog postings. But in the larger picture, really, who measures the conference’s success by whether the wifi was overloaded or that there were too many commercial pitches from the main stage? What the organizers got right was creating a space where people could talk to one another easily and freely and openly, without being defensive or aggressive.    (KW4)

I’m of two minds of this reaction. BlogHer is a traditional, hierarchical gathering, but there’s obviously a strong culture of participation and interaction. Culture goes a long way. If you have good culture and good people, it’s hard to throw a poor gathering (although it’s certainly been done).    (KW5)

However, just because you manage to throw good, even great gatherings, doesn’t mean that you can’t do better. As I wrote last June:    (KW6)

There’s also a lot they can learn about even more powerful models of collaboration and transparency. For example, I liked their approach to the BlogHer conference, but I couldn’t help thinking about how they were going through the exact same process that HarrisonOwen went through 20 years ago before he invented OpenSpace. It’s not an indictment of them, but a constant reminder that those of us who are passionate about collaboration are still not close to knowing what everyone else knows, and it’s further reinforcement that BlueOxenAssociates‘ mission is an important one.  T    (KW7)

My not-so-secret plot is to suck Elisa, Lisa, and Jory into the growing Blue Oxen community (probably starting with the next “Tools for Catalyzing Collaboration” workshop), so that we can all learn from each other and leapfrog the great work that many of us are already doing. Be warned, ladies!    (KW8)

The Story of Glormf: Lessons on Language and Naming

Jack Park recently asked about Link As You Think on the Blue Oxen Collaboration Collaboratory. I’ve written several blog posts on the matter, but there’s not much else out there. This was a great excuse for me to tell a few vignettes about Shared Language and the importance of names.    (KMO)

Glormf    (KMP)

This is Glormf, courtesy of the uber-talented cartoonist, Brian Narelle.    (KMQ)

(KMR)

Fen Labalme coined the term (originally spelled “glormph”) at an Identity Commons retreat in July 2003. We were strategizing about next steps, and we found that we were all struggling to describe what it was that we were all working on. Although we all had different views of the proverbial elephant, we were also convinced that we were talking about the same thing. In an inspired moment of clarity, Fen exclaimed, “It’s Glormf!” Much to our delight, Brian was listening to the conversation and drew Glormf for all of us to see.    (KMS)

Glormf’s birth lifted a huge burden off our shoulders. Even though Glormf was mucky, it was also real. We knew this, because it had a name and even a picture, and we could point to it and talk about it with ease. The name itself had no biases towards any particular view, which enabled all of us to use it comfortably. Each of us still had a hard time describing exactly what Glormf was, but if anyone challenged Glormf’s existence, any one of us could point to Glormf and say, “There it is.”    (KMT)

We had created Shared Language, although we hadn’t rigorously defined or agreed on what the term meant. And that was okay, because the mere existence of Shared Language allowed us to move the conversation forward.    (KMU)

Ingy’s Rule and Community Marks (KMV)

Ingy dot Net‘s first rule of starting a successful Open Source project is to come up with a cool name. I like to say that a startup isn’t real until it has a T-shirt.    (KMW)

Heather Newbold once told a wonderful story about how Matt Gonzalez’s mayoral campaign buttons galvanized the progressive community in San Francisco and almost won him the election. As people started wearing the green campaign buttons, she described the startling revelation that progressives in San Francisco had: There are others out there like me. A lot of them. I was amazed to hear her speak of the impact of this recognition, coming from a city that has traditionally been a hotbed of activism.    (KMX)

There’s a pattern in all of these rules and stories. I struggled to come up with a name for this pattern, and the best I could do for a long time was Stone Soup (courtesy of the participants in my 2004 Chili PLoP workshop). I loved the story associated with this name, the parable of how transformational self-awareness can be. But, it wasn’t quite concrete enough for my taste.    (KMY)

I think Chris Messina‘s term, “Community Mark“, is much better. Chris has actually fleshed out the legal implications of a Community Mark, which I recommend that folks read. Whether or not you agree with him on the details, the essence of Community Marks is indisputable: Effective communities have Community Marks. Community Marks make communities real, just as the term “Glormf” made a concept real. That’s the power of Shared Language.    (KMZ)

Pattern Languages and Wikis    (KN0)

Pattern Languages are all about Shared Language. Much of Christopher Alexander‘s classic, The Timeless Way of Building, is about the importance of names. In his book, Alexander devotes an entire chapter to describing this objective quality that all great buildings have. As you can imagine, his description is not entirely concrete, but he does manage to give it a name: “Quality Without A Name.” Call it a copout if you’d like, but if you use the term (or its acronym, “QWAN”) with anyone in the Pattern Language community, they will know what you’re talking about. Shared Language.    (KN1)

Ward Cunningham was one of the pioneers who brought Alexander’s work to the software engineering community. He created Wikis as a way for people to author and share patterns. Not surprisingly, an important principle underlying Wikis is the importance of names. Regardless of what you think about WikiWords, they have important affordances in this regard. They encourage you to think of word pairs to describe things, which encourages more precise names. They discourage long phrases, which also encourages precision as well as memorability. The more memorable a term, the more likely people will use it.    (KN2)

Ward often tells a story in his Wiki talks about using Class-Responsibility-Collaboration Cards to do software design. One of the things he noticed was that people would put blank cards somewhere on the table and talk about them as if there was something written there. The card and its placement made the concept real, and so the team could effectively discuss it, even though it didn’t have a name or description. (Ward has since formalized leaving CRC cards blank as long as possible as a best practice.) This observation helped him recognize the need and importance of Link As You Think, even if the concept (or Wiki page) did not already exist.    (KNG)

Open Source: Propagating Names    (KN3)

One of Blue Oxen‘s advisors, Christine Peterson, coined the term, “Open Source.” In February 1998, after Netscape had announced its plans to open source its browser, a few folks — Chris, Eric Raymond, Michael Tiemann, Ka-Ping Yee, and others — gathered at the Foresight Institute to strategize. At the meeting, Todd Anderson complained that the term, “Free Software,” was an impediment to wide-scale adoption. After the meeting, Christine called up Todd and suggested the term, “Open Source.” They both loved it. But, they didn’t know how to sell it.    (KN4)

So, they didn’t. At the followup meeting a few days later, Todd casually used the term without explanation. And others in the room naturally picked up on the term, to the point where they were all using it. At that point, they realized they had a good name, and they started evangelizing it to the rest of the community.    (KN5)

Names change the way we think about concepts, and so propagating names widely can shift the way people think about things. This is what happened with “Open Source.” This is what George Lakoff writes about in Moral Politics.    (KN6)

The mark of a good name is that people naturally start using it. A name can come from the top down, but it can’t generally be forced onto people.    (KN7)