Archive for the 'Thoughts' Category

Wordpress 2.7 - Impressive!

I’ve just upgraded my blog to the latest beta release of the Wordpress platform, 2.7 Beta 3.

On the whole, I am extremely impressed with the new admin interface. On first glance, the interface is cleaner, my templates and ALL my plugins appear to be fully functional in the new environment. The dashboard, is easier to read and with the addition of drap and drop ‘web parts’ the screen can be customised to the users own requirements.

One of the problems I have found so far (and this only appears to affect those with a sidebar (Delicious) in Fire Fox 3), is the web parts on the right hand side of the screen seem to creep into the WYSIWYG editor. Ok, this is a minor fault in a beta release which I’m sure will be resolved prior to releasing to market.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Thoughts on “Read Write Gov”

Yesterday, a colleague and I attended the first Read Write Gov event, held at Peterborough City Council. There were three very good presentations from Dominic Campbell, Steph Gray and Hadley Beeman, in addition to the practical workshop arranged by Dave Briggs. For the first event, the attendance was around 20 individuals, many from Cambridgeshire with some travelling from as far away as Coventry and Great Yarmouth.

Upon arrival I managed to speak face-to-face with numerous contacts in Twitter, discussing ideas, development platforms and a whole host of other things.  This is one of the key benefits of Twitter; it aided in ‘beaking the ice’ as the vast majority of delegates were already communicating in the online world.

Dave Briggs commenced the event with introductions and background on the speakers and opened the floor to the first speaker, Dom Cambell.

Dom Campbell, of the FutureGovConsultancy is currently employed as the Interim Social Media Manager at the London Borough of Barnet (LBB). LBB have been doing alot of work around engagement, consultancy, advertising and discussed gaining value from the social media tools that are implemented. Dom referred to the WhereILive website, a community focused, interactive website, targetting engagement with the residents along with the leaderlistens blog.

Dom discussed how LLB’s implementation of the Google Alerts service has proactively enabled the Authority to deal with comments being posted online about the Authority. This is something that I have already implemented at GYBC. Already the findings are interesting and I feel this is something that will be of benefit in gaining feedback and response to the launch of our new site.

Steph Gray, Social Media Manager at DIUS presented the issues and problems around making social media happen in Government. Steph’s presentation began with the phrase “I want one of those”. Steph discussed the problems of implementation and the commitment, technology and follow up required to ensure the request is delivered, required and maintained. Steph provided a the following 10-point list of key aspects to consider when implementing social media within Government.

  • Interactive websites need interactive organisations
  • Focus on content, not platform
  • Find and support the pioneers and champions
  • Be honest about scope and boundaries
  • Protect information that needs to be protected
  • Integrate with other sites and channels
  • Make it FUN
  • Enable remix
  • Enhance progressively - accessibility, interactivity and engagement
  • Evaluate intelligently and share openly

The final presentation was given by Hadley Beeman of the London Deanery. This presentation in particular was of great interest to me, as this covered the issues and considerations required to be met when developing a new application.

Hadley presented the Synapse system, a collaboration tool between the London Deanery, NHS Trusts, Students and a whole host of other individuals and organisations involved in the development and training of junior medical staff. The system is effectively a central hub of communication, based at the London Deanery, developed mainly with PHP, my preferred web development language. The collaboration tool is designed to remove the paperwork present in the current manual system, provide additional value to the users and simplify, if not remove, the vast majorit of manual processes undertaken.

Hadley and her team began the project back in February. As there were no initial ideas as to the business requirements for such a system, Hadley was granted a research period of two months inorder to understand the needs and requirements.

The system involves a user dashboard, a “one stop shop” for students to find out the information that affects them during their studies. One of the key functions that was highlighted was the ease of enabling students to find out which individuals play key roles in their development, a system previously undertaken using a complex formula.

Hadley raised a number of issues that were encountered during development and also issues that had to be overcome due to previous problems. One of the key issues was around scepticism of the systems’ success and the other on security. Due to the publicity and concern around the previous doctor application system was implemented, the attitude has been ‘once bitten, twice shy’.

The final activity was a workshop called the social media game. The game involved delegates drawing up project requirements and then identifiying social media tools that could assist with the projects requirements, within an allocated budget.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Thoughts on ‘Building The Perfect Council Website’

On the 16th July, I attended the SOCITM Insights/E-Gov Bulletin Event entitled “Building the Perfect Council Website”.

The day was very interesting and the key note speech by Gerry McGovern gave everyone some excellent ideas to take back and also sparked some controversy. I’m not sure how some of the suggestions would go down within the corporate environment, however, there were some very good points all the same.

The main points that came out of the key note were:

  • Don’t keep your customers on your site for any longer then needed to allow them to complete what they came to do - remember the customer is time poor.
  • Customers should not need to understand the organisational structure in order to complete a task.
  • We take their money and time, the customer will only be more frustrated and angry if they cannot complete the task they want to - promptly.
  • Focus on what the customer is trying to do, attempt to complete the tasks your customers undertake and experience the journey for yourself.
  • Ensure the navigation is appropriate - not focused around organisational structure.
  • Make the top tasks are ‘do-able’ from the homepage, keep these tasks up-to-date and ensure the website is customer centric.
  • Remove press releases, policies and strategies - these are non productive, and, who reads them anyway?
  • Remove 90% of the content - it’s not maintained, never read and is probably there as a FOI dumping ground. The content should be productive, efficient, relevant and to the point.
  • Testing and improving the website should be a continual, relentless process.
  • Being with the customer is the essence to managing websites - 80% of web management is focused around observation.
  • Stop the political messages (Our leader says…).
  • Do not use the website as justification of purpose.
  • Remember - great websites are ugly but functional.
  • Boredom is the worst reason to change the website.
  • Remove Government jargon and other acronyms - revert to plain English - this will assist with search.
  • Page titles should be unique - remember people control search and not organisations.
  • Use the website as a medium for channel shift away from the contact centre - NI14.
  • Personalisation doesn’t work.
  • Councils must remember that the “We are not the centre of the universe” - the customer is.

One of the key points that struck a chord with myself was about the removal of irrelevant content. My Councils site, like many others, has been used as a repository for storing “stuff” that is out of date and irrelevant to the customer, but may assist with FOI requests. When in reality, this is rarely the case; it only makes the management of the site more complicated; decreases search functionality, make navigation harder and irates the customer. Instead, the website should be split into three sections, transactions/core information, corporate data and an archive.

The customer should be able to undertake prompt electronic transactions with the Council and then continue with what ever task or activity they wish. Relevant, efficient and productive information and content should be written in plain English, easy to navigate to and find within the search. Finally, the endless store of information and “stuff” that the Council produces (strategies, policies, press releases etc) should be stored within an “archive”; easily accessible by search should a user require such information. However controversial this may be with some, this will assist with channel shift and encourage online interaction with the Authority and, ultimately, improve the customers journey.

The other key point was around personalisation. I feel that personalisation assists the customer in their journey and is an excellent tool, used in the right context. Personalisation works extremely well for Amazon, Ebay, Play and other big online stores. They can suggest items that you may be interested in based around previous purchases and searches.

I am initially looking at personalisation on a smaller scale. There are different elements of personalisation, each of which have different impacts on security, privacy and ultimately, the user. In my opinion, the two key forms of personalisation are:

  • Anonymous personalisation - predominately session based - focused around basic information provided by the user and doesn’t require the storage of personally identifiable information.
  • Authenticated personalisation - Targetted to individual users and requires users to be registered and authenticated against a database/other system prior to being granted authorisation to priviledged information.

My Council is currently implementing a Web Improvement Project that will enable us to provide a new, more accessible website and a structured framework to further develop upon (more on this later). Some of the changes that my Council will be implementing in the first instance, will be focused around non personally identifiable information, as such as the customers postcode. This will enable the homepage to be customised to where the customer lives and provide information on the day bins are collected, find out who there Councillor is and so on. However, should a user not wish to provide such details, this will not impact on, or restrict their journey. Ultimately, as other systems are integrated with our new website, we will have to implement authenticated personalisation for areas as such as Council Tax and Benefits.

The other key seminar was “The use of Web 2.0 techniques on Council Websites”. This seminar had speakers from Jadu, Redbridge and Devon County Council.

Having met Carl Haggerty, Web Innovations, New Media and Portal Manager from Devon County Council the night before; I had a very good insight into the develop ents that they were undertaking and how they were integrating Web 2.0 techniques into their redeveloped site. The other important factor here for myself was that both Great Yarmouth Borough Council and Devon County Council use the same Web Content Management System. As Devon were only at the development and early implementation stages with their new site, it was nice to have Steve Johnson from Redbridge to discuss their site, achievements and the resulting impacts and savings.

After attending Gerry McGovern’s Key Note and the Web 2.0 Seminar, I already had alot of ‘fodder’ to begin working with. And, to be honest, the rest of the day, and train journey home, was spent digesting the information that had been provided during the morning session.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]