Talking Technology

Todd Johnston posted an outstanding summary of our informal session this past Saturday. He mentioned our first exercise, which was to have Todd, Gail Taylor, and Tiffany Von Emmel explain how email worked to Matthew O’Connor and myself, who had had sudden bouts of amnesia. Todd wrote, “This exercise, as you may imagine, did a lot to uncover assumptions, vantage points and metaphors we use to shape our understanding.”    (LX9)

The point of the exercise was two-fold. First, we wanted the group to have a better understanding of how the Internet worked. Second, rather than tell them how it worked, we wanted them to figure it out by thinking through the problem. Most of us have the mental tools to understand technology; we just choose not to use them. We wanted to get them to use them.    (LXA)

What was interesting about the exercise was that they did an excellent job of drawing a basic conceptual picture. However, when Matthew and I started asking probing questions to help fill in the gaps, they abandoned their mental models and started reverting to buzzwords. They mentioned things like packets and algorithms and server farms, all of which demonstrated knowledge of Internet lingo, but none of which was necessary to explain how email worked.    (LXB)

Matthew pointed out that techies often do the same thing. When confronted with basic questions about technology, they often start throwing around concepts and language that aren’t critical to the core question. In these cases, they do this because they’re unaware of the other party’s mental models and are feeling around for context.    (LXC)

Why would non-techies do the same thing? In this particular case, it was for the exact same reason. Even though Matthew and I were playing dumb, they knew that we knew the answers. When we started asking questions, they abandoned their model and started feeling around for the answers we might be looking for, hence the lingo.    (LXD)

When one person has knowledge that the other person doesn’t have, that often results in a power relationship, and power relationships affect how people behave. What makes this relationship dangerous is when people assume that this knowledge is somehow sacred and unattainable. Many non-technical people are guilty of this. It’s evident when people preface their statements, “I’m not a techie,” as if that makes them incapable of understanding technology. It’s an attitude problem that stems from fear.    (LXE)

The important thing is that everyone is capable of understanding technology. Don’t let those supposedly in the know bully you away from being confident in what you understand and what you don’t understand.    (LXF)

On a separate note, Todd also describes Finding Your Hey, an exercise that the band, Phish often performs. Todd first told me this story two years ago, and I dutifully blogged about it, but I didn’t know what it was called, and I didn’t know the exact quote. It’s a wonderful story.    (LXG)

Collaboration as a System

I spent this past Saturday in Sebastopol “tutoring” Gail Taylor, Todd Johnston, and Tiffany Von Emmel on online Collaborative Tools. I lured Matthew O’Connor into helping by boasting of Gail, Todd, and Tiffany’s deep thinking about and practice of collaboration.    (LVC)

One of our exercises was to walk through all of our respective digital workspaces, demonstrating how we read and wrote email, and worked with online tools. I had gotten some idea of how Matthew worked when we paired at the Wikithon earlier this month, but I was still blown away by his walkthrough. He’s really thought deeply about his work processes and has optimized his online workspace accordingly.    (LVD)

Matthew expressed surprise that he was the only one who had done this, especially since I had proclaimed these folks to be gurus. I didn’t have a chance to discuss this with him on Saturday, so I thought I’d post some thoughts about that here.    (LVE)

To be good at collaboration, you have to treat it as a system. That system includes things like communication, community, Knowledge Management, learning, and leadership.    (LVF)

Most Collaborative Tools companies are either in the communication or the Knowledge Management business. They’re usually selling pipes, PIMs, or document management tools. All of those things have something to do with collaboration, but they are not in and of themselves collaboration. Then again, no tools are. A hammer is a tool for hammering, but it is not itself hammering.    (LVG)

When I think about High-Performance Collaboration, I envision groups with excellent Group Information Hygiene. Ideally, you’d also like every member of the group to have outstanding Personal Information Hygiene (like Matthew), but it’s not a prerequisite. You’d like to see every member to be past a certain threshold of competence for all aspects of the system, but I don’t think it’s necessary for everyone to be great at all those things. On a great basketball team, you’d like everyone to be in good shape and have good fundamentals, but some players are going to be superior shooters while others will be great rebounders. It’s not necessary, nor realistic, nor possibly desirable to have 12 Magic Johnsons on a team.    (LVH)

Implicit in my One Small Change post is that there is no one thing. I can think of a number of small, concrete changes that could result in significant improvements in collaboration. This is one of the main reasons why Pattern Languages — collections of named, concrete patterns — are fundamental to The Blue Oxen Way.    (LVI)

Personal Information Hygiene is a critical pattern, because it fosters trust. My advice to groups with trust issues would be to eschew squishy exercises and look at people’s Personal Information Hygiene instead. However, past a certain level, I don’t see great Personal Information Hygiene as being the primary hallmark of a great collaborator.    (LVJ)

Welcome, Gail and Todd!

Those who follow my blog regularly know how much I respect, admire, and occasionally collaborate with Gail Taylor. Some of her stories have trickled onto this blog, but they represent only a fraction of the thinking that she has helped inspire. Gail and her co-conspirator at Tomorrow Makers (and son), Todd Johnston, have been long-time fans of Wikis, and they recently joined the blogosphere. If you’re interested in deep thinking and great stories about collaboration, I strongly recommend subscribing to their new blog. As expected, there’s already a rich set of stories and thinking there, with much more to come. Welcome, Gail and Todd!    (L5C)

While I’m at it, it’s also worth mentioning Matt Taylor‘s real-time notebook. Matt is another one of Gail’s co-conspirators (and her husband), and his online journal has been available for many years. It’s not technically a blog yet (no RSS or Permalinks), so you can’t subscribe to it, but I highly recommend perusing it. There’s an amazing wealth of information there.    (L5D)

Phish and Collaboration

Todd Johnston told me a story about Phish, which he read in Nubar Alexanian‘s book, Where Music Comes From. When the band practices, one member will start riffing, then the other ones will join in one-by-one, all with their eyes closed. When a band member feels like they’re all in sync, he yells, “Hey!” If all the members yell at the same time, the band is collaborating.    (GFT)