Showing posts with label information architecture. Show all posts
Showing posts with label information architecture. Show all posts

Friday, March 27, 2009

What are the best blog platforms for Australian government departments?

If your Department or agency is considering getting started in blogging it's worth considering the platforms that others in government are using to meet their needs.

Looking across the Australian government, there are now at least several different platforms used to deliver successful blogs.

For example the ABS's Statistically speaking blog uses Blogger (as I do for my blog), a free service from Google, whereas DEEWR's Training.gov.au project blog, the Austrade blog, the Australian War Memorial's blog, the Victorian Public Service Continual Improvement Network and the Sydney Observatory blog use Wordpress, also available for free, or in a paid version.

A couple of others I can't determine the system used - if anyone can tell me which system their blogs are using I'd appreciate it (including Defence, DBCDE and Mosman Library).

Considering the platforms I can identify, there's some clear benefits for agencies and for their audiences,

  • The platforms are familiar - they are in common use across the internet (therefore offer familiar controls and functions)
  • They are simple for government business areas to set-up and operate with little or no ICT involvement required
  • They are hosted through third parties, rather than requiring government investments in infrastructure and bandwidth
  • They provide the capacity to plug in RSS, photos, videos, analytics and various other tools quickly and easily - again with little or no ICT overhead

  • They offer configurable moderation of comments
  • They support single or multiple-author capabilities


In my view these are all useful in getting government blogs up and running quickly with a minimum of cost or stress. They also allow the primary focus of blogging activity to be on managing content and responses rather than on managing technology and development.

If you are looking further afield at the options for blogs, Elance has published a good article covering some of the most common blogging platforms, appropriately titled The Best Technology Platforms for Bloggers.

Read full post...

Thursday, March 19, 2009

eGovernment interoperability is a cultural, not a technical issue

This post from Oliver Bell's OSRIN blog, eGovernment Interoperability Frameworks, time for a rethink?, served to crystalise thoughts that have been bouncing around in my head for awhile.

Oliver contends that most of the technical standards for interoperability via the internet have been resolved, with commercial and citizen usage of the internet built on these standards over the last ten years or more.

He argues that the primary issues remaining are around the cultural willingness for different parts of government and different governments to work together and with the commercial sector to deliver interoperable services online.

While I am not an IT architect by training (in fact I come from a business stream), my formal education and twenty years of working experience have taught me a fair amount about how to connect systems together to achieve outcomes (not always IT systems).

In my experience there are no insurmountable engineering issues - you can always find a way to exchange data in a meaningful way using the right translators and formats.

However sometimes the engineering issues appear to be insurmountable because of entrenched interests and policies - human rather than technical issues.

These often arise, in both commercial and public sectors, out of procedure-driven cultures, political struggles, poor communication, lack of knowledge, pride or prejudice.

Solve these cultural and human issues, allocate some funds and the engineering issues around interoperability largely go away.

Read full post...

Monday, February 09, 2009

What would you do? Balancing intranet needs across corporate and local objectives

James Robertson of Step Two Designs has published an interesting scenario regarding how a mid-sized government agency can meet global needs (corporate communications, top-level strategy, culture), while also meeting varying local needs.

He's opened the floor for ideas on how to most effectively support the needs of both management and staff.

Judging by the comments so far, this isn't a unique challenge. A number of Departments and agencies are wrestling with similar scenarios and the tensions between top-down and bottom-up needs.

Take a look over at Tackling the global-local challenge?



Type rest of the post here

Read full post...

Monday, January 05, 2009

Vic government publishes intranet IA best practice analysis report

The Victorian government has published the Intranet Information Architecture Best Practice Analysis report, conducted by the IA Strategy project team in the Web Domain Group, Department of Human Services (DHS) Victoria.

The analysis is available in summary and in full from the eGovernment Resource centre.

One of the writers of the report, Suze Ingram, has also published comments on her blog as 10 Intranet Best Practice (and more...).

The best practices outlined in the report are supported by evidence statements from various intranet experts to help intranet teams support their case when arguing for improvements.

One of the most interesting sections for me is regarding adequate resourcing of intranets. To quote the report,

It is crucial to the ongoing success of an intranet, that intranet teams are treated and funded at the level of other vital business tools and projects. A successful intranet needs the appropriate staff and resources so they can research, develop and produce.

In his “Managing the Intranet and Teams” report, Jakob Nielsen’s research has calculated that the average size for a core intranet team is five people. As a percentage of an organisation’s total employees, the average proportion of people with responsibilities for the intranet is 0.27% (for an organisation the size of DHS - approximately 12,500 staff - this equates to 33 staff). Some of these team members had other job responsibilities as well; team members often worked only part-time on their intranet. Nielsen asserts that “this is a small number given that intranets are a majority productivity and communication tool for organisations”.

Read full post...

Thursday, September 18, 2008

Improving an intranet staff directory

My team has been throwing around approaches for improving our internal agency staff directory on the intranet to make it more of a knowledge resource for staff.

As this is the most used tool in our intranet (people need to contact other people), improving the service contributes measurably to our staff's capacity to collaborate and discover the information necessary in their roles.

The more we can streamline people discovery, the more time we can save staff.

Thus far discussions have focused on our own experiences across a number of online staff directories over the years.

For my contribution to the discussion, from my experience over a twenty year span, the first staff directories were based on the paper phone directories used before intranets were common - alphabetical lists of names, titles, teams and phone numbers, divided by region or area.

These lists - and intranet directories - were useful in finding a known person, were you could identify their name and area.

However they had more difficulty in locating unknown people - subject matter experts - as area and team names did not always reflect their activities and without knowing who to contact it was hard to find an appropriate name.

Also traditional staff directories are only name, number and rank - they do not provide details on skills, relationships or communities, which help link people collaborate more effectively.

Therefore I've described three cases I want our future staff directory to cover.

1) Locating details for known people

  • Finding contact details and physical locations (the basics of a directory)
  • Discovering the skills, subject matter expertise, internal networks and communities of these people (a profile-based approach to help staff broaden their engagement with others)
  • Placing these people in the organisation structure (via a dynamic organisational chart - therefore enabling staff to identify substitutes and managers when people are absent)
2) Locating experts
  • Ability to search on skills, topics or networks to find people with the expert knowledge required (the experts might be unknown to the searcher, or known people for whom the searcher was unaware they had this expertise)
3) Engaging networks of knowledge
  • Ability to search for networks of people sharing specific skills or subject matter expertise, in order to link in with them to form formal or informal Communities of Practice

As part of these cases, we're considering Facebook and LinkedIn style features, such as,
  • staff profiles, to provide staff with the opportunity to humanise their listing and be more visible as an expert in their field
  • optional staff photos (so you can identify with a person when calling or emailing, or recognise them when first meeting)
  • linking of skills, topics and interests, so that clicking on a word provides details on other staff who have indicated similar expertise or knowledge
  • Listing affiliations, to internal project teams and other formal and informal networks or communities within the organisation, to assist the formation of Communities of Practice and to build staff engagement with the agency.

Involvement in all of these areas would be optional, allowing staff to better self-manage their privacy. However, as in any situation involving information sharing, you get greater value when you share than when you silo knowledge.

Over time this approach lends itself to integration with collaboration tools, forums, wikis, groups and blogs, as well as team-based tools such as group calendars and mailing lists.

We've been looking online for reference material on the topic of staff directories, drawing on the experiences of a number of private sector organisations who have implemented similar types of directories.

A couple of the resources we've found useful include,


I'm very interested in the experiences of other government and private sector organisations in this space - so drop me a comment if you have suggestions to add.

Read full post...

Monday, September 15, 2008

The growth of e-health in Australia

Futuregov has an excellent article, An Australia quest for e-health discussing progress in the Australian e-health scene.

It is good to see that there is a clear understanding of the need for a national approach - tying states into one consistent system, rather than individually building separate systems in each state at additional cost.

In the geospatial area, WA and QLD have launched state-centric systems, with other states considering their own systems. This has taken place while AGIMO plans a national geospatial system within the AGOSP program. They share the same standards, however I'm not clear on whether they have shared technologies and costs.

Read full post...

Monday, September 08, 2008

Getting the basics right - US presidential hopefuls fail website navigation

Forrester Research has released a report critiquing the navigation of the websites of John McCain and Barack Obama, claiming that both fail basic navigation tests by potential voters.


Nextgov reported in the article, Web sites of both presidential candidates fail to connect with users, that,

Forrester used five criteria in its evaluation: clear labels and menus; legible text; easy-to-read format; priority of content on the homepage; and accessible privacy and security policies. McCain's site passed two of those benchmarks: clear and unique category names and legible text. Obama's site succeeded in one area: straightforward layout making it easy to scan content on the homepage.

Neither site gave priority to the most important information on the homepage, or posted clear privacy and security policies, Forrester concluded.
This came on the back of another report by Catalyst, which tested seven criteria. The Nextgov article quotes that,
Catalyst asked individuals to perform seven tasks while evaluating each campaign site, including donating money, reading the candidates' biographies and finding their positions on specific policy issues. Obama's site stood out for its design and navigation, but users were confused about certain labels on the homepage, such as "Learn," which contained links to information about the Illinois senator's background and policy positions.

What were the lessons for all government sites?
  • A modern professional look is critical for drawing in users and making them want to use the site.
  • Effective prioritisation of information (most important at top) and clear, simple navigation are important for the success of a website, but if the look isn't right users won't stay long enough to use it.
  • Focus on the most important information and reduce the clutter, direct users to the most useful information, activities and tools for them.

Read full post...

Thursday, September 04, 2008

The future of the internet - and how to stop it

Jonathan Zittrain's new book, The future of the internet - and how to stop it, presents a compelling picture of how the internet has evolved from the 'sterile' and unchangeable computer systems of the 1960s and 70s into a 'generative' environment, enabling individuals around the world to freely develop applications and services and distribute them widely.

The book then looks at what may come next - the impacts of security and privacy holes and the increasing attempts to limit innovation in order to solve these issues.

It provides a compelling view of where we might be headed if we do not take steps at politic and managerial levels to change the direction.

The book is available freely online, notated by readers in an innovative collaborative approach to exploring the written word.

Jonathon has also presented many of the key themes of the book in various lectures, such as the one below.


Read full post...

Friday, August 22, 2008

Website/intranet redesign or realignment - is there good reason for change?

My team's web designer forwarded me the article Good Designers Redesign, Great Designers Realign from A List Apart earlier this week.

It looks at the justification behind design decisions - whether to change the design, layout and information architecture of a website or product - dividing it into two camps.

Redesigners - who base their decision on emotional responses to aesthetics.

It’s been 2 years since our last redesign.
Our current stuff just looks old.
A redesign would bring new traffic to the site.

Realigners - who based their decision on strategic objectives and user needs.
Market trends have shifted. Should our website be adjusted accordingly?
Our users’ needs have changed. Do we need to adapt?
We’ve added 3 new sections and a slew of new content to the site over the last 12 months. Are we presenting content as effectively as we can?
Our current website does little to convey the strength of our product offering.
Does our online presence enhance or devalue our overall brand perception?
I don't believe the line is ever that clear cut, sometimes aesthetics are used to sell strategic changes and sometimes vice versa. I also do not agree that realigners are 'better' designers (for whatever value of 'better').

However I do feel the article does touch on a key factor for management, of websites or any other system or people, perceptual versus objective truth.

Often as web managers we are the closest to our own sites, seeing blemishes that are less visible to others. On the other hand we may also accept and overlook fallacies and faults that others perceive as major flaws. It's a little like being in a relationship. We often simultaneously see more and less in our partner than others can from an external perspective.

Therefore when deciding whether to make design or IA changes it is crucial to step outside our own emotional engagement and seek the views of our audiences, our peers, management and neutral parties.

Otherwise we may - knowingly or unknowingly - be primarily driven by our own personal views or emotional responses, while publicly justifying changes based on organisational goals or audience need (or simply on the ultimate reason that 'it looks better').

I can think of times in the past where for personal or organisational reasons I've redesigned a website or intranet simply due to aesthetics. I can think of more times when there were reasons driven by audience needs or organisational realignment.

I can also remember times when I made aesthetic choices, but justified them as strategic decisions.

These are the decisions to be guarded against as they are, in my view, the most likely to lead to errors of judgment.

It's about being honest with yourself and understanding your own drivers.

Do you operate as more of a realigner or redesigner?

What would your peers say?

Read full post...

Sunday, August 10, 2008

Weekend viewing - The CIO vision series, a recent focus on Commonwealth government agencies

As a business professional in the online space I have always found it important to grasp the views of our IT colleagues to help us work with them more effectively.

If you have some free time over the weekend, ZDNet's CIO Vision series is well worth reviewing.

I've been watching the series for a couple of months now, particularly the recent interviews with the CIOs of ATO, Centrelink, Defense and Customs.

The private sector CIO interviews through the series are also very insightful.

Read full post...

Tuesday, July 29, 2008

What's the level of security risk from government's internal IT staff?

Over the last week a rogue IT employee in the San Francisco Department of Technology Information Services has held the city to ransom - locking down many of the city's services by refusing to disclose an administration password.

The employee, Terry Childs, helped create the city's FiberWAN network , used for controlling the city's emails, law enforcement records, payroll, and personal records. It controls 60 percent of the city's municipal data.

Using his access as administrator, Childs stopped other authorized network users from accessing parts of the network and gave himself access to parts from which he should have been restricted.

To compound this, the city apparently did not keep adequate system backups, and so cannot restore the system from an earlier state.

Fixing the situation is likely to take several weeks and cost in the order of $500,000, including hardware and system changes.

Childs was taken to court by the city, with a US$5 million bail set - that's five times as much as is usual for a murder in California.

Why did Childs lock down San Francisco? Network World reports in IT administrator pleads not guilty to network tampering that,

He became erratic and then hostile with colleagues after a recent security
audit uncovered his activity on the network, according to a source familiar with
the situation.


An article in Wired, San Francisco Admin Charged With Hijacking City's Network, discusses how Childs could have brought down the entire San Francisco city's network if he'd wanted to.

Fortunately for San Francisco, as reported in eFluxMedia, Childs finally turned over the password to San Francisco's Mayor on 24 July - claiming that only the Mayor was trustworthy enough to have the password.

Do you know how much power your department's IT team has?

Read full post...

Sunday, July 27, 2008

Online government forms don't have to be boring

I'm one of those quirky people who finds forms intensely interesting.

I've had a great deal of past involvement with market reseach and online transaction sites which has emphasised to me how important effective and usable form design is in order to ensure that forms achieve the goals set.

In my current role I've guided my team into supporting a number of research projects and we're currently reviewing and redeveloping our website and intranet forms capacity - touching on every other area of the business.

So I was very interested to watch Jessica Ender's presentation at the Web Standards Group (WSG) in Canberra last week.

Jessica, who owns Formulate Information Design, a specialist form development consultancy in Canberra, gave a very professional and passionate talk focusing on the four layers of a form and the appropriate process to use when developing a form.

She brought it together with the four Cs of good form design, clear, concise, clever and contextual.

While much of this was not new to me, Jessica's talk placed it into a new context and I'll be revisiting our approach to the redevelopment of our forms based on her insights.

What type of methodology do you use for developing forms?

Are your online forms effective?

Read full post...

Saturday, June 28, 2008

Make government data freely available

An interesting article was released in the Yale Journal of Law & Technology earlier this year discussing a view that government should focus on providing usable data online rather than full-blown websites.

Titled Government Data and the Invisible Hand , the premise was quite simply explained in the abstract:

Rather than struggling, as it currently does, to design [web ]sites that meet each end-user need, we argue that the executive branch should focus on creating a simple, reliable and publicly accessible infrastructure that exposes the underlying data. Private actors, either nonprofit or commercial, are better suited to deliver government information to citizens and can constantly create and reshape the tools individuals use to find and leverage public data.
This approach is very much at odds with the current approach both in the US and Australia, where in most cases the respective governments provide both the data and all the interpretation designed to meet the needs of specific audiences.

Via the current approach, data can becomes difficult to extract, or is presented in a way that is not useful. On that basis these websites are difficult to use. They are also expensive to develop and maintain and difficult to keep current.

The approach in practice

I've encountered both approaches in Australian government websites.

In a past role, managing the website for a private sector water and energy utility, one of the consistently most trafficked areas of our website was local weather. This section had only a peripheral involvement with the main focus of the site, however the level of usage made it important to retain.

We did not run this weather service ourselves. Instead we used a raw data feed provided by the Bureau of Meteorology (BOM) for free. The data was simply customised and represented in an attractive way in our website.

Ours was not the only organisation using this data - a number of other organisations had built businesses though providing weather information - sometimes combined with video, maps, commentary or other feeds. These sites collectively attracted more traffic than the BOM itself.

To my recollection, provided this data was not packaged and directly resold commercially, the BOM had a policy of giving away the data freely.

This approach helped ensure that the public were able to access accurate information, to the public good. It is important to note that BOM data was collected and processed by people and equipment already paid for out of the public purse.


On the other hand, the Australian Bureau of Statistics (ABS) provided a great deal of the data I used in my day-to-day role.

This data was preprocessed by the ABS into tables or excel documents. These were often chunks of information that were not much use to my audience.

My team spent many hours manually deconstruct and reconstruct the ABS data into different forms to make it useful for our corporate needs.

The ABS did not provide data as a raw feed. While the ABS did gave away its data for free online - and this was fantastically useful - the overhead that went into its website inevitably made it less timely, therefore reducing its value in a commercial sense.

So, in comparison:

BOM
  • Gave its data away for free online (public access to public data)
  • No data analysis required (lower cost to the agency, faster to market)
  • Referrals from everyone reusing the data (reach)
  • Enormous innovation in how the data was 'mashed' with other sources / analysed and presented (lower cost to agency, transference of risk of misinterpretation to private sector)

ABS
  • Gave its reports away for free online - but not the raw data (public value but less timely)
  • Provided intensive data processing (quality assurance but higher cost to the agency, slower to market)
  • Limited online reuse, therefore fewer referrals (lower reach)
  • No innovation in data analysis and presentation (higher analysis/presentation cost to agency, any risk of misinterpretation stays with the agency)
In my view BOM's approach seems to be both lower costs and risks for the agency and delivers greater public benefits, greater data use, innovation and agency reach (referrals).

Bt the way, it's worth pointing out that BOM is the most trafficked government website in Australia. ABS, despite a wider range of statistics, is much further down the list.



Can the data approach be used across other agencies?

I believe it can. Even in my agency we release numbers and resources which could be indexed and provided in a raw data form for reuse.

We also have a website estimator for calculation purposes. There are around a dozen similar estimators that do a similar job - several providing virtually the same result as the official estimator. However those 'fan' estimators cost nothing to the public purse to create or maintain.

So if members of the public are prepared to create these tools, why should the agency?

Granted this last example is a little more tricky than that - the estimation process is time-consuming and maximising accuracy is a key goal.

However there are other government websites and tools which could and would be delivered by private organisations and individuals, if only the government allowed access to the data stream.


Level the playing field

Note that the article does not suggest that government should stop analysing data and presenting this analysis in websites.

What it suggests is to provide the raw data on a level playing field, thereby allowing private and public organisations the same capacity to use it.
The best way to ensure that the government allows private parties to compete on equal terms in the provision of government data is to require that federal websites themselves use the same open systems for accessing the underlying data as they make available to the public at large.
This means that government agencies such as the ABS can continue to provide reports for people who choose not to do their own analysis.

However it opens the field to innovation and the use of various data sources to make connections that government, in a siloed form, is not as able to do.

This levelling is critical - if the government wants to see innovation it should not hold back the 'secret sauce'. The data needs to be available in a way that allows private and other public enterprises to use it in an equal way.

Open systems are available today via standards such as XML and RSS - look at how Google syndicates maps and ads or how Facebook allows the creation and dissemination of applications.

In conclusion

Government has a crucial role to play in the collection of data across the country. This is a task well suited to the public sector as it is in the public interest that this be available.

However government doesn't have the systems or culture to be best suited to interpret and combine this data or make it useful for individuals and organisations.

Government should provide interpretations - however it should not hold an artificial monopoly over this.

By allow other organisations to access the raw information innovation in its presentation can occur more rapidly, providing deeper insights for the public good.

Make government data freely available.


Does anyone have other examples of where government collected data has become freely available? I'd love to blog about the successes.

Read full post...

Wednesday, June 25, 2008

Considering using Microsoft SharePoint for government websites and intranets? Consider your options carefully

I've seen a lot of hype about SharePoint, Microsoft's solution for, well, just about anything related to online.

The product has been promoted as a Information Management system, as a Web Content Management system (Web CMS), as a replacement for shared drives and file systems, as an enterprise search tool and even as a platform for enterprise applications.

Amazingly enough it can fulfil all of these roles. However like other jack-of-all trades, it's not necessarily the best product for any one of them as detailed in this post, Advice for (prospective) SharePoint customers.

I've particularly been seeing a lot of push for SharePoint in the public sector.

Where agencies have selected a Microsoft technology path there's many good reasons to consider SharePoint as well - less complex environments to maintain, easier to train and recruit staff, there's plenty of synergies that can be leveraged with other Microsoft products.

However when considering any product for a role as important as being the engine of your online channel it's valuable to understand your options and undertake appropriate due diligence before investing public funds.

For instance, the initial purchase price of a Web CMS solution is a very small part of the picture, there's the lifetime cost to consider as well.

Generally I'd expect to use the same platform over a 3-5 year window at least, with substantial ongoing development to meet changing organisational needs. The cost of this development can be substantial.

Another major consideration is the staff costs related to content authoring and publishing. This is the real cost to staff in terms of the time required to use a system in the workplace. While a Web CMS might be cheap to purchase, if it is difficult or time-intensive to use that will seriously compromise the success and the viability of your online channel.

Other factors to consider include content migration, the split of responsibilities between IT and business areas, the cost of extensions to the system and the overall network and hardware costs of the system.

So while SharePoint is one options - and I've seen excellent implementations of the technology in agencies (such as in DEWR) - there are over 140 Web Content Management Systems available for purchase in Australia.

Many of them work very well within a Microsoft environment.

Read full post...

Tuesday, June 17, 2008

How many options are too many?

Donna Spencer has written a very thoughtful piece on how many items were ‘too many’ to have in a navigation bar on a website.

Entitled, How many items in a navigation bar it's well worth a read.

She argues that the 7+/- 'rule' is more of a myth and offers some suggestions on how to evaluate when a longer navigation bar is appropriate.

Adding my 2c, I think it's also important to consider the importance of each item to your audience to ensure the menu is appropriately arranged.

This doesn't always mean placing the most popular item at the top of a list, or far left of a navigation bar.

If this occurs it is possible that your audience will stop reading at this first item and not go on to look at other menu choices that would better fulfil their needs.

But what's a better option?

Alphabetical?
By order of steps within a process?
Drawn out of a hat?

Have you ever organised or read about an experiment testing which menu ordering approach maximises use by customers?

Read full post...

Bookmark and Share