Friday, July 24, 2015

Redefining innovation within the public service

The Canberra GovCamp dialogue was held on Wednesday, one of a series of events across Australia, both part of Public Sector Innovation Month and a lead-in to a full GovCamp in November.

Attendees included both current and former public servants, academics and private sector interested parties - all interested in discussing how to foster and focus public sector innovation towards material improvements and outcomes.

The half-day event had an interesting panel discussion on what is (and isn't) innovation, and the factors that support or hinder it's use as a tool to improve governance and service delivery outcomes, with a number of interesting points raised.

It also featured a Conversation Cafe mapping the room's views on what triggers public sector innovation and what type of innovation occurs, as well as views on the value of public sector innovation - which will be mapped together with the results from the other GovCamp Dialogues across Australia and should prove interesting reading. I tweeted the Canberra responses on Wednesday as below.


Following this, the GovCamp Dialogue gave participants a taste of how full GovCamps tend to operate, holding three participant-driven sessions where those attending could nominate topics and discuss each for twenty minutes in various groups.

This was a useful introduction to those new to GovCamps, and participants took to it with gusto.

For someone who's been around this scene for awhile, the event was a good opportunity to refresh my views on public sector innovation, and the biggest idea of the day for me was outlined by Mick Chisnall, formerly the Director of the ACT government's Government Information Office.

Mick suggested that government needed to treat innovation more as experimentation than as a project.

While I'd not thought of it specifically in this way, I believe he's on the money.

Projects in government have clearly defined scopes, resources, timeframes and steps in order to achieved the desired outcomes and don't generally support failure within the fabric of the process.

Innovation, on the other hand, is a process involving exploration and experimentation. While it can involve a defined scope and desired outcomes, often the path to success is littered with learning experiences - what might be otherwise termed 'failures'.

Innovation often involves a large component of rapid and iterative testing of assumptions and exploration of different avenues, with the data collected from each attempt helping to inform and focus the path towards the desired outcomes.

As Thomas Edison said to American Magazine in 1921:
"After we had conducted thousands of experiments on a certain project without solving the problem, one of my associates, after we had conducted the crowning experiment and it had proved a failure, expressed discouragement and disgust over our having failed to find out anything. I cheerily assured him that we had learned something. For we had learned for a certainty that the thing couldn't be done that way, and that we would have to try some other way."
This innovation process is hard to foster within today's project methodologies. Prince II, PMBoK and others of their ilk all exist to systemise projects to minimise the risk of failure and efficiently manage resources towards the delivery of a clearly defined objective.

Few support an iterative failure-led approach to success where many avenues must be explored to identify those that may be productive.

Indeed, a formal review of innovation within the APS in 2013 found that senior managers were very reluctant to discuss their failures at all, To quote from the blog post linked,
Innovations can fail and information on why this has occurred is highly important. However, there was reluctance amongst respondents to provide information on unsuccessful innovations, with around 80% survey participants stating that they “did not have a least successful innovation”.

So how do we marry innovation processes with project methodologies?

My thought is that we provide some tolerance for both the known and unknown unknowns, supporting feasibility studies and Agile-based methodologies within a project framework. We should also follow more start-up thinking around 'minimum viable product', continuous A/B testing and improvement and break larger projects into smaller goals, achievable in a few months.

We also need to foster a rethink of the concept of failure in the public service. A failure is a situation where something didn't work AND we learnt nothing at all. Even learning that a given approach doesn't work is valuable information that can support further effort towards a solution.

So long as a 'failure' allows us to redefine the scope to exclude certain paths, and data is collected and shared to understand why an approach or solution didn't work, it is not a failure.

This may require some reshaping of Project Offices and management of the expectations of public sector decision-makers, Ministers and citizens, but it would be well-worth it to support a more innovative public sector.

In an age of wicked problems we need to foster creative thinking.

This can only happen if we ensure that innovation is treated appropriately as experimental and exploratory work, rather than shoehorned into existing project management processes with little tolerance for 'failure'.

Read full post...

Thursday, July 23, 2015

How important is geographic location for a digitalised public sector workforce?

Canberra is full of large buildings full of public servants, all working together on a daily basis to serve the needs of government and the community.

While some can work remotely, from their home or on the road, there's still significant barriers to teleworking in the public service.

Whether it's the need to install a secure connection in a person's home, check the OH&S layout of their kitchens or simply a reluctance on the part of managers to allow staff to work outside their sight.

While companies like Cisco have had a hotdesking approach for many years, with staff able to go into any office, sit at any desk and start working with full access to their digital files and phone, only a few government agencies have recently made it possible to hotdesk within their own environment.

There's no clear pathway for any Australian Public Servant to sit at any desk in any government office and work effectively without complex and time-consuming IT steps (if it's possible at all).

There's a large and growing productivity cost to this kind of IT inflexibility.

From the huge ICT costs  in moving workers and changing system access that's involved when governments rip agencies apart and put them back together in different configurations during Machinery of Government changes, to the lost opportunities to employ the best person for a job because they don't live - and won't move - to a specific geographic region, governments are increasingly being shoehorned into a lose-lose situation where their technical environments damage their ability to deliver outcomes.

I've had significant experience in teleworking. In the late-90s, while living in Sydney, I was also lead designer on a commercial game developed by a team in Adelaide, that I met in person a total of once.

When working for a start-up at the turn of the century, nominally in an office in Sydney, I also regularly travelled and worked from the UK, Singapore and the US.

Into the 2000s I wrote books and articles for a range of publications from my home, my local playground (having young kids), or pretty much any location where I had access to technology and close proximity to an internet connection.

After moving to Canberra I cofounded an oil exploration company with someone who soon moved to Sydney. We established a board with Directors based across Australia and in Asia, and employed a team in Texas to explore an oil field in the US, with almost all of the company's business conducted online.

However when I look at roles in government today (particularly some of the interesting digital roles that have popped up in recent times), they still require an individual to be physically situated near a specific office. Some even offer to help pay people to relocate their entire lives to be closer to these jobs. There's a little more leeway for senior executives, who might get assisted accommodation and travel to allow them to work a city away from where they live.

Sure there's still many people normalised into working in the same office with the same people every day. However there's a growing number who've learnt the art of working anywhere, building and managing remote teams and achieving bodacious goals.

Certainly there's roles that require a physical presence - face-to-face customer service (when not delivered digitally over screens), inspectors and jobs that involve moving physical goods from place to place (until robots and remotely controlled drones take over).

However I'm hard pressed to think of many other roles in government that actually require staff to be physically present in the same office all the time. Policy development, program development and delivery, grant management, communications, IT, HR, Finance, phone and online customer service, briefing Ministers and stakeholder engagement - all these roles could be delivered effectively remotely with appropriate technology, security and mindsets.

In some of these roles there may be some need to physically meet one's colleagues, customers and stakeholders for some of the time, but none require workers to all live in one geographic location, to work in one office, often in one big room like battery hens.

There's also many roles where mobility is a distinct advantage - anyone working on a whole-of-government taskforce, or who regularly meets stakeholders, moves between offices for meetings, or has a distributed team. These people would gain enormously from being able to work wherever they happen to be.

So how important is geographic location for a digitalised public sector workforce?

Objectively it's no longer important at all.

Read full post...

Tuesday, July 21, 2015

How does government manage the consequences of an imbalance in speed of transparency & speed of accountability?

One of the emerging challenges for governments in the online age is managing the discrepancy between the speed of transparency and the speed of accountability.

With digitalisation and the internet, the speed at which government information is made public is becoming faster, with it being easier to collect, aggregate and publish information and data in near or even real-time.

We see this particularly in public transit data, where many cities around the world now publish real-time data on the location and load of their buses, trains and trams, and in the health industry where a number of states have begun offering near real-time data on the congestion in emergency waiting rooms.

We're also seeing similar near real-time reporting on river levels, dams, traffic congestion and closures, and estimated real-time reports on everything from population to national debt levels.

This trend is expanding, with the Sense-T network in Tasmania pioneering an economy-wide sensor network and data resource. Similarly the Department of Finance in Canberra is working on a system to provide real-time budget information on government expenditure down to every $500 for internal management and public transparency purposes.

This trend is a leap forward in government transparency, providing citizens, bureaucrats and politicians with far greater visibility on how our governance systems are performing and far more capability to identify trends or patterns quickly.

We're seeing a similar transparency event at the moment, with the expenses scandal enfolding the Speaker of the House of Representatives, Bronwyn Bishop, related to her use of a helicopter and several charter flights to attend political fund-raising events.

What this event has also highlighted is that while Australia's governance systems are increasing the speed of transparency, our capability to apply that information to accountable decision-making isn't consistently accelerating at the same rate.

In other words, while we increasingly can obtain the information needed for rapid decision-making, the entrenched processes and methods for decision-making in government are lagging far behind.

We see this in the failure rate of IT projects, which can drag on for years after it's clear they will fail, when laws fail to work as they should and it takes months or years to amend them, when the public has judged a politician's actions, but parliament can take no formal action for months due to being out of session.

Of course many sound reasons can and are given by bureaucrats and politicians as to why decisions need to take lots of time.

Decision-makers from the pre-internet world will say that they need to ensure they have all the necessary data, have digested it, reflected on it, considered alternatives and consequences, consulted widely and only then are able to tweak or change a decision.

This is a fair position with many defensible qualities - it reflects the world in which these people grew up, when decision-making could be undertaken leisurely while the world waited.

However both management theory and the behaviour of our communities have changed.

Start-ups grow and become huge companies based on their ability to make decisions rapidly. They are continuously experimenting and testing new approaches to 'tweak' their businesses for greater success. This is underpinned by streams of real-time data which show the consequences of each experimental change, allowing the organisations to adjust their approach in very short time-frames, minimising their potential losses from sub-optimal decisions.

The community equally reacts very quickly to evidence of poor decisions and bad outcomes, with the internet, particularly social media, fueling this trend.

While this doesn't mean the community is consistently in the right on these matters, it does require decision-makers to respond and address concerns far more rapidly than they've had to in the past - 'holding the line' or 'depriving an issue of oxygen' are no longer effective strategies for delaying decision-making into the leisurely timeframes that older decision-makers grew up with.

This issue in the disparate speed of transparency (data release) and accountability (clear and unequivocal response) is growing as more organisations release more data and more of the public is collecting, collating and releasing data from their interactions with organisations.

The imbalance is fast becoming a critical challenge for governments to manage and could lead to some very ugly consequences if politicians and agencies don't rethink their roles and update their approaches.

Of course governments could attempt to sit back and 'tough it out', trying to hold their line against the increasing speed of transparency and accountability. In my view this would result in the worst possible result in the long-term, with increasingly frustrated citizens resorting to more and more active means to have government take accountability for their decisions in the timeframes that citizens regard as appropriate.

My hope is that government can reinvent itself, drawing on both internal and external capabilities and expertise to find a path that matches fast transparency with appropriately fast accountability.

I'd like to see governments challenge themselves to test all of their historic assumptions and approaches - reconsidering how they develop policy, how they consult, how they legislate and how they engage and inform the community, in order to address a world where 'outsiders' (non-public servants) are identifying issues and worrying trends at an accelerated rate.

Perhaps we need a radical new ways to develop and enforce laws, that provide scope for experimentation within legislation for agencies to reinterpret the letter of a law in order to fulfill it's desired outcomes and spirit.

Perhaps we need continuous online consulting processes, supported by traditional face-to-face and phone/mail surveys, which allow government to monitor and understand sentiment throughout policy development and implementation and allow a 'board' of citizens to oversee and adjust programs to maximise their effectiveness over time.

Perhaps we need mechanisms for citizens to put forward policies and legislation for parliament to consider, tools that allow citizens to recall politicians for re-election or a citizen-led approach to determining what entitlements are legitimate for politicians and what they should be paid, with penalties and appropriate recourse for citizens to sack representatives who fail to uphold the values the community expects at a far greater speed than the current election cycle.

There's sure to be many other ideas and mechanisms which may help deliver a stable and sustainable democratic state in the digital age of high-speed transparency and accountability - we just need governments to start experimenting - with citizens, not on them - to discover which work best.

Read full post...

Friday, July 17, 2015

Have you visited data.gov.au lately? We're beginning to witness the 'Open Data Multiplier'

PS News has a great report on the growth of data.gov.au - linking to a report on the Department of Finance's blog which indicates the site added 100 datasets in June.

The site has also upgraded to provide more data visualisation capability for users, as well as a responsive template for improved mobile access.

Most interesting was the high use of the service over GovHack, with 4,755 user sessions by 2,618 users. The most popular datasets included intellectual property government open data 2015, ABC Local online photo stories 2009-2014 and sample household electricity time of use data.

I've written about some of the interesting Govhack prototypes over at The Mandarin in the article, GovHack 2015: a wildly successful idea that keeps spawning more, where I also wrote about how participation is a useful way for agencies to test and support 'edge' innovation without committing scarce personnel and funds.

From what I've been hearing over the weeks since Govhack we're reached something of a tipping point with open data in Australia, with governments beginning to seriously recognise the value of sharing data in this manner.

Those benefits are not just external to agencies, such as transparency, economic growth or community engagement, but also internal.

Internal open data benefits to government include improving agency decision-making (through greater awareness and access to collected data), improved data quality and fostering innovation and creativity.

As a result of reaching the tipping point, I expect to see continuing significant growth in the quantity and quality of open data available across Australia, as well as more targeted and useful data as agencies become more sophisticated in their data release (as I've outlined previously in my Open Data Generations Roadmap)

This will stimulate what I've termed the Open Data Multiplier.

As with the network effect, where the value of a network increases exponentially with the number of participants (think about telephones or the internet), the Open Data Multiplier means that each additional dataset released for reuse creates a growing number of possibilities to combine it with existing data, or use it on its own, to prompt even more interesting and diverse innovations.

However the Open Data Multiplier only operates when the community and agencies are engaged with open data. Without this community both inside and outside of the public sector, data sits 'on the shelf', generating no value at all.

This is where volunteer-run events like GovHack are valuable for fostering a positive civic hacking culture.

Agencies also have a role in fostering both an internal and external culture of data-based innovation through supporting GovHack and similar events, and running their own separate challenges on agency-specific topics (as Transport for NSW and Public Transport Victoria have done).

The internal benefits don't stop at data either. The same challenge model, once adopted by government, can be used more broadly for policy and service design and in finding diverse solutions for government problems - as has been successful in Challenge.gov and is used by VicHealth and thre ACT government.

Indeed I ran a similar service design challenge for the Victorian Government at GovHack, the first exploration of such an approach at that event. The learnings will help guide Victoria's government in identifying when to use similar approaches and in designing and running future challenges.

All of this follows on from opening up government data, creating a more permissive and experimental sandpit for innovation and sharing.

And it starts with a visit to data.gov.au - have you visited lately?

Read full post...

Wednesday, July 15, 2015

Where have all the senior public servants disappeared to?

I've been attending a number of networking and other business events in the last month across Canberra, and have noticed that amongst all the CEOs, CTOs, Financial Directors and similar, that there's been no senior public servants in attendance.

While there was a good turn-out of public servants at one event I've attended, the Life beyond Lanyards launch last week, these were mid-level or lower.

So I'm beginning to wonder about how much actual cross-fertilization is going on between senior public servants and the private sector, how much senior public servants are getting 'out there' to meet and interact meaningfully with business owners.

Of course this is one person's impression over a short time period at a limited number of events, but when I think back over the last ten years, it's rare for senior public servants to spend much time with their colleagues in the corporate sector.

Definitely there's arranged events, speaking at conferences, attending lunch seminars and the like, but as soon as their part is done, senior public servants tend to race back to the office rather than shoot the breeze with their private sector equivalents, to discuss broader issues and topics.

Of course they have good reason - senior public servants are incredibly busy meeting their commitments to Ministers, managing their organisations and keeping work flowing through approvals and initiating work programs.

The culture of Australia's public service, for the most part, involves dedicated and hard work in service of the government of the day, in order to serve the citizens of the country.

However I think that sometimes working on their business is as important as working in their business. This is something that good corporate executives and small business people alike learn - that networking to form relationships, that consulting and learning from colleagues across other industries, is a key to improving their own organisations and achieving success.

This is a key ingredient in innovation - associating with people from many walks of life, rather than simply with one's one public sector colleagues.

Successive Australian governments have recognised the value of this cross-fertilisation, and the APS has also fostered bringing private sector people into senior government roles as a way to foster a broadening of attitudes, rather than the 'groupthink' that can emerge from any group of people with similar backgrounds, career paths, values and experience.

This has had mixed success in my view, many people with extensive private sector but without public sector experience don't last that long in SES roles, due to the level of difference in approach and views.

The current fledgling program of seconding senior public servants into the private sector is another attempt at achieving the same end - bringing a broader set of viewpoints and experience (as well as larger and more complex networks) back into the public sector, thereby improving the effectiveness of policy design and delivery and fostering innovation.

I hope this works well - but I don't believe either of the above are the full solution to this wicked problem.

What we need is for senior public servants to be mandated and supported to recognise that building deep relationships across and understanding of the sectors they serve is a valid and important part of dedicated public service.

This means delegating more tasks and approval authority downwards to leave senior public servants with time, and the mandate, to spend less time checking grammar and more time associating with groups and individuals outside of government.

Who knows, it could even help foster the external credibility of government.

Read full post...

Bookmark and Share