I’ve heard more than one government client say that he or she didn’t have the time or budget to think about the implications of mobile when developing online content. Getting approved content online in both official languages and in accordance with multiple TBS policies and standards was daunting enough, and it stretched staff and budgets. If considered at all, “mobile” was thought of in terms of mobile applications. read more
Category: User Experience
A massive migration of content currently sitting on various government department websites is set to culminate in one home for most Canadian federal government information and services: Canada.ca. This new site will let anyone look for content without having to visit multiple websites. read more
(part 5 of 5)
When we present usability test results, whether for a new web application, an internal system, or a website, we are often met with grim faces due to low success rates. As usability experts we know that low success rates are actually a sign that we’re doing our job well. Receiving high success rates across the board is usually a sign that those tasks are working well, and the design is successful; however, it should also tell you that you should be testing different tasks.
(part 4 of 5)
In the early GC web days we were still very much about providing an electronic version of print publications (e.g. brochures, fact sheets, etc.). But what usability experts have learned in more recent years is that we don’t read the same way online as we do with paper. Instead, users generally like to scan quickly, looking for bold headings and keywords that stand out. Think about it this way: when was the last time you read a web page from top to bottom, left to right, in entirety?
(part 3 of 5)
As explained in the TBS Guidance on Implementing the Standard on Web Usability, “a good navigation approach focuses on tasks; it does not represent an organizational chart”. But how literally should we really take the word task?
(part 2 of 5)
Historically a common tendency when architecting government websites, especially intranet sites, has been to organize information by the structure of the institution, or rather, by who owns the information. At first glance this can often seem like a logical approach to organizing web content. And although we are getting much better at moving away from this type of web information architecture (IA); there do, however, remain a number of problems with organizing web content by organizational design that we should keep in mind.
(part 1 of 5)
There’s no doubt about it, GC institutions are having difficulties with governance when it comes to the web. In recent years we’ve shifted to a user-centred model, and that means more stringent attention needs to be paid to what is published, why it is published, and when it should be un-published.
As tempting as it may be to use your unadorned PAA as a GCDOCS folder structure, be wary; what looks like an ideal shortcut, in most cases it turns out to be a “false friend” that may result in mismanaged IRBVs and severe end-user dissatisfaction. Here are 6 reasons why the PAA alone is not sufficient for your EDRMS/GCDOCS implementation.