FLOSS Usability Sprint Quick Impressions

Coming to you live, quick impressions from our fourth FLOSS Usability Sprint:    (LZC)

  • Each of our sprints have had a distinct personality. One thing that strikes me about our participants this time is how well all of them understand and buy into usability. One big reason for that is our projects — we have three repeat projects plus Firefox. It also reflects nicely on a growing shared understanding on what Open Source and usability are, and how we can marry the two together.    (LZD)
  • After having gone through three and a half of these sprints, I find that I have inadvertently become a knowledge repository for a ton of great learning about both usability and Open Source. While I love the learning, I can’t help but think that there’s someone in the community with a greater individual stake than I — a usability practitioner or an Open Source developer — who’s missing out on a great personal opportunity to serve that same role and really become a champion and leader of the cause.    (LZE)
  • Great space + great people + great process = Group Genius. It never fails.    (LZF)
  • People who have never participated in this type of event before don’t realize how exhausting it is. This is not Bar Camp. Yeah, we’re connecting, we’re knowledge-sharing, and we’re having fun. But we’re also working. And it’s really fun watching these folks — after an exhausting week of regular week — crank away on these projects. If work were always this fun, the world would truly be an interesting place. It feels even better knowing that we’re working on tools that will make an impact on the world at large.    (LZG)
  • Google‘s very own Leslie Hawthorn is awesome. I know, I know, I’ve gushed about her before. But it needs to be said again and again and again.    (LZH)

Wikipedia Virgin No More

Yesterday, Erik Moeller asked me to look at the Wikipedia entry on Intellipedia. Curious as to the timing of the request, I checked my feeds, and sure enough, a few articles on Intellipedia had cropped up.    (LGQ)

I figured the best people to review the accuracy of the article were those involved, so I passed Erik’s request along to them. However, in reviewing the article myself, I noticed that somebody had linked to my picture of the Intellipedia shovel, along with a short description. The description was slightly off, so I decided to fix it. In doing so, I lost my Wikipedia virginity.    (LGR)

If you want to be technical about it, I wasn’t a real Wikipedia virgin. I’ve vandalized the site anonymously on more than one occasion. That’s right, vandalized. It was a cool trick I picked up from Ross Mayfield as a way to demonstrate in front of a live audience that yes, anyone really can edit Wikipedia, and more importantly, that Wikipedia is self-healing. I don’t do it anymore, because the bots have gotten smarter, thus eliminating one of the main points of the demonstration.    (LGS)

The first time I told this story to Wikipedians was when I was introducing myself at the Hacking Days Wiki developers summit at Wikimania 2005. I said, “I’ve never edited Wikipedia, but I have vandalized it on more than one occasions.” I thought it was pretty funny, but no one laughed. It could have been that people had a hard time picking up on the irony in English, but I think people just didn’t think it was funny. So for all of you Wikipedians hearing this story for the first time, blame Ross.    (LGT)

I nearly edited Wikipedia for real in 2004, when I was finishing up my research on Open Source adoption in Brazil. In my original draft, I told some great stories about the rise of grassroot communities in Brazil, and to my horror, the editors cut them out. I decided to insert them into Wikipedia, but I never got around to it. Maybe I’ll revisit this, especially now that Lula is back in the news.    (LGU)

I’ve spoken at both Wikimanias, and I’ve talked to many folks about Wikipedia, so I’ve always felt a little guilty about not having actually edited it. Then at this year’s Wikimania, I learned that Ward Cunningham hasn’t edited it yet either. (It’s captured on this recording.) That helped, but now the guilt is gone for good.    (LGV)

How does it feel to have finally edited it? To be honest, it’s no different than editing any other Wiki. Personally, I find that really cool. It’s further confirmation that as big as Wikipedia has become, at its core, it’s still just a Wiki. It reminds of the original exchange between Jimbo Wales and Ward Cunningham on Ward’s Wiki about Wikipedia:    (LGW)

My question, to this esteemed Wiki community, is this: Do you think that a Wiki could successfully generate a useful encyclopedia? — Jimbo Wales    (LGX)

Yes, but in the end it wouldn’t be an encyclopedia. It would be a wiki. — Ward Cunningham    (LGY)

Of course, my assessment isn’t quite fair, either. I haven’t experienced a Wikipedia edit war first-hand or a negotiation over Neutral Point Of View. More things to look forward to!    (LGZ)

The Google Gradient

Aaron Swartz wrote an interesting piece about the so-called Google bubble. He then proposed a way around the bubble, which he called the Google “gradient.” Having just wrapped up an event that Google sponsored, I can give some first-hand thoughts on Aaron’s piece. In short, the gradient already exists, and boy, is it a doozy.    (LG0)

Both Allen Gunn and I have worked with many, many generous companies on events like the FLOSS Usability Sprint, and we both agreed that Google was unquestionably the easiest, most accomodating company we’ve ever worked with. Here’s a snapshot of my experience:    (LG1)

  • Earlier this year at DCamp, I meet Rick Boardman, a user experience engineer at Google. We talk about the FLOSS Usability Sprints, and he says, “That’s pretty cool. If you ever want space for a sprint, we can do it at Google.”    (LG2)
  • Gunner and I decide it’s time to do another sprint. I email Rick. Rick says, “No problem. I’ll dig up food for you guys too.” I look down at my list of negotiation points when dealing with potential sponsors, reread Rick’s email, shrug my shoulders, and throw the list away.    (LG3)
  • I check out the space, and it’s outstanding. Wide open room that’s reconfigurable, lots of whiteboards, plenty of breakout space, open WiFi.    (LG4)
  • Rick introduces me to Leslie Hawthorn, who’s involved with Google’s Open Source programs and managed Summer of Code. Leslie is the epitome of a Yellow Thread. Here’s an example of a common exchange. Me: “Leslie, I know it’s last minute, but can you do [insert any number of requests here] for us?” Leslie: “Sure!”    (LG5)
  • I get to Google early on Friday. Leslie gives me a walkthrough. To my surprise, she has Google schwag bags for all of us. She also has special badges for us, so that participants don’t have to sign the usual visitor NDAs.    (LG6)
  • There are about six security guards surrounding our space throughout the whole event. This should have been unnerving, except they were all very friendly, they kept opening doors for the participants, and they made it safe for us to leave our computers lying around the entire weekend.    (LG7)
  • Leslie supplies us with snacks, beverages, and most importantly, coffee throughout the event. We eat lunch both days at Slices, one of the excellent cafeterias on campus. The food is local, organic, and delicious. (Gunner and I do our best to cancel out all this healthy food by bringing pizza and donuts and by taking the group out for adult beverages and more unhealthy food afterwards.)    (LG8)
  • Four Google employees participate, including Rick and Leslie. All of them kick butt. I didn’t know Leslie’s background beforehand, but as it turns out, she completely rocks out with the Drupal team, thus increasing my respect for her by another order of magnitude. More common exchanges with Leslie during the event. Me: “Leslie, can you help us with [insert many more requests here]?” Leslie: “Sure!”    (LG9)
  • Total number of pain-in-the-rear problems that the Google bureaucracy creates for us that are inevitable when working with large companies on open events like these: 0.    (LGA)

Perhaps this was an isolated experience. Perhaps the next time we work with Google, this so-called “bubble” will be in full effect, and we’ll curse and swear about how terrible the bureaucracy is there. All I can say is that I’ll be able to tell you all for sure soon, because I fully plan on there being a next time. Many thanks to Leslie and Rick for being such outstanding hosts!    (LGB)

FLOSS Usability Sprint III

This weekend, Aspiration and Blue Oxen Associates are once again co-hosting FLOSS Usability Sprint III, the pre-eminent event for bringing usability to Open Source projects. This year, we’ve moved venues from San Francisco to Mountain View. Thanks to Google and especially Rick Boardman for sponsoring the event!    (LET)

As always, we have a great set of participants, and it should be both productive and fun. What’s even cooler for me this year is that one of my projects, HyperScope, will be a participant. I love it when things converge! The other projects are Drupal, Social Source Commons, Socialtext Open, and Sustainable Civil Society. Really looking forward to it!    (LEU)

The Future of Intelligence, Part 1

About six months after 9/11, I came across a book by Gregory Treverton, who served as the Vice Chair of the National Intelligence Council under Bill Clinton. The book, Reshaping National Intelligence for the Age of Information, was published shortly before 9/11, and its insights into the state of national intelligence were both revealing and prescient. It’s a remarkable book, and it got me thinking more deeply about the incredible cultural and organizational challenges of national intelligence. Not coincidentally, around the same time, I was starting to synthesize my ideas on collaboration, a process that resulted in my founding of Blue Oxen Associates.    (L7T)

Things are starting to come full circle. Over the past year, I’ve found myself engaged in conversation with a number of people in the intelligence community, and it culminated in a two day workshop with the CIA this past week. It’s been somewhat of a surreal experience, given that I’ve spent much of the past four years working side-by-side with progressive and Open Source activists, many of whom consider the government an antagonist at best, an enemy at worst. Moreover, my one previous brush with government work — a project with the FAA — left me with a less than favorable view of how our federal agencies work. The culture there is stifling, especially in comparison to the Bay Area. There is a stated desire to learn and to improve, but there is very little real commitment. Those who actually want to do something are trapped under a blanket of repressive indifference, and those who manage to do something anyway are usually completely marginalized by their superiors and even their peers.    (L7U)

All that said, the fundamental challenges regarding intelligence are dear to my heart, and I find myself paying a bit more attention when these conversations and opportunities present themselves. I firmly believe that deep knowledge about collaboration is spread across a number of domains, and the only way to acquire this knowledge is to engage with each of those different communities. This especially holds true with intelligence, where the knowledge product itself is sensemaking and actionable knowledge.    (L7V)

I am also a patriot. That word has attained somewhat of a negative connotation over the past five years, which is not necessarily a bad thing, because it has forced us to deeply reexamine our values. I’ve gone through this process myself, and I’ve walked away even more sure of my feelings. I’d like to make both this country and the world a better place. Those two goals are not orthogonal.    (L7W)

Last year, I met Darniet Jennings, an intelligence researcher, at WikiSym. We’ve had a number of interesting conversations since, and he participated in our first “Tools for Catalyzing Collaboration” workshop. About six months ago, he referred me to a paper written by Calvin Andrus entitled, “The Wiki and the Blog: Toward a Complex Adaptive Intelligence Community.” Andrus, who is with the CIA, wrote this paper last year, and it has since become the de facto reference on the role of Social Software in intelligence.    (L7X)

I’ve found the majority of these kinds of whitepapers shallow and uninteresting. Andrus’s paper is anything but. Rather than offer some simplistic portrayal of these tools while repeating the same tiresome anecdotes and misconceptions over why they’re useful, Andrus frames the conversation in terms of systems theory. He cites Ludwig von Bertalanffy and Jane Jacobs, and he praises decentralization, localization, and emergence. The depth of his paper comes from this framing, which establishes the correct higher-level goals and philosophy behind these tools and which surfaces the intelligence community’s real challenges. The paper has flaws, but they are minor.    (L7Y)

The fact that such a paper exists and that it has been embraced by the intelligence community makes me hopeful, but that hope is tempered by Treverton. Andrus writes about the importance of empowering local, bottoms-up action, and he cites Tip O’Neill‘s famous maxim, “All politics is local politics.” For those who might perceive of the intelligence community as being overly centralized, this seems to be a refreshing viewpoint.    (L7Z)

However, Treverton suggests that this view is not foreign to the intelligence community at all. In fact, he writes that “intelligence analysts tend toward the long view and to take the world as a given.” Treverton then cites the very same O’Neill quote, writing, “Because they [intelligence analysts] are so immersed in the local, they are by profession believers in the adage attributed to former U.S. Congressman Tip O’Neill that ‘all politics is local politics'” (181). In contrast, policy makers tend to care less about the long view. Transforming national intelligence is not enough. We need to transform the relationship between intelligence and policy.    (L80)