Friday, October 26, 2012

Where ideas go to live and/or die

I just finished reading Steven Johnson's "Where Good Ideas Come From" and it's an absolute must read for anyone interested in the sweet science of innovation; he's actually got a TED talk that addresses some of these issues but it isn't nearly as compelling as the book).

I was so impressed with the book that I simply had to abandon my traditional Monday Book Review format and bring you a little something deeper. At its core the book is about the origins of good ideas, while explaining these origins Johnson goes through seven integral (and interrelated) concepts of innovation:

  • the adjacent possible
  • liquid networks
  • slow hunch
  • serendipity
  • error
  • exaptation
  • platforms

What follows is a blend of the most pertinent excerpts form the book and my own thoughts on how those excerpts relate to the public sector writ large (warning: it's a long post, I've been chewing on these ideas for weeks).

The Adjacent Possible
The adjacent possible is a a kind of shadow future, hovering on the edge of present state of things, a map of all the ways in which the present can reinvent it self. Yet it is not an infinite space, or a totally open playing field... What the adjacent possible tells us is that at any moment the world is capable of extraordinary change, but only certain changes can happen. The strange and beautiful truth is that is that its boundaries grow as you explore those boundaries. Each new combination ushers in new combinations into the adjacent possible. (p.31)

Think of the adjacent possible as the doors leading out of the room you are in. The more you explore what's behind those doors, the more doors you find to explore. The key lesson here - one that I have argued repeatedly - is that exploring the edges of the organization is what creates the room for growth. In short, organizations need people who are willing to be nomads; they need tricksters who walk the line; they need people to open doors to new ways of thinking.

My own experience is that I find it is rather easy to stand out as someone who engages in these types of activities because (in my view) its the path least travelled by fellow bureaucrats. No one ever speaks out against the notion that the public sector needs to be more innovative (its an untenable position) but my sense is that few of us actually invest time in truly understanding (and pursuing) what is required to achieve it. This is, at least in part, attributable to a culture that rewards keeping conversations within established (and hierarchical) channels. Anyone who has ever been "corrected" by a manager for corresponding with a colleague above their current pay grade knows this truth intimately.

It's fair to say that the general criticism levied by many against governments in general is that they aren't exactly environments that breed innovation; which I suppose leads us to the question, what kind of environment creates good ideas? According to Johnson:

The simplest way to answer it is this: innovative environments are better at helping their inhabitants explore the adjacent possible, because they expose a wide and diverse sample of spare parts - mechanical or conceptual - and they encourage novel ways of recombining those parts. Environments that block or limit those new combinations - by punishing experimentation, by securing certain branches of possibility, by making the current state so satisfying that no one bothers to explore the edges - will, on average, generate and circulate fewer innovations than environments that encourage exploration. (p. 41)

One of the key points that Johnson makes later in the chapter is on the idea of sustainability and that while there may be incredibly innovative individuals who leap ahead of what is currently possible, the innovation they bring to the market isn't sustainable because the prerequisite doors within the adjacent possible haven't been unlocked yet. If organizations are looking to embrace a sustainable approach to innovation they need to do a better job of weaving exploration and solidification into their business fabric. The (slightly frustrating) implication for would fast moving innovators and earlier adopters is likely that they need to slow down and work on building a foundation that will support their downsteam efforts rather then simply jumping ahead to those efforts right now.

Liquid Networks

According to Johnson ideas don't happen in a vacuum. While we tend to characterize the greatest ideas of our times as sudden strokes of genius and "aha moments", this characterization is incredibly flawed and often misleading:

A good idea is a network. A specific constellation of neurons–thousands of them–fire in sync with each other for the first time in your brain, and an idea pops into your consciousness. A new idea is a network of cells exploring the adjacent possible of connections that they can make in your mind. This is true whether the idea in question is a new way to solve a complex physics problem, or a closing line for a novel, or a feature for a software application. If we're going to try to explain the mystery of where good ideas come from, we'll have to start by shaking ourselves free of this common misconception: an idea is not a single thing. It is more like a swarm...  
When you think about ideas in there native state of neural networks, two key preconditions become clear. First, the sheer size of the network: you can't have an epiphany with only three neurons firing...The second precondition is that the network be plastic, capable of adopting new configurations. A dense network incapable of forming new patterns is, by definition, incapable of change, incapable of probing at the edges of the adjacent possible. (pp. 44-46)

Density matters; it affects the size of the adjacent possible. Maintaining a dense and diverse network is important for anyone looking to be more innovative. The more ideas you come up against the more raw materials you have for connections to be made betwixt them. Malleability also matters; yet public sector working environments are anything but plastic. I hope that public sector work environments loosen up a bit as people are increasingly realizing that less rigid environments are more conducive to innovating than rigid ones.  If you are asking yourself how to push your brain towards more creative networks, Johnson agues that:

The answer, as it happens, is delightfully fractal: to make your mind more innovative, you have to place it inside environments that share that same network signature: networks of ideas or people that mimic the neural networks of a mind exploring the boundaries of the adjacent possible. (p. 47)

Slow Hunch
... the snap judgements of intuition - as powerful as they can be - are rarities in the history of world-changing ideas. Most hunches that turn into important innovations unfold over much longer time frames. They start with a vague, hard-to-describe sense that there's an interesting solution to a problem that hasn't yet been proposed, and they linger in the shadows of the mind, sometimes for decades, assembling new connections and gaining strength. And then one day they are transformed into something more substantial: sometimes jolted out by some newly discovered trove of information, or by another hunch lingering in another mind, or by an internal association that finally completes the though. (p. 77)

I suppose there is some sort of ironic corollory that can be drawn between slow moving bureaucracies and the slow hunch, I'd rather side step it and instead focus on the heart of the matter, namely that:

Because these slow hunches need so much time to develop, they are fragile creatures, easily lost to the more pressing needs of day-to-day issues. (p. 77)

One of the biggest challenges facing governments is that they tend to focus on the immediacy of pressing needs to the detriment of the longer game. Its the cultural underpinnings that give us table dropped documents, last minute changes, and rush translations.

The premise that innovation propsers when ideas can serendipitously connect and recombine with other ideas, when other hunches can stumble across other hunches that successfully fill in their blanks, may seem like an obvious truth, but the strange fact is that a great deal of the past two centuries of legal and folk wisdom about innovation has pursued the exact opposite argument, building walls between ideas ... Ironically those walls have been erected with the explicit aim of encouraging innovation. They go by many names: patents, digital rights management, intellectual property, trade secrets, proprietary technology. But they share a founding assumption: that in the long run innovation will increase if you put restrictions on the spread of new ideas ... The problem with these closed environments is that they inhibit serendipity and reduce the overall network of minds that can potentially engage with a problem. (pp. 123-124)

I'm not sure this needs elaboration; it may be sufficient to poke you in the direction of thinking about how open to serendipity your organization is, whether or not you are encouraged to meet and engage in dialogue with people outside it, and how important it is that you be physically present in the office even when its inconsequential to your ability to deliver on your responsibilities.

"The errors of the great mind exceed in number those of the less vigorous one." This is not merely statistics. It is not that the pioneering thinkers are simply more productive than less "vigorous" ones, generating more ideas overall, both good and bad. Some historical studies of patent records have in fact shown that overall productivity correlates with radical breakthroughs in science and technology, that sheer quantity ultimately leads to quality. [There is a] more subtle case for the role of error in innovation, because error is not simply a phase you have to suffer through on the way to genius. Error often creates a path that leads you out of your comfortable assumptions ... Being right keeps you in place. Being wrong forces you to explore. (p. 117)

Again, think about how accepting of failure your organization is; are the majority of new projects are born out of comfortable assumptions - the way we've always done things - or are they prompted by an admission that something is a miss and needs to be fixed from the ground up?


Taking ideas from other sectors and applying them to the public sector is what Johnson calls exaptation:

If mutation and error and serendipity unlock new doors in the biosphere's adjacent possible, exaptations help us explore the new possibilities behind those doors. A match you light to illuminate a darkened room turns out to have a completely different use when you open a doorway and discover a room with a pile of logs and a fireplace in it. A tool that helps you see in one context ends up helping you keep warm in another. (p. 156)

I've said repeatedly to people that if they want to be recognized as an innovator, all they have to do is look in the direction others aren`t. If the entire organization is looking left, look right. The marginal value of another set of eyes looking left is negligible. The value of the first set of eyes to look right is enormous.

What would you rather be known for?

Platform building is, by definition, a kinds of exercise in emergent behaviour ... platform builders [don't] just open a door to the adjacent possible. They build an entire new floor. (p. 183)

The above statement isn't surprising if you are already familiar with the idea of government as platform; however what is surprising is what Johnson has to say about the potential of bureaucracies to be a platform:

Government bureaucracies have a long and richly deserved reputation for squelching innovation, but they possess four key elements that may allow them to benefit from the innovation engine of an emergent platform. First, they are repositories of a vast amount of information and services that could be of potential value to ordinary people, if only we could organize it better. Second, ordinary people have a passionate interest in the kind of information governments deal with, whether it's data about industrial zoning, health-care services or crime rates. Third, a long tradition exists of citizens committing time and intellectual energy to tackling problems where there is a perceived civic good at stake, And, finally, the fact that governments are not in the private sector means that they do not feel any competitive pressure to keep their data proprietary. (p. 196)

The first three points are bang on - and make a great case in support of open data - however Johnson's final point, that governments don't feel competitive pressure to keep their data proprietary, is (in my experience) wrong. There is tremendous pressure to keep things out of the public sphere, to minimize data sharing, and horde information; furthermore these pressures are felt at both the organizational and individual levels.

A visual conclusion selon moi

Based on my interpretation of Johnson's book; I've cobbled together the following chart that shows where I think ideas go to live and where they go to die (click to enlarge):

Originally published by Nick Charney at
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney

Friday, October 19, 2012

What I did last night instead of blogging

I miss colouring; don't you?
I've been chewing on a lot of things this week; but instead of sitting down and writing, I sat down with some of the people that matter the most to me.

I sat down and coloured a picture with my kids; something I haven't done for a long time.  My daughter commented about how happy she was that we were all at the table together enjoying the same activity.

I sat down with my mother and we talked a bit about how my folks are doing and what's coming down the pipe in the near future.

I sat with my wife and talked about our immediate concerns: my experience chaperoning our son's field-trip; some of the challenges she is facing in her current role as an acting manager within the provincial civil service; and the ongoings of her class that night (she is currently completing her Master's of Education).  Then we just poked around on reddit for a bit, laughed hard, joked around some more as I tucked her in, and laughed even harder.

I sat down with one of my oldest friends to shoot the shit, take a load off, and play some video games.

And finally, I sat down with myself and wrote this simple note that I wanted to share with you:  
Remember to nurture your relationships, its often far too easy to forget how important to you they really are.

Originally published by Nick Charney at
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney

Friday, October 12, 2012

Is it time to stick a fork in internal cost recovery?

"Stabby" by Amy McTigue
Apologies in advance to those working in departments or agencies based on cost recovery models or whose work itself is to manage internal cost recovery processes within the public sector; what follows isn't a discussion about you, your worth or your dedication to public service in so much as a discussion (at the conceptual level) about the cost recovery model within which you are working.

Here's my understanding of how cost recovery works

Agencies based on cost-recovery models are usually ones that provide common yet specialized services to other departments and agencies; common so much they are in demand by all of the organizations they serve and specialized in so much as they usually pertain to one specific service (e.g. information technology, learning and development, legal services, etc).

The rationale is that centralizing these services and administering them centrally costs less than administering them in a distributed fashion, and intuitively this seems to make sense. What I don't understand, and what I've been thinking about a lot this past week is why organizations bother building infrastructure to recover costs from what is (at the end of the day) just another part of the same organization. Why do organizations insist on moving monies from one area to another knowing full well that they will be passed on again to the organization who will ultimately deliver the service for which the money is allocated. Here's what I mean (click the image to enlarge):

Imagine that the box above represents the entire enterprise. Within that enterprise Org Alpha is in charge of the monies, Org Bravo is responsible for mandate "Y" and Org Charlie is a supporting service based organization that has to deliver Service "X" to all of the organizations within the enterprise.

In order to Org Bravo to achieve its mission it gets funding from Org Alpha and in turn redistributes a portion of it to Org Charlie in exchange for Service "X". This results in funds being sent and received twice along the path and likely results in a portion of those resources being burned in the transaction as people need to manage that process.

My question is this: If the enterprise knows that the ultimate destination for a subset of the funds is Org Charlie and knows that those funds are required to deliver the necessary and valuable Service "X", why not simply send the funds directly?

If enterprise resources are scarce, and there is a common understanding that all of the Orgs are a part of the same enterprise, the thought of burning even a small fraction of the enterprise's precious resources as those resources are moved should give rise to a cost avoidance strategy whereby the enterprise moves resources as little as possible prior to directing Orgs to expend them. Why doesn't the enterprise simply declare the importance of these value added services as self-evident and do away with the additional resource shuffling? (again, click to enlarge)

Originally published by Nick Charney at
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney

Tuesday, October 9, 2012

Scheming Virtuously: A Handbook for Public Servants Disponible en Français

As you may or may not know I was trying to raise $4,000 dollars (crazy I know) to have my whitepaper, Scheming Virtuously: A Handbook for Public Servants into French. I had someone step up and offer to take on the translation, for which I am incredibly thankful and appreciative.

In return for their generosity, I offered the funds raised to a charity of their choosing but sadly we didn't hit the fundraising target so the donations were returned to those who pledged them; that said, I want to say thank you to everyone who got behind the campaign and pledged their support.

I've set up a permanent page on this site to host both the English and French versions of the Scheming; I invite you to share the document as widely as you see fit and in the language of your choosing; again thanks to my friend Doug Hadden at Freebalance for facilitating the translation of the original text into French.



Originally published by Nick Charney at
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney

Friday, October 5, 2012

Sometimes it is about the technology

It's not about the technology, its about the people.

It's a phrase I've uttered probably more than a thousand times in the last five years. It stems from the understanding that technologies will come and go (quickly, almost at a whim) but behaviours change slowly and as a result we should focus our attention on cultivating the behaviours we want to see within our organizations, not chasing shiny new objects across the internet.

But at a certain point - and I just might be there for a couple of very specific work related reasons right now - it is about the technology.

It's about access to the tools I need to do the job the way it needs to be done; or perhaps more rightly the way I know it could be done if I had access to the tools to it.

I don't know about you, but I'm a little tired of being asked to build a house with only a hammer

Don't get me wrong, I still completely agree with Clay Shirky when he says that the tools don't truly get interesting until the technology gets boring; but I am also of the mind that if we want to jump start the culture we need to be able to experiment within the adjacent possible and in so doing show people the art of the possible.

Without even blinking, I can name at least three things we (at the officer level) need better access to: crowd-sourcing technology, data visualization tools, and live dashboards with the latest business intelligence.

I wish I had a snappy conclusion, and I apologize now for the abrupt ending, but all I can think of is:

Originally published by Nick Charney at
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney

Tuesday, October 2, 2012

MBR: Trust Me I'm Lying: Confessions of a Media Manipulator

I decided I was going to read a book a week every couple of weeks for a year, here's a quick review of this week's book.  You can see the ongoing list here.

Basic Info

Trust Me I'm Lying: Confessions of a Media Manipulator by Ryan Holiday

Why I read it

A buddy of mine gave me a heads up about the book after he heard Ryan Holiday on Q that week. I hadn't heard the interview, but based on how my friend reacted, I figured I had to pick up a copy of this book (Note: I listened to the interview after reading the book, even if you don't grab the book, the interview is worth the 24 minutes or if you prefer video, Holiday sat down with Andrew Keen for an interview).

How it connects to the Public Sector

The book makes you rethink the relationship between blogs and the mainstream media. While Holiday is talking about the tech/celebrity scene in the US when you consider his experience in the context of the public sector it gives you pause. It makes you wonder about how much of the coverage of the Hill is based on PR spin and speculation instigated by media manipulators like Holiday leveraging traffic hungry blogs, if you don't think it can happen, I'd encourage you to look into the Shirley Sherrod Scandal for a reality check (FYI Holiday goes into detail about this example in his book).

What I got out of reading it

The book confirmed my suspicions that a lot of what you read out there (online) is bullshit; and it has made me even more sceptical of the blogs covering the tech scene than I was.

The biggest takeaway for me was that fact checking (regardless of your profession) is probably one of most important (and in time pressured environments often overlooked) parts of your job; the last thing you'd want to do is provide advice to the powers that be based on some speculative blog posts spun by someone like Holiday.

While at times Trust Me I'm Lying reads like a a revenge book (Holiday basically gives the finger to a lot of the online powers that be) the underlying message is compelling: a short shadow of the future and perverse business models built on pages views creates intense competition for your attention while simultaneously delivering you sub-par and filler content; whereas a longer shadow of the future - say like the one I try to adopt with this blog - offers less immediate short term gains but (hopes) to deliver more compelling and useful content (and thus impact) over time.

Originally published by Nick Charney at
RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Nick Charneytwitter / nickcharneygovloop / nickcharneyGoogle+ / nickcharney