How Facebook has become a risk for public servants, and what you can do about it

If you are one of the majority of public servants with a Facebook account, then it may be time to reconsider how you use the service.

As discussed in ZDNet's post, Is Facebook damaging your reputation with sneaky political posts?, Facebook is now posting messages in your timeline and saying you 'Like' the messages simply because you once 'Liked' the Facebook Page that posted them.

So what does this mean, and how is it a risk to public servants?  Here's how it works.

When you 'Like' a Page in Facebook, Facebook assumes this means you also like all the content, status updates, images and other material, that may be posted on that Page by its administrators.

To be 'helpful' Facebook will automatically place some of the Page's content in the newsfeeds of your Facebook friends, with a notice that you 'Like' the content.

Facebook calls this a feature, as quoted in the ZDNet article,

To help people find new Pages, events, and other interesting information, people may now see posts from a Page a friend likes. These posts will include the social context from your friends who like the Page and will respect all existing settings.

This may sound innocent enough, but what it means in practice is that if you ever 'Liked' a Facebook Page for any reason, any new content posted in that Page may now appear to your friends as explicitly 'Liked' by you.

As Pages can change administrator, content and focus, that innocuous Facebook Page on pet rabbits you liked two years ago may now start spewing controversial, obnoxious or otherwise inappropriate content into your Facebook friends' newsfeeds - with each piece of content indicating that you 'Liked' it.

This could merely be embarassing, or it could put your career at risk.

Say you 'Liked' a Facebook Page for a charity you support that works in a policy area covered by your agency. Due to a change in government policy, that charity loses funding and, as a result, begins posting messages on its Facebook Page which are strongly critical of the government's new policy to galvanise their supporters to write to the Minister. Even worse, one of the Page's administrators has been radicalised and frames some of these messages in very strong, almost abusive, language.

These messages begin appearing in the newsfeeds of your friends, complete with a notice that YOU 'Liked' them. Incidentally, you don't see them yourself because Facebook doesn't notify you that they're doing this and these messages don't appear in your own newsfeed.

One of your friends (a colleague at your agency) is horrified that you'd act so unprofessionally and sends screenshots of the messages with your 'Like' to HR, notifying them that you've broken the public service code of conduct by publicly criticising your agency and the government.

You get called in for a discussion with your manager and a HR representative, who shows you the screenshot and asks you to explain your conduct...

Will they believe you when you claim ignorance?


Now compound this issue by thinking about every single Facebook Page that you've every Liked.

Any of them could begin posting messages which could embarrass you, or threaten your job and, thanks to this Facebook feature, indicate automatically that you 'Liked' each message.

Even worse you don't even know when they're doing it because you don't see these messages in your own newsfeed.


So what should you do to deal with this?

Assuming that you're not prepared to close down your Facebook page or, at least, unLike all pages that you have liked, I recommend that public servants look at their 'Likes' page (accessible from their Favourites page) and cast an eye over the pages they've Liked to see if any are likely to post content that will get them in trouble in their friends' newsfeed.

Then make this a regular habit - check all your pages every month to see what they're saying.

Finally, bring this issue with Facebook to your agency's attention, so you'll not be accused of 'Liking' content you didn't.

Read full post...

View summary...

Mapping social media channels to engagement levels (based on IAP2 spectrum)

I developed the Online Engagement Spectrum around three three years ago, based on the IAP2 Spectrum  of Public Participation (PDF) and some complementary work by Bang The Table (no longer at the original web address).

As Gadi Ben-Yedah over at his IBM's Business of Government blog has begun a series of posts considering how social media can be used by government to engage online based on the IAP2 Spectrum, I thought it was timely to repost my Spectrum for people to consider.

To view Gadi's first post, go to Social Media for Public Participation: Step 1 - Inform

Online Engagement Spectrum 1.2

Read full post...

View summary...

Are Australia's web developers failing to deliver accessible websites?

In a recent story in ITNews, Accessibility checker surfaces errors, John Hibbert claimed that a new Mental Health website, www.mindhealthconnect.org.au, operated by the National Health Call Centre Network and funded by the Department of Health and Ageing, didn't meet the Australian Government's minimum web standards.

Based on a review using the ACheck tool for the minimum WCAG 2.0 'A' level of compliance, John reported that the checker:

highlighted two known problems, 245 "potential problems", 20 HTML validation errors and 115 cascading style sheet problems on the site.

I tend to always take the results of these tools with a grain of salt. Many of the reported validation errors and style sheet issues are often repeats of one single issue, or are not really issues at all, and the two known problems would take a couple of minutes to fix and do not pose direct accessibility risks at all.

However this article does highlight a concern I've had for several years - whether Web Developers, contracted to produce these sites for government, always have the appropriate skills and knowledge to develop accessible websites.

I've seen this type of issue repeated a number of times. A policy or program area, possibly with support from a central communication or IT area, goes out to tender for a website. Web Developers respond, get assessed and the successful tenderer goes about creating the site.

A few months later the site is complete with days to spare before the Ministerial launch - but fails accessibility testing by the agency.

"We didn't understand how important accessibility was to you" says the Web Developer. Note that I was in the room when these exact words were said to an agency by a reputable web developer regarding a website which was developed iteratively and we'd been giving them feedback about accessibility for a number of weeks.

So what happens next?

If accessibility was not explicit mentioned in the contract, the Web Developer asks for more cash to meet the requirement, even though it is a baseline requirement for all government websites across Australia, and says it won't be ready for launch.

If an accessibility level was explicitly agreed to in the contract, the Web Developer grudgingly assigns a junior developer to 'sort it out' - with a vague promise that it will be done in a few weeks or months.

The agency is left having to launch a website which doesn't meet the minimum and fix it as soon as possible afterwards - all because the Web Developer didn't recognise and act on the legal requirement for accessibility.

Of course there's many examples where Web Developers have done exceptional accessibility work for agencies, however I have seen and heard too many issues where professional Web Developers didn't understand the accessibility requirements of governments.

Delivering an inaccessible website to a government agency will cause that agency to break the law and expose it to enormous risks of legal damages. No vendor should ever put their client in this type of position knowingly, particularly where it is so easily avoidable.

My view is that any Web Developer that doesn't deliver a government website to at least the minimum accessible standards (unless otherwise explicitly agreed to by the agency in question) should not receive any payment until they have addressed all accessibility issues.

They should also lose their right to bid for other government business until they can prove they have fully trained their staff on accessible web design.

These may be harsh and strong measures, and I doubt they will be considered due to contractual and practical issues.

However if a vendor contracted to sell a government agency a car that turned out to not be street legal or rent them a building that turned out to not meet the building code, government would walk away without paying and ask for damages, plus be very cautious about working with that vendor again.

Why should it be any different with illegal websites?

Read full post...

View summary...

Australian government Twitter list expanded to 553 accounts

I've been working away in my (copious) spare time to update the list of Australian government Twitter accounts - representing all levels of government.

It has now reached 553 accounts - which has also forced me to start a new Twitter list due to their 500 follower limit.

You can view the spreadsheet embedded below, or access it at: http://spreadsheets.google.com/ccc?key=0Ap1exl80wB8OdHNKVmQ5RVlvQWpibDAxNHkzcU1nV2c&hl=en

You can subscribe to the listed australian government accounts using my Twitter lists:
Australian-gov-tweets (500 accounts)
Australian-gov-tweets2 (my new 'overflow' list)

I haven't yet created by level or by state lists yet - but will do so when I have time.

If you're aware of any Australian government Twitter accounts I've missed, or if your agency starts a new account, please update the list directly, or let me know so I can update it (my main issue in maintaining the list's currency is that government agencies are poor at telling people about their new social media accounts).

Please look at the Stats and By population tabs in the spreadsheet for the list to see how many accounts there are by category, state and government level, how long the average Twitter account name is, when accounts were started and the most popular months for starting accounts, plus the ratio of Twitter accounts to population at state and national levels.

Read full post...

View summary...

What should agencies do when social media channels close down?

Last week I received the following email:

Dear Hashable Users,

We regret to inform you that the Hashable mobile apps and Hashable.com will be shutting down on July 25th. The service will be unavailable after this date.

While we are still very passionate about making better connections and meeting new people, the time has come for us to focus our energy elsewhere.  

Some of you have stored valuable information in Hashable, and we want to give you the opportunity to save that data for your own records.  If you’d like to receive a file with your complete history, please log onto Hashable.com, navigate to the "Profile" tab, then to the “Your History” section on that page. You can download the file by clicking “Export full history to .csv” and accepting the dialog that pops up.

We are incredibly grateful for all the people we have met through Hashable.   Thank you for all your support, and we hope to connect with you again in the future. 

All the best,

The Hashable Team

It made me think about the situation that faces organisations when the social media tools they use close down.

How does the organisation tell people interacting with them via the service? Where will they move the community to? Can they extract and reuse any data they or their community have entered into the service? Who else will be able to access and reuse this data?

With the thousands of social media tools that now exist it is inevitable that a proportion of them will close down. In fact I've been surprised at how few have done so - largely because of the low cost of keeping them running.

Where agencies are using these services, what is their recourse? It's hard to hold a company to a service level, or sue, if you're paying next to nothing for access and the service is domiciled in another country with no local presence.


The key is to prepare and risk-manage before beginning to use these types of services.

Define why and how you'll use a social media service, what data you will be providing into the service and what data you wish to collect (and in what timeframes and formats).

Ensure you've carefully scrutinised the privacy policy and terms of use, both for your sake and for your audience - you may have an obligation to point out differences between your privacy policy and the policy of the service.

Check that the service allows you to extract your data if necessary and, if required, also confirm whether you can delete your account and purge all data.

Devise written exit plans for likely future scenarios. These should, at minimum, include:

• The social media service closing down in an orderly fashion,
• the social media service closing down suddenly and unexpectedly (for a short time or permanently),
• the social media service being bought and integrated into the offering of another company, or
• your program ending and needing to be closed down, even when the social media services you are using are still going strong.

These plans provide a framework to help you, your management and your successors to manage any shut-down in a measured way. They also form part of your governance and risk-mitigation strategy.

It's also important to put in place a regular back-up and review strategy. Back-up data from your account by downloading it every month (or if the service doesn't support this, reconsider if you're happy using it).

Also periodically review whether your stated purpose for using the service still reflects how you, and your audience are using it, and whether you need to adjust your approach or your data management policies. This review should include checking whether the service's privacy policy or terms of use have changed - avoiding the risk of the 'slippery slope' where you create your agency's account under a strict privacy policy, but find that your rights have eroded over time.

Together with the above, keep an eye on emerging services that might build on the tools you already use. I don't recommend switching horses regularly, however if a social media service important to you and your stakeholders is closing, knowing where you can move the community to maintain the conversation is important to have at hand.

As is often quoted, failing to plan means you're planning to fail.

This is as true for social media as for any other channel or project. So prepare yourself for the future by planning and keep a watchful eye on the services you use and how and why you're using them.

Read full post...

View summary...