Tuesday, April 19, 2011

2011 Intranet Innovation Awards are now open for entries

The fifth annual global Intranet Innovation Awards have just opened and you have until Tuesday 31 May to submit your entry.

What I particularly like about these awards is that the judges aren't simply looking for the best Intranet, you can simply submit the best functionality or feature in your Intranet. This means that if you have a 'average' internet, but have one brilliant and innovative feature you can enter just that feature and have a chance at winning.

The four categories for the Awards include,

  • Core intranet functionality
  • Communication, collaboration and culture
  • Frontline delivery, and
  • Business solutions
Full details of the categories, with examples, and the scoring criteria is available on the entry page.

Read full post...

Monday, April 18, 2011

Advertising agencies, digital agencies, web developers & printers - you need to understand government's online requirements

It has been an interesting experience working with advertising and digital agencies, web developers and printers while in government - particularly having been on the other side myself for more than ten years.

While some are very good, others definitely 'need development' - particularly in the web delivery space.

Government has a number of requirements for websites and other online properties, however it sometimes appears that these are not always well understood by service providers - or maybe it is simply that some may occasionally seek to 'cut corners' on quality to increase profit margins.
 Service providers are expect to know the mandatory government web requirements when responding to government tenders. As AGIMO states in the WebGuide:
Service providers should be familiar with the Mandatory Requirements and the other guidance provided by the Web Guide when responding to Australian Government tender processes for relevant services.
Below is a list of things that service providers really, really need to know when building Australian Government websites:
  • Complying with WCAG's accessibility minimums is a mandatory requirement for government
    I've been told by supposedly experienced (private sector) web developers that the Disability Discrimination Act 1992 doesn't apply to government, and that it is optional for governments to meet WCAG requirements as it is a 'non binding international agreement'.
    I've also been told by web developers that they won't implement some accessibility features because they 'believe the site is accessible enough already' - despite not meeting WCAG standards.
  • A scanned document turned into a PDF isn't accessible under WCAG 2.0
    Telling me that a scanned document - essentially an image - is accessible to screenreaders if it is converted to PDF doesn't communicate that you're a 'web professional with more than 10 years experience'.
    A Microsoft Word document or InDesign file converted to a PDF also won't meet the Australian Government's minimum standards.
    When you provide PDFs to government, if you are not also providing the content in an alternative accessible format, you will often not meet your contractual requirements.
  • You must include a privacy statement, disclaimer and appropriate copyright notices on government websites
    Telling government staff that a 'Website privacy policy is only necessary if you're collecting email addresses or other information online' is incorrect and creates significant risk for your client.

  • Government Departments can use social media channels
    There is no stricture forbidding Government agencies from using social media channels for communication or engagement activities. In fact many already do - and often in more advanced ways than the private sector.
    There's also no 'conclusive study showing that Australians don't want to associate with agencies or government campaigns via social media channels'.
    There's also limited need for government to engage 'social media experts' who don't understand how to use social media services - such as having a Twitter account that doesn't use hashtags or retweet others or writing a Facebook strategy that just lists the standard Tabs and doesn't provide evidence of expertise in using 3rd party applications or iframes to customise a Page.

    Having an account illustrates you're aware of a channel, using the account well demonstrates your expertise.
  • Building a fake persona on a social media channel then revealing it as fake and a government promotion can be considered false and misleading practice
    Suggesting to a government agency that they should create fake personas and interact as though they were real, build a following or trusting friends and then unveiling the activity as a campaign at the end isn't good advice to provide any organisation.
    Sure there's LonelyGirl and the Jacket Girl, and several other instances of actors used to create fake personas - but never by government agencies. Providing the truth is important in government campaigns and being authentic is important to build trust and respect online. Creating fake personas usually isn't conducive to these and can also break the acceptable usage terms of services such as Facebook (which you should read).
Finally here's some tips - collected from discussions with my peers across a range of government agencies and jurisdictions:
  • We don't need you to build us a CMS and we don't want to finance the creation of your own 'you-beaut' in-house CMS and then pay you every time we need it upgraded. Consider building expertise in an off-the-shelf product - particularly an open source platform with global support.
  • Frontpage doesn't qualifies as a modern web development tool used by experienced professionals. It also leaves code in your pages if you don't edit it out (caught!)
  • We do often notice when you copy code and leave the original author's name and credentials in the (web page) source without appropriately compensating or crediting them.
  • Everyone knows that designers love arty fonts, but if the government agency doesn't own the rights to them they can't use them. 
  • Making all the text links in a website into images isn't a good idea - it makes them inaccessible!
  • Audience usability testing should almost always be a required step in web design. Even if your random sample of three staff really liked the design and could use the functionality, what does the website's audience think?
  • Background music is never acceptable in a website. Self-playing video is only acceptable where there's accessible alternatives and the video can be controlled by the user.
  • Government agencies don't want to pay for your custom reporting system that only you can access so you can give us interpreted results for web traffic. Use a standard web-based platform and give the agency access to the reports.
  • Don't tell agencies it will cost $5,000 per month to host a small government website via your ISP. Particularly when their website lists their prices (up to $30 per month) - oops!
  • When a government agency asks for an email newsletter system with double opt-in subscription, bounce detection, automated unsubscribe, open and click-through reporting, simply using a web-form to collect email addresses and sending emails via Outlook is not a quality outcome.
  • When asked to design a website for an agency to implement in-house, don't provide code or custom functionality that can't be used or build on the agency's platform.
  • It doesn't cost $10,000 to add a share button / reporting system / embed a YouTube video into the website - particularly when the agency is providing all the code for you.
  • You're not a 'Government 2.0 pioneer' if you've never heard of the Gov 2.0 Taskforce, the eGovernment Resource Centre or this blog. Knowing Obama used social media in his first Presidential campaign no longer earns brownie points.
  • Even if this is 'the first time' a government agency has asked you to make a website or PDF accessible to WCAG 2.0 standards, that doesn't mean that your previous standard will meet current government needs.
  • Just because your contact in government hasn't had previous experience developing websites doesn't mean they aren't supported by people who have a lot of experience.
Any other gems out there that people are prepared to share?

Read full post...

Wednesday, April 13, 2011

Round up from the Canberra Gov 2.0 lunch

Several people have blogged about today's Government 2.0 lunch, and I've linked to their posts below.

I also took some notes on Alison's talk, as follows:

Community Management
Tools/tech are not community. Community is about the people and their relationships and may, or may not, be formed using all different kinds of tools.

Three roles of community managers
  • Leader - guide, initiator
  • Participant - listener, curator
  • Advocate

Risks of communities
  • Legal - terms of use, copyright, etc
  • Departmental - reputation, internal rules
  • User risks - behavioural, personal attacks, bullying, suicide, self-harm

Risk mitigation
  • Timescale for non-permissible content being live (if post-moderation)
  • Community guidelines - separate to terms of use (impersonation, sock puppets - multiple accounts, etc)
  • Content assessment chart (what is permissible, not permissible)
  • Escalation policy
  • Internal community guidelines

Other notes
  • Community management is not a 9-5th role (what are you going to do with the other 140hrs per week, public holidays, staff holidays, etc)
  • Pre-moderation not recommended as it stifles discussion, but it may sometimes be useful in sensitive discussions.
  • Never delete content - just hide from public view (keep reasons, why removed, who did it)
  • Facebook can be a pain due to its lack of capability to hide comments rather than delete them
  • Don't pre-guess your community by deciding on the topics that should be discussed - such as in a forum. This can fragment the community into groups too small to be sustainable. Instead first build the community, then open up specific topics based on need.
  • Ensure you set context for the community, otherwise you might find the community takes its own direction without your influence.

    Project CODE
    Also at the lunch, Professor Rachel Gibson of the University of Manchester presented an overview of Project CODE (Comparing Online Democracy and Elections), a UK-funded project looking at the impact of social media use by politicians and citizens on the outcomes of elections, focusing on the US, UK, France and Australia.


    Other blog posts about the lunch

    Read full post...

    Tuesday, April 12, 2011

    The journey to social public service

    We often talk about the professional values of the public service - honesty, integrity, respect, courtesy, care and responsibility.

    These professional values comprise a major part of the Australian Public Service's (APS) Code of Conduct, and similarly are prominent in many public service codes and charters in Australia and around the world.

    They aim to define and shape the professional behaviour of public servants in the interest of better governance.

    However in many of these codes and charters, again including the APS Code, there's one extremely critical behaviour that isn't named. Communication.

    Perhaps this is because communication is assumed to be at the core of other professional values, perhaps it is believed that communication is implicit in any act of public service.

    Whatever the case however, communication - social interaction between individuals and groups - is necessary in virtually all public service activities. Improve communication and other improvements follow - understanding, information exchange, engagement, efficiency, physical outcomes.

    If we consider improving communication as one of the key ways to improve the effectiveness of any public service, then it is worth considering the impact of poor communication.

    What does this look like? Individuals that choose to not share their experience and learnings. Siloed teams that hoard information to preserve their jobs. Hierarchical structures with communication bottlenecks. Agencies that take the view that they own data collected with public fund and that cannot be shared with other government agencies, let alone the public.

    In all of these cases the solution isn't always to hold an enquiry, change processes, break structures apart (or put them together) or even change leaders.
    However the solution must also involve increasing communication - sharing data, information, experience and best practice so that individuals and teams alike can grow, adapt and improve their effectiveness.

    In the corporate sector this is often termed a 'social business', one that recognises that its survival and success is based on making every staff member as effective as they can be, tearing down any barriers that reduce their individual or collective prowess.

    In the public sector I call this a 'social public service', one where there are open lines of communication across professions, programs and policy areas. Where both individual and team learnings are shared - not just within a team, but across the entire public service. Where individuals are valued not by the knowledge they horde, but the knowledge they share and their personal contribution to the net wisdom of their team, branch, agency, entire service and across multiple services at various levels of government and in different jurisdictions.

    I've glimpsed aspects of the social public service across the Government 2.0 community, where many people are willing to share their experiences with others in other agencies and at different levels of government. I have also glimpsed it in certain professional groups in government, where Fraud officers and Freedom of Information units share experiences across agencies in order to build their own capabilities, at conferences and at events.

    However once people return to their own agencies the budding social public service seems to fade almost into non-existence. Occasionally it is useful to know who to call in another agency for information or support, however the widespread and collaborative creation of knowledge and best practice still remains in its infancy.

    Over the next ten years, as the Government's Gov 2.0, APS reform and innovation agendas unfold, and as we see a new generation of public servants, digital natives used to social media interactions, take on increasing responsibility, I believe we'll also see an increasing trend towards a social public service.

    In fact I believe there's few ways that any of the 'old guard', who built their careers on silos and hoarded knowledge, can slow or stop this trend. As society and policy grows in complexity, individuals will increasingly specialise in smaller areas and, rather than forming new and smaller silos, will need to interact with each other to form a holistic policy and societal view.

    This mirrors the progression of the sciences, which started as an undifferentiated topic - 'scientists' who studied the entire world around them - and fragmented into specialised disciplines. These disciplines, similar to the public servants of today, formed silos defined by their area of speciality and then, over the last twenty years, have begun re-converging, with many major discoveries coming from the combination of specialists from different fields.

    Equally we're seeing more and more public policy issues that cross 'traditional' portfolios. There's more and more collaboration between government levels and increasing requirements for people to cross-skill.

    This progression will drive the impetus towards a social public service, supported and facilitated by an array of communications tools, amongst them - and possibly the most important - social media, used to collaborate, communicate and empower.

    So what will this future social public service look like?

    Possibly flatter and more fluid, with cross-functional groups formed as needed to develop a given policy, manage a project or program or deliver an outcome, less loyal to departments, divisions and branches and more loyal to the public service as a whole, more adaptable to change, less separated by portfolio or layer, more focused on customer service and definitely more communicative and social.

    Read full post...

    Friday, April 08, 2011

    Should the government be leading on computing energy-efficiency?

    As government increasingly digitalises, one of the hidden costs is the increase in electricity use by government computers and servers.

    More computers equals more power use, more cost and, ultimately, more strain on electrical generation across Australia.

    So a practical way for the government to prompt energy-efficiency, not only for the government itself but across the country, may be to mandate the electrical use of the computing devices and data centres it is willing to buy.

    We've been seeing some companies with a large data footprint looking to reduce their power use per device for a number of years now.

    Google has led a massive program to reduce power use across the hundreds of thousands of servers it needs to deliver the most popular website in the world. While search is the company's main business, their main cost is power, so it makes good economic sense, as well as good environmental sense, to minimise the power they need. Google unveiled their work several years ago and releases data quarterly on their data centre performance through its Google Data Centers website.

    Facebook, which has begun competing with Google for the top global site position, has now come out and made its data centre design open source, freely available for other organisations to use. As discussed in this article from ZDNet, Facebook open sources its server, data center designs: Hardware fallout to follow, the strategy is designed to reduce costs for Facebook, as well as prompt large hardware manufacturers to focus on improving the energy efficiency of their servers.

    More information is available at Facebook's new Building Efficient Data Centers with the Open Compute Project page and at OpenCompute. We're not talking small savings here - Facebook reports a 38% reduction in energy use coupled with a 24% reduction in costs in one data centre.

    Imagine if government took a leading position on energy-efficiency for computers and data centres. With over 162,000 staff in the Commonwealth public service and around 5,000 websites, there's massive scope to encourage positive structural change in the computing field.

    Like Google and Facebook, government's job is not to design the most cost and energy efficient data centres.

    However there's potentially massive cost savings and economy-wide efficiencies if we introduce policies which encourage data centres to continually reduce their energy costs.

    Read full post...

    Bookmark and Share