Tuesday, October 30, 2012

Integrating LinkedIn into your agency's social media activity

Facebook, Twitter and YouTube have become the staple platforms for commercial and public sector social media engagement in Australia - driven by the level of activity on those sites by Australians.

However LinkedIn, while used personally by many in business and government roles (around 16% of online Australians - over three million people), has lagged behind in its official use, particularly by government agencies.

LinkedIn, it is fair to say, is a curious beast in social media terms. Rather than being a place where people gather socially to chat and build friendships, it is a business networking site for discussing work-related issues and sharing useful resources.

Conversations on LinkedIn are frequently quite detailed, involve case studies and examples, tend to be more fact-based and involve less emotion and opinion than is seen on social networks such as Facebook and Twitter.

While lurking is possible, LinkedIn's real value is in the meeting of professional minds on complex issues, making it far less 'fun' to use, but far more valuable to power users.

I have used LinkedIn for professional purposes for years, building a large network of people I wish to maintain contact with, using it for finding staff, researching organisations and locating particular expertise. I contribute less frequently to groups in LinkedIn, but find several are sources of great knowledge on specific topics.

For agencies the case for LinkedIn use is different to the case for other online tools as LinkedIn is less effective as a communications platform, but can be quite valuable as a recruitment, contact management and stakeholder management tool or as a source of knowledge and expertise across many professional topics.

I believe this difference in purpose has held its use back in government as LinkedIn is less often used by communication teams and more often used by engagement and HR teams - who have been slower to adopt online channels in their every day work.

However, with over three million users, LinkedIn is now becoming important for locating and assessing staff and stakeholders and needs consideration within agency recruitment and engagement strategies. Through an organisation's LinkedIn profile agencies are able to tell potential staff what they do and offer, provide access to careers and information on their key goals and services or products.

By having an organisation page, individuals working at an agency can also link themselves to it - which provides the organisation with a view of which of their current staff are active on LinkedIn and also provides a way to keep an eye on alumni for prospective hiring back or approaching for expertise and knowledge of past events.

Of course, with organisations across Australia, or internationally, sometimes having the same name, registering your organisation with LinkedIn is also important to 'own' it before someone else registers it (if they haven't already). I recall having an interesting experience back at the Child Support Agency where staff in Australia were being accidentally associated with the UK's Child Support Agency before I could establish the Australian listing in LinkedIn.

For certain agencies (IP Australia, Austrade and the Department of Industry, Innovation, Science, Research and Tertiary Education, for example), LinkedIn also offers opportunities to build business connections and lead or participate in appropriate topic groups in far more cost-effective ways that traditional 'round table' engagements.

So who is using LinkedIn right now in government and how?

Unfortunately the use of LinkedIn by agency isn't yet tracked by government social media lists, nationally, in Victoria, NSWQLD or WA.

However, some agencies have begun using it, such as the Department of Prime Minister and Cabinet, FAHCSIA and the Department of Education, Employment, and Workplace Relations which have provided a profile, but no jobs or 'products'.

The Department of Health and Ageing has gone slightly further, listing key campaigns and the Brisbane City Council uses LinkedIn to advertise jobs.

However the government agency most effectively using LinkedIn in Australia that I've come across is  Queensland Health, which has customised its landing page to offer news and updates, lists jobs and provides plenty of supporting information on joining the organisation.

This last example shows what is possible with LinkedIn to attract quality recruits and draw back experienced alumni.

Groups, which are not linked to organisational profiles, also provide ways to connect and engage stakeholders. The most notable one I'm aware of in Australian Government is AusGoal, used to discuss the open access and licensing framework being put in place for commonwealth and state governments and share relevant information from around the world.

It is possible that there are many other government groups on LinkedIn, hidden behind passwords and only accessible to a selected few, as well as the many unofficial government groups publicly listed which government staff already belong to (such as the Online Communicators Forum).

In either case these organisational profiles and groups may offer benefits to agencies beyond the use of social networks for broad public engagement. The real challenge within agencies is to rethink the management and purpose of social media - from communication and engagement with large communities, to also include the use of social networks, such as LinkedIn, in more narrow, focused and specific interactions beyond the communications sphere.

Read full post...

Monday, October 29, 2012

Why do agencies struggle with FOI and open data so much?

The linked email conversation (in a blog post), Freedom of Information Request for Classification Data, provides an interesting insight into the struggles government agencies are having with FOI and open data and with the difficulties applicants are having accessing data which should be available in reusable formats.

In this case information which is publicly available and searchable has been made less accessible by an agency in their site (breaking a site scraper). Then after the developer asks the agency for access to the data under FOI the agency (after several delays) offers to make it available for $4,000.

As far as can be determined from the information provided, the process for releasing the data - which is already in a database - simply requires a single SQL command.

The appearance is that the agency is being badly let down by its IT systems or staff - or that it is unwilling to provide the data.

Either situation is a sad reflection on the agency and on the commitment of the government to openness.

I'll keep tracking this request - as are also a number of people in the open data space - to see how it is resolved, and how long it takes to do so.

Read full post...

Friday, October 26, 2012

Remembering to say thank you to citizens

Every day thousands of citizens donate their time and energy online to help government agencies across Australia.

They respond to feedback surveys on websites, provide submissions to consultations, share agency updates on Twitter and Facebook, participate in government-run online groups, provide tips and case studies to help government campaigns help others, create blog posts, websites and pages supporting government activities and even develop apps that add value to government data.

Much of this is done out of passion and interest in supporting the community, not for direct financial or personal benefit.

So wouldn't it be nice for agencies to sometimes say 'thank you' to the citizens that support public servants to do their jobs serving the government of the day and community?

I know several institutions that have learnt the art of saying 'thanks'.

There's appreciation of the efforts of teams in government operated hackathons, the Victorian State Library has invited its largest online supporters to 'meet the team' events at the Library to recognise their selfless activities and the National Library has recognised the largest contributors to Trove in several ways.

However there's many agencies who still forget the simple art of saying thank you to people outside their own walls.

Whether it is physical get-togethers, certificates or letters signed by the Minister or Secretary, a personal email from the online team, public recognition online in a Facebook group or some other method, saying thank you is one of the most important, and human, gestures that can be made to create a positive lasting relationship.

My wife and I will always treasure this simple thank you from the WSPCA last year.

The NAB has taken another route with the video below.

So think about it. When was the last time your agency thanked citizens for giving up their valuable time  to help your agency? What can you do more of to recognise their support, and encourage more of it in the future?



Read full post...

Thursday, October 25, 2012

How should governments treat mobile apps in an age of open data?

EmergencyAUS app
I had a very interesting conversation the other day regarding the challenge of government mobile apps in the age of open data.

The example used was the EmergencyAUS app, which has been developed by Gridstone Pty Ltd.

As an app created by a commercial entity, EmergencyAUS aggregates emergency information released by a variety of state and federal agencies and presents it through a single interface.

The public can also take photos of emergencies and share them through the app. Best of all the app is free to use

Alongside this, Australian governments have also released mobile apps related to disasters and
DisasterWatch app
emergencies. Federally there is Disasterwatch, released by the Attorney-General's Department, which also aggregates emergency information from a variety of state and federal agencies.

At state level there's several emergency apps now available, but particularly notable is the Victorian Country Fire Association's CFA FireReady app.

This is available across all major mobile platforms and while it focuses on Victorian fire emergencies (including backburning), it also allows the public to take photos of emergencies and share them through the app. These photos can even be used by the CFA to help inform their staff regarding developing issues.

Essentially the commercial app and government apps are competing. They all aggregate information from openly released emergency and disaster data and all have a similar aim - to help inform Australians of critical events occurring near them or near their families and friends.
CFA FireReady


Generally governments in Australia take the position that they do not compete in providing services where commercial entities are prepared to do so. They essentially try to minimise where they compete with private enterprise.

So this example raises some clear issues. As government releases more data in reusable formats (open data), there are likely to be more commercial entities who use this data to create mobile apps or other services.

So should governments stop making apps for this data, and leave the field to commercial entities?
Should governments restrict themselves to apps for data that doesn't have commercial value?
Should governments continue to compete against private firms in creating apps?

To answer these questions I think it is vital for government to begin to think about mobile apps (and websites for that matter) as strategic assets and infrastructure rather than costs or PR tools.

Mobile apps as infrastructure

Government built the telephone network in Australia because it was not commercially viable for a private player to invest in this type of infrastructure. We're now repeating this process with the NBN. We did the same with roads, electricity networks, water networks, the Commonwealth Bank, Qantas and other core infrastructure.

However past a certain point it became viable - even desirable - to sell some of this infrastructure to private concerns, with appropriate legal safeguards in place (such as foreign ownership in Qantas and Telstra's universal service obligation).

To develop some new infrastructure governments began looking at public private partnerships - such as toll roads and utilities such as ActewAGL (the ACT's electricity provider).

These have either taken the form of co-investment in development, and co-ownership in some fashion, or the form of complete private ownership, with the government simply providing incentives, support or ideas to the private sector.

Finally there's infrastructure that government has been totally hands-off during development - such as for mobile networks and for virtual infrastructure including search engines.

Mirroring these to mobile apps (or websites), there's five categories for government to consider:

  • Critical - apps which governments consider core to its ongoing business and therefore both creates and maintains, retaining ownership on an indefinite basis (though commercial entities may create their own versions).
    ie: Emergency management apps, train/tram/bus timetable apps
  • Very important - apps which governments believe must be provided and will make, however are not critical for them to own on an ongoing basis, and therefore may sell to private concerns (with appropriate distribution and maintenance conditions and perhaps a 'resumption' clause if the private concern ceases development)
    ie: Traffic or toilet map apps.
  • Important - apps which governments prefer are developed, but are only prepared to partially invest in - via partial funding or other support or a partnership with private entities.
    ie: Crime statistic/locations, parliamentary information or library/gallery works apps.
  • Interesting - apps that governments find interesting, but not worth investing in. In this case they may release the ideas and data for the apps and leave up to private enterprise to develop - or not.
    ie: Sports field locator or health information apps.
  • Uninteresting - apps which government doesn't care (from a public benefit perspective) whether they are created or not and leave entirely to the private sector.
    ie: most apps you'll find in app stores

Based on this model government agencies need to think about the criticality of a particular app to their core business and act accordingly, treating the apps as an infrastructure investment.

Here's examples of my thinking.

Critical apps
Emergency and disaster apps can be considered critical public safety tools, provided by governments to ensure citizens are informed and supported in times of crisis.

As a core function of government, while private sector organisations may also develop them, agencies would still develop and maintain good quality apps to ensure public safety and information concerns are met.

While commercial entities may develop similar apps, this is not a reason for government to cease maintaining its own, as the government must ensure that a service is provided to the community and commercial entities may stop maintaining - or even withdraw from sale - their apps at any time, leaving a gap that the government's apps will continue to fill.

Very important apps
Traffic apps, while very important for managing traffic congestion and supporting productivity, are not core to the responsibilities of government agencies, but offer significant public value.

Therefore governments would develop these apps, but potentially may sell them to private concerns to maintain and profit from, with provisos that they deliver a certain quality of information and, should the private company decide to stop maintaining the app, the code and app go back to the agency (like an exploration lease for minerals).

The sale of these apps should be considered a cost-recovery exercise as well as pricing the value of the service to the community, ensuring that the public receive some return for the value transferred from public to private hands.

Important apps
Parliamentary information apps, such as ones providing Hansard feeds and information on proposed laws and parliamentary schedules are useful and important to government, however are not essential, or very important to government. Hence it makes sense for government to contribute to the development of these apps - financially or through support - however government shouldn't invest in their creation.

Co-investment might be done through grants or matching funds - such as if a private entity ran a Pozible or Kickstarter fund raising activity and an agency agreed to match up to $X dollars raised.
Support might include access to key individuals, research or data which would support the creation of these apps, or promotion of them through Ministers and agency media contacts and networks (potentially with a level of endorsement).

Interesting apps
Interesting apps, such as one providing the location of all sports fields in a city, might be suggested by a council or agency as an idea, based on data they've released or an identified community need. A paper prototype or business case prepared, but rejected, within the agency may even be released to flesh out and provide context and direction for the app. However agencies and councils would not deem these apps important enough to co-invest in or support, leaving it up to the private sector whether to take on and own the idea or not.

Charging for mobile apps

Another consideration for governments is whether they should charge for apps they create and manage.

I have mixed views on this. There are definitely services that government provides as 'user-pays'. Why should people who don't use the app share in paying for its development and maintenance?

Charging for an app can also provide some funding for its maintenance and improvement over time - very useful where government agencies provision for app development, but have a time limit on funding for it to be maintained and improved, updated to reflect changes in mobile operating systems or even released on new platforms as they emerge.

However in many of these cases the mobile app may not be core to government service provision and potentially could be provided by the commercial sector rather than the public. Perhaps it should be sold off, or left to private hands rather than maintained by government.

If there's a mobile app that your agency is considering charging users to buy or use, perhaps, instead, it is a candidate for sale to a commercial entity to run and maintain, with the sales price being the value of the app.

Or if it is core for government agencies to provide as part of their service mix, should it really be charged for?

In summary


When having a discussion in your agency regarding whether you should make a mobile app, or leave it to the private sector to do - or are thinking about charging users a fee to buy or use your app - it is useful to consider the five categories above and into which your mobile app fits.

If the app is core to your agency's operations it should probably be developed and managed under your agency's watchful eye. If it isn't core, you should think about how important it is and use this to frame your decision on whether to build it yourself, support a private entity to do so or simply give the idea away.

Read full post...

Wednesday, October 24, 2012

Free our data - a great presentation from Pia Waugh

Open Data advocate Pia Waugh spoke recently on the topic of freeing government data at Ignite Sydney 9 (an event where speakers get five minutes and 20 slides to say their piece).

It provides a strong view as to why governments need to open up data to the community and is definitely worth viewing and sharing.

Read full post...

Bookmark and Share