Sheldon Chang’s SocialWave Blog

Sheldon Chang, a member of our Collaboration Collaboratory, recently announced a new blog: SocialWeaver: Building Real Communities Online. Sheldon has a startup called SocialWave that builds online communities as a way to strengthen communities within neighborhoods. He’s thought quite a bit about community-building in general and has a lot of interesting things to say, which is why I’m very glad to see him join the blogosphere.    (W1)

In his first post, “A Real Model for the Virtual Community,” Sheldon suggests that people must feel comfortable to build their online identities in order for an online community to be successful. This requirement prevents effective online communities from truly scaling.    (W2)

Sheldon’s blog entry generated some discussion in the collaboratory. John Sechrest discussed latent energy in forums, emphasizing the role that lurkers play in the effectiveness of an online community. He also posed and elaborated a theory of group size: The maximum size of a manageable community is 256 people. (Ross Mayfield described a more scientific theory of group size, based on Robin Dunbar’s research, at his talk last November.)    (W3)

ChiliPLoP 2004 Hot Topic

My proposal for a Hot Topic on patterns of collaboration and High-Performance Communities at ChiliPLoP 2004 has been accepted. We’ll be identifying and discussing these patterns and creating and refining the language, building on previous work by Blue Oxen Associates and others.    (VD)

PLoP (“Pattern Languages of Programming”) is a workshop devoted to reviewing pattern languages. The Hillside Group sponsors several of these workshops throughout the year. Although the original mission focused on patterns for software engineering, the scope has expanded to cover practically everything, technical and not. As far as I’m concerned, these folks are the experts on writing good Pattern Languages, regardless of topic.    (VE)

I’m looking for people who’d like to participate in the workshop. You do not have to be a member of the Hillside Group to attend, although you will have to register for Chili PLoP ($600 before March 1, or $500 for commuter participant). If you’re interested in improving collaboration or learning more about Pattern Languages, I highly encourage you to attend. Chili PLoP 2004 will be held April 13-16 in Carefree, Arizona. Drop me an email if you’re interested in participating or if you have further questions.    (VF)

Tools As Place

When we first launched the Blue Oxen Collaboration Collaboratory, a few people expressed some confusion about the tools. Specifically, one person said, “I’m not sure whether I should post ideas to the mailing list or the Wiki.”    (UG)

Someone I’m working with recently asked a similar question. Our project has a group blog and a Wiki, and this person expressed confusion over where to post a story.    (UH)

In both cases, my answer was, “It doesn’t matter.” Or at least it shouldn’t. My philosophy about collaborative tools is that they shouldn’t lock you in. As long as I can do all of the things I want to do with the information once it’s in a tool, I’m happy. This is not the status quo with today’s collaborative tools, but it’s something we’re working very hard to make happen. You can see some of the fruits of that labor in the tools that we use at Blue Oxen, and the tools that our collaboratory participants have created.    (UI)

That said, certain tools facilitate certain patterns better than others. Blogs seem to facilitate Story Telling better than Wikis. I think the main reason for this is that blogs are designed to be personal spaces, whereas Wiki pages are implicitly deindividualized.    (UJ)

What patterns does email facilitate? Email serviceably facilitates many patterns. That’s a blessing and a curse. It means that email is an all-purpose collaborative tool. But, when groups are using email in conflicting ways, it becomes burdensome. (See Problems With Email for more thoughts on this.)    (UK)

The ideal solution is to use an integrated suite of tools, each of which are there to facilitate specific patterns. If these tools are appropriately interoperable, then there won’t be “wrong” ways to use the tools. But, there will still be optimal ways to use these tools. Discovering what’s optimal requires practice. Hand Holding also helps.    (UL)

Email (and archived mailing lists in particular) plays two important roles in this suite of tools. First, it’s excellent for notification. Second, it’s excellent for Chatter. It can be as real-time as instant messenging, but the end result is more structured.    (UM)

I think there’s a niche for a tool for discourse that is even more structured than email or threaded forums. I don’t think Wikis are the answer. I think group blogs and tightly bound blogs come close, but are not quite right either. I’ve been sketching out the design for a tool I believe will fill that niche, which I’m calling Abelard for now. The design is in its infancy, so I won’t say anything more about it now. However, you’re welcome to view (and contribute to) its Wiki page, which contains a brain dump of the ideas. Comments and questions (in any form — on my Wiki, on your blogs, or via email) are welcome.    (UN)

Huberman on Communities of Practices and Forecasting

Bernardo Huberman, the director of the Information Dynamics Lab at Hewlett-Packard, gave a talk at Stanford on January 8 entitled, “Information Dynamics in the Networked World.” Huberman covered two somewhat disparate topics: Automatically discovering Communities Of Practice by analyzing email Social Networks, and a general forecasting technique based on markets.    (TX)

The first part of his talk was a summary of his recent papers. I’ve alluded to this work here many times, mostly in reference to Josh Tyler and SHOCK. The premise of the work is similar to that posed by David Gilmour in his recent Harvard Business Review article.    (TY)

Huberman described a technique for discovering clusters of social networks within an organization by analyzing email. The key innovation is an algorithm for discovering these clusters in linear time. The algorithm, inspired by circuit analysis, treats edges between nodes as resistors. By solving Kirchoff’s equations (which gives “voltage” values for each node), the algorithm determines to which cluster a node belongs.    (TZ)

The second part of Huberman’s talk was enthralling: Predicting the near-term future using markets. This is not a new idea. A very topical example of a similar effort is the Iowa Electronic Markets for predicting the outcome of presidential elections.    (U0)

The methodology Huberman described (developed by Kay-Yut Chen and, Leslie Fine) aggregates the predictions of a small group of individuals. It works in two stages. The first provides behavioral information about the participants, specifically their risk aversion. Huberman remarked that risk aversion is like a fingerprint; an individual’s level of risk aversion is generally constant. In the second stage, participants make predictions using small amounts of real money. The bets are anonymous. Those predictions are adjusted based on risk aversion levels, then aggregated.    (U1)

Huberman’s group set up a toy experiment to test the methodology. There were several marbles in an urn, and each marble was one of ten different colors. Participants were allowed to observe random draws from the urn, and then were asked to bet on the likelihood that a certain color would be drawn. In other words, they were guessing the breakdown of colors in the urn.    (U2)

Although some individuals did a good job of figuring out the general shape of the distribution curve, none came close to predicting the actual distribution. However, the aggregated prediction was almost perfect.    (U3)

The group then tried the methodology on a real-life scenario: predicting HP’s quarterly revenues. They identified a set of managers who were involved in the official forecast, and asked them to make bets. The official forecast was significantly higher than the actual numbers for that quarter. The aggregated prediction, however, was right on target. Huberman noted that the anonymity of the bets was probably the reason for the discrepancy.    (U4)

The discussion afterwards was lively. Not surprisingly, someone asked about the Policy Analysis Market, the much maligned (and subsequently axed) brainchild of John Poindexter’s Information Awareness Office. Huberman responded that the proposal was flawed, not surprisingly suggesting that this technique would have been the right way to implement the market. It was also poorly framed and, because of the vagaries of politics, will most likely never be considered in any form for the foreseeable future.    (U5)

I see many applications for this technique, and I wonder whether the Institute for the Future and similar organizations have explored it.    (U6)

As an aside, I love how multidisciplinary the work at HP’s Information Discovery Lab is. I’ve been following the lab for about a year now, and am consistently impressed by the quality and scope of the research there.    (U7)

“Low-Focus Thought” in Knowledge Management Systems

David Gelertner wrote an essay called “The Logic of Dreams” (a chapter in Denning and Metcalfe’s Beyond Calculation: The Next Fifty Years of Computing), where he discussed the creative process. Gelertner suggested that there are two kinds of thought: high-focus (analytical, logical) and low-focus (free association). The former we understand well (according to the Gelertner); the latter we barely comprehend.    (TI)

Low-focus thought is the story of weak ties, not just in the context of Social Networks but of ideas in general. It’s a story that is told over and over again. A poet smells a rose, and is reminded of his lover. Friedrich Kekule dreams about a snake biting its tail, wakes up, and solves the structure of benzene. Grace Hopper remembers an old play from her college basketball days and figures out a memory-efficient algorithm for her A-0 compiler.    (TJ)

Gelertner was interested in implementing low-focus thought in Artificial Intelligence software. I’m interested in facilitating low-focus thought via Knowledge Management systems.    (TK)

In the past year, my tools and processes have revealed a number of unexpected connections. For example, last August, I blogged two interesting articles about Marc Smith and Josh Tyler. The following morning, I happened to be rifling through some old articles, and discovered papers written by Smith and Tyler that I had previously archived.    (TL)

Old-fashioned tools and a little bit of karma led to these discoveries. I wanted to eliminate one of the stacks of papers on my floor, which was how I accidentally came across the Smith article. Later that morning, I was searching for an email that a friend had sent me earlier, and it just so happened that the same email contained the reference to Tyler’s paper.    (TM)

These discoveries were largely due to luck, although the fact that I keep archives in the first place and that I review them on occasion also played a role. I don’t want to oversell this point, but I don’t want to undersell it either. Many people don’t archive their email, for example. Many groups don’t archive their mailing lists, a phenomenon that baffles me. More importantly, many people never review their old notes or archives, which is about the same as not keeping them in the first place. All of that knowledge is, for all intents and purposes, lost.    (TN)

Good Knowledge Management tools facilitates the discovery of these weak connections, and make us less reliant on luck. Blogging is great, because it encourages people to link, which encourages bloggers to search through old entries — both of others and their own. This is an example of tools facilitating a pattern, and it’s one reason why blogs are a powerful Knowledge Management tool.    (TO)

I’m excited about the work we’ve done integrating blogs and Wikis using Backlinks and WikiWords, because I believe these tools will further facilitate low-focus thought, which will ultimately lead to bigger and better things.    (TP)