A Happy Information Hygiene Moment (and a Great Explanation of the Backfire Effect)

Yesterday, my sister shared this Oatmeal comic that wonderfully explains the backfire effect, the phenomenon where seeing evidence that contradicts our beliefs hardens those beliefs rather than changes our minds.

I love The Oatmeal for its engaging and often humorous visual explanations of important concepts. (XKCD and Nicky Case are also brilliant at this.) My sister knows this, and asked me if I had seen it before. Even though I loved this one, it didn’t ring a bell.

So I did what I try to do in situations like this. Rather than just file it away in my Evernote (where I have thousands of clippings that I almost never see again), I went to record it on the human perception page under “Confirmation Bias” on the Faster Than 20 wiki. To my delight, I found that I not only had seen it before, but I had already captured it on my wiki!

It’s a practice I call good information hygiene (a term coined by my colleague, Chris Dent). When we do it well, we’re not just filing things away where we can find them, we are continually synthesizing what we’re consuming. The act of integrating it into a larger knowledge repository is not only good information hygiene, but is also a critical part of sensemaking. Doing it once is great, but doing it multiple times (as Case and my colleague, Catherine Madden, have also explained beautifully) makes it more likely to stick.

Here’s another, simpler example that doesn’t involve a wiki and may feel more accessible to folks tool-wise. In my late 20s, I met Tony Christopher through my mentor, Doug Engelbart. We had such a great conversation, when I got home, I wanted to make sure to enter his contact information immediately into my contact database. When I opened it, to my surprise, he was already in there! I had very briefly met him at an event a few years earlier, and I had recorded a note saying how much I had enjoyed that short interaction.

I love when moments like this happen, because it shows that my tools and processes are making me smarter, and it motivates me to stay disciplined. I wish that tool developers today focused more on supporting these kinds of behaviors rather than encouraging more fleeting engagement with information.

Networked Tools and the Email Bottleneck

My friend and colleague, Tony Christopher, recently wrote a wonderful paper entitled, “Tools for Teams: Beyond the Email Bottleneck.” There are two things I really like about the paper, and there’s one thing I want to nitpick here.    (MDS)

First, the good stuff. Tony introduces a new term, “networked tools,” to connote tools that are on the network. These include shared calendars, file repositories, and so forth. Why is this useful? For starters, most people have no idea what a collaborative tool is, and that includes many folks who are ostensibly in the business.    (MDT)

What is a collaborative tool? It’s a tool that facilitates collaboration. Certainly, a shared authoring tool like a Wiki has affordances that facilitate collaboration. But a plain old text editor is just as legitimately a collaboration tool, because it can also be used to facilitate collaboration (for example, when used on a Shared Display).    (MDU)

When most people talk about collaborative tools, what they’re really talking about are networked tools, which is why I think Tony’s term is much more apt.    (MDV)

The main point of Tony’s paper is not to invent a new term, but to shift the focus away from the tool and onto an organization’s needs and processes. His specific advice is a bit oriented towards larger organizations, but the essence of his argument is true for everyone.    (MDW)

My only nitpick with Tony’s paper is that he chooses to pick on email, a favorite practice of another person I like to nitpick on this point, Ross Mayfield. (In fairness to Ross, he’s clearly being a troublemaker — or a good CEO — when he declares email dead, as he’s also written clearly about using email effectively in the context of collaboration. And he’s spot on about occupational spam.) Tony writes:    (MDX)

Email undermines the centralized accumulation of knowledge that could benefit the organization both during the project and long after it’s over. Organizations that have not evolved from email to a broader set of networked tools face lost oportunities and hidden costs.    (MDY)

It’s a bit of a red herring to blame email, because email is a Swiss Army knife. You can do a bunch of things with it, but you’ve got to figure out how to take advantage of this flexibility. This is even more difficult with groups, because if some folks are using their email differently from others, its effectiveness as a collaboration tool drops.    (MDZ)

I suspect that most organizations would see orders of magnitude improvements in how they collaborated if they went through the steps that Tony suggested, then reexamined how they could use email more effectively.    (ME0)

A very simple example of what I mean came out of a conversation with Tara Hunt earlier this week. I was talking to Tara and Chris Messina about their work to move the Freecycle community to something more appropriate to their needs. I observed that while Freecycle could definitely use a better support tool, it’s a great example of how you can leverage a simple mailing list to do amazing collaborative work.    (ME1)

Tara noted that there are 3.5 million people currently on Freecycle, which is amazing. She also observed, “Imagine how many people they would have if the tool were better.” A fair point indeed. When you’ve thought carefully about your patterns and you’ve reached the limit of your tools, the next step for coevolution is to improve your tools. Freecycle — currently serving 3.5 million people effectively — is definitely at that point. Most organizations are not.    (ME2)

Dumbells and Collective Intelligence

I’ve been a member of 24 Hour Fitness ever since I moved out here, mostly frequenting their Mountain View location. Now that I’m in San Francisco, I go to the location on Ocean Avenue (when I’m not sitting on my lazy butt, that is). Here’s the amazing thing about that location. It’s about three times as big as the Mountain View location, with about three times the number of dumbells. And yet, it is impossible to find the weights you’re looking for there. They’re always scattered all over the place, and no one ever racks them where they’re supposed to go.    (K9J)

Tony Christopher once told me a story about this timeshare cabin he and his family rent. Someone (the owners I think) had the bright idea of actually labelling the drawers so that all of the inhabitants know exactly where to find the silverware and where to return it when they’re done. Brilliant, right? And it works for Tony and his timesharing cohorts.    (K9K)

All gyms already have this for their free weights. And most gyms I’ve been to are decent at keeping their free weights in order, although this is partially because they have some staffer reorganize them on a regular basis. Well, this apparently doesn’t happen enough in San Francisco, and for whatever reason, those who frequent that gym aren’t smart enough to put things back where they belong. And all of us suffer as a result.    (K9L)

This is as good of a metric for measuring a group’s Collective Intelligence as any: How well does a group keep its tools or its artifacts in order? There are two approaches to rating high on this metric: imposing discipline on a group from above, or hoping that your group is smart enough to figure it out on its own. When the latter happens, you’ve got self-organization, and it’s much more compelling than the top-down alternative. This, of course, is what makes Wikis so interesting.    (K9M)

The Unjoy of Panels

I’m a veteran panel moderator. I’ve been doing it since high school, and I think I’m pretty good at it. But I’m thinking about retiring from the business.    (JKL)

Last week, I moderated the SofTECH / SDForum July meeting on “Architecting Community and Collaboration Solutions.” Tony Christopher had suggested me to Ron Lichty, the meeting producer. Ron and I, as it turned out, had met a few years earlier at a GivingSpace workshop. Ron explained to me his goals for the panel, told me who the panelists would be, and I said, “Sign me up!”    (JKM)

The panel went well. The panelists — Tony Christopher, Zack Rosen, Sylvia Marino, and Scott Wilder — were great. Everyone told lots of great stories, but also respected the other panelists, and no one tried to dominate the floor, which made my job incredibly easy. More importantly, the audience was engaged with the topic and the panelists. Ron was great also. He had done a masterful job of organizing the event and preengaging the panel.    (JKN)

The problem was that the panel format was wrong. Panels work best when they emerge as entertaining and informative roundtable discussions. As good as our panelists were, that was not going to happen, because the format did not optimally align with our goal — educating the audience. A panel format can achieve this goal — and ours did — but only in a broadcast model, which does not maximize group potential.    (JKO)

It was clear from an informal poll I took at the beginning of the panel and the number of faces I recognized that we had a lot of expertise in the audience itself. It would have been far more engaging and educational for all involved had we done a more interactive format, where we spent an hour in break-outs, possibly followed by a moderated plenary discussion. The panelists, in this scenario, would have been co-participants with the rest of the audience.    (JKP)

I moderated two panels and gave a talk at last June’s Collaborative Technologies Conference. One panel was in a traditional format for reasons largely out of my control, but I decided to play with the other two formats. In both of those cases, I turned the tables on the audience, rearranging the stage format into a circle, and basically played discussion moderator rather than panel moderator. Several people had already camped out in the back with their laptops open — almost assuredly planning to check email rather than listen to the talk — and a look of fear and shock came over their eyes when I told them to join me in the circle.    (JKQ)

Several people approached me afterwards and praised the format. (My favorite moment was one night at dinner, when I introduced myself to Stowe Boyd, who wrote a great essay on panels. Upon hearing my name, Stowe said, “I want to thank you.” I was completely baffled by this, as we had never met, and Stowe had not attended any of my talks. Apparently, he had heard about my panels — probably from Arieanna Foley — and he was grateful that someone had tried something different.) These folks were clearly suffering from panel fatigue, and just the fact that we were doing something different and engaging improved the experience wildly for them. I guarantee that the circle format was also more informative for the audience as a whole, because it addressed their specific concerns and it introduced a set of viewpoints far more rich than just mine or a panel’s.    (JKR)

As much as people respond to these more interactive formats, they are mere baby steps. Kindergarteners get in circles, for pete’s sake. Pre-school can be fun, but once you’ve been in kindergarten, you don’t want to go back. Facilitation techniques like Conversation Cafe and Open Space are at the first grade level, Aspiration is at second grade, and MGTaylor is at third. The latter techniques augmented with cutting edge collaborative tools is at least the fourth grade level, and we’ve only scratched the surface as to what’s possible. It’s just sad that the vast majority of conferences are at the pre-school level.    (JKS)

There are situations where panels work well as a format, but they are vastly overdone. In any case, don’t let this post prevent you from inviting me to moderate a panel. Just expect me to make some strong demands concerning format.    (JKT)

(See also Mary Hodder‘s excellent panel diatribe.)    (JKU)

Online Community Summit: Marc Smith

I spent last Thursday and Friday at the Online Community Summit in Sonoma, California. Forum One, which organizes the event, brought together a fantastic group of folks — about 60 people, including corporate and grassroot community facilitators, foundations, venture capitalists, consultants, and researchers. Zack Rosen joked that he wanted to come to this gathering, because he always sees the same people at the other events he attends, and he didn’t recognize anybody at this one. I saw several familiar faces — Zack, Tony Christopher (who informed me of the event), Jerry Michalski, Jan Hauser, Paul King, Thomas Kriese, and others — and recognized the names of several other attendees, but most of the group were new to me.    (2E1)

I enjoyed meeting and talking with Marc Smith, whose work I’ve blogged on multiple occasions, and who kicked off the day by giving a fantastic overview of the work he’s doing at Microsoft. Marc is doing very, very good stuff, and I’m not just saying that because it overlaps with some of our own work and thinking.    (2E2)

NetScan performs a variety of data analysis on USENET newsgroups based entirely on postings, and presents those metrics in useful ways. A lot of the innovation is in the visualization (see his slides for examples), and the visualization software is freely available. Some key points:    (2E3)

  • About two percent of the 13 million USENET users post three or more days a year. That doesn’t sound like much, but it works out to a quarter of a million people.    (2E4)
  • Support communities need about 40 active posters to be sustainable.    (2E5)
  • The metrics you expect depend on the type of newsgroup. The alt.binaries.* newsgroups have lots of posts, lots of posters, and very short threads. Metrics describe the interaction, but to place a value judgement on these metrics, you need to combine them with qualitative analysis.    (2E6)
  • Marc posed a bunch of metrics to look for in a healthy community: retention of leaders, interaction, size and growth, topical focus, speed, and host participation.    (2E7)

I am amazed that more people have not done this kind of research. The opportunity for evolving our applications in useful ways is tremendous. As Marc sardonically stated, “There’s a little room for conversation in our UIs.” Marc showed a few possible directions in which to evolve UIs, but whether or not these features will show up in future applications remains to be seen. There’s a tremendous opportunity for Open Source developers to study this research and implement its findings in their own applications.    (2E8)

Marc also described Project A U R A, which I blogged about a year ago.    (2E9)