Tag Archives: public service

Public Service Reform: The Myth of Failure

2 Replies

I’m getting ready to give my talk at the Public Service’s Executive Summit conference – a group that includes the CIO’s of all the federal ministries and other IT people engaged in service delivery. Although many of the themes will be reminiscent of the APEX talk I hope to blog on some of the newer themes later.

Leading up to the talk I’ve been reflecting on this notion of failure in the public service.

Frequently, when discussing the issue of public service sector reform, public officials seem to be of two minds. On the one hand I hear some advocates – let’s call them the entrepreneurs – argue that the public service needs to be more forgiving of risk and support innovation. Others – let’s call them the caretakers – regularly remind me of how government is different from the private sector. That unlike the private sector, which can take risks and fail, the government cannot. The consequence of the ‘caretakers’ predominance is everywhere: it explains why the government is slow to adopt new technologies and ideas, as it prefers to observe others figure them out and then move cautiously.
Myself, I’m a big supporter of the entrepreneurs – if you can’t fail then you can’t experiment, and while that means it’s hard to make things worse, it also makes it very, very difficult to make things better.

More importantly however, I find the latter statement interesting…  and also troublingly evasive and unrealistic.

It is true that many government services are essential – and the costs of a failure (however defined) can be high. But this is not true of all government services. All across government there is latitude for experimentation and new ideas – and indeed it takes place – but slowly.

More importantly however, the caretakers statement ignores reality. Government programs – like those of many organization – fail on a regular basis. Ask anyone whose worked in the public service, they’ll tell you of programs that never launched, got killed because they didn’t work, or that are continuing to operate and receive funding, but essentially don’t work (indeed, entire ministries come to mind…).

These can even include critical services. Aboriginal policy in Canada has been broadly “failing” for over two decades – and the consequences have been pretty atrocious. If one thought there was a zero risk threshold issue, I might have through this was it. While I believe that ‘caretakers’ are genuinely concerned that new technologies and approaches may increase the risk of failure there may be another, more troubling reason. ‘Caretakers’ may rightly fear that new technologies and structures because they create new types of failure. Failures that the bureaucracy is not practiced in the art of discretely hiding.

This is a powerful motivating factor. Failure, particularly failures that become public can at best cause Ministers great discomfort, discomfort they are likely to recreate for those who work for them. It’s an understandable and real concern. But in many instances the status quo of service and policy can also be dangerous. Experimentation – and as a result risk taking – is the only path I can see out.

Don't Ban Facebook – Op-ed in today's G&M

5 Replies

You can download the op-ed here.

The Globe and Mail published an op-ed I wrote today on why the government shouldn’t ban face book, but hire it.

The point is that Web 2.0 technologies, properly used, can improve communication and coordination across large organizations and communities. If the government must ban Facebook then it should also hire it to provide a similar service across its various ministries. If not it risks sending a strong message that it wants its employees to stay in your little box.

One thing I didn’t get into in the op-ed is the message this action sends to prospective (younger) employees. Such a ban is a great example of how the government sees its role as manager. Essential the public service is telling its employees “we don’t trust that you will do your job and will waste your (and our) time doing (what we think are) frivolous things. Who wants to work in an environment where there own boss doesn’t trust them? Does that sound like a learning environment? Does it sound like a fun environment?

Probably not.

—–

Facebook Revisited

DAVID EAVES
SPECIAL TO GLOBE AND MAIL
MAY 17, 2007 AT 12:38 AM EDT

Today’s federal and provincial governments talk a good game about public-service renewal, reducing hierarchy, and improving inter-ministry co-operation. But actions speak louder than words, and our bureaucracies’ instincts for secrecy and control still dominate their culture and frame their understanding of technology.

Last week, these instincts revealed themselves again when several public-service bureaucracies — including Parliament Hill and the Ontario Public Service — banned access to Facebook.

To public-service executives, Facebook may appear to be little more than a silly distraction. But it needn’t be. Indeed, it could be the very opposite. These technology platforms increasingly serve as a common space, even a community, a place where public servants could connect, exchange ideas and update one another on their work. Currently, the public service has a different way of achieving those goals: It’s called meetings, or worse, e-mail. Sadly, as anyone who works in a large organizations knows, those two activities can quickly consume a day, pulling one away from actual work. Facebook may “waste time” but it pales in comparison to the time spent in redundant meetings and answering a never-ending stream of e-mails.

An inspired public service shouldn’t ban Facebook, it should hire it.

A government-run Facebook, one that allowed public servants to list their interests, current area of work, past experiences, contact information and current status, would be indispensable. It would allow public servants across ministries to search out and engage counterparts with specialized knowledge, relevant interests or similar responsibilities. Moreover, it would allow public servants to set up networks, where people from different departments, but working on a similar issue, could keep one another abreast of their work.

In contrast, today’s public servants often find themselves unaware of, and unable to connect with, colleagues in other ministries or other levels of government who work on similar issues. This is not because their masters don’t want them to connect (although this is sometimes the case) but because they lack the technology to identify one another. As a result, public servants drafting policy on interconnected issues — such as the Environment Canada employee working on riverbed erosion and the Fisheries and Oceans employee working on spawning salmon — may not even know the other exists.

One goal of public-sector renewal is to enable better co-operation. Ian Green, the Public Policy Forum chair of Public Service
Governance noted in an on-line Globe and Mail commentary (Ensuring Our Public Service Is A Force For Good In The Lives Of Canadians — May 8) that governments face “increasingly complex and cross-cutting issues … such as environmental and health policy.” If improving co-ordination and the flow of information within and across government ministries is a central challenge, then Facebook isn’t a distraction, it’s an opportunity.

Better still, implementing such a project would be cheap and simple. After all, the computer code that runs Facebook has already been written. More importantly, it works, and, as the government is all too aware, government employees like using it. Why not ask Facebook to create a government version? No expensive scaling or customization would be required. More importantly, by government-IT standards, it would be inexpensive.

It would certainly be an improvement over current government online directories. Anyone familiar with the federal government’s Electronic Directory Services (GEDS) knows it cannot conduct searches based on interests, knowledge or experience. Indeed, searches are only permissible by name, title, telephone and department. Ironically, if you knew any of that information, you probably wouldn’t need the search engine to begin with.

Retired public servants still talk of a time when ministries were smaller, located within walking distance of one another, and where everyone knew everyone else. In their day — 60 years ago — inter-ministerial problems were solved over lunch and coffee in a shared cafeteria or local restaurant. Properly embraced, technologies like Facebook offer an opportunity to recapture the strengths of this era.

By facilitating communication, collaboration and a sense of community, the public services of Canada may discover what their
employees already know: Tools like Facebook are the new cafeterias, where challenges are resolved, colleagues are kept up to date, and inter-ministerial co-operation takes place. Sure, ban Facebook if you must. But also hire it. The job of the public services will be easier and Canadians interests will be more effectively served.

David Eaves is a frequent speaker and consultant on public policy and negotiation. He recently spoke at the Association of Professional Executives conference on Public Service Renewal.