Tuesday, November 15, 2016

Asking 'what should be the limits on how public servants engage in social media' is the wrong question

The Australian Public Service Commission (APSC) has just released a consultation paper asking for feedback regarding how public servants may be able to 'Make Public Comment' specifically focused on social media.

It's great to see the APSC consulting on this area. It is subject to rapid change, both in the nature of the approaches and tools available for public servants to comment online, and in regards the evolution of thinking and expectations within the public service itself.

For example, Gov 2.0 and the current follow-on push for digital transformation has continued to attract new groups of potential employees and partners to the APS. These are groups with their own established (generally active, transparent and outspoken) approaches to online engagement - creating challenges for existing public sector hierarchies in both recruitment and management of these cohorts and acculturalising them to current APS norms.

Equally the blurring of the lines between private and professional continues to grow. With government policy now essentially touching on every aspect of life, existing public servants can feel constrained and muted by current requirements to not comment negatively on any policy area.

This is whether it be a public servant/parent dealing with schooling challenges, a public servant/carer dealing with NDIS challenges, a public servant/driver dealing with road infrastructure challenges, a public servant/patient dealing with health challenges, or a public servant/former immigrant dealing with family unification challenges. In all of these cases, even if their career is in a totally unrelated area of the public service, it is unwise for them to share even privately via their social media channels comments critical of the policies which are impacting their lives in a real and significant manner - just in case their public service friends report them and their public service bosses decide to define their comments as less than appropriate.

At the same time with the increasing normalisation of social media as the primary 'town square' for civil discussions (though not always so 'civil'), younger people, former APS staff (such as myself) and others who might at some point work in or to governments, are more enabled and likely to debate or share contentious political and policy issues via social networks without full consideration of the likely views of older-fashioned agency management and the impact on potential employment or contracts.

Similar to the lament of police and other security services ten years ago, who found it increasingly hard to hire individuals able to conduct important undercover work, due to the widespread adoption of social media (forcing a shift to profile cleansing from profile hiding), it's rare for any young person to not have an active social presence online, potentially touching on a range of politically sensitive topics - if not crossing professional lines with beach and party shots.

Similar to the debate over whether children should be seen and not heard, I've witnessed a number of older senior APS managers express their ongoing views that public servants should neither be seen nor heard in public debate - despite this going further than even the existing guidance for how public servants may engage in public discourse.

Moving on to the current consultation process, there's a few assumptions in the approach which could significant impact the outcomes.

Benefits vs Risks

Firstly the entire consultation, while nominally appearing to aim to be neutral, overwhelmingly concentrates on the negative impacts of public comments by public servants.

The approach largely overlooks the benefits of having an engaged workforce, interested and knowledgeable about a policy area, able to engage effectively in online debates - providing facts, busting myths and communicating compassion and concern for the communities impacted by policy decisions.

Some organisations outside the public sector have realised the value of staff as advocates for an organisation - that every staff member is connected to hundreds of peers, friends and family members who are potential customers or clients. However it seems only rare public sector organisations have recognised the same potential.

Imagine the impact of having 4,000 Health Department staff sharing the latest PBS drug additions, or carefully explaining government policy to communities who haven't been on the same journey to recognise why alternate approaches look fine on the surface, but have significant long-term negative impacts.

Imagine having over 30,000 Human Services staff sharing the latest information on changes to welfare programs, the release of new apps, or helping parents considering separation to understand their potential financial obligations to their children in a divorce.

The upside of having staff engaging socially is immense where staff are provided with the right access to tools, advice and potentially training - more effective than spending millions on 'shouting at' communities via traditional media, or even online communication campaigns.

However taking this positive approach to staff social engagement relies on a critical factor that increasingly appears in short supply in the public service - trust. Senior executives in the public sector have long been shown to be significantly disconnected from their staff - with regular APSC studies showing enormous differences in perceptions as to how well senior managers communicate and with work satisfaction levels.

With rolling pay disputes, increasingly employee concerns around the casualisation of workforces, fewer opportunities for staff to progress and ongoing budget cuts, there's a range of factors already impacting on trust relations within agencies - a largely negatively focused social media policy, designed around preventing bad behaviour rather than enabling and supporting good behaviour, is merely another straw on the back of the increasingly concerned camel.

Policy for the future of the APS

Looking further at the consultation, while it doesn't specifically exclude any group from consulting, the placement and approach strongly favours current APS staff, or the hyper-interested (such as myself).

This means the consultation will largely be biased around current staff and their current expectations, having little consideration of potential staff who increasingly consider their ability to engage freely on social media as a right rather than a privilege restricted by an employer.

This could lead to amended guidance on social media engagement that progressively discourage good people from potentially considering APS roles, particularly in emerging areas related to digital.

Given social media comments are forever, there's an entire group of young, university educated, visionary and innovative people who, under strict APS social comment policies, may never be eligible for APS employment based on their past personal views 'poisoning' their ability to be impartial.

The questions for consideration included within the consultation are quite broad and I've covered each below with my views.

1. Should APS employees be prevented from making public comment on all political issues? Should there be different rules for different groups of APS employees?

Even Ministers only focus on their own portfolio policies and challenges, so it's highly impractical to expect public servants at any level to be sufficiently across all political issues to be able to avoid commentary on topics that affect them personally, but may (to a greater or lessor extent) also touch on significant political issues.

Equally with political policies now touching on most areas of life, even indirectly, there's little that a public servant could say that could not be deemed a public comment on a particular issue, even if via a slightly drawn bow by a hostile outside party.

The impact of this would be similar to the impact of the current APSC policy, to cause many public servants to choose not to engage in public debate at all. Given that public servants are generally well-educated and well-informed and trained to form opinions based on evidence, this presents a significant loss to public debate within Australia and the exclusion of expertise that could otherwise shift and shape national views.

I'm aware of experts who have been effectively silenced in their areas of expertise due to a government engagement for a different set of their skills. This weakens Australia's democracy, rather than protects it.

While it may seem prudent to at minimum limit the scope for public servants to engage publicly at least within their own policy area, the area in which they have greatest experience and expertise, this is also counter-intuitive.

I do believe that public servants should strive to present the positives of current policy positions and effectively communicate set government to the public including, if they so choose, via their own social media accounts - even when respectfully making it clear that their views might differ from the government's, but that their role is to carry out the policies irregardless of personal opinion.

However in areas where policies are under debate, not yet confirmed by government or otherwise not set, public servants should have the right to choose to engage in the public debate and express their views in a respectful manner. Due to their experience in their own policies areas, it would be expected that their views would be well-informed and therefore support the public debate.

In essence I believe that public servants should be exemplars of public engagement in democracy, not simply 'bag carriers' for agencies. Through positive, respectful and evidenced sharing of their views they not only contribute to the content but to the shape and effectiveness of public debates in Australia, fostering effective democratic engagement - thereby supporting Australia's underpinning principles as well as perceptions of the public service and government.

As to the second question, of different rules for different groups, I understand how more senior or personally expert public servants can have a bigger impact on public debates - and this is appropriate, when used sensitively. This is no different from the different regard to voices from across Australia's democracy - different groups will always hold different voices in higher, or lower, regard, based on positional influence, knowledge or celebrity.

Constraining more knowledgeable or senior public servants to keep a debate 'level' makes no practical sense, and while I can see where certain elected or senior appointed officials may have concerns over being 'outshone' or having their decision-processes impacted by senior public servants, or more hierarchically junior celebrity individuals or experts, this is more related to ego than to good policy formulation processes.

Ultimately evidence and outcome effectiveness should drive policy processes - and even when this isn't perfectly the case, agencies should always strive to champion the right approach and leave it to elected officials (who can also be unelected) to make decisions on particular courses. As such allowing public servants to speak in undefined policy areas with respect and evidence is totally appropriate and supports robust and engaged democratic processes (even if this may at times personally annoy Ministers or senior public servants with specific ideological agendas).


2. Should APS employees be prevented explicitly from making critical public comment about services or programs administered by their agencies?

While this question appears reasonable on the surface, it overlooks the sheer scale and extent of some agencies, and the absence of effective internal processes to manage programmatic issues or failures.

Firstly, certain programs and services are frequently moved between agencies due to machinery of government changes or due to agreements between agencies where one may deliver services for another. This means that a public servant having issues with a program one week, and commenting about this publicly, could suddenly find themselves under investigation after a Minister or senior public servant decides to move the service into their agency.

Secondly, the scale of agencies, and the lack of communication of their range of activities, can mean that public servants may be unaware that a particular program or service is actually administered by their agency, particularly if delivered by external contractors or other agencies. Again this could easily catch out public servants who are not omnipotent - an expectation that is unrealistic when even Ministers can often be unaware of all the activities in the nooks and crannies of agencies within their remit.

Finally, agencies must commit to having effective internal dispute resolution processes for staff having issues with specific programs or services administered by their agencies. These are in place in some, but not all cases - leaving some public servants with no internal avenue to resolve disputes and thereby driving some to speak out publicly. Agencies would eliminate a significant amount of the potential for this risk by instituting effective internal dispute resolution processes.

If public servants are using and finding concerns with certain services or programs from their agency it is highly likely that members of the community will be as well, meaning that staff concerns should be treated like a canary in a coal mine - an early indicator of an issue that the agency needs to address and solve.

Essentially APS employees should not be prevented (if that were even possible) from making critical public comment about services or programs administered by their agencies. However they should be held to a high standard of providing evidence, of engaging respectfully and making it clear that these are their personal views only. Few programs will achieve 100% happiness rates amongst the communities affected by them, and recognising and acknowledging alternate views, even from within the organisation delivering them, is a sign of a mature and secure organisation committed to continual improvement and the engagement of staff who will act to improve outcomes, not merely remain silent about poor ones.

3. Should senior public servants have specific limitations about making public comments?

Per my response to the first question - no. However they should be held to a high standard of evidenced and considered responses, and selective engagement.

It is still relatively rare for senior public servants to actively engage in public discourse, particularly via social media channels - and this is a significant loss of role models who could help set a respectful tone for engagement across the community. If senior public servants fear criticism, or fear criticising their Ministers publicly this helps reinforce a status quo where their expertise, knowledge and experience is subordinated to snap decisions, supporting the gradual degradation of trust and respect in government and agencies.

Where senior executives strategically engage in public debates as 'eminent Australians' they both enrich the conversations and model a form of democratic engagement that others across the community are influenced to follow.

That said, this engagement should be respectful and carefully timed, rather than proliferate. They must also ensure that they demonstrate that they can work effectively with Ministers' offices even when disagreeing with policy. This can be a delicate high wire to walk and many current senior public servants may not have the depth of experience with social channels to carry this out effectively. This will change over time.

Currently few senior public servants engage at all via social channels, and I believe this is a significant loss to public discourse in Australia.

4. Should public servants posting in a private capacity be able to say anything as long as it includes a clear disclaimer stating that the opinion they have expressed is purely a statement of their own opinion and not that of their employer and is otherwise lawful?

Looking at this realistically, any public servant, or individual, can set up a pseudonymous account and say anything they want with limited chance of detection or identification (due to the large number of such accounts). Indeed it is likely that a number of public servants already do this in order to be part of the groups they wish to associate with online.

I believe that public servants, by way of their employment, should be held to a higher standard of engagement than general citizens, therefore should be expected to remain fair in their comments and criticisms, obey all laws regarding abusive or otherwise inappropriate behaviour on social media channels (as suggested in the question) and is evidenced where feasible - noting that not all areas of opinion lend themselves to evidence.

Public servants should model the digital engagement behaviour that a democratic society should aspire to, helping to foster productive and insightful debate, dispel misinformation and accurately direct people to where they can receive the help they require.

Currently I believe that APSC gudiance is more directed at an outdated view of 'impartial', which includes 'passionless' and 'unemotional'. Public servants should be free to be excited and passionate about their work and about principles that matter in democracy. This positively enhances their perceived capacity to be effective in service to the public, whereas emotionless engagement only serves to diminish effective debate.


5. Are the requirements of the APSC guidelines expressed clearly? Can they be made simpler and easier to understand?

I have never been a fan of the current APSC guidelines for public comment via social media.

They leave too many gray areas for senior management discretion around what is meant by 'harsh or extreme', 'strong criticism' or 'disrupt the workplace' - which I have seen used negatively against exceptional people by jealous bosses, to the loss of the public sector.

They are too broad, effectively covering every policy from every parliamentary party or independent - leaving public servants in a live minefield where, at any time, additional mines can be placed under their feet.

Overall they are negatively focused - looking at the downside risk of social media engagement without fully embracing the potential benefits of effective involvement by public servants in public discourse.

As an ex-public servant this blog, which touches on various policy areas, programs and initiatives - often in a critical but constructive manner, would never have been started under this APSC policy. Given my readership and the level of positive engagement it's had, I can't see how this would have been a better outcome for the public service.

Equally I've not been prepared to work directly for a government with this level of restrictive social media policy, and have spoken to many other people from the private world who ceased considering a public service career after seeing the draconic provisions in the current guidelines.

Of course the majority of the public service have continued to work productively under the current guidelines, however I saw an 80% reduction in public servant engagement online in the twelve months after its introduction - with many people closing down social accounts, going silent or shifting to pseudonyms to protect themselves.

This has had a negative impact on the online public policy debate in Australia and these personal accounts cannot be replaced by departmental accounts, which do not have the peer-to-peer engagement or influence of individuals online.

Looking at the international perspective, there's now far deeper and more constructive engagement by US, UK and NZ public servants on social channels then by Australians.

Ultimately, under the current APSC guidelines, any Australian public servants who wish to participate in public democracy online must weigh the negative impact if they ever stray, in their management's opinion, over a wide gray line, even only once within thousands of posts.

This makes the risk to the individual simply not worth it - but the cost to Australian democracy of the silencing of these voices is immense.

Read full post...

Monday, November 07, 2016

It's time to provide feedback on Australia's Open Government Plan

Last week the government released Australia's draft Open Government National Action Plan, a requirement to join the international Open Government Partnership, for community consultation.

Australians have until the 18th November (Edit: extended from 14th based on community feedback) to comment on the plan, at which stage the government intends to move to rapidly endorse it via Cabinet and begin implementation.

The plan is available as a PDF download from the government's Open Government Partnership website (ogpau.govspace.gov.au) as well as in web format (much easier to read) at the civil society Open Government Partnership Network site (opengovernment.org.au).

I've included the 14 commitments proposed below in brief - for more detail click through to the sites. (Edit: thanks to Asher for corrected number).

Transparency and accountability in business

The Government will enhance Australia’s strong reputation for responsible, transparent and accountable business practice. 

Open data and digital transformation 

The Government will advance our commitments to make government data open by default and to digitally transform government services. 

Integrity in the public sector  

The Government will improve transparency and integrity in public sector activities to build public confidence and trust in government. 

Public Participation and Engagement

The Government will improve the way the Australian Government consults and engages with the Australian public.

Read full post...

Wednesday, October 26, 2016

It's past time for governments to mandate security levels for all internet-connected devices

On the tail of the 2016's Census issues dealing with four relatively small distributed denial of service (DDOS) attacks, the US East Coast was recently hit by a massive DDOS attack that succeeded in taking offline, or at least slowing down, major sites - from Amazon, Twitter and Spotify to PayPal and Netflix.

This major attack, involving millions of devices, had global impacts - including impacting the websites of range of Australian companies - retailers, banks, media services, insurance companies and hotels.

This type of attack isn't new - for years organisations have had to harden their computers and networks to fend off DDOS and more focused hacking attempts.

In fact a DDOS attack is often considered one of the most unsophisticated approaches - simply flooding a network with an unmanageable number of requests from hundreds, thousands or millions of hijacked devices until the routers and web servers collapse under the pressure.

However this latest attack was different in several regards to what organisations now should plan for.

Firstly it was on a scale that few had imagined. The company targeted, Dyn, provides backbone services for the internet and was well prepared for massive DDOS attacks. However this attack was at a scale that even such a service was unable to fend off without significant disruption for hours.

Secondly, the approach didn't use the normal range of compromised and poorly patched internet-connected devices to launch and sustain the DDOS attack. Normally hackers conscript or buy access to 'botnets' made up of hundreds or thousands of poorly maintained computers on insecure networks, using malware on these PCs to launch an attack.

In this case, however, the people responsible used open source hacking software to tap into a network of devices connected to the internet - security cameras,  Digital Video Recorders and web cameras, amongst other types.

The majority of these devices were older, with many were linked to one specific Chinese manufacturer who develops white-label products for others to brand and sell. Most relevant, these devices had little if any security in place to prevent hijacking. They are also unpatchable - they can never be secured in ways that make it hard, if not impossible, for hackers to take them over.

In other words, these non-computing insecure devices are a permanent threat to the internet. They can easily be used in malicious or military cyberattacks by anyone with the inclination to do so.

While the manufacturer has issued a recall for these permanently insecure devices (though its unknown how many devices will be returned as part of this process), the growth of the 'internet of things', where DVRs, smart fridges, air conditioners, cars and all kinds of household and work appliances are linked to the internet for monitoring and management purposes, poses a growing threat to the ongoing viability of the internet.

With billions of devices progressively being connected to the internet, there's little in the way of mandated or legislated requirements for devices to be secure to a given standard at a point in time, or have their software regularly upgraded to ensure that known security risks are patched.

While most countries specifically regulate and test products designed for health use, power use and radio spectrum to verify they won't cause harm, few nations have similar requirements for security.

Largely this remains in the general 'fit for purpose' terms in relevant trade practice legislation, which is effectively useless when a device, such as a baby monitor or smart fridge, can remain fit for purpose and be used in a economic or politically inspired cyberattack at the same time.

This isn't a future issue. I can name six types of non-computing devices in my home which are, right now, internet capable - DVRs, TVs, web cameras, security cameras, air conditioners and light globes.

Households across Australia, and the world, are rapidly adopting or upgrading to these devices for convenience and improved management purposes - but security requirements are lagging badly.

This is an area where it's not sufficient for governments to trust that manufacturers and retailers will 'do the right thing' on an ongoing basis.

Some manufacturers and supplies  might cut corners in their software, or not realise the significance of how their devices could be remotely accessed and used maliciously. Others may discontinue products or go bankrupt, leaving devices unsupported.

The end result is not necessarily a risk to the consumer who bought the product, but rather a broader risk to society that these devices are used in an attack that damages companies or governments.

There's also a risk that companies or unscrupulous governments may use these 'smart' connected devices themselves to spy on citizens. Indeed this may already be happening.


Now some governments, such as the Australian Government have begun offering advice to citizens on how to secure their personal networks. A good home firewall will, currently, help keep many potentially insecure devices protected against external risks.

However this is merely a stopgap. Firewalls have flaws, can be bypassed and are not consistently installed or maintained by households.

With internet-connected devices already proliferating, many already in households and businesses may be impossible to secure, as were many of those used in the recent US cyberattack.

For governments to protect societies against cyberintrusions - economic loss, political damage and inconvenience, there needs to be far more consideration of the potential risks around internet-connected devices - and fast.

Extra: I've just read a post that sums up this issue very eloquently, so have embedded it below...

Read full post...

Monday, October 24, 2016

For how long should we judge people by a few intemperate comments?

Over the last few weeks we've seen several prime examples of individuals being judged and convicted by comments they made at some point in the past.

Most would now be aware of the leaked tape of Donald Trump and Billy Bush, whose 'locker room talk' recorded in 2005 has led to an exodus of support and new sexual harassment claims against the US Presidential Candidate, and Bush's exit as a NBC News anchor. Trump has said that 'no-one respects women more than him' and apologised for his words, stating they were merely words and that he'd never act in such a way (prompting a number of women to come forward with examples of a pattern of behaviour).

Some may also be aware that last week Twitter fired Greg Gopman after a month, when TechCrunch republished one of Gopman's Facebook comments from 2013, in which he called homeless people 'trash'. Subsequently to his comment, and before the Twitter firing, Gopman had quickly apologised and taken a number of actions to help the homeless community in his city.

Without commenting on the merits of either sequence of events, I believe that society, and organisations, need to seriously consider how to manage intemperate comments by individuals and their ongoing impact on lives.

We now live in a world where almost any comment may be recorded and kept indefinitely - and can resurface at anytime.

These comments may be said in the heat of the moment and later repented, or may form part of a long-term pattern of behaviour that defines an individual's approach and thinking.

However in the hothouse of modern media, context is quickly lost. The distinction between a pattern of abuse or bad character and an occasional momentary weakness or bad behaviour rarely survives a media and social media scrum.

Even positive or neutral comments, or a moment in time video, recording or photo , when used out of context, can have a devastating impact on an individual's future prospects, their ability to contribute to society, as well as on their family, friends and employer.

With teenagers experimenting with social norms in public social channels, and fast-shifting social norms catching older people out for unwise comments made decades ago, few of us can truly say that none of our past comments cannot, and will never, be used against us.

Moving forward do we want to be a society where we drag everyone down to the worst versions of ourselves - where we glory in ripping and tearing others apart for momentary lapses of judgement, fast regretted?

Or do we wish to be a society that glories in redemption, that allows people to make mistakes, correct them and move forward and upwards to their best selves - provided they actually do.

Organisations need to decide when they will they stand behind individuals who make a few mistakes and correct themselves, even in the face of a media storm. They need to decide where to draw the line between intemperate mistakes and intolerable character flaws and patterns.

Otherwise we're heading toward a society where there's no second chances, no room to grow and improve from one's 17 year old self. A society where those of truly bad character conceal themselves and thrive (even into high office) by claiming that everyone who has ever made a mistake is just as bad as them.

The first step required is to have that conversation - in the media and in organisations. We should not 'walk past' a discussion and simply seek to control information in the hope of protecting otherwise good people from the mistakes of their past.

The standard you walk past is the standard you accept.

Read full post...

Wednesday, October 19, 2016

Support my ePetition for a better Australian ePetition site

Openness in government is supported by low barriers to engagement between citizens, agencies and politicians.

For example, making the House of Members' Register of Interests available publicly is great - but not THAT great if it is only available for viewing in hardcopy in one location in Canberra between the hours of 9-5pm (which used to be the case).

Recently the Australian Government launched its ePetitions site, designed to make it easier for citizens to petition government on specific issues or goals.

You probably didn't see any media headlines about it, or even government announcements - nor is the site easy to find via search or within the Parliament House's website.

If you do find it - the approach is uninspired and basic. I reviewed it compared to three other ePetitions sites internationally, and it just didn't stack up on usability, accessibility, attractiveness or tone. Read my comparison here.

There's ePetition platforms available that are far more developed and inviting, and there's lessons from international ePetition sites that clearly weren't learnt.

The cost to us, to Australia, is that people won't engage with Parliament and the Government in the ways they could, reducing the openness and effectiveness of the process.

So... I created an ePetition to Parliament. It ask them to mandate the Department to work with the broader community to implement a true Web 2.0 ePetitions platform.

This platform should be equivalent to the best of breed internationally and embed best practice design principles (such as from the Digital Transformation Office).

Slightly to my surprise, they've published my ePetition, though without actually telling me - another issue with the Aussie process.

Therefore I'd appreciate if you could sign my ePetition at: http://www.aph.gov.au/Parliamentary_Business/Petitions/House_of_Representatives_Petitions/Petitions_General/Petitions_List?id=EN0028

And then please share this ePetition with your networks.

Read full post...

Thursday, October 13, 2016

Disruption is often simply a failure to prepare and evolve

Digital disruption is one of the buzz terms of the last few years, underscoring the increasingly rapid changes in society, industries and governments as new ideas and techniques enabled by digital technologies take hold.

Photo by Tsahi Levent-Levi
While some embrace this disruption (generally those doing the disrupting), for many it remains an unsettling or even negative concept.

Disruption implies a disturbance or breakdown in the existing order, a situation where the status quo is overturned in an unpleasant way. To disrupt a process is seen as interfering with the ordinary course of events, and 'disruptors' of events or organisations are rarely looked on in a positive light.

While many disruptions are predictable, they are often not avoidable - such as the impacts of a natural disaster or the consequences of a terminal illness.

Equally disruptions in business and governance, through new technologies, ideas and approaches, can often appear to come rapidly out of 'left field', even when they can have been expected for a long time.

However in many of these cases, disruption has a much greater impact on societies and organisations than it needs too, not because it was unexpected or not discussed, but because leaders refused to see the writing on the wall, and begin a process of communication, adaptation and evolution soon enough.

A classic example is Kodak Eastman - the inventor of the digital camera, whose business was destroyed by the product it originally designed and marketed.

Kodak did not go bankrupt because no-one within or outside the company could see the impact of digital cameras, or their widespread adoption into mobile phones, laptops, tablets, drones and more. The company failed because the company's leaders chose to believe that their business could not be disrupted, that their name, reputation and products would allow them to survive no matter where the market went.

As a result they adapted too little and too late to the 'digipocalypse', where film cameras rapidly disappeared and even the digital camera market fell as people started using other devices as their primary photographic tool.

When I hear business and government leaders speak of disruption, of new industries replacing old or new thinking flushing out the old, I often wonder how much is just talk and how much actual action is taking place in their organisations to adapt to new realities.

Few disruptions are truly unpredicted, although their course may be unpredictable, with some technologies being rapidly adopted and others festering amongst early adopters for decades.

Organisations that are truly committed to survival and growth don't talk about the 'disruption' due to digital, but of the opportunity to re-imagine their business models and redesign their operations, preparing for and adopting innovations and new ideas in an evolutionary manner.

By preparing early and evolving continuously these organisations never actually face actual disruption, because they are almost always in the right place at the right time, with the talent, tools and techniques at hand to move with the market, rather than trying vainly to keep up.

When these organisations are tripped up by market or social change, it's due to velocity, not disruption, and they remain well-equipped in talent and tools to pivot their operations to minimise any disruption.

If your organisation is facing digital disruption, consider why that might be the case.

Was the disruption truly unpredictable? Or did your management fail to watch the market closely, or ignored advice on the basis of their belief that the status quo was unshakeable?

Is the disruption due to a lack of preparation in the face of a clear and present danger? Or due to an unwillingness to change, even at the point of extinction?

While change is a constant feature of business and social environments, disruption is simply what happens to organisations who fail or fear to face change. Organisations that do not design structures, generate strategies or train and recruit staff who can lead and support the internal transition in a prepared and evolutionary way.

Therefore any organisation that has been disrupted should first look inwards, not outwards, for the cause, and take appropriate steps to ensure that, if it survives, it never makes the same mistake again - to inadequately prepare itself for environmental and market change.

And any organisation that foresees disruption ahead should be preparing now. In order to turn a potential disruptive event into a much less impactful, evolutionary step, that causes far less disruption or damage and buoys the organisation to greater future success. 

Read full post...

Thursday, October 06, 2016

Free range 'strike teams' of specialists are a long overdue innovation for Australia's public service

I'm very pleased to see that the Australian Public Service Commission is finally considering the introduction of 'free range' teams of public servants, unattached to specific agencies, who can provide specialist skills as and where needed.

I proposed this type of team while I was working within government almost ten years ago now, as I could see that there were a range of skills that agencies did not require continuously, but were needed across the public service all the time.

This included experienced community engagement professionals, a range of digital talents as well as design and implementation specialists.

Until now the hierarchies of the public sector have been designed against such free-roaming talent, able to converge as 'strike teams' to assist agencies when they need it, and move on to other assignments when the need wanes.

There's still the strong (almost feudal) hierarchies in place, but it seems that the innovation agenda, combined with diminishing resources and an increasing need for specialists, are helping to wear away the resistance to the recognition that it's all one federal public service.

I always found it peculiar that senior public servants were adamant that they served the government of the day, but chose to do so by building rigid organisations that made it harder for skills to move around, to be 'lent' or 'shared', but instead hoarded people as jealously as they hoarded data.

This always seemed a sub-optimal strategy for government, but one with very deep roots.

There's still a number of challenges ahead for the APSC in realising this idea. It still has to navigate the hierarchies of power - some agencies might wish to hold onto talent for too long, with brush fires between agencies that need similar resources at similar times. There's also likely to be all kinds of power struggled between agency 'owned' resources and the floating specialists, who may be seen as fly-by-nights, dropping in to offer their wisdom, then leaving the mess behind for agency staff to clean up.

The APSC must find public servants with the right psychology and mindset to move around, without having a 'fixed abode' or a hierarchy to protect their position and career progression.

Many people who work in this way already are contractors or consultants and may see little benefit in giving up salary for supposed job security, while new entrants from the private sector, who might be more used to mobility, may not find public service cultures or approaches congenial to their working styles.

However I'm glad the APSC is making the attempt, and hope it will be widely supported, particularly by smaller agencies with less capacity to hire or contract the specialist skills they need.

Read full post...

Friday, September 30, 2016

Australian government ePetitions compared to international models

Australians might be surprised to learn that the Australian parliament only agreed to formally accept ePetitions in July 2015.

That was five years after it was formally recommended to parliament and follows a trend towards epetitions set by other digitally advanced democratic nations, such as the UK and USA.

In September 2016 the Australian Department of Parliamentary Services launched its epetition site allowing people to create and sign epetitions at aph.gov.au/Parliamentary_Business/Petitions/House_of_Representatives_Petitions/Petitions_General - yes that is quite a mouthful.

I've reviewed Australia's site compared to comparative sites released in the US, UK and Canada to form some conclusions on how well we've done.

However, unfortunately for Australians, the model used for Australia doesn't measure up well.

UK - ePetitions

The UK's epetitions site launched in August 2011 at petition.parliament.uk and has been restructured several times over the last five years.

Today it is a sleek, easy to access platform that hides all the technical mechanics the UK parliament requires for petitions behind a usable and simple step-by-step process.

It's very simple to find and sign a petition, with the process for responses explained clearly on each petition's page. 

Sharing tools are embedded to make it simple to encourage others to sign. It's easy to view signatures geographically by electorate (great for parliamentarians and respondents alike).

The data for each petition is immediately available via a standards-compliant data format.

The process for creating new petitions is also simple and seamless.

It uses plain English and employs a range of assistive approaches to ease first-time petitioners through the process. This includes examples of how to write a petition and flagging information that will be required in later steps so the petitioner can pre-prepare.

The site uses text matching to find similar petitions so that a petitioner can choose to sign a pre-existing petition, rather than create a near-identical one - a step that saves effort for both petitioners and for the public servants who need to manage the system.

There's clear warnings when a petitioner reaches irrevocable steps, and the system supports and encourages sharing - to help the petitioner get the petition to audiences who may wish to sign.

All in all it's a solid and well-thought out system with excellent usability - very important when considering that most people rarely petition government and need a helping hand to navigate what can be a complex and seemingly irrational process for those who do not think like bureaucrats or politicians.

USA - WethePeople

The US's epetitions site is similarly five years old - launching in September 2011. Named WethePeople and located at petitions.whitehouse.gov, the site is structured differently, but is just as simple to use, as the UK's version.

While the site doesn't offer the same geographic mapping as the UK site does, it does provide very clear step by step instructions for both signing and creating petitions and is equally clear on the goal number of signatures required for consideration.

The government's responses to epetitions (which must reach 100,000 signatures to get a response) are clearly provided with the petitions themselves, making it easy to understand what was asked and how it was responded to.

The US system requires that people creating a petition must create an account - a small barrier to entry, but one that helps with screening. 

It also makes it easy to track repeat petitioners - a useful thing for a government, if slightly invasive in privacy terms for an individual.

Something I don't like about the site is that after creating an account it sends a confirmation email with a randomly assigned password in plain text. People who don't respond straight away could easily get caught out with identity theft, although the site does force you to change it after you confirm your email.

However when changing your address the site does provide an idea of how strong your password is and makes helpful suggestions on how to improve it (something I think all government sites requiring login should do by default).

Once a petitioner has an account they also get a dashboard to track their petitions, though unfortunately it doesn't also track petitions they have signed or autofill your details when you choose to sign a petition. This may be done for privacy reasons, but there's also huge convenience and utility in these steps.

The process for creating a petition is brilliant - laid out step by step.  

The ability to look at past successful petitions as examples is a nice touch and very helpful for first-time petitioners, and the filtering approach helps guides people to structure their petitions well. 

Later in the process petitioners also get to tag their petitions by topic, providing a useful way of filtering them to the appropriate agency and providing useful statistics for the government on the 'hot topics' for citizens.

The system doesn't have the matching of similar petitions as the UK system does, but nevertheless it's very polished and well executed.

Canada - e-Petitions 

Now the Canadian epetition system is interesting as it debuted in December 2015, less than a year before Australia's system. As such it hasn't had the same amount of time as US and UK sites to refine and restructure based on use. but has the opportunity to learn from their experiences to implement the best of both sites in a Canadian context.

The site is very simply named petitions.parl.gc.ca, similar to the US and UK epetition platforms, but has taken a different approach to either the US or UK sites.

There's no ability to see the latest petitions on the main page, users must use a search tool or click to see all live petitions. This shifts the propensity for people to browse and choose to sign by adding a small 'one click' barrier to the visibility of petitions.

When a user clicks on 'View all petitions', what they see doesn't really provide enough information to decide whether to sign. Another click is needed to view the details of any specific petition. However the screen does help people refine down to a topical area quickly, unlike the US and UK sites and the keywords by petition are useful, if perhaps put ahead of more useful information such as the title and summary of what a petition is asking.

The language, unfortunately, is a touch more bureaucratic than in the US and UK sites, with petitions titled by number and reference. These may be useful to bureaucrats, but have limited meaning for users and could have been hidden from petitioners and respondents.

Petitions provide a numerical breakdown of respondents by provinces, but no map view and no easy way to download the data without screen-scraping.

Responding to a petition is slightly more complex than in the US and UK epetition sites, with it being mandatory to provide an address and phone number as well as the usual name, email address and confirmation that you're really a resident of the country. The response form is also less friendly than the other sites, using now old-fashioned red asterisks to denote mandatory fields.

Creating a petition involves an equally complex sign-up form, where a user must avow they're a Canadian - so I've not looked into the creation process. I do anticipate that it would not quite be as sleek and refined as the US and UK versions.

The responses to petitions, like in the US site, include all petition information and those that have been responded to can be found easily through the top menu of the site. However the responses are provided as PDFs rather than within the page. This adds an extra step to the process of reviewing a response and most are only one page long, so I feel this is a poor approach, adding complexity with no benefit for users.

Australia - e-Petitions

Similar to the Canadian site, Australia's epetition site is quite new, so some rough edges can be expected. 

However I did not expect as many rough edges as I found, given there's some excellent examples above to learn from.

Also as the code for WethePeople is available as opensource, it is it relatively quick and easy to start with all the US's experience and build from there. 

To start with, Australia's epetitions site doesn't have a short web address like petitions.aph.gov.au, it is deeply buried in the site at www.aph.gov.au/Parliamentary_Business/Petitions/House_of_Representatives_Petitions/Petitions_General

Now it could be argued that as Senate, House of Representatives and Committees might all accept petitions but operate differently, it needed to be buried within each of these section of the site. 

However this could have been easily handled through a single multi-choice question in a petitions process, leaving all petitions to live at the same simple petitions.aph.gov.au address - without requiring petitioners to do the hard work of understanding how government operated.

On top of this the petitions process doesn't come up in the first page of search results when looking for 'petitions' - a critical but easily fixable mistake. 

This type of simple oversight dominates the entire Australian epetitions process, with it being pretty clear than the work was done with little reference to international benchmarks or usability testing.

Moving on to the actual processes, there's currently no petitions listed so it's not possible to analyse the process for signing a petition. I would have expected that the APH would have done some work to ensure there were a few petitions at launch, as other governments did. 

Clearly this wasn't the case, with the APH potentially taking more of a 'build it and they will come' approach rather than promoting the availability of the site widely before and during its launch. The impression that leaves me is that the APH didn't really want to create this site and doesn't really welcome petitions - they'd prefer to not hear from citizens or have the hard work of dealing with any resulting work.

Regardless of whether this was the case - the impression, or perception, is the thing - and the lack of any petitions to sign at launch reflects badly on the site.

Moving on to the creation process, the process for doing so is well explained in the first page (image above) - though with far more text than is necessary (as illustrated by the other epetition sites above).

Some of the steps on this page, and later pages, are not well communicated, using very subjective and bureaucratic terms - such as "Language (must be moderate)". 


I'm not sure what 'moderate' actually means and I doubt most Australians would be able to guess what a bureaucrat would consider 'moderate language'.

However using more words to explain these types of terms would be a mistake - instead the entire page should be written in plain English, aimed at about the 5th grade level. 

In fact I quickly tested the language on the main page, and it scored at a current grade level of 10.5 - well above what is considered acceptable. The subsequent creation pages score even higher, with terms bandied around that are rarely used outside of Canberra's bureaucracy and would serve to confuse, frustrate or even upset many Australians.

The process for filling in an epetition is OK, clearly stepped out, but with far too many steps (and words) on each page. There's no way to compare your petition with existing petitions - as the UK site does - though as there's no existing petitions to compare with I'm not too concerned about this as yet.

It will become a source of additional work for public servants and frustrations for users down the track however.

There's a lot more questions and information requested than in other epetition processes - with a lot of form fields to complete, which will effectively deter many people from establishing an epetition. Whether this is a good thing, however, depends on whether you're a bureaucrat first or a citizen first (I think it's a poor approach).

Nowhere could I see clarity on the thresholds at which you might get a response to a petition, making the entire process seem like a black box - a digital black box, but a black box nonetheless.

The entire process felt very cold and impersonal, unlike the UK and US experiences - which were warm and inviting.

Given parliament serves citizens, I think it is better to strive to leave users feeling they were important welcomed guests rather than nuisances and intruders into a hostile space.
This lack of warmth was particularly characterised by the final 'thanks for submitting a petition' page - which neither thanked the petitioner, nor gave them a feeling they were important and valued. 

Even the title of the page remained 'Request a new e-petition' rather than thanking the petitioner for their engagement in Australia's democracy.

Given how often politicians and public servants complain that Australians are disengaged from politics and democracy, the way this entire epetition creation process was constructed makes it very clear that the government itself holds a lot of responsibility for pushing people away, rather than welcoming their contribution.

Summary

So given my review of the four epetition processes, from Australia, Canada, the UK and US, I can say that I'd happily and enthusiastically recommend both the US and UK approaches, slightly favouring the UK due to it's maps and sharing tools.

Canada's site is OK for a first attempt. It doesn't appear to have learnt a great deal from the US and UK experiences and asks more than it needs from citizens, but it remains usable and functional if not inviting.

Unfortunately Australia's epetitions site is a very poor effort, and reflects poorly on the government, our public service and Australia's claims of being innovative and digitally progressive.

About the most positive thing I can say about it is that at least we now have the site - so there's a starting point to improve from.

However any competent usability designer would not have built the site in the way it has been built - and it seems more of a 'tick and flick' developed with internal resources on little or no funds (not that it would have cost a great deal to have done a good job).

I'm very disappointed at the APH's efforts - and have created an epetition for people to sign accordingly (though I doubt it will make it through the APH's scrutiny process - which is far more involved than for any other jurisdiction compared).

I truly hope the APH spends more time looking at benchmarks internationally and can convince the government that epetitions are a key interaction tool with citizens, so having them feel invited and effective is critical for supporting a positive view of government.

I'll be looking in on the site from time to time to see how its going - and would happily help the APH improve the site if asked (in fact I reached out last July, but never heard from them).

This isn't just a box that government has to tick, it's a vital avenue for citizens to engage with government and an advanced democracy like Australia should recognise the importance of doing it well.

Read full post...

Tuesday, September 27, 2016

Party time for GovCMS as it hits 102 sites, well ahead of target

It's party time at the Department of Finance as GovCMS continues its growth surge, from 78 sites less than a month ago to 102 sites this week.

This means the Drupal-based platform is tracking 70% ahead of its 2016 targets, demonstrating how successful a well-engineered and supported digital platform can be in government if well designed and supported.


While some of the growth may have come from agencies shifting away from GovSpace, which shuts down next year, part is also coming from state, territory and local governments who are beginning to consider the platform seriously.

While mandating a single webCMS and platform might be a step too far for Australian governments, the approach of providing a cheap and effective platform, with full standards support, a growing developer base and interoperability of plugins and modules (which can be reused across agency sites), is providing a strong 'pull' effect.

This 'pull', rather than a 'push' (mandated) approach to service design is one that government can also apply to citizen and business services, so I'm hopeful that the GovCMS experience is demonstrating to agencies how the carrot can be more powerful than the stick.

Given that even the Digital Transformation office has now fallen into line, after the DTO initially considered building its own WebCMS for the Gov.au site, GovCMS has been a massive success for government in Australia, and for the Department of Finance in particular.

GovCMS is supported by Acquia, the commercial entity created by the developers of the open-source Drupal platform, with a variety of local development partners involved in the development of specific agency sites.

Read full post...

Friday, September 23, 2016

Innovative leadership involves walking in the rain

I've rarely seen a better example of leadership in action than in the juxtaposition of these two photos, kindly shared on LinkedIn by Jean-Michel Wu of McCann Worldwide.


Now let's be clear up front - these are carefully selected images, presenting single moments in time - so they aren't necessarily representative of the style of either leader represented, either the US's political leader, Barack Obama, or business leader (and Republican Presidential nominee) Donald Trump.

However the notion of a leader who shields himself, at the expense of others, as compared to a leader who shields others before themselves, is one that anyone aspiring to leadership or in a leadership role should reflect on.

We've seen many examples of 'leaders' who fail to take responsibility for their own actions, or for the actions of those under their direction. These so-called leaders shield themselves while actively or passively allowing others to take the blame for actions or inaction that they were ultimately responsible for.

Example abound of this practice. In government there's functionaries falling on their swords to protect their Ministers, and senior public servants pushing the blame downhill, to junior staff, or to vendors.

In the private sector there's many examples of this type of behaviour, although it is not as often on public display. However it is sufficiently common that it has become an advertising punchline.

When this type of behaviour is displayed by leaders it erodes trust and respect - in them and in the organisations they lead.

When the behaviour becomes public it can be devastating to an organisation's brand and reputation - but even if it remains hidden within the walls, it can significantly affect an organisation's performance over time.

One of the casualties is likely to be innovation and invention, as employees witnessing 'scapegoating' or 'passing the buck' behaviour by their leaders will be less inclined to take risks in order to avoid getting the blame.

Another casualty is organisational culture, which will tend to become more secretive as staff hide potential mistakes and fearful, as staff worry about being made the next example.

Whereas a leader who shields others, 'running interference' and supporting their staff will foster a very different culture. Staff will be more inclined to innovate as they know they won't be blamed for failure, and their managers will ensure they get credit for their successes.

A shielding approach also gives teams the room to solve problems rather than hide them, paying enormous dividends in the long-run.

Cultures will be more open and inclusive with this second type of leader. Staff more collaborative and sharing, rather than hoarding information to protect their roles.

Of course there must still remain appropriate mechanisms for managing poor performance - but these will be seen as fair and equitable, rather than vindictive or aimed at protecting the upper echelons from their own decisions and actions.

Organisations that encourage, foster and employ leaders who choose to shield their staff, even sometimes at personal expense, will ultimately be more successful - more innovative and more adaptable.

So if your organisation is trying to foster an innovation culture, a good start is for its leaders to walk the talk by walking in the rain.

Read full post...

Wednesday, September 21, 2016

Breakthrough or Buddy-up - Two Strategies for Chief Digital Officers

Growth of the Chief Digital Officer (CDO) role has been incredibly rapid over the last few year, reflecting the increasing importance of technology to organisational success and survival.

However not all CDO roles are created equal, with enormous variation in their responsibilities, resourcing and capability to generate change, in the form of digital transformation, in the organisations they serve. Some have direct responsibility for business lines and IT teams, others serve primarily as advocates and influencers in the C-suite, with little in the way of direct reports or operational responsibilities.

The candidates appointed as CDOs have also vary enormously in background, some from 'pure' IT careers, others from a mix of IT and business and still others from business-based disciplines.

 An additional complication is that due to there being so many new CDO roles emerging, in many cases both the organisation and candidate are new to the role. This means the definition of the role might not be as clear as for well-established and understood roles, organisations may be less clear on what characteristics they require.

 A new CDO must also find their way and negotiate their position in the C-suite in a game of reverse musical chairs, where other executives may be looking for ways to gain advantage from the new seat and player at the table.

(Graphic courtesy of CDO Club.
Keep an eye out for the Chief Digital Officers Worldwide update for 2016)

In many cases CDOs have been external hires, including from international sources. Some public sector organisations have brought in experience from the private sector, though I've not seen the reverse as yet.

This can add additional complexity to the role. An 'outsider' brings their own cultural and workplace practices, which is often an advantage in a CDO role, but can require a significant adaptive phase for both the Officer and organisation. New CDOs from different environments can require some time to build the relationships and alliances necessary to achieve results and to learn how to navigate an organisation's formal and informal decision-making processes.

When it comes to performing the role successful, there's a spectrum of strategies available to a new CDO.

At one end of the scale there's the 'breakthrough' approach, where the CDO mandates and forces change on an organisation.

At the other end is the 'buddy-up' approach, where the CDO functions as an expert adviser and councillor, supporting colleagues and staff to make change themselves.

I've been fortunate enough to observe both approaches in practice, witness the comparative successes and failures over time.

In this post I wanted to provide a little insight into how these strategies can, and are, applied, the potential outcomes for the choice a CDO makes and what organisations should look for when hiring the right CDO for them.

Looking at the 'breakthrough' approach first - in its purest form this is a 'no holds barred', even violent, way to stimulate organisational change by actively pushing through any barriers to digital transformation.

It requires a forceful and driven CDO with massive resilience who is prepared to take on personal consequences for their strategic approach. Within an organisation it often results in adversarial situations where a digital transformation is imposed on unwilling business and IT areas, ending careers and bruising many survivors.

Internationally many CDOs who have adopted this strategy to a significant extent have had quite short tenures, coming into an organisation and driving digital transformation relentlessly for a year or two, then either moving on to the next appointment or requiring a personal break to rebuild their resilience.

It is not a tactic for executives who wish a long-term career with a specific organisation, or even in a specific industry or country, as the crash through tactics are not congenial to building good long-term relationships and alliances.

Used strategically this approach can break down long-term barriers to change and innovation, squeeze out old-fashioned and outdated thinking and renew an organisation to move forward in a more cost-effective and digital way. Some organisations may require this 'shock treatment' to shift from their current track to a more sustainable one, whereas the buddy-up approach would not provide significant impetus for them to transform.

Used poorly, this strategy can alienate potential allies, damage competent individuals and generate a 'winners and losers' culture, where people feel forced to choose sides. Any resulting digital transformation can be short-lived, reliant on the CDO remaining in their role, with other executives and middle-managers rolling back to their comfort zone after the CDO is gone.

A common tactic for individuals who oppose this approach is to simply wait until the CDO moves on, although sometimes repairing the damage a breakthrough strategy does to trust and respect within an organisation can take years.

The buddy-up approach is far more collegiate and is built on alliances and expertise rather than direct power and force. This strategy is better attuned to patient executives who are willing and able to spend the time building trust and leading executives and staff to a place where they feel empowered to choose adopt digitally transformational changes, rather than having these changes forcefully imposed on them.

The approach builds good long term relations and suits executives who wish to build a long-term career in an organisation or across a sector. It works well in situations where a CDO has little direct power (direct responsibilities or budget) but is a respected key influencer, with peer-level access to others in the C-suite.

The speed of digital transformation achievable using this strategy tends to be far slower, particularly in the initial stages, than via the more aggressive breakthrough approach and may not suit organisations that require a rapid transformation. However, in the longer term, the pace of change can accelerate rapidly as it no longer must be solely driven by the CDO but has become embedded in how the organisation operates.

For organisations with firmly bedded down cultures, there's a risk that the buddy-up approach will get lost in the mix, with the CDO's efforts absorbed into the organisation rather than propagating change. We've seen this many times in the past, where the introduction of a new approach becomes so diluted within the existing culture that, like a drop of ink in a glass of water, it vanishes without a trace.

Used strategically the buddy-up approach is very effective at bringing the organisation with a CDO, generating a deep-rooted top-to-bottom change in culture over time. By avoiding adversarial and 'winner take all' situations, staff across the organisation retain their unity in being on the same team without aggressive competitive, or even bullying, behaviours.

Used poorly the buddy-up approach can be ineffective, with the CDO ignored, or their efforts co-opted and absorbed into business as usual without the level of digital transformation required by an organisation. Also, due to a slower ramp up as trust relations are built, the approach can be too slow for organisations facing imminent threats to their survival.

Fortunately many CDOs understand that their role involves using a blend of the strategies above, based on their resources, influence and environment. Knowing when to apply a breakthrough strategy rather than a buddy-up strategy is the real art of being a CDO, and organisations should be careful to select executives who have demonstrated a careful balance of both, even in situations where one strategy needs to be dominant.

The real danger for organisations - and CDOs - is when they rely too heavily on either the breakthrough or buddy-up strategy.

An over-reliance on breakthrough risks any digital transformation successes being short-term, poorly embedded in an organisation and leading to a 'pushback' that can damage digital initiatives in the organisation for years to come.

An over-reliance on buddy-up can conversely result in a failure to implement the digital transformation required, leaving an organisation in a worse position as its rivals and markets shift.

When hiring CDOs, it's important to not just look at their past short-term successes in transformation, but also their record of fostering enduring digital transformational change and strong relationships.

Those who rely too much on breakthrough tend to have shining successes to their credit, but poor senior relationships and a trail of past engagements where organisations cannot demonstrate significant lasting business value from the CDO's efforts.

CDOs who prefer buddy-up approaches can appear to have less spectacular careers, with most of their successes shared, but come well-recommended and respected. Again it is important to consider if their past engagements have resulted in lasting business value to the organisations they have served.

For those aspiring to be a Chief Digital Officer, it is important to develop the capability to apply both breakthrough and buddy-up strategies, and particularly the emotional intelligence to know which is appropriate to apply. Having experience using both strategies effectively is of enormous benefit when seeking a CDO role.

It's also critical for those stepping into a CDO role to understand and negotiate the use of breakthrough and buddy-up strategies, to ensure that the CEO, Board and other executives understand why the CDO is taking a particular course at a particular time.

A CDO more experienced with buddy-up strategies will need to communicate clearly why the alliance approach to collective change is being applied when working in an organisation that took on a CDO to aid in a rapid digital transformation.

Conversely a CDO selecting breakthrough tactics will need to make it clear why they are choosing an aggressive approach to digital transformation to avoid alienating other executives and staff who may feel trampled or excluded, and losing their mandate before the transformation is embedded.

Most importantly for any prospective or new CDO is the ability to know your own strengths and weaknesses, and seek opportunities where your personal attributes are beneficial to your role.

Using myself as an example, in my roles in large organisations I've often strayed too far into breakthrough territory, reflective of my past experience in business startups, where speed of outcomes is paramount over relationships or process. I've also had several roles where breakthrough was the only viable strategy due to the timeframe and environment.

I have learnt from others, who have mastered the approach, to apply more buddy-up tactics - particularly during my experience in government, where strategic alliances are essential to foster deeper and longer-term digital transformation.

However my natural inclination is more towards breakthrough, and I perform better in environments where, on balance, I can use this strategy more often.

Others may find they naturally prefer to apply buddy-up strategies, or are evenly balanced between the two.

Whatever your personal preferences, you'll likely do best in a role that reflects how you operate.

However regardless of whether you're applying breakthrough or buddy-up strategies, keep in mind the ultimate goal - to redesign organisations to be successful in a digital world.

Organisations live or die by their people, and selecting the right match of CDO and organisation, and the right blend of buddy-up and breakthrough strategies is essential for their digital transformation and success.

Read full post...

Thursday, September 15, 2016

Farewell to GovSpace.gov.au - a bold and successful government initiaitve

On the 25th August the Department of Finance in Canberra announced that its bold experiment in providing a central website infrastructure for agencies, Govspace, was coming to an end after almost seven years.

I still remember feeling excited at the original launch of Govspace.

At the time I was working in the Department of Health as Online Communications Director.

I was theoretically responsible for the department's entire web presence, although many of the 150+ websites operated by the department were directly controlled by the business area funding their development.

It was still a time when business areas wanted a new website for every new initiative and would pay through the nose for those sites.

Business areas would often spend tens or even hundreds of thousands of dollars to digital agencies, or our internal IT team, to have each new site built.

It was a frustrating time for me as there wasn't a simple way for the department to procure low cost sites. We didn't have the capability to easily build or buy websites based on open source web content management systems (WebCMSes), such as WordPress, that used free or cheap themes rather than hand-crafted custom-designed graphical interfaces.

Even Health's internal IT team had to charge six figure sums for simple websites due to the costs they had to incur and offset when using the department's mandated internal web content management platform (Lotus Notes) to deliver them. Each internally built site had to be custom coded and designed by experienced IT staff, making it a relatively slow, as well as expensive, process.

So when the Australian Government Information Management Office (AGIMO) in the Department of Finance unveiled Govspace in March 2010, the floodgates opened.

Suddenly every agency could access a low-cost open source webCMS on pre-approved secure government infrastructure. It could be used to deliver both small specialist websites as well as services such as blogs.

Finance were trusted, reliable, secure and a central government agency - one of 'us' (government) not one of 'them' (private sector companies).

Govspace launched with a single pilot site, the Department of Treasury’s Standard Business Reporting blog. The platform expanded quickly, reaching 25 sites using the platform in a year.

I was one of the first to leap on. I worked within Health to dissuade one of our Communications teams from paying a digital agency at least $40,000 for a new website for an information campaign and convinced them to trust me (and Finance) to make use of the Govspace infrastructure - which at the time came at the very attractive price of 'free'.

Finance was able to spin the site up in a matter of weeks, WordPress was easy to use, so the Comms team was able to directly put the content in place. We had the website live within six weeks - compared to a 3-6 month process with a digital agency.

In the end we did spend some public money, about $42 on a custom WordPress theme, but saved the department over $35,000.

At an internal planning day shortly after the site went live the Comms team proudly shared how easy it had been to get the website in place. This lead to a flood of interest from other area.

That one site raised the internal awareness that the Department had been paying too much for websites, leading to enormous savings over time.

Govspace wasn't designed to cater for every site - it was primarily a platform for simple Gov 2.0-style sites, with blogs and other interactive features. Even so my team helped put at least another half-dozen new websites onto the platform over the next few years.

Even when Finance had to bite the bullet and start charging agencies for the costs they incurred for the platform, Govspace remained one of the lowest cost website options for government.

You can read the posts from the first birthday of Govspace, from AGIMO's then Branch Manager, Peter Alexander (now COO for the Digital Transformation Office) and from AGIMO's Mike T (with my comment still below).

Govspace continued to grow in use over several years, with over 110 government sites using the platform at some stage. The chart below shows the traffic for periods I've been able to source data for.



Over the last few years the site has seen a natural decline as agencies shifted to GovCMS, Drupal or their own lower cost WebCMS frameworks.

Today Govspace hosts 26 live public sites - virtually the same number as the platform had after 12 months.

With Finance's decision to close the platform all those sites will have to move to their own infrastructure by the start of 2017. After that, Govspace will be no more.

While this makes me sad, I support the decision by Finance to close down the GovSpace platform. It had a good run. However Govspace is fast being replaced by more modern web platforms, particularly GovCMS.

I'd like to personally thank all the relevant staff at the Department of Finance for how diligently they ran and maintained the platform, even after AGIMO was disbanded and running a whole-of-government infrastructure stopped being an important role for the department.

While for many inside and outside government the closure of Govspace might be seen as just the termination of a 'surplus to needs' service, I believe this is the end of an era for government IT.


Govspace was instrumental in revolutionising many aspects of how Australian government viewed digital.

The platform helped transform how Australian government agencies looked at website development and costs.

The use of WordPress for a public whole-of-government platform also widened the door for open source software to be considered by agencies.

Govspace helped propel government web sites from a 20th century 'brochure-ware' approach to become more engaging and interactive.

The impact of Govspace has echoed across government, and will continue to echo for years to come as agencies continue on their digital transformation journeys.

Farewell Govspace and thank you to everyone involved with the platform. Your contribution to government's digital transformation has not been overlooked.

Read full post...

Bookmark and Share