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)

A Series of Open Conversations

What the heck is Blue Oxen Associates supposed to be about. Why the heck am I in this business? Forget about my Elevator Pitch for a moment. Forget about collaboration and collaboratories, Pattern Languages and Purple Numbers. What do I want, and why do I care?    (K1V)

I haven’t been able to answer these questions to everybody’s satisfaction, but I’ve found folks of all types who get either it or me pretty quickly and who share many of my hopes, dreams, and values. Being around these people has kept me going both personally and professionally, and further catalyzing this community is a big part of what Blue Oxen Associates is about. I often think about the negativity that one of my mentors, Doug Engelbart, faced for so long early in his career, and I’m grateful at how different my world has been.    (K1W)

Katrin Verclas and Seb Paquet are two of my favorite conversational partners. I’ve had the pleasure of working with Katrin (and Allen Gunn, another favorite) on the FLOSS Usability Sprints. I haven’t had the opportunity to work with Seb yet, but I’m quite certain it will happen eventually.    (K1X)

Katrin is in Massachusetts, and Seb is in Montreal. My conversations with both are always incredibly rich, and I’m constantly wishing that we could talk more often and that we could capture some of those conversations. Of course, thanks to technology (and a bit of process), we can.    (K1Y)

In the spirit of old school letter writing, I’ve proposed to both of them a series of conversations with a twist. Instead of emailing back and forth, we’ll post our letters on our blogs so that others can participate and hopefully join in.    (K1Z)

I think the open conversations will be revealing and hopefully entertaining. Katrin has already kicked things off with a nice list of things she wants out of her career and life. I’ll respond in my next blog post. And when Seb decides to return to the blogosphere (*nudge, nudge*), we’ll have an open conversation as well.    (K20)

I’d love to have conversations with many others, beyond what already occurs on our respective blogs. If you’d like to join in on this little experiment, write me a letter and post it on your blog. Don’t forget to link back here so I can find it.    (K21)

Looking forward to the conversations!    (K22)

Drive On

Most folks know Richard Gabriel for his Worse Is Better essays, his work with Pattern Languages, and his involvement with the Hillside Group, among many other things. I know him as an invaluable and exceptionally generous sounding board for my crazy ideas over the past three years.    (JOQ)

Now there’s an opportunity to know Richard for one of his greatest passions: poetry. Drive On, a book of lyrical poetry, is now available.    (JOR)

Patterns at WikiMania 2005

When I first met Christine Peterson (now a Blue Oxen Associates advisor), she told me the story about coining “Open Source.” The sign of a good name, she explained, is when people naturally start using it on their own. At a meeting of developers and evangelists in early 1998, rather than argue strongly in favor of the term, she introduced it subtly. Although the response wasn’t enthusiastic at the first, everyone in the room found themselves using the term, and by the end of the meeting, they all agreed to evangelize it.    (JMS)

Similarly, my strategy for introducing and identifying patterns of high-performance collaboration is to subversively introduce patterns into various communities and then to listen. If people naturally use a pattern in conversation, the name is probably good and the pattern itself is probably real and repeating. As people become familiar with the concept, they are more likely to identify and name other patterns. Over time, the language shifts your thinking, giving you a cognitive framework for thinking about, talking about, and improving collaboration and collaborative tools. Moreover, the process itself is iterative and collaborative, which is both the right way to develop Pattern Languages and also another application of collaborative patterns.    (JMT)

I’ve been giving some variation of a stock talk on patterns for over a year now, including last week at Wikimania 2005. It usually consists of a quick introduction, a few examples, and an interactive portion where I tease out patterns from the audience. The audience banter is always the best part. It’s always different, and it’s provided me with entertaining anecdotes, new patterns, and better pattern names.    (JMU)

Last week, I mentioned four patterns that Wikis facilitate: Permission To Participate, Shared Display, Visible Pulse, and Working Draft. Tim Starling followed my talk with an overview of Mediawiki development, and when he mentioned their IRC channel, he said, “This is our community’s Visible Pulse.” I love it when the process works!    (JMV)

The discussion teased out other patterns, especially Celebration and Initiation. (Linda Rising and Mary Lynn Manns mentions both of these in their book. They have a better name for the latter, but I don’t remember it off-hand.) One person told a great story about both. His team met for the first time in Australia, and before embarking on their project, they brewed beer that they planned on drinking after they finished their project.    (JMW)

Other patterns observed and not observed at the conference and within the community:    (JMX)

  • The Celebration at the end of the conference was great, but the Initiation wasn’t particularly remarkable. This isn’t unusual for conferences, where Initiation tends to be in the form of a keynote.    (JMY)
  • One pattern closely related to Initiation is Introductions. At conferences, this generally comes in the form of name badges, which we had at Wikimania. I think there’s a huge opportunity for further facilitating this pattern at conferences, which is something Blue Oxen Associates is working on. Hacking Days also would have been significantly more effective if we simply went around the room each day and quickly introduced ourselves. It’s one of those patterns that sound obvious when you hear about it, but is often forgotten when actually designing an event.    (JMZ)
  • Conferences usually do Water Cooler well, and Wikimania was no exception. We had long lunches, a party on the last night, an IRC channel, and some organized activities in Frankfurt am Main for stragglers following the conference. In particular, the organizers did two things really well. The Haus der Jugend was an excellent choice of venue, because it was an intimate space where social interaction was practically unavoidable. Most of the participants stayed at the hostel, which meant that there was always an interesting conversation to be had by simply going downstairs and hanging out in one of the common rooms. Plus, most of us who stayed there also had roommates, which is not typical for the conferences I attend. The restaurants and bars — touristy though they were — were in very close proximity, which made it easy to grab a beer and talk. (Food is a closely related pattern.) Finally, Hacking Days served as an unintentional Water Cooler, at least for those of us who were not Mediawiki developers. Coming early is something the organizers should encourage more widely next time.    (JN0)
  • I’m very biased towards highly interactive event design, and it seemed like it would have been especially appropriate for a Wiki conference. That said, the panel format worked better than at most conferences, and I think the Wiki culture of Permission To Participate had a lot to do with that. The audience interacted easily with the presenters at all of the talks I attended, and most of the speakers did a nice job of incorporating feedback into their presentations. One thing they did not do well was actively promote and integrate the conference Wiki as a place to take notes and have additional discussions. Again, this seemed surprising for a Wiki conference — yet another indication that making patterns explicit is a good thing.    (JN1)
  • Another favorite — also found in Linda and Mary Lynn’s book — is Spotlight On Others. This runs rampant throughout the Wikipedia community, which is wonderful. Tim cited me when mentioning Visible Pulse, and by the next morning, Sunir Shah had incorporated Permission To Participate into his talk on conflict resolution. I found this time and again in people’s talks. One reason it occurred so often during the conference is that the organizers used a Wiki to develop the program transparently. People watched other people’s talks develop and incorporated their content even before the conference began.    (JN2)
  • A critical pattern, especially for inter-organizational collaboration, is Neutral Space. Wikipedia would not have been successful if it did not have an open content license (which facilitates Neutral Space) and, to some extent, if it were a for-profit company. At the board panel on the last day, several people brought up the question of online ads. On the one hand, ads have the potential of bringing in a tremendous amount of revenue, which could be put to good use for the community. On the other hand, it breaks the Neutral Space pattern that has served Wikipedia so well. The community was more or less split on this issue. My vote: No ads!    (JN3)

One last pattern that I both observed and missed was Users Talk To Developers, a pattern I first described in, “An Introduction to Open Source Communities.” Previously, I criticized the Mediawiki developers for not practicing it enough. With the whole conference finally behind me, I want to both soften and and strengthen my statement.    (JN4)

Many of the Mediawiki developers came to the project as Wikipedia contributors. Brion Vibber, one of the leaders of the project, probably never would have joined had it not been for the Esperanto Wikipedia, of all things. After having more time to interact and observe the developers, I think that on average, community interaction is more prevalent among the Mediawiki developers than it is with many other projects.    (JN5)

That said, it’s still not nearly what it can and should be. During the sessions on politics and developing countries, several panelists complained that the tools had a way to go to meet their needs, and yet, none of the developers were attending their sessions. Hossein Derakhshan noted that techies are generally not interested in issues outside of their sphere.    (JN6)

Not all the blame falls on developers, however. As great as it would have been to see more developers abandoning the technical sessions in favor of the more social ones, it would have been fantastic to see more Wikipedia contributors attend some of the technical sesssions. Both communities need to learn and respect each other’s language if they truly want to engage collaboratively. Bridges are critical to make this work. Note that this applies not only to Mediawiki, but to all Open Source projects.    (JN7)

J. Fairchild and Community Space

Katrin Verclas, co-director of Aspiration and co-organizer of the FLOSS Usability Sprint, wrote a fantastic piece entitled, “Great Good Spaces for Community, Activism, and Better Software.” It’s no accident that we connected when we first met at the Advocacy Developer’s Convergence last June. Even though our missions are different, there’s great overlap in our thinking and philosophy. That holds true with the other organizations Blue Oxen Associates has partnered with as well.    (ID7)

A critical element in building strong community and in facilitating effective collaboration is having the right space. As Katrin points out, this holds true for both physical and metaphysical (or online) spaces. I had three intellectual inspirations in starting Blue Oxen: Doug Engelbart, Christopher Alexander, and George Lakoff. Christopher Alexander is an architect who wrote about Pattern Languages in the 1970s, which was all about designing great spaces, spaces that were alive, that had this Quality Without A Name. Blue Oxen is trying to understand and discover patterns of effective collaboration, which encompasses issues of space.    (ID8)

When Katrin wrote her piece, we were looking for a space to hold our sprint, and we weren’t finding a place that satisfied us. Luckily, I had a wildcard in my back pocket. Jeff Shults was the manager of the knOwhere Store in the late 1990s, which was MGTaylor‘s showcase for its collaborative environment and process. When the store closed, Jeff purchased all the furniture and bided his time until he could open his own space. That time came late last year, when he struck an agreement with SFIA to manage their new space on 10th and Mission in San Francisco.    (ID9)

I first met Jeff at Planetwork in 2003, but the first time we worked closely together was at the 7-Domains Workshop last July. Jeff is literally an environmental master. He has this sixth sense for configuring spaces to maximize collaboration. He has both thought deeply about the subject and has practiced it for some time. He’s also a fantastic listener, which is an attribute he shares with all the great facilitators I know.    (IDA)

I had seen the space last fall, and to say that it was in rough condition is an understatement. But in early January, when we still hadn’t found a good space, I decided to call Jeff anyway. The transformation the space had made in the course of two months was amazing. Although Jeff hasn’t officially opened his facility, he not only let us use his space, but he agreed to be one of our sponsors.    (IDB)

I can’t tell you how many people walked into our event last week, looked around, and said, “Wow, what a great space!” I’d hear this, laugh, and respond, “You don’t know the half of it.” All of us have an intuition that allows us to recognize a great space when we see one, an intuition that sadly doesn’t wake up often enough. But you have to discover the thinking and hard work that goes into creating such a space before you can truly appreciate it.    (IDC)

Jeff’s company and space is called J. Fairchild. If you need a great meeting space in San Francisco, talk to Jeff and let him know I sent you his way.    (IDD)