Showing posts with label administration. Show all posts
Showing posts with label administration. Show all posts

Friday, January 20, 2017

The Problem of Administrivia

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

I have often said to my public sector colleagues that We have seen the enemy and it is us

By that I simply mean, more often than not we get in our own way. Someone wants to try something innovative but there's a myriad of reasons why they can't: policies, directives, compliance, because it flies in the face of the way we've always done things. But everyone knows we wrote the rules, we enforce the rules, and we reinforce the culture.

It's easy to say its complicated, and there's a lot of moving pieces 

One could highlight that often whenever someone looks for the flexibility they think they need to try something new they are denied permission to do so. That those who would grant them license see themselves as gatekeepers that enforce existing rules rather than enablers looking to forge new, better -- 21st century -- ones.

And so we continue to ask for permission rather than beg forgiveness

But this surely this is madness. Bureaucrats assembled, huddled in a boardroom somewhere, parsing sentences into the myriad of its different possible meanings. Expending scarce resources through repetitive discussions, constant email traffic, and the endless 'what ifs', 'ands', and 'buts' about what is possible and what is not.

All the while Rome burns

A large part of the "innovation problem" in government is quite simply the degree to which public servants prioritize their organizations' own internal machinations over creating public value for Canadians.

In my old unit we referred to this as administrivia (you may know it as 'feeding the beast') and our rule of thumb was to avoid it whenever possible. We realized that the organization often doesn't understand the true opportunity cost it pays for administrivia.

The work is often low value that is either speculative, over-engineered, for 'back pocket' products, and/or faux deadlined. It produces not only a burden on individual civil servants but can also clog up information channels. In short, it's a tax on productivity, a barrier to innovation, and it undermines civil servants' ability to create public value.

But it's also sexy

It creates a false sense of urgency, importance, and sometimes even achievement. It can give you an immediate goal or deliverable that is achievable in the short term. It creates an incentive system to prioritize tactics (the next deliverable) over the strategy (the long game). Administrivia creates a strong incentive to shorten your shadow of the future, ignore the horizon and focus inward. It's easy to be enthralled, especially if you have trouble connecting your work to more tangible outcomes out there in the wild.

The allure of administrivia is dangerous and I fear that it has supplanted far too much meaningful work across the system. How much time does the average public spend focused on the internal machinations of their own department?

Technology isn't helping

We wrongly prioritize electronic communication, creating confusion and leaving too much room for interpretation. It amplifies the adminstivia tax. Instant communication creates false urgency. Email can reinforce or level hierarchy depending on how it used.. The spirit and tone with which someone writes something writes isn't necessarily the same with which it is read.

If there is anything I've learned about electronic communication, it is that it always creates more ambiguity than face-to-face communications. This is not a new lesson, but those who don't learn it and take it to heart are doomed to repeated it. My advice is pick up the phone, schedule a meeting, look your colleague in the eye and find common ground together.

It's one way to cut the adminstrivia - the other is taking a step back and looking at the bigger picture.

Wednesday, June 24, 2015

Slack


by Kent Aitken RSS / cpsrenewalFacebook / cpsrenewalLinkedIn / Kent Aitkentwitter / kentdaitkengovloop / KentAitken



This isn't a thorough exploration of slack's role in organizations, just a few things that were on my mind recently. Would love to hear your thoughts.


But first, an aside


I've been living in Ottawa for seven years, while most of my family lives on the east coast. My mom's side of my family usually has a mid-summer and a Christmas get-together each year, and I haven't made it back east for either in years. It eats at me. It'd be worth my while, but every year I run quickly into the limits of my vacation days and travel budget, especially when it's a given that I'll be going back to PEI to visit my dad, and Newfoundland to visit my farthest-flung brother.


This has been a powerful dynamic in my life for the last half-decade. Every time I book a trip I'm both excited and conflicted, aware that I'm making tradeoffs, aware that some people - that I think very highly of - will go unvisited in a given year.


Collaboration and relationship-building (or, policy and communications, and never the twain shall meet)


To segue somewhat: last week a speaker was asking where the communications people were at a public administration conference. Some people pointed to general tension or misunderstanding between the two worlds, and I threw in a more functional reason, analogous to the above story. We are, as they say, in "an era of fiscal restraint," with tight scrutiny on travel, conference, and training budgets. We all understand that the lines between fields such as policy and communications are blurring, that there are inter-dependencies, and that collaboration is incredibly important. But for an given practitioner, staying informed about their field is still the primary concern, and they're naturally going to maintain relationships with their core community first.

Economically, it's like an artificial cultural ceiling on the supply and demand of public servant relationship-building and collaboration. The question is whether that ceiling is appropriately set in pursuit of broader system goals.

It has become en vogue to ask about communities and conferences, "Who else needs to be here? Who else should we be talking to?" Which is a good question, but if you can't get to their communities, and your community is a few bullets down the priority list for them, it's impractical to expect anyone to bridge that gap.

Creating slack, in this case, would be treating relationship-building with core communities as a given - creating room on the margins to better understand the peripheral players that influence our portfolios.


Innovation


Google's 20% innovation time doesn't work for everyone. We were all excited about it five years ago, but if it doesn't square with culture, if innovation isn't actually a core goal (which is often appropriate), or if your work doesn't progress through that style of idea generation, it's a silver bullet with no gun and no werewolves.

Since, we've matured in our debate about free time and innovation. Is it slack in the system that generates innovation? Or pressure? It's hard to say, and the only true answer is probably "it depends". However, a recent research paper adds an interesting thesis to the debate (h/t)The short version of the paper: school breaks lead to a sharp increase in Kickstarter ideas being launched and funded because it creates time for mundane tasks.

Their conclusion is that slack time does indeed lead to innovation, but not for the reasons we thought. Instead of allowing creativity and the generation of ideas, slack time allows people the time to execute and move their ideas forward.

However, many public administrators opt for the pressure approach, or are limited to it as an option. In an age of "do better with less", I've seen a worrying trend of people being forced to rush the "better." These are ideas that might work, given the time to do it right. But when people are asked to Innovate right now!pressure gets the better of rigour.


Slack


Slack, as it's traditionally regarded, is expensive. However, it seems probable that it's often worth it, albeit in hard-to-measure ways. If that's true, we have two options: create slack, or re-define activities like relationship-building, idea-sharing, focus-grouping, assumption-testing, and the like — those intangibles often first in line for the chopping block — as part of the job description, as part of the ongoing pressure.