The Government of Newfoundland and Labrador recently embarked on a Web Renovation Project in preparation for the implementation of a content management solution. During this project, the government performed various house cleaning' tasks including organizing and validating content, organizing servers, developing a new user interface standard, developing an information architecture and taxonomy, and developing a set of user Personas and Scenarios.
This case study will examine the process used to develop the personas and scenarios, as well as some of the tangential outcomes that helped to drive the web initiative.
Personas are fictional characters representative of actual groups of users and their needs. They serve as a quick reference and reminder of who you're designing for. Scenarios describe the persona’s process in achieving a goal and highlights opportunities for features and functionality development. Personas and Scenarios are tools that allows for a greater understanding of users, positions users at the center of the design process, and simplifies design decisions. When effectively used, personas and scenarios result in improved user experience, more satisfied users, and repeat visitors.

The process of developing personas and scenarios is comprised of three stages: identifying market segments, data collection, and development of the personas.
Early analysis of the web traffic highlighted a significant amount of traffic generated from government employees. This discovery was interesting in that it shows that the government website is not only an important tool for the public, but also it’s employees. From this discovery, two primary user groups were identified: Employees and Public.
Ideally, one on one interviews would be held to gather data on the various segments, however, due to the scope, and time limitations, the research was limited to three mechanisms for gathering data:
A Web survey was deployed on all main government web pages to gather information regarding who visits our sites, what they are looking for, if they have any difficulty finding that information, and what (if anything) may be missing that we could provide in any future designs. The survey focused on the two primary user groups (government employees and public), branching into two separate streams of questions for each group. The questions and available responses are detailed in the next section.

There were 1957 responses to the online survey over the two week period. Many of the questions were used to derive the persona attributes, but two questions let the public and employees respond with what information and services they were looking for, and how they thought the website could be improved. These question were left unstructured, allowing the respondents to speak their mind. The results were then categorized, grouped, and ranked. The results have been charted for both the public and employees.




From the analysis of the responses, there were several key findings:
The responses from the survey were then used to populate the attributes of the personas. We wanted to proportionally represent the employees and public, and settled on 10 personas to do this (4 employees and 6 public personas). This is a little more than what we would ordinarily develop, but considering the two user segments (public and employees) it was required to fully represent all the attributes. Names and photos were selected as well to start the development process.

An email survey was distributed to all departments to retrieve more specific information on the types of information and services being sought by the public and other government workers. Departments were asked to respond with the top ten requests for information or services, and who generally makes the request.

An analysis of the governments web logs was carried out to determine actual traffic to different departmental website. These results are combined with the survey results to help generate realistic scenarios for the ten personas. The Government of Newfoundland and Labrador manages over 50 individual websites, that generate in excess of 50 million pages views a year.
Analysis of the annual traffic by website generates a proportional view of the information or services that the public and employees are seeking. Further analysis of the monthly traffic highlights seasonal trends in website traffic, which can be used to deduce specific information or services. Analysis reveals six websites that possess spikes in traffic that exceed the standard deviation by more than 25%. The sites and the peak month(s) are as follows:
Data from the web logs, email survey, and web site survey were used to develop information and services sought by our personas. The information and services would form the basis of the scenarios for each persona. The information and services has been mapped to the personas in the table blow

Having established our list of personas with corresponding attributes and information or services they are seeking, it was now time to develop the personas and the related scenarios. This is where creative writing plays a major role. Stories were developed to match the attributes with the activities. The resulting 10 personas and scenarios can be downloaded as a pdf.
The results of the online survey have been instrumental in developing the personas and scenarios for the web strategy project. They are also very useful in helping to give direction to the web strategy going forward.
From the online survey analysis, we can see a strong correlation between what people are looking for, and what they would like to see improved on the web site. This correlation highlights five areas where the government can achieve the highest return for its investment:
Many of the comments from the survey respondents were task focused questions phrased as ‘How do I..’ or ‘I want to…’. The information architecture will have a greater impact if it is task-centric from the user’s perspective. As the tasks of employees can differ from that of the general public, some consideration may be given to a dual taxonomy structure. This solution is most appropriate with a content management system that is capable of customizing the users’ display based on the requesting IP address.
When selecting the content management solution, higher priority should be given to the systems that help to improve the contents quantity, quality, and currency. These features should include the following:
With 7% of the public requesting improvements to the governments search engine, this is not one of the highest priorities, but still is statistically significant. With 32% of the respondents indicating that they use the search engine, this improvement will benefit a large portion of the users. The solution needs to be fast and cost effective, which supports the current initiative to use Google mini.
One quarter of the employees and 8% of the public that responded indicated that they would like to see improvements made to the directory. Of primary concern was the currency of the data. This can be accomplished by providing a web interface directly to the government’s active directory. The government is currently implementing an active directory project. The Web Strategy group should investigate if this project encompasses a web interface that can be integrated with the government’s web site. There are numerous inexpensive add-ons to active directory for this purpose, such as http://www.nakisa.com, http://www.webactivedirectory.com, or http://www.intervate.com. To achieve the greatest value for the user, the product should include the following features:
14% of the respondents use the job board. This is a significant portion of the users that could benefit from an improved features set of the job board. There are numerous low cost pre-built job board solutions, such as http://www.jobbex.com, or http://www.webscribble.com. Features of the solution should include:
| Powered by Nabble | See how NAML generates this page |