Reconsidering Analog Solutions in the Digital Era

Friday, April 21, 2017

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

Earlier this week Kent wrote a piece entitled Deep Dives, or Long Drags in which (to summarize) he posited that while we've all agreed that the world is more complex, we've done little in terms of redesigning our institutions to deal with that complexity.

It's a conversation he and I (and others) have had repeatedly and I often boil it down to "If we were looking to solve problem x and we weren't bound by our current institutional array where would we start?"; essentially advancing a clean slate approach to thinking through the problematic. Now perhaps that's an unreasonable starting place given we can't simply start from the ground up, a more realistic starting point is likely the Tamarack deep dive that Kent references:
"There were no panels, no real keynote speakers, and no “big names” as hooks. Most of the conference programming was led and delivered by three experts from Tamarack. It was more like a curriculum than a conference; they clearly spent a lot of time deciding on what participants needed to learn and preparing sessions to get it across. It came with a textbook-length package of tools and further reading."
At which point Kent pivots into the practical operations of an organization that tends to prioritize short term tactics over long term strategies.

Herein lies part of the problem

The professional non-partisan civil service is -- we are told -- supposed to take a long view, play the long game, have a long shadow of the future. However digital technologies that are designed to make things as easy, intuitive, and expedient as possible are conspiring against those who would play the long game (See: 5 Things About Online Public Engagement).

It not a stretch to say that the same technologies that allow us to gather more information, to be better informed, and to make more evidence based and/or stakeholder informed decisions are also the technologies that create paralysis by analysis, jam our communications channels, and inflate the perception of risks associated with any course of action (presumably because we can better foresee the consequences).

Herein lies a possible solution

The Tamarack example is an interesting one to me because its analog, not digital. Its about putting the right people in the room and working them through a process within an appropriate amount of time and with the appropriate (and detailed!) supports. Its not too far off from the school of thought that argues we ought to be spending 95% of our time defining the problem and 5% solving it.

We often jump to digital as a driver of or potential solution to our most pressing problems, maybe we ought to pause more often before we do. Perhaps we ought to reconsider the merits of analog (slow!) solutions in the digital era.

Deep dives, or long drags

Tuesday, April 18, 2017
by Kent Aitken RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Kent Aitkentwitter / kentdaitkengovloop / KentAitken

The idea that problems are increasingly complex is incredibly common. It's taken as a truism. If that's the case, why haven’t we reorganized our institutions to deal with it?

*****

A quick story. In March I was at a Tamarack conference on community engagement, and I was struck by the design details of the event.

There were no panels, no real keynote speakers, and no “big names” as hooks. Most of the conference programming was led and delivered by three experts from Tamarack. It was more like a curriculum than a conference; they clearly spent a lot of time deciding on what participants needed to learn and preparing sessions to get it across. It came with a textbook-length package of tools and further reading. To some extent this is a luxury of small events, but I’ve seen it done well with 300 people, too.

This is what we’d expect of that organization; Tamarack's business is designing and facilitating collective learning and decision-making processes. Their President, Paul Born, used an example about being approached to facilitate the development of a homelessness reduction strategy in one community. The process he designed was a 2.5 day session with the key actors in the ecosystem, including senior leaders from government, NGOs, and business. He considered it the minimum amount of time required to work through the issue, have participants meaningfully reflect, and to build commitment to action.

At this point I’d like to contrast this with what I’d consider the standard approaches. Conference panels that work more like back-to-back short presentations, often without trained moderators, that barely scratch the surface of an issue. A universal meeting format of presenting an issue followed by discussion and decision, 20 minutes tops. A premium on brevity and simplicity in written materials.

Our group knowledge transfer and decision-making systems are, unequivocally, not designed for complexity.

I suspect that the common reaction to the idea of getting the 100 most influential people in a system to work through an issue for 2.5 days would be that it’d be impossible. That’s way too much time. Which is exactly what facilitators, designers, and consultants hear. “Can you help us do this?” “Yes, and it’ll take X amount of time.” “That’s too much, it has to be a half day max.”

We give lip service to the idea of complexity, but we certainly don’t behave like we appreciate it. If a given issue is complex, then it requires a deep dive and sustained attention. But if every issue brief is two pages, it’s hard to tell the difference between those that should be two pages and those that should be a book.

At which point I’m sure someone will tell me to be practical. Executives don’t have time to explore issues for 2.5 days or read long briefings. And of course I agree, but it’s exactly the problem*.

And here’s the result: instead of deep dives, we do long drags. It’s when you find a four-month project creeping into 18-month territory, and one more month doesn’t seem like much of a big deal. It’s when you realize that you have to scramble to bring stakeholders to the table that you hadn’t originally identified. It’s when you’re sending just one more briefing up, or having just one more meeting, to work out an issue with a proposal. It’s why everyone is comfortable with the oxymoronic word “reconfirm.”

This is very different from, say, agile software development. In that case, the complexity and constant iteration is scoped, planned, and designed for. But for these long drags you underestimate the amount of time and effort required, and uncover and resolve issues as much by accident as by system.

Complexity is a defining feature of the digital era, and we are not adjusting our governance structures to manage it. Just the opposite, in some ways: as authority and information became distributed and hyperconnected, the pressure towards centralized decision-making and message control became stronger. Governments have grown by orders of magnitude since we developed our conceptions of accountability, and we’ve increasingly realized that the sharp lines between issue areas are more porous than we once thought, making them effectively much broader. If your portfolio is health, it’s also education, social security, and the economy.
What hasn’t grown is the time, tools, or resources to deal with boundaryless problems with many stakeholders: everything from the most intractable policy problems to building user-centred digital services. You need deep dives, the time to do things right, and people empowered to test ideas and work across organizational lines.
To do it, governments will need to either free up senior leadership from day-to-day issues, or push authority further down the chain**. If they aren’t willing to - which is, admittedly, a reasonable position - then the appropriate conclusion is to revise expectations downwards: for the ability to solve wicked problems, collaborate between jurisdictions, or rework internal systems to create more coherent public-facing services.
I may be naive for thinking that this system can be changed, but we’re all naive if we think we can get better at dealing with complex problems if it stays the same.



*Every project lists senior executive commitment as a success factor, which is a resource that doesn't scale up with complexity. At which point it's worth noting that executives tend to overestimate the success of corporate initiatives, and underestimate the scope of organizational problems; executives are already spread more thinly than they think.
**I'd consider the Codefest events that brought internal and external communities together to develop the Web Experience Toolkit to be a shining example of both designing an event to make progress on complex work and of working-level employees having the authority to lead it.

Policy Shapers vs Policy Makers

Friday, April 7, 2017

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

The Clerk of the Privy Council spoke at the Policy Community Conference a couple of weeks ago. He made an interesting distinction between policy makers and policy shapers that I thought bore repeating.

Public servants aren't policy makers, they are policy shapers. If you want the privilege of choosing than run for office or work politically. In short, to govern is to choose.

If you want to shape, advise, influence, and steward, then the public service is the place for you.

This was particularly poignant given I've spent the last few months advancing a program proposal that -- while evidence-based and viable -- was ultimately not chosen by the elected government.