Embrace GCPEDIA as a technological David

by Nick Charney

---

Last week I applied the lens put forward in Gladwell's latest book, David and Goliath: Underdogs, Misfits and the Art of Battling Giants, to the GCPEDIA project and in so doing suggested that GCPEDIA's success to date is the result of it being a David among Goliaths (See: GCPEDIA: A David Among Goliaths). After publishing the piece I had a number of people reach out to me and suggest that I should take the narrative a little further.


The Real Value of GCPEDIA is as light layer

I used to be of the one-wiki to rule them all mindset; and while I have great disdain for the duplication of technological solutions to collaboration they are sadly inevitable, at least in the short term. Technological consolidation is always possible, but it seems to me that it's a long and convoluted road over which few can successfully travel at any given time.

Since then I've come to realize that GCPEDIA's true value is its fluidity and the fact that it is a light layer that can not only co-exist with departmental systems but can fill the gaps in them; offering safe spaces to learn about collaboration and otherwise disintermediate all of the restrictive structures in place inside, among, and between our organizations.

If we accept the idea of GCPEDIA as a light layer then the question of how to scale starts to look very different; it leads to an important question, a question I stopped just short of asking last week.

Should we focus on turning technological Davids into Goliaths?

Last week I wrote:

"The project's success to date is due in no small part to the fact that it (and its administrators, stewards and advocates) have chosen to pursue paths that the Goliath mindset would otherwise have ignored: it's open source, offers users no ability to lock out others from their content, is housed in a department that technically doesn't have the mandate to house it, is supported by a small and highly dedicated (mission driven) team, and remains the only universally accessible zero barrier to entry collaboration solution within the Government of Canada."

If the above is true, then moving GCPEDIA in the opposite direction by either deploying a proprietary alternative, paying licensing fees, allowing users to restrict access to content or throwing large administrative resources will ultimately undermine and/or jeopardize its continued success. In other words, the approach isn't how do we turn this David into a Goliath? But rather, how do we make this David the best possible David it can be?

How do we embrace GCPEDIA as a technological David?

When framed as such, the answer seems fairly obvious. Stay the course, and embrace GCPEDIA and the things that have made GCPEDIA successful. GCPEDIA has been many things to many people but to me it has always been a beacon of hope that government can in fact be agile, can embrace a more open ethos, and can meet its demands for collaboration at an incredibly low cost when it chooses to do so.

And I for one, sure hope it stays that way.

GCPEDIA: A David Among Goliaths

by Nick Charney

---

Last week I picked up Malcom Gladwell's latest book, David and Goliath: Underdogs, Misfits and the Art of Battling Giants, and crushed it over the course of a couple of days*. The book explores the power asymmetries between incumbents and upstarts and how successful upstarts exploit those asymmetries by engaging in unconventional tactics. The book takes its title from the biblical story of David and Goliath and is a deeper look at a phenomenon he wrote about for the New Yorker in 2009 about an otherwise untalented basketball team that started to dominate when the coach decided to employ a full court press.

If I had to boil down the essence of the book it would be this: David (the underdog) loses when he battles Goliath (the incumbent) according to Goliath's rules; however if/when David refuses to play by Goliath's rules, he greatly increases his chances of success.

The argument is compelling and seems to makes sense intuitively (and perhaps in my case experientially) but is it a lens that can be applied to the organizational context, and if so what examples could be used to illustrate the case?

GCPEDIA: A David among Goliaths

The project's success to date is due in no small part to the fact that it (and its administrators, stewards and advocates) have chosen to pursue paths that the Goliath mindset would otherwise have ignored: it's open source, offers users no ability to lock out others from their content, is housed in a department that technically doesn't have the mandate to house it, is supported by a small and highly dedicated (mission driven) team, and remains the only universally accessible zero barrier to entry collaboration solution within the Government of Canada. It sits in stark contrast to departmental solutions to collaboration, many of which are costly, license heavy software(s) that offer users the ability to restrict access to their content and tend to be administered by large administrative bodies who are seized with administering the administrivia of the administration (if you get my meaning).

Having been close to the project during its early years, keeping an eye on it, and knowing a number of people close to the project today, I can say with some degree of certainty - and without compromising anyone's confidence - that the project's core challenge is and always has been seen as how do we, borrowing Gladwell's language, transform this David into a Goliath. How do we take this thing that has been successful not because of the rules but in spite of them, into something more stable? How do we take GCPEDIA from an upstart to an incumbent?

What I find absolutely fascinating is the related fact that GCPEDIA disintermediates so many of our traditional power structures - hierarchy, geography, group and level, ministry, etc - that it is not only a David among Goliaths but rather that it enables Davids to rise up among the Goliaths. It provides an alternative path to non-traditional sources of power, influence and opportunity by allowing peoples' work to break out of its normal constraints and be easily shared with the organization writ large and be put to use by any one of the 250,000+ individuals working across the enterprise.

This is precisely one of the points that Nicco Mele argues in his book (similarly titled) The End of Big: How the Internet Makes David the New Goliath (which, incidentally, we reviewed here), that many of the technologies being built today have an inherently anti-institutional ethos built right into them and thus reinforces that type of culture - a culture of upstarts that is fundamentally at odds with the traditional cultures of hierarchy.

After thinking it through, I can't help but see some sort of connection between the fact that while GCPEDIA may be a David among Goliaths, its under-tapped potential is to enable Davids among Goliaths, and that ultimately even if it is successful, our cultural upstarts will ultimately face the same challenge as our technological ones: how to scale.


*Despite being familiar with Gladwell's work and the theses of his books (which have penetrated the mainstream due in part to his popular narrative style), I never actually took the time to read any of his books. After reading David and Goliath, I have since read both Outliers and Blink and am in the middle of Tipping Point.