Tuesday, January 31, 2012

Should Ministerial staff reveal their affiliations when commenting on political matters online?

Much of Australia's population doesn't realise there is a difference between Australia's public servants, who are employed and work for the state in an apolitical fashion, and Ministerial and other political advisers and staff, who are employed and work directly for politicians and political partie.

However there is a crucial difference at the moment as to how these two groups are expected to behave online.

Public servants work under a public servant code of conduct and, both federally and in most states and territories, there's also specific guidance for social media conduct. This generally includes the requirement to identify oneself appropriately when speaking officially (on behalf of an agency) or in a professional or personal context.

However the situation isn't the same for political staffers, who may not always operate under formal social media conduct guidance. This can lead to situations such as this one, Party trolls shall not pass, or be named, recently published in the Canberra Times.

Given the events on Australia Day, and much of human history, it's clear that a combination of passion, youth and ideology can lead to errors of judgement - some more serious, some more minor.

Now what may you get when you combine passionate young political party supporters with social media?

Clearly there's a lot of potential for risk, which could also affect other online engagement activities in government (by politicians or by agencies).

So how should this risk be managed?

Should there be a bi-partisan code of conduct for political staffers engaging on social media, perhaps even an independent watchdog to monitor activity?

Should individual parties 'manage their own backyards' - albeit in potentially different ways and with different tolerance levels?

Or is the current approach OK?

Read full post...

Friday, January 27, 2012

When will we see gamification in government?

Gamification refers to the practice of making non-game activities more like games by incorporating achievement-based reward systems.

Under gamification, using government examples, when your project or mission is complete you might receive a 'completion badge' (such as a letter from the Secretary, an Australia Day Award, or a medal). Or when you attain a higher level of proficiency in a particular skill you'd receive an 'achievement' or rise on the 'leaderboard' (such as a bonus or a promotion).

From the examples above, there's clearly already aspects of gamification at work. Rewarding achievement, success and skills acquisition is a standard part of business and forms the basis of merit-based advancement systems - not just games.

However the gamification process involves a much greater level of achievement-based recognition, than has commonly been used in organisations.

Rather than six-monthly and annual reviews and awards, gamification is based on rapid, but less valuable rewards for achievements as they occur.

This is an effective behaviour modification approach, as both the gaming and game industries would testify to. Rapid gratification means that patterns of behaviour are reinforced at a deeper level, resulting in a greater likelihood of the desired behaviour being repeated.


Gamification has begun to have a significant impact on a number of businesses. Online badges and achievements are the basis for the success of services like FourSquare and contribute indirectly to the success of services such as Facebook and Twitter (through the size of your friends list and the frequency that people respond to your posts).

They are also widely used by airlines (frequent flier miles) and supermarkets (shopper dockets and petrol discounts) and have promotional uses in many other industries (scratch and win tickets and similar).

To-date these gamification tools have been primarily deliberately used for marketing purposes - to influence customer behaviour (although mostly for commercial purposes and extremely rarely in government communication campaigns).

However with the announcement of the addition of achievements, badges and a leaderboard to Microsoft's Visual Studio coding community, it is clear that the shift to using gamification for training and employee management is already beginning.

Where will this go in the future in government and in business I wonder.

Will employees begin receiving achievements for completing specific courses and mastering skills their employers wish them to master? Perhaps even one for joining the company, and one for each year's service?

Will there be leaderboards based on standardised performance on specific tasks (brief writing or timeliness of ministerial responses - using an algorithm that compensates for frequency and complexity of briefs)?

Will these achievements, badges and leaderboards begin to influence promotional prospects or pay rates - even holidays (turn in five badges for an extra week of leave)?

Will organisations take on the example of armed forces, who already issue achievements and badges to motivate and recognise achievements and where leaderboards do influence access into elite units and specific roles.

I guess we'll have to wait and see how far gamification will go in government, and in business. However the experimentation has already begun.

Read full post...

Wednesday, January 25, 2012

Don't forget the why of Gov 2.0

In any job it is easy to get caught up in the details - the what and how of what we need to do, day in and day out, to deliver the outputs demanded of us.

Whether it's writing a brief, building a website, managing a social media channel, responding to a crisis or some other activity driving our actions, the focus is on what we need to do and how we need to deliver.

However amongst all this activity it is important to take time out periodically to consider why we are doing what we do.

What is the purpose of our activities, what are the outcomes we want, not simply the outputs.

This is particularly important for Government 2.0, which is essentially a set of strategies, tools and techniques - not a goal in and of itself.

When, as an individual or an agency, we decide to use social media to communicate or collaborate with our stakeholders and citizens, or release data in machine-readable formats for reuse, we need to consider why we are taking these steps. What is the goal we're trying to accomplish, or the change we're trying to make.

We shouldn't be engaging in Gov 2.0 activities because of the 'bling' of working with cool technologies, the thrill of doing something new first or the kudos from peers, speaking engagements and awards.

The Gov 2.0 activities need to help us deliver on the why we are there. Helping the public to make better choices, helping government better understand its customers and what they need to live full and rich lives.

Government 2.0, just like government, is a tool to achieve a desired goal - a happy, healthy, fair society where everyone can live securely and with mutual respect and understanding under a transparent and accountable system.

So stop, take a breath and consider why you're doing what you're doing. Think about whether you've picked the right approach - the 'how'- and whether there's more, less, or different things which you could do to best achieve your why.

Put your why first - decide why you are going to do what you are going to do - before you decide what you will do and how.

Also consider the video below - the power of considering the why - it can do much more than assist aligning your Government 2.0 initiatives, it can reshape organisations or revolutionise the world.

Read full post...

Monday, January 23, 2012

New Inside Story policy: provide your full name for publication or your comment won't be published

I have had a great deal of respect for the Australian Policy Online (APO), produced by the Australian National University and University of Swinburne.

For several years the site has been a fantastic venue for serious discussions of public policy options, and a very useful source for policy resources and research. The site also, without prompting from me, republished several posts from this blog.

However, after commenting on an article in the Inside Story section of APO late last week, I received an email from the editor pointing out a change in their commenting policy.

Now anyone who submits a comment to Inside Story, as part of APO, must provide, and be prepared to have published, their full name. This new policy is detailed following their full articles using the text as below (highlight is mine):

Send us a comment

We welcome contributions about the issues covered in articles in Inside Story. Well-argued and clearly written comments are more likely to be published, and we’re now asking all contributors to provide their full name for publication. Because all comments are moderated, they will not appear immediately. Your email address is never published or shared. Required fields are marked *.
Now while I appreciate the sentiment of an editor who wishes to avoid spurious comments from people using pseudonyms or commenting anonymously, I found myself uncomfortable with the prospect of a website that forces anyone who comments to publicly reveal their real name in full.

I wrote a piece about this very topic a few months ago for Mumbrella, Toughen up - we need online anonymity, which discussed the various pitfalls involved in forcing people to reveal their real identity.

While I am sure it isn't the intent of this policy, one major risk - particularly relevant to a policy discussion site - is that of excluding certain groups from the conversation.

This includes people who, if their identity is published, may face physical or financial risk, those in witness protection programs, people who fear online attack if their views are taken the wrong way, those involved with policy making who have suggestions or questions, those under the age of 18 and more.

In many policy areas there are people who need to be cautious about revealing their real names publicly for legitimate reasons - whether the topic be health, law and order, immigration, development, gambling, climate change or something else.

While it is the right of each publication or website to define its own moderation and publication policies, the effect of this policy may be to silence people who have valid and important contributions to make, reducing the richness, robustness and usefulness of discussions.

If the primary concerns of Inside Story's editor and publisher are inappropriate comments, defamation, personal attacks and the like, these can be handled through pre-moderation (which they do already), backed up by a public moderation policy and community guidelines (which I cannot find in their site).

Alternatively Inside Story could require people to register and provide their real name in their account details, then publish comments under a name or pseudonym that the user selects. This would ensure they had real names if needed and allows regular contributors to maintain a consistent identity while still providing them with sufficient room to make valuable comments that otherwise they may not feel comfortable doing.

When Inside Story's editor, Peter Browne, (also credited as the Commentary Editor of Australian Policy Online) emailed me last week to ask if I was happy to have my comment published under my full name I thought about it for a few minutes and then decided that while I didn't mind my name being connected to my comments, it was time to take a stand, the damage to the public conversation could be too great. So I said no.

I won't be commenting further on Inside Story or Australian Policy Online while their current policy is in force, nor will I spend as much time reading the site. They remain welcome to republish my blog posts (which are licensed under Creative Commons, so I can't really stop them even if I had wanted to).

This decision may make me slightly poorer, however I believe Inside Story's decision significantly weakens their effectiveness and inclusiveness. The unintended consequence of forcing people to have their full name published alongside their comments is to make all of Australia poorer by stifling public policy discussion, particularly amongst those whose views most need to be heard.

I hope government agencies do not follow the same course on fulll names. It would severely restrict the value of the online channel to collect input on policy consultations and thereby make good policy harder to develop.

For the record, I've included a copy of my email exchange with Peter Browne, Commentary Editor of Australian Policy Online and Editor of Inside Story:
From: Peter Browne
Dear Craig, 
I’m not sure whether you noticed, but we now ask people commenting on articles to provide their full name for publication. Are you happy for your full name to appear with this comment? 
Cheers,
Peter Browne
Editor
From: Craig Thomler

Hi Peter, 
I didn't notice this policy change. I have now looked through your 'about' pages and see no mention of this - nor of your moderation policy. 
I would normally be happy for my full name to appear on my comment, and all my comments online are made on the basis that people can track down and find out who I am if they wanted to. 
However I'm not comfortable with a site that forces people to provide their full name publicly. This requirement prevents many people from commenting - those in witness protection programs, minors (such as 17yr olds), those concerned about stalkers, bullying, identity theft, privacy and so on. 
I see your policy as reducing the potential for open public dialogue without providing any safeguards. A backward step that only damages your reputation. 
It is also impossible to enforce anyway - people can use fake names and email accounts, thereby making your policy useless.
If your concern is around identity, have people register and use a unique username (which may or may not be their full name) - you still have their full name in the background, however they are not exposed publicly. 
If your concern is around inappropriate content, this should be managed through anti-spam and moderation techniques, potentially using the registration process above to allow you to identify and manage persistent offenders (where IP address isn't enough). Your moderation policy should be published so that commenters understand the basis on which they will be assessed. This is simply a matter of respect and setting the context of a discussion - similar approaches are used in face-to-face meetings. 
So in this case, I decline the publication of my comment and will not comment further on APO until your policy is adjusted to not require the publication of full names and is made easily accessible in your site along with your moderation guidelines. 
I will also be publishing this email in my blog to show the perils of requiring full names and linking to my post for Mumbrella: Toughen up - we need online anonymity (http://mumbrella.com.au/toughen-up-we-need-online-anonymity-58441). 
Cheers,
Craig
From: Peter Browne

Dear Craig,
My view is that if writers use their own names then responders should too. The policy is at the bottom of each article, just above the comment field. 
Cheers, Peter

From: Craig Thomler
Hi Peter,
Thanks for pointing this out. I had looked for dedicated 'Community guidelines' 'Comments policy' or 'Moderation policy' pages and looked at your summary articles, where I can still register or log-in to comment, but do not see the same message.
I now have looked at a full article and can see the text. It remains unclear on what basis you moderate.
Here's an example of what I mean by a moderation policy: http://myregion.gov.au/moderation-policy
I appreciate you believe that writers and commenters should have the same rights - although writers are often contributing for different reasons and have different agendas for expressing their views, some are even paid to do so, directly or indirectly (aka not necessarily by you). 
It will certainly be interesting to see how you decide to represent the writer when you receive an article from someone in a witness protection program or a whistleblower, and how you will treat comments. 
Cheers,
Craig

Read full post...

Friday, January 20, 2012

Should you design websites for the '1%'?

A concern I’ve had for the last ten years is how websites are designed and approved by organisations (both in government and the commercial sector).

In a better-than-average world, when asked to develop a new website or improve an existing one, the web team goes out to discover what users think of the site.

This involves identifying the site’s key audiences and using surveys, focus groups, other research and past feedback to identify good and bad design and usability features. After this the team come up with concepts, tests them on audiences and refines.

 (In a average or worse world the web team isn’t given the time or resourcing to do all this research, so short-cuts the process with their ‘best guess’ design improvements based on feedback and experience. This is far too common but can still deliver improvements.)

When the web team reach final agreement on a few design alternatives, they go to senior management for approval, often with a detailed case explaining all the design decisions.

And this is where the process breaks down.
  • “Can you make the website more blue? I want it to be bluer.”
  • “I like (pick a random site visited in the last day). Can you redesign it so that our website looks just like that one.” 
  • “I don’t use search, I use menus, so can you move the search to the bottom right of the page” 
  • “I don’t believe anyone wants three columns in a webpage, please restructure to two columns.” 
  • “It’s too hard for me to find anything, can you simply list all the main site categories and pages in the homepage.” 
  • “We’d prefer to organise information by our divisions rather than by subject, I’m sure that would be much easier to understand” 
  • “We actually wanted the website to look just like the printed brochure” 
  • “I like the shirt I am wearing today, make the website the same colour”

Suddenly web teams have to reassess what they are attempting to deliver and who they are delivering for.

Their collective expertise and research is no longer relevant.

The audience of the site is no longer relevant.

They are designing for one person, or a small group of people – decision-makers who are often not the target audience and possible don’t even use the website.

This is a source of great frustration for web teams. They are no longer designing for the 99% of their audience, they are designing for the 1%.

Now what if this process was turned on its head...

Rather than having an executive or Minister approve a website, we instead released several near final designs for A/B testing on online audiences (as organisations like Google, Amazon and Microsoft do), a proven and effective technique, or took the final couple of design alternatives and put them online for the public to vote on and thereby approve.

Of course there would still need to be some level of senior executive involvement in defining the organisation’s overall requirements for the website. The site does have to meet the organisation's goals.

However the actual approval would come from the audience, the 99%, people using the website, the people you wish to communicate with, support, engage or influence.

Radical? Maybe.

Effective. Certainly.

Doable?

Read full post...

Bookmark and Share