Intranets Government Agencies 2001-2020 Free
Intranets Government Agencies 2001-2020 Free
By Kara Pernice, Amy Schade, Jakob Nielsen, Patty Caya, Mathew Schwartz, Candice
Goodwin, Maria Rosala, and Anna Kaley.
May 2021
Copyright © 2001–2018 by Nielsen Norman Group, all rights reserved. To buy your own copy, please go to
www.nngroup.com/reports/best-government-agency-and-public-sector-intranets
About This Free Report
This report is a gift for our loyal audience of UX enthusiasts. Thank you for your
support over the years. We hope this information will aid your efforts to improve
user experiences for everyone.
The research for this report was done in 2011, but the majority of the advice
may still be applicable today, because people and principles of good design change
much more slowly than computer technology does. We sometimes make older report
editions available to our audience at no cost, because they still provide interesting
insights. Even though these reports discuss older designs, it’s still worth
remembering the lessons from mistakes made in the past. If you don’t remember
history, you’ll be doomed to repeat it.
We regularly publish new research reports that span a variety of web and UX related
topics. These reports include thousands of actionable, illustrated user experience
guidelines for creating and improving your web, mobile, and intranet sites. We sell
our new reports to fund independent, unbiased usability research; we do not have
investors, government funding or research grants that pay for this work. Visit our
reports page at https://www.nngroup.com/reports/ to see a complete list of these
reports.
HOW TO SHARE
Do not link directly to the PDF file (the hosted address could change). Instead, we
encourage you to distribute the following link to the report’s page on our website to
allow people to decide whether to download it themselves:
www.nngroup.com/reports/best-government-agency-and-public-sector-intranets/
Copyright © Nielsen Norman Group; All Rights Reserved. To get your own copy, visit:
www.nngroup.com/reports/agile-development-user-experience
Copyright Notice
This report is free, but it is still copyrighted information that may be updated from
time to time, so please don’t distribute this file or host it elsewhere.
Even when people post documents with a private URL to share only with a few
colleagues or clients, search engines often index the copy anyway. Indexing means
that thousands of people will find the secret copy through searches.
1
Intranet Design Annual reports are available for download at http://www.nngroup.com/reports/intranet .
2
See separate report, Usability of Intranet Portals: Report from the Trenches,
http://www.nngroup.com/reports/intranet/portals.
WORKFLOW SUPPORT
A persistent theme among the winners is that usability was dramatically improved by
restructuring the intranet’s information architecture to focus on job support. That is, they
grouped content and tools that are used together in the same intranet area, even if different
departments supply the information. For example, the Workplace Safety and Insurance
Board of Ontario created a special Manager’s Page with various forms, procedures, and tips
for supervisors. The same intranet also had a professional practices page for nurse case
managers.
Unlike our winning designs, many intranets use navigation that mirrors the “orgchart,” and
organize their information architecture based on departmental structure. For many
organizations, basing intranet structure on workflow is a new concept.
At the workflow features level, many good intranets have a calendar of events. The U.S.
Senate Republican Conference takes this basic intranet component two steps further by
highlighting critical, scheduled votes, and providing remote access to the information
through BlackBerry mobile devices. In fact, the Senate Republican Conference intranet has
extensive support for remote access, which acknowledges that senators and their staff often
roam widely and spend significant time at events outside the office.
In our recent tests of the usability of Web-based About us information, 3 users frequently
struggled with government websites because of the sites’ overwhelming use of acronyms
and insider lingo. Although such bureaucratese should be fought on public-facing websites,
it’s highly appropriate to use specialized terms on government intranets. The Government
Offices of Sweden, for example, has a compact navigation bar that provides direct access to
individual ministries’ pages by clicking on a one- or two-letter abbreviation for each
ministry. While you should never expect a member of the general public to click on “J” when
looking for the Ministry of Justice, such abbreviations improve communication efficiency
inside an organization where people regularly use such terminology.
3
See separate report About Us: Making it Easy for Visitors to Find Company Information on Corporate
Websites, http://www.nngroup.com/reports/about.
TECHNOLOGY
Unfortunately, technology chaos continues to reign in intranet implementations. The ten
winners used a total of nineteen different software solutions to run their intranets. This
underscores a fact: we’re nowhere near the point where we could recommend, based on
usability, a few good intranet packages. Currently, there seems to be no relation between
the technology used and the intranet’s quality. In other words, when it comes to intranet
software, it’s a matter of how it’s being used, not which packages you buy.
The winners’ five most often used technologies were Microsoft SQL (60%), Microsoft IIS
(40%), ColdFusion (30%), Lotus Notes (20%), and Plumtree (20%).
USABILITY METHODS
The average winning team employed 3.4 different usability methods during its redesign
project. This is a good deal more than the 2.7 methods used by the winners of our annual
design competition in 2003. In general, combining multiple usability methods is beneficial,
because each makes its own contribution to the final design quality.
One reason government intranet teams employ more usability methods than other types of
sites is that they often have to emphasize accessibility for users with disabilities. Several
winning designs even performed actual accessibility testing with employees with disabilities,
something that’s rarely done in the private sector. As a result of either testing or required
guidelines, several of the winners made good changes to their designs to increase
IMPROVEMENTS IN METRICS
Compared to many of the best private-sector intranets, the winning government intranets
seemed to better track their projects’ metrics, possibly reflecting a tendency in government
agencies to closely watch expenses and to have defined processes in place.
As one might expect, the U.S. Defense Finance and Accounting Service, being good
accountants, collected the most extensive metrics on their intranet redesign’s financial
impact, calculating total savings of 200 staff years. Specific intranet areas realized
impressive improvements in usability metrics, including a human resources (HR) page,
where productivity increased by 300% following the redesign. Even more importantly, the
agency’s management recognized the intranet’s strategic contribution to the organization’s
overall productivity. For example, a plan that’s currently underway will reduce the time
needed to generate accounting reports from forty-five days to twenty-one days; the project
involves more than 200 tasks. This truly ambitious undertaking goes far beyond redesigning
individual pages, or even conceptualizing the intranet as a stand-alone entity.
Emphasizing “usability in the small”—targeting specific intranet elements for “quick win”
improvements—is also important because it can generate immediate ROI for an
organization. For example, the U.K. Department for Transportation saved £130,000
($228,000) by relocating its employee newsletter to the intranet. Anecdotally, many
organizations noted other “usability in the small” benefits—such as increased intranet user
morale—after making even small intranet improvements.
The greatest intranet benefits, however, come from utilizing the intranet for business
process reengineering. The Workplace Safety and Insurance Board of Ontario, for example,
unified information from sixteen spreadsheets into a single intranet tool, dramatically
improving caseworker performance.
Analyzing the winners showed that the largest performance gains came from projects that
finally delivered good intranets to organizations that previously suffered under miserable
ones. For example, London Underground increased the number of employee visits to the
intranet from 1,000 per week to 70,000 per week—an astounding gain of 6,900%. Note,
however, that increasing intranet use by 100% to 200% is a more common result of
improved usability.
Here’s a takeaway if you have a bad intranet that employees are shunning or labeling as
useless: don’t despair. Rather than abandoning your intranet, regard it as a prime candidate
for improvement. In fact, based on projects we’ve seen, you can generally expect a usability
redesign to more than double intranet use. You can thus position the redesigned intranet as
a tool to enhance employees’ productivity, leading to their respecting the intranet, and
ultimately contributing to it and its success.
4
Winners in our last three design annuals have come from the following countries: Australia, Canada,
Germany, Norway, Spain, Sweden, Switzerland, the United Kingdom, and the United States.
Department for The Department for Transport's intranet expedites processes that previously required
Transport (U.K.) considerable time and legwork. Transnet is both a communications medium and a
reference library that helps employees find accurate information and confidently do
things for themselves.
Department for Looking at this intranet’s simple presentation and consistent design, you’d never
Victorian imagine that much of the content was originally taken from seven very different
Communities intranets. Its simple design, plentiful content, seamless integration, and creative
(Australia) touches all help meet the organization’s goal of unifying staff from fifteen different
business units.
Department of What started at nine separate, dissimilar intranets has become one cohesive design
Veterans Affairs that helps employees easily find the information they need. The design team achieved
Mid-Atlantic this by defining simple goals and creating achievable processes for meeting them.
Health Care
Network (U.S.)
Federal Reserve The Federal Reserve Bank of Richmond intranet is a communication tool that keeps
Bank of Richmond 1,500 users in several different locations apprised of current happenings. Forums and
(U.S.) other information collections keep employees in touch. Persistent navigation presents
the most needed and used applications, and makes this intranet very straightforward
to use.
Government The Government Offices of Sweden’s intranet supports an impressive number of tasks
Offices of Sweden under one attractive design. More striking still is the fact that this elegantly designed
intranet also unites all of Sweden’s central ministries (the highest level of the national
government’s executive branch) as well as the nation’s embassies and foreign
missions. This jam-packed but uncluttered intranet makes it easy for employees to
find relevant information about each other, their organization, and the world.
London Some designers feel that making sites accessible will hamper usability or aesthetics.
Underground On the contrary, considering accessibility during design often leads to interfaces that
are not only accessible for users with disabilities, but are easy for everyone to use.
The London Underground intranet is evidence of this phenomenon. In their list of
target users, designers included people with visual or mobility-related disabilities.
They then devised several designs for accessibility reasons that ultimately helped all
users.
Senate Republican Consistent with its goal to communicate, the U.S. Senate Republican Conference
Conference (U.S.) intranet is available on multiple devices for many staff members around the nation.
The inventive features, exhaustive content, and consistent navigation all make this a
winning government intranet.
Workplace Safety Following much investigation and fabrication, designers of this intranet created
and Insurance imaginative tools and demonstrated their eminent strength—letting users simplify or
Board of Ontario eliminate otherwise painful and time-consuming processes.
(Canada)
5
Nielsen Norman Group’s research report about accessibility and usability for the Web, Beyond ALT Text-
Making the Web Easy to use for Users with Disabilities (Coyne, Nielsen) includes guidelines about designing
usable and accessible websites, and is available for download at
http://www.nngroup.com/reports/accessibility.
6
See the W3C’s Web accessibility guidelines for more information about coding accessible websites.
http://www.w3.org/WAI/
SUMMARY
The DFAS team valiantly consolidated more than 200 individual websites and three portals
into one intranet, the ePortal. This collaborative workspace provides direct access to more
than 10,000 lines of searchable and reusable content, and lets employees communicate and
work effectively.
The ePortal hosts more than sixty organizational and issue-based communities and more
than 100 short-term projects. To govern the use of collaborative workspace, the ePortal
functional team established new business rules to transition away from e-mail for
collaborating on issues and managing events. The ePortal provides content version control
and reduces bandwidth requirements for e-mail attachments.
The user’s MyPage offers a glimpse of the intranet’s vast content. The Directors Message,
press releases, and other news keep employees up to date. All intranet pages have a
somewhat similar setup, with titles for sections, and similar items divided into boxed-off
areas (referred to as portlets). The top horizontal navigation is present on all pages.
The intranet consolidates business processes and facilitates budget and performance
integration. For an intranet to meet these goals, it must be well organized. The team
achieved this by dividing the content into three main sections: the knowledge directory,
communities, and personalization.
The knowledge directory is essentially a filter. It categorizes massive amounts of
information from document repositories, file systems, and websites into an enterprise-wide
taxonomy that organizes access to communities, projects, and applications.
Communities let business users and administrators create composite applications. Various
teams—including project teams, departments, business units, customers, partners, or the
entire organization—can collaborate and share information through communities, which can
be managed separately, securely, and hierarchically. Like content provided through portlets
and personalized portal pages, communities can include content and functionality adapted
for specific users.
Communities also offer better user support by providing new and accurate content. The Self
Help community, for example, lets content providers find procedures and answers on their
own. Each community also has a portlet that provides contact information if users need
information that they can’t find online.
Users personalize the site on their MyPages area, choosing information, services, and
interactive tools on up to six personalized pages. They can also organize the presentation of
their personalized portal pages with up to three columns and eighteen different color
schemes, meeting each user’s specific needs. Users can also access a low-bandwidth or text
version of the portal.
The intranet offers extensive HR information in the Human Resource community, such as
benefits information, promotion and retirement calculators, promotion and new hire lists,
and a Who Do I Contact? portlet that provides users answers based on their topic and
business line. News headlines about HR appear in the page’s center column, so users stay
abreast of HR happenings. Using the myHR Applications portlet, employees can monitor
their personnel information. They can also view their official personnel record there and
their Total Compensation Statement.
The design team’s recent usability testing and redesign of an HR page resulted in an
increase in effectiveness of more than 300% and a decrease in overall task time of more
than 50%—a fantastic triumph.
Managers need access to additional information and applications. To make it simple for
them, management-related information resides in the HR community’s Supervisor’s Corner.
The layout is similar to other HR pages, but the content is aimed at managers.
The ePortal includes many more features, such as eLibrary, which houses searchable and
reusable information. The DFAS Directory stores employee telephone numbers, office
symbols, job titles, and locations. In addition, employees can submit training requests for
themselves, and managers can submit training request for employees. The Rumor Has It
feature lets employees submit rumors to senior management for response.
These and a plethora of other features help DFAS employees work together resourcefully.
That process, plus templates, keeps the intranet content’s appearance consistent.
Documentum flags approved content as “active,” assigns read permissions based on the
content’s “organizational owner” attribute, then forwards it to the Web cache every hour.
TECHNOLOGY
The DFAS ePortal runs on Unix and, as documented above, uses a combination of
Documentum and Plumtree Content Server to maintain design and manage portal content.
DFAS also uses Documentum for everyday document management.
Content Server lets business users with no HTML or programming skills generate articles,
updates, and announcements. It also allows universal searching of all DFAS resources—
including the knowledge directory—which means that users spend less time searching, and
portal administrators only have to manage one search index.
Portlets give users preconfigured tools and services, which can be further customized. Each
page has up to three columns; users drag and drop interface elements when creating their
personalized portal. Low-bandwidth and more accessible versions are also available.
The intranet also offers online project management, and online form creation and
management.
Online project management includes collaboration tools such as threaded discussions with
easy-to-use forums. Team members can create and track project tasks, and even assign
tasks to other users on a group calendar.
Documents can be checked in or out, or rolled back to a previous version. Users can also
subscribe to various e-mail alerts for such things as new forum postings, document
availability, and community content updates.
The software also lets content managers create online forms automatically. Templates give
them a range of features: data calls, calendars, polls, and surveys. DFAS uses Plumtree
Studio; content managers don’t have to do any coding.
Developers also get an integrated application-building environment. One especially useful
feature is shared authentication resources, which lets developers integrate new applications
into intranet URLs, reducing the number of times a user must log on.
USERS
DFAS has about 15,000 personnel at twenty-six national and international locations. It is
the world’s largest finance and accounting operation.
USER TASKS
• Read news
• Use the employee directory to search by name, telephone number, organization
code, and location
• Train online through the Self Help community, and read its FAQs and tip of the
week
• Collaborate on projects
BACKGROUND
“In the mid-1990s and long before portals were even considered an option, the DFAS
intranet started much like most federal agencies: we had a small group of employees that
were familiar with the working of the Internet, could spell ‘HTML,’ and who were good at
developing and managing applications,” says Johnson. So, DFAS gave the group
responsibility for creating websites, managing content, and driving DFAS’s Internet
strategy.
The approach was successful—perhaps too successful. Frequently, DFAS would develop an
on-location website to support customers, only to find that another DFAS business unit
targeted the same customer with an almost identical website. Besides duplication of effort,
the Web group didn’t scale with the number of sites, eventually making the content creation
and updating process “long and cumbersome,” notes Johnson. On the other hand, the Web
presence represented “a huge leap beyond mail and the telephone,” she says, and
dramatically improved information sharing with customers.
The next-generation intranet was dubbed InfoWeb. Yet InfoWeb lacked a crucial feature—
“the enabling tool set that could foster knowledge management,” notes Diane (Dee)
Crawford, the DFAS ePortal program manager. Intranet information improved and
integration reduced duplicate efforts, but DFAS hadn’t changed its work style to maximize
the new possibilities. DFAS continued to search for a content management tool able to
delegate content creation and allow collaboration.
At roughly the same time, between 1999 and 2001, DFAS leadership was visiting a who’s
who of successful U.S. corporations—Microsoft, Motorola, Hewlett Packard, Ford, IBM,
Lockheed Martin, Raytheon, Bank of America, and Computer Sciences Corporation—to study
their success.
The companies had one thing in common: a portal. “Each had applied some sort of portal
technology to enhance performance, facilitate customer service, and increase technological
support to management and the workforce,” says Norman E. Noe II, DFAS’s chief
knowledge officer.
Based on its findings, DFAS management created a “one organization, one identity”
initiative. Creating a prototype portal, and migrating multiple portals and over 200 websites
to a single portal, however, would take time.
The initiative got a boost in February 2002 when DFAS director Thomas Bloom stated that
DFAS could not be a world-class finance and accounting firm without implementing an
enterprise portal. Work began in earnest.
The mandate: roll out a prototype in sixty days using existing software and licenses. The
portal didn’t yet have a budget. The intranet design team, formed by representatives from
the offices of business integration, the chief information officer, and technical services,
developed the initial requirements, drafted a deployment plan and methodology, and
Before releasing the new intranet, DFAS also created a series of twenty-five intranet
training modules, to take users from logging in to page customization to advanced searches.
TIMELINE
• February 2002: Team formed to create one portal for entire enterprise using
existing software and licenses. Deadline: sixty days.
• May 2002: With portal requirements finalized, development begins. Though portal
development hadn’t been budgeted, $2.5 million for the entire rollout is re-
RESULTS
As befits a project that constantly met tough deadlines with room to spare, the portal
launched ahead of schedule. The rollout “executed on time and under the government’s cost
estimate, and the portal was deployed agency-wide on a newly designed and tested
production platform before July 2003,” says Noe.
The portal meets the “one organization, one identity” mandate in spades. The new portal
consolidates three old portals and more than 200 websites. Users have access to more than
10,000 lines of searchable and reusable content. Project teams can rely on content version
control and can store documents on the intranet, meaning fewer e-mail attachments gobble
up network bandwidth.
In fact, through new organizational guidelines, the ePortal team hopes to completely switch
users from e-mail to the intranet for such tasks as trading documents or collaborating on
events by the end of 2004. By the end of 2005, DFAS expects all collaboration to be done
via the intranet.
Currently, the intranet contains sixty communities and supports more than 100 business
projects. Many of those were transferred from the previous portal, but new ones have also
sprung up to handle recent projects, such as decreasing the accounting cycle to twenty-one
days (see below).
Based on before-and-after usability testing, DFAS was able to quantify a number of
improvements. For example, reduced sign-on helps employees move more quickly to
different parts of the site, while improving employee access to HR information reduces call
center and printing costs. Overall savings: approximately 200 staff years.
By consolidating many online applications, including time and attendance reporting, e-
learning, a resume builder, and a mentoring-network tool, DFAS reduced the time it takes
to support those applications, saving more than ten staff years.
The new portal also improves knowledge capture and reuse. “One of the growing issues
within the federal government is the aging workforce and the loss of critical knowledge as
LESSONS LEARNED
Insights from Dee Crawford and Norman Noe:
Employees always resist change. “As the old saying goes, ‘It’s tough to think about
draining the swamp when you are surrounded by alligators.’ While transitioning functions to
a portal would add tremendous value, improve customer service, and foster savings, it’s
hard to start moving toward that when DFAS managers are trying to ensure that the
soldiers in the trenches in Afghanistan and Iraq are being paid correctly. This is not a new
SUMMARY
Transnet, the Department of Transport (DfT) intranet, expedites processes that in the past
required considerable time and legwork. Transnet is both a communications medium and a
reference library. This combination helps employees find accurate information and
confidently do things for themselves.
Transnet began within the parent Department of Transport, Local Government and the
Regions (DTLR) and before that resided in the Department of the Environment, Transport
and the Regions (DETR). In these departments, the intranet had been owned by the IT
Services Division and Information Management Division, respectively, both of which had
diverging views about what an intranet should do and be. DfT’s communication directorate
inherited Transnet with the goal of making it a communications tool. More specifically, the
intranet was to help align communications about external department work with its internal
audience, so all staff members could see how their own work contributed to the
department’s overall plan.
Daily news items are published on the Transnet homepage and users receive a link to the
weekly bulletin via e-mail. The intranet offers users extensive news and information,
including daily press releases, messages from the Permanent Secretary, access to the staff
handbook and the business plan, and news about department management and new
initiatives.
To address criticisms of the previous intranet, the team created an uncluttered homepage
and a properly configured search engine. To simplify navigation, the top horizontal menu
appears on every intranet page, as do breadcrumbs and a simple search field (in the upper-
right corner). The team studied site statistics to learn which site areas got the most use,
and put links to those areas in the left-hand navigation. The right side of the homepage
features the Managing DfT section, which is filled with information about senior
management and the work of DfT.
The intranet offers several accessibility features. After acquiring screen-reader software, the
team used it to assess how the site might perform for seeing-impaired users. Revamping
table layouts is only one major change that they made based on their research. For users
with low vision, the site offers a high-contrast style sheet or the user’s standard Windows
style sheet.
The corporate organization chart is designed for pleasant online viewing—unlike many other
commonly used PDF “org charts” that feature tiny boxes and impossible-to-read text. Using
the left-hand navigation, users choose the group they are interested in. The group appears
on the main page on the right, and is obviously labeled. The chart provides pictures, names,
job titles, and an e-mail link. Users can also click on a name to drill down and see that
person’s direct reports.
The intranet gives users access to many online forms, such as accident and incident
reporting, overtime claims, and project initiation documents. It also offers online booking
forms for special events, such as the Equality and Diversity Unit’s program of visits and
talks called “Valuing Diversity.” Users can also advertise items or services for sale on an
intranet-based notice board.
The intranet team developed forms for specific departments as well. For example,
communication directorate line managers must report any team member’s absence to the
directorate’s management. Previously, a global e-mail sent every Monday morning asked
managers to report their team absences for the preceding week, and the process required
much back-and-forth e-mail communication. To improve efficiency, the Transnet team
developed a simple intranet-based form that lets line managers report absences effortlessly,
and eliminates the extra, unnecessary steps for clarification. Managers receive an
automated weekly message reminding them to complete this form.
CONTENT MANAGEMENT
For content management, the team selected Abacus e-media’s Webstructure software and
customized it to suit the DfT.
“Webstructure is written in ASP, uses a SQL database server back end, and sits on a
Windows 2000 platform running IIS,” notes Iain Anderson, Transnet team technical
manager.
Various DfT divisions and larger business units each appoint a content owner to manage
their intranet updates. As the intranet has grown, so has interest in having a content stake
TECHNOLOGY
The team designs more complicated pages—with tables or interactive features—in
Dreamweaver. Mini-applications, such as the staff notice board, accident-reporting system,
and a Windows XP question-and-answer board, run on a Microsoft Access database.
The search engine is Open Objects’ KBroker.
USERS
The intranet is used by the central DfT—known as DfT(C)—as well as by other government
agencies connected to the GSI. Those agencies include the Highways Agency, Maritime and
Coastguard Agency, Vehicle and Operator Services Agency, and the Driver and Vehicle
Licensing Agency.
DfT employs about 1,800 people, and statistics reveal about 2,500 Transnet users, so DfT
knows the intranet is reaching people in other agencies.
BACKGROUND
Understanding the history of Transnet requires a review of the department’s numerous
name changes and several business reorganizations.
In November 1997, the first intranet for DfT—then known as the Department for the
Environment, Transport and the Regions (DETR)—was completed. Called InfoNET, it used
Microsoft FrontPage, was pure HTML, and was revolutionary for its user base. As the original
instruction manual noted, “The pages in the InfoNET are connected by links (called
hypertext links). When the links are within text, the text is usually colored blue or red and is
underlined but links can also be within graphics.”
In March 2000, InfoNET got its first major overhaul, with improved usability, interactive
forums, and some online forms. Both search and rudimentary distributed-publishing
capabilities were added, and the online telephone and business directories were updated.
In June 2001, DETR became the Department for Transport, Local Government and the
Regions (DTLR). The immediate intranet change: a redesigned logo.
That October, the communication directorate, which managed DTLR’s website, took over
responsibility for the intranet. Whereas the previous intranet teams held technology-centric
viewpoints, the new team had a mandate: transform the intranet into a communications
tool.
TIMELINE
• November 1997: First intranet launched.
• October 2001: Communication directorate inherits intranet responsibility.
• December 2001: Intranet redesign project begins.
• Early 2002: Initial proposals accepted for the Transnet intranet.
• April 2002: Content owners given three months to review material.
• July 2002: Intranet design finalized.
• August 2002: Old content migrated to new intranet.
• September 2002: Transnet launches.
• November 2002: Web designer/developer joins team; begins creating interactive
features.
• May 2003: CMS introduced.
LESSONS LEARNED
Insights from Alison Hadley:
Use external researchers. “It’s difficult for the team to be objective about their own
work.”
Invest in training. “Improving the intranet team’s professional skills has given us more
influence with content owners, as well as the ability to provide a better publishing service.”
Create room to breathe. “We developed the design over a nine-month period before
introducing the content management system. Although it meant a second migration, it also
meant we were not constrained by too rigid a template at the start.”
SUMMARY
Given this intranet’s simple presentation and consistent design, you’d never guess that
much of its content was derived from seven very different intranets. The intranet’s
uncomplicated design, plentiful content, seamless integration, and creative touches all help
meet the goal of unifying staff from seven different divisions.
The Department for Victorian Communities (DVC) was established in December 2002 due to
government changes following the Victorian state election. DVC brings together fifteen
business units that were previously attached to seven host departments, seven IT networks,
and seven different intranets. The Department Secretary launched the new intranet, DVC
Net@Work (to celebrate, staff members were given Net@Work mouse pads). “The new
intranet reflects the fun environment and the diversity of people that it has brought
together,” says Melanie Hughes, communications adviser. The intranet supports
approximately 600 staff members primarily located in its main Melbourne office, but DVC
also has offices in other Melbourne locations and in regional areas throughout Victoria.
The intranet provides the right amount of content, elegantly packaged. The homepage’s
news section is updated weekly. Headlines and short summaries give users enough
information to decide whether they want to read further. Understanding the importance of
fresh content, the team addressed this technically and organizationally. First, designers built
the site for distributed authoring. Second, the group immediately established a team of
authors representing each of the department's business units. More content authors will
continue to be trained. There is also an archive that contains previous homepages so people
can refer to past articles.
The rotating Faces of DVC banner includes images of the staff members. Displaying both the
image and name helps staff identify each other. This is especially helpful given that the
department is just over a year old and employees have come from many different locations.
On the intranet, employees get access to procedures, policies, support for work activities,
statistical data and information resources, and information and services related to staff work
conditions and professional development. The About DVC area supplies a department
overview, including facts about ministers, executive profiles, the organization chart, and
strategic and corporate information.
We often encounter corporate intranets that are organized by units and functional groups
rather than by user tasks, which can make it difficult for users to find information—
particularly when they don’t know which group handles which duties. In DVC’s case, the
designers understood their audience and knew that people from the many business units
would each come with knowledge of their own previous processes and terminology. Thus,
the intranet’s left-side navigation is organized by subject rather than by departmental
structure. This makes finding content easy, and also facilitates the integration of business
units’ content. The left-side navigation is persistent across the intranet, and breadcrumbs
help users keep their context. On every page, links to the site’s most popular areas appear
in the second row of the top, horizontal navigation.
Overall, the site’s text is well written. Black text contrasts well with the white page
background, and bold headlines help users to scan text. Pictures are used to enhance
messages.
In the left-side navigation, clicking a link such as What's Happening expands the menu.
These second-level links are divided into subject clusters such as: Bulletin board, Events,
News, Media releases, Fun@DVC, and VicGov Trading Post. This second level of links
prevents the list of top-level links from getting unruly.
The What's Happening section keeps employees abreast of current events, including DVC-
related activities and seminars, national and international news, and weather. To keep
Pictured: The What's Happening section keeps employees abreast of current events,
including DVC-related activities, Melbourne events, national and international news,
and weather.
Having fast access to current contact information is crucial. The Contacting People
navigation link leads to an intranet section containing links to DVC’s phone and location
directory, the Whole of Victorian Government Directory, public phone books (business and
residential), and key DVC contacts.
A New Starters section helps new employees familiarize themselves with the department
and find answers to questions. In studying intranets, we often see cases in which new
employees are too embarrassed to ask a certain question, or don’t want to bother their
manager or administrative assistant. In such cases, having the information available on the
intranet lets them find answers independently and privately. In this intranet’s case, the
information is comprehensive, supplying everything from payroll forms to the code of
conduct. New employees can also enter required information about their personal details
and banking and tax information, as well as apply for a security pass or schedule a training
course.
This comprehensive intranet succeeds in uniting not only information from various sources,
but the department staff as well.
TECHNOLOGY
The Victorian Department of Infrastructure (DOI) hosts the Windows 2000 server hardware
and software running the intranet. DOI handles all of DVC’s information technology via a
shared-services-arrangement contract.
The team selected DOI-developed intranet technology, though it came with some
constraints. For example, users must enter their username and password to move beyond
the intranet homepage. “DVC hoped to avoid this password requirement, but this wasn’t
possible,” says Hughes, adding that it’s a DOI security policy requirement, and DOI hosts
the intranet. Still, she says, “the advantages of using a pre-existing system definitely far
outweighed [the benefits of] starting from scratch.”
USERS
DVC’s intranet supports approximately 600 staff members; most are in Melbourne, but
some are located in regional Victoria offices.
The intranet supports several DVC divisions and business units:
• Office of Commonwealth Games Coordination
• Sport and Recreation Victoria
USER TASKS
• Find information about DVC news and events
• Access salary and vacation time information
• Pay invoices
• Claim expenses
• Access the DVC phone and location directory, the Victorian government directory,
or public phone directories
• Contact the IT help desk and read IT updates
• Find the organizational chart, strategic documents, and information about ministers
and senior management
• Read messages from the DVC Secretary (the head of the department)
• New employees access key employment documents: tax and bank account
information; security pass applications; key HR policies, including the employee
code of conduct; and information on staff amenities such as parking, bicycle racks,
and shower location.
BACKGROUND
DVC was created in December 2002, following the previous month’s Victorian state
elections.
The intranet was one of five “Establishing DVC” projects begun concurrently. The other four
were to create shared service arrangements for IT, HR, and finance, and move 470 of DVC’s
600 employees to one building.
One of the business unit’s staff, Meigan Geileskey, had extensive Victorian government
Internet experience and was appointed DVC intranet project manager. She immediately
established a provisional intranet. “As DVC staff were initially working on seven different IT
networks and in different buildings, a short-term solution was to develop an interim DVC
intranet accessible via the Whole of Victorian Government Intranet,” she says. As in any
reorganization, the fledging DVC staff members—who were initially located in different
buildings—wanted information. As an example, Geileskey notes that “details about the staff
move to the new building were well sought after.”
The transitional intranet, built in Dreamweaver, lacked distributed authoring or built-in
archiving, but “it served as a short-term solution for the department until the development
of the current intranet,” says Geileskey.
Pictured: The first design for the DVC intranet. Feedback from the Web group and
randomly selected staff members from different levels and business units helped
enhance this version to create the intranet DVC has today.
The project team also tested navigation terminology and subsequently eliminated terms
that users viewed as too clever. “We initially based our terms on the successful DOI model
and then tested these on DVC staff,” notes Geileskey.
For example, on the DOI intranet, “people services” refers to professional development
information in the HR section. “This term didn’t make sense to DVC staff because our
department is based on community—people—services, so DVC staff thought that this term
meant what services DVC is providing to the community,” notes Geileskey. The new, DVC-
friendly term is “staff services.”
In the end, “Quite a bit of time was spent on tailoring navigation terms for DVC to ensure
users could make sense of the site architecture easily,” she says.
Finally, the new intranet was branded as DVC Net@Work, and mouse pads were created to
herald the launch.
TIMELINE
• July 2003: Intranet project begins with assignment of project manager and
immediate research into existing Victoria government intranets. Over the next six
months, DVC staff migrates to a common building.
RESULTS
Six months after the project began, and with an ambitious timetable, DVC Net@Work went
live. Today it “provides a central point for access to information for all staff,” notes Hughes.
The intranet has already improved not just staff information access, but cross-departmental
communication. Internal communications at DVC also have a consistent look and feel and
staff members have easy access to major DVC applications, an often-requested feature.
Work Tools and Services, for example, groups such things as procedures, policies, work
activity assistance, and templates for briefings, memos, and letters. Second-level headings
are clustered by subjects, such as finance, IT, projects, and communications. “You can find
everything you need to do a task in one area, rather than scattered throughout the site,”
notes Geileskey. Clicking on Projects, for example, leads to project templates and
guidelines, contacts for project assistance, and departmental project news.
DVC also trained a network of content authors (more are on the way), and expects
continued intranet improvements as authors devise new content.
To keep content fresh, users can set content expiration dates in the CMS. “It sends a
reminder e-mail to the content author and administrator that the content page will expire.
This can be overridden if required,” notes Geileskey.
The CMS archives the homepage and news by date. For recurring events, authors can save
time by retrieving and updating existing content.
The intranet team also created an electronic document center (EDC), a Lotus Notes
database repository of useful DVC documents. Content authors can publish links to the
documents on the intranet, making them easy to share. Typical EDC documents include
reports, charts, procedures, forms, and policies.
Intranet searches return results from not only the intranet, but also the EDC, including a
link, last date updated, and location.
Pictured: The Library Catalogue, an externally built application, utilized the DVC
intranet style guidelines so that the finished product blends with the intranet.
LESSONS LEARNED
Insights from Andrea Appleby:
Make the intranet a team effort from the start. “At the start of the project, a conscious
decision was made to involve as many staff as possible. It’s important to develop an
intranet ‘with’ the staff that are going to use it, not present a completed product that no one
knows about.”
Insights from Melanie Hughes:
Engage people early. “Forming the Intranet Reference Group gave us the opportunity to
utilize expertise across the department and provided the group with the opportunity to give
their input into what they wanted from an intranet. This in turn created more buy-in—a
majority of the reference group members then became content authors and advocates,
encouraging others to be authors.”
Thank your workers. “At the same time as the content authors were trained, we also
promoted their involvement and put their names up in lights as departmental champions
and early adopters so as to cement their participation and highlight their role to
management.”
Create a communications strategy. “A communications strategy was invaluable to
promote, road test, and introduce staff to the intranet prior to its launch. DVC intranet
posters were developed and distributed to each floor of the building. We put regular intranet
SUMMARY
What started as nine separate and very different websites has evolved into one cohesively
designed intranet that presents a unified message to employees and helps them easily find
the information they need. The design team achieved this by defining simple goals and
creating design processes to meet them.
The U.S. Department of Veterans Affairs Mid-Atlantic Health Care Network (VISN 6) has
eight medical centers and twelve outpatient clinics in three states, and a service area that
includes 1.25 million veterans and 85,000 square miles. In fiscal year 2003, VISN 6 served
more than 200,000 unique patients. Last year, VISN 6’s annual budget exceeded $975
million and it had approximately 10,000 employees.
With so many responsibilities and users to support, the organization realized it needed one
intranet. Originally, the VISN 6 headquarters office and four of its eight facilities had each
created their own intranets. The look and feel of each was distinct, yet much of the content
was similar; VISN 6’s management knew it needed to overhaul this approach and prevent
further duplicated effort. While revamping, management took the opportunity to pursue an
additional goal: streamline the processes and procedures, and align them with the
organization’s goal of being thoroughly patient-focused.
The team established a common interface for the entire intranet, including templates.
Content providers can access information about these templates, as well as appropriate
assets, on the intranet. In addition, content officials who maintain their own content must
receive content-tool training and training on the required templates. Before any content is
published, the webmaster reviews it to ensure that it adheres to usability standards and
design templates.
Enforcing standards can be difficult at some organizations, but for VISN 6 it was surprisingly
easy to implement them, says Charles (Chuck) Jones, VISN 6 webmaster. “Most content
owners are happy that the design has been taken care of for them, so they only have to
focus on content. However, there are a few who express disappointment about not being
able to exercise their creativity.” Another challenge the team overcame during the redesign
process was trying to design the new site while maintaining multiple, local intranet sites.
Now the VISN 6 intranet provides one integrated website that is a source of information for
all employees. Additionally, the intranet helps promote a sense of integration among all of
the facilities, so employees view their facility as part of a larger health care network. “The
intranet site was originally built as location for links to a variety of VA, government, and
private sector websites that would help employees in the performance of their duties, and
enhance the mission of the VA Mid-Atlantic Health Care Network,” says Pamela Howell,
Pictured: The main page of Medical Library Online. Each page has its own online
holdings and links to different electronic medical library products purchased by
individual facilities, VISN 6, or the VA as a whole. Technically, each facility’s holdings
The team also incorporated several Web applications into the intranet. Contracting
personnel can access the VISN 6 Solicitation and Contract Log, for example, which lets them
track solicitation and contract information on requests for goods and services. Public affairs
officials can access an application that lets them update a facility events calendar, local
news articles of interest, and other communications functions, which can then be made
available to all employees.
In addition to job-specific assistance, the intranet also provides more general support, such
as phone and contact information, policies and memoranda, up-to-date performance data,
VISN programs, all VISN and medical center policies and information bulletins, performance
data for the VISN network, links to employment- and benefits-related sites, links to VISN’s
partner agencies, VISN 6 facilities’ news and events, and online educational resources.
The intranet also offers online education—thirty intranet-based courses—to train employees
in a variety of areas. The course page’s methodical layout and class descriptions help staff
members understand course objectives, and the Next button makes pages easy to navigate.
Course contents are well outlined, as is the course length and the students’ standing at any
given time. At the end, students can take a quiz to measure their newly acquired
knowledge. Results are immediately scored, and if a student passes, his or her name, ID
number, date, and course title are logged into a database accessible to educators. If
students fail, they can retake the course or the quiz.
The site also provides timely, accurate news—a feature that users appreciate. “Our
technology has changed significantly over the last several years, and that allows us the
privilege of being able to stay very topical with our news, and actually present it as it
happens,” explains Daniel F. Hoffmann, the VISN 6 network director. “This allows our
employees to tap into the news, not only for their own medical center, but also to obtain
news and events from other medical centers. The other added value to us, from a VISN
point of view, is that it has the mark of reliability associated with it. If it gets on our
website, by definition, it is reliable news. The website has a certain immediacy and reliability
that our employees, VISN-wide, can tap into from their local facilities. They have a greater
appreciation for how they fit into the total schema and care of our veterans.”
With so much news and so many links and applications on the intranet, the team decided to
filter information to help users find what is specific to them. They faced challenges,
however, when trying to offer personalization features, as VA’s headquarters places
restrictions on the use of persistent cookies. The team came up with a creative solution that
still follows the rules: they use session variables, which lets them provide customized
One of the most unique design features also uses session variables to display facility-
specific information. Jones explains, “Our VISN has an ongoing program where we strive to
see all patients within twenty minutes of their scheduled appointment times. We track data
regarding how we are doing on this measure. We then upload the data to the website
quarterly, so that employees can see how we are doing.”
Pictured: Simple graphs help employees monitor the progress of meeting goals. Data
for the bar charts is generated on the fly, so the information is up to date. A message
from the network director explains the importance of the charts.
Visually impaired users can also access performance results. A version of the page for
vision-impaired users simply lists raw performance data so users can listen to screen-reader
software read the results.
In addition to the specific features, the intranet also has a more symbolic value: The design
and content mirrors and supports a shift in VA’s goals toward more patient-focused care.
The information and applications on the intranet coincide with and strengthen the
organization’s overall goal, as every intranet should.
TECHNOLOGY
The VA Office of Information Field Office in Silver Spring, Md., hosts the ColdFusion
application server and Microsoft SQL 2000 database running the VISN 6 site. For searching,
the intranet uses the VA intranet search engine, which spans all twenty-one VISNs, but
limits returns to results with “netsix” (VISN 6) in the address to keep them relevant.
USERS
The intranet is available to all full-time VISN 6 employees with PCs or VPN access—about
10,000 people in three states. Users range from physicians to maintenance workers
employed at eight medical centers and twelve outpatient clinics. The intranet is also
accessible to the Veterans Health Administration at large—which has 200,000 employees in
twenty-one VISNs.
BACKGROUND
In 1999 and 2000, the VISN 6 office and four of its eight VISN facilities each created and
maintained their own separate intranets. The look and feel of each was distinct, though
much of the content was similar. In 2002, the VISN 6 network director wanted to
consolidate the various VISN 6 intranets into one to promote a sense of one healthcare
network. A consolidated intranet would be an authoritative source for internal news and
information, and would free many site content managers from creating what was essentially
duplicate content.
In January 2001, VISN 6 hired a new webmaster. For the one-intranet redesign, he met
with the head of each VISN 6 intranet, evaluated what was on the various intranets and
why, and continued to liaison with each intranet head as he designed a new intranet.
“Because some of the facilities had already developed local intranets, it was a tough battle
to sell the concept of one integrated website, so I adopted a ‘bridge’ solution that would
serve as version 1.0,” says Jones. This stopgap intranet standardized design for all intranets
while leaving content creation to each facility.
Before long, sites began repurposing content from the main VISN intranet. “We have very
limited resources, especially in information technology, so having a number of people
creating and recreating the same thing seemed inefficient,” says Jones. The push toward
one intranet increased. Jones also designed several Web applications able to return facility-
specific results from a single database. Now he had to transition from many intranets to
one, and at the same time overcome political roadblocks from the VISN 6 facilities that had
their own intranets.
TIMELINE
• Jan. 2001: Full-time webmaster hired. The VISN office and four of the eight VISN 6
facilities each had independently operating intranets.
• February 2001: Webmaster meets with existing intranet heads.
• July 2001: Design and development of intranet “version 1.0”—nine separate
intranets that used identical templates to standardize the look.
• January 2002: Design and development of intranet “version 2.0” begins. Purpose:
eliminate frames, revamp content creation, and migrate best content to a new,
single intranet.
• March 2002: Version 2.0 goes live.
• March 2003: Prototype of current site created.
• April 2003: Redesign for unified intranet begins, along with content ownership
revamping.
• July 2003: New site development begins. Structure, navigation, and templates
developed; templates filled. Web applications for posting and generating
performance data finalized.
• November 2003: New site goes live.
RESULTS
With one integrated site serving all eight VISN 6 facilities and their headquarters, site traffic
doubled practically overnight—good news for the “one intranet” campaign. Users gained
access to much more content, though much of it was pre-existing. “In the previous intranet
version, content owners had to physically link from the local website to the VISN site, and
many did not do that,” notes Jones.
The new intranet’s shallow information structure lets users get anywhere within three clicks.
Many users e-mailed with positive comments, especially about the new design and content
arrangement.
The new site features a news and events section with teasers on the homepage, which
keeps it looking fresh. Using a Web application, public affairs officers at each site post news
and events directly to their facility’s homepage. “As a result, employees are more aware of
what is happening at their facilities and others throughout the VISN,” says Jones.
The new intranet mirrors changes in VA thinking. “As our organization moves more and
more toward an integrated healthcare network that is veteran-focused, cost-effective, and
value-added, our intranet site needed to be a reflection of that. It was that desire that led
LESSONS LEARNED
Insights from Charles Jones:
Work with politics. “Pay attention to the internal politics of the organization. It is much
easier if you can find a way to work with it, rather than against it. By utilizing the facility
parameter on the homepage and setting a few session variables, I was able to design a site
that looked, walked, and talked like a facility intranet, but is actually the VISN intranet.”
Start small, delegate well, then build. “Prototype whenever possible. Involve subject
matter experts and make them immediately responsible for content. Also, develop your
policy for posting information before you go live with your website. Most importantly, when
it comes to application development, develop something that works first, then make it
pretty. Don’t try to do both at the same time.”
7
Section 508 includes accessibility related laws in the United States. For more information, see
http://www.section508.gov/
SUMMARY
The Federal Reserve Bank of Richmond’s intranet, 5Spot, 8 is a communication tool that
keeps 1,500 users in several different locations apprised of current events. Forums and
other information collection keep employees in touch, and the persistent navigation—which
presents the most needed and used features—makes this intranet very straightforward.
To heighten employee awareness of work-related information, the intranet offers a
comprehensive news section for the entire district, as well as local news for Baltimore, Md.,
Charlotte, N.C., and Richmond, Va. Delivering this timely and relevant information can
increase employee knowledge of the Federal Reserve System, the Fifth District, and
departments within the Fifth District, and help users make more informed business
decisions.
The intranet also facilitates business-related collaboration among its users, including a large
group of traveling bank examiners, and operations employees who don’t have PCs at their
workstations. News and forums can also foster a sense of community among departments
and locations in the Fifth District.
The homepage’s center column is reserved for news. Here, users can get a quick overview
of the day’s district, local, and national headlines. National Headlines features a mix of
headlines selected from Factiva—typically about Federal Reserve System banks,
supplemented by general national news headlines. Links to More District Headlines and More
National Headlines provide easy access to complete lists of the day’s headlines.
8
Meaning of the Name: Five spot is a casual term for a five-dollar bill. The number five is significant because
Richmond is the Fifth Federal Reserve District.
The main news page’s Spotlight calls out the most interesting or important news items. In
addition to dating the items and featuring clearly written headlines, this section offers links
to local news items, which reinforces location.
As for traversing the site, persistent navigation makes this a breeze. Menus are organized
by task and employ simple terminology. Designers focused on making menus easy to use,
because research revealed that users had difficulty locating information and performing
tasks on the previous intranet.
In the new menus, top-level choices expand for more selections, which keeps the top-level
list short. Unlike cascading pull-down menus, 5Spot’s expanding menus do not pop-up over
the content area and interfere with users’ view of the current page. Users can also take
advantage of the small plus and minus signs at the top of menus. These signs let users
expand or collapse the entire menu with a single click. The red arrows to the left of the
menu choices indicate subsections.
Breadcrumbs combine with a gray-highlight bar in the left-hand navigation to show the
current page’s location in the site structure. The black heading at the top of each page also
names the main section, and beneath that, a red heading shows the subsection. Third-level
subsections are indicated with a smaller black heading below the red subhead.
The top, horizontal navigation—which the designers call utility navigation—appears in the
black bar at the top of every page. The designers carefully selected this section’s links to
Pictured: The Phonebook page, where users can search for a person using many
different criteria.
Even with the intranet’s simple navigation, some users will prefer to search. Thus, an open
field is available in the top-center area of every page. For those who want to construct more
complex searches, they can click the Advanced Search link, leading to a page that lets them
enter Boolean searches without having to know the Boolean syntax.
The intranet designers and organization managers realize that quality-of-life satisfaction can
increase job satisfaction. Thus, the intranet offers more personal features in the Employees’
Corner, which is for and about employees—not the bank. The online employee marketplace
is one very popular tool there that lets employees advertise items and services. This
Pictured: Users can buy and sell personal items using the Marketplace area of the
intranet.
There are many other features in the Employees’ Corner, including cafeteria menus; gym
hours; fitness class schedules; information about health and wellness topics; information
CONTENT MANAGEMENT
The Federal Reserve Bank of Richmond uses Interwoven’s TeamSite, introduced in August
2003 as part of an intranet redesign.
The 120 content providers use one of twenty templates—built in-house using designs from
Ironworks Consulting—and have a list of which templates to use for a particular kind of
content. There are two style guides, which cover writing and design. “We’ve also distributed
a copy of the sitemap, labeled to show which template should be used in each area of the
site,” says Trisha Meade, 5Spot’s lead content editor.
TeamSite routes submitted content to a department or group manager for subject-matter
sign-off. From there, the corporate communications department reviews and edits the
material for adherence to style guides, then publishes it. Corporate communications also
contributes all corporate- and district-level content. This distributed content-authoring
approach is a legacy of the previous intranet’s organic growth.
TECHNOLOGY
Interwoven’s TeamSite handles content management. The Web server is Sun’s iPlanet. Code
editors and development tools include Macromedia Dreamweaver MX, Macromedia
Homesite+, UltraEdit32, TextPad, GNU Emacs, and WebSphere Studio Application
Developer. Adobe Photoshop, CorelDraw, and The Gimp handle graphics. Application servers
are Macromedia ColdFusion and IBM WebSphere. For prototyping, the intranet team uses
Microsoft Access; Microsoft SQL Server runs on the live intranet. ColdFusion’s Verity
software handles intranet searching.
USERS
The intranet supports 1,500 users in Baltimore; Charleston, W. Va.; Charlotte; Columbia,
S.C.; and Richmond. Also, the bank plans to introduce kiosks to serve employees who don’t
have PCs.
USER TASKS
• Access national, system, district, and local news, and view news archives
• Find forms, policies, procedures, and manuals based on a variety of parameters,
including department, topic, need, and form name
• Plan meetings and register outside guests
• Access the employee phonebook, key contacts, or technical support information
• Review cafeteria menus and check the weather at any location
• Access HR information, and view HR and IT training schedules
• Learn more about the Federal Reserve System, the Federal Reserve Bank of
Richmond, and all fifth-district locations
• Access resources available through the bank’s research library
• View archives of news and employee publications
• Buy and sell items in the online employee marketplace
• Access travel applications and information from a central location
BACKGROUND
The Federal Reserve of Richmond’s intranet launched in July 1996, after the Federal
Reserve’s Board of Governors commissioned an intranet and invited the twelve district
banks to join. As each joined, it built its own site; no common guidelines existed. That ethos
However, the test did encourage the team to add more routes to existing information. “For
example, if a user wants to set up an online meeting, he might expect to find that in the
Meeting Planner section, as well as under Forms and References. So we decided where
content would live and then, based on the test results, put links in other areas where users
had told us they would look for it,” says Trout.
TIMELINE
• October 2002: Current and proposed content analyzed. User survey developed and
released.
• November 2002: Conducted user group discussions. Created user profiles.
• December 2002: Started information architecture design. Developed a functions
and features list and a site map.
• January 2003: Developed screen layouts. Started work on label testing, wire-frame
testing, and analysis. Finalized homepage and template designs. Started training
plan.
• February 2003: Wrote style guides. Began modifying existing applications to fit the
new 5Spot look and feel, and started creating the technical environment.
• March 2003: New tool development began on the meeting planner, QuickPoll, and
weather-information feed.
• May 2003: Completed design and QuickPoll tool development.
• June 2003: Began testing applications.
• July 2003: Began creating new content for launch. Completed application-
development work.
• August 2003: Completed content creation and editing. Conducted final testing.
5Spot launched.
RESULTS
The redesigned intranet improves information location, employs a CMS with better
publishing workflow capability, and adds features to improve employees’ productivity.
Whereas the previous site lacked news, for example, employees can now access national,
district, and local news, updated daily, on the intranet.
The new site is also more inclusive, with content creators at different offices contributing
location-specific news. “Users told us that the previous site was Richmond-centric, with few
benefits for users outside Richmond. Now users in every location can find information
Pictured: The services roll-up application, accessible via a link from any intranet page,
lets users sort departmental and group services by title, department, or subject.
LESSONS LEARNED
Insights from Sandy Tormoen:
Intranet development is different. “We tried to apply application-building processes to
intranet development, but this project was too complex. Analyzing issues from afar didn’t
work either. You have to just get your feet wet and go.”
Insights from Kendall Meddows:
SUMMARY
The Government Offices of Sweden’s intranet supports an impressive number of tasks, all
joined in an attractive design. What’s more striking is that this simple design and single
intranet actually unite all of Sweden’s central ministries (the highest level of the national
government’s executive branch) as well as Sweden’s embassies and foreign missions.
Most of those working at the Government Offices—political appointees and civil servants
who work as administrators, legal advisors, analysts, and secretaries—are involved in
drafting and processing government bills, reports, and national legislation. All Government
Offices’ employees—approximately 4,300 in Stockholm and 600 at Sweden’s missions
abroad—have access to the intranet. The intranet can also be accessed on security-
approved laptops. Through the intranet, all of Sweden’s national ministries’ can access
information, news, and tools presented in one consistent structure with a common look and
feel.
The intranet supports tasks such as: accessing organizational and HR information, policies,
and handbooks; searching external news feeds; accessing law texts; viewing job listings;
accessing the Government Offices’ registry; signing up for internal training programs;
booking travel arrangements; searching for and booking library resources; accessing
various forms; and reviewing and editing employee profiles and locations in the telephone
directory. Examples of less vital but nonetheless popular tasks include viewing cafeteria
menus, posting items for sale, and taking interactive surveys.
The elegant homepage alone offers many features. At the top of the homepage, the color-
coded tabs link to the main pages of the Prime Minister’s Office, each of the ten ministries,
and the Office for Administrative Affairs. The links in the upper right go to the government’s
external websites in both Swedish and English. The right-side column has links to the
9
The name of the central section, Insidan, translates as both “the inside” and “the inside page” (sida denotes
both “side” and “page” in Swedish). The names of the ministry sections are, for example, “the Justice page,”
Justitiesidan, or “the Environment page,” Miljösidan, for the Ministry of Justice and the Ministry of the
Environment, respectively.
While the summary news items on the homepage are helpful, employees are also able to
explore more news using the intranet’s Newsservice/Nyhetstjänsten feature. The Registry
link accesses the Government Offices’ registry through a central database. Employees can
search back to 1992 across ministry borders and easily get a list of archived items.
The intranet uses a common design throughout. This reduces confusion when users look for
information, contributes to a single-organization culture, and cuts down on learning time
10
TT is the Swedish equivalent of the Associated Press.
Pictured: Main pages for two different ministries show the similar page designs. On
the left is the Ministry of Culture/Kulturdepartementet. On the right is the Ministry of
Justice/Justitiedepartementet.
As on many intranets, the Government of Sweden’s employee directory is one of the most
popular features. Users can search by name, telephone number, ministry, or department.
Search results include employee information such as name, extension, cell phone, forward
to, title, department, and e-mail. This intranet offers not only employees’ basic
organizational information, but also something far more innovative. It gives information
about the employee’s current whereabouts, such as if an employee is away on a business
trip or gone for the day, and when he or she will be back. Other intranets provide this
feature, but because users typically must log in to the intranet to update it, the information
often becomes stale and inaccurate. In this case, however, the employee can easily change
this information via telephone or through the central switchboard, and the information is
automatically edited in the intranet’s employee directory.
This jam-packed though uncluttered intranet makes it easy for employees to find relevant
information about each other, their organization, and the world.
CONTENT MANAGEMENT
A custom-developed intranet tool, built in 1999 with ASP for the front end and SQL
database for content storage, lets designated employees publish short news items. They can
also preview content, and set a go-live date and time.
Intranet and Web editors publish longer articles using Microsoft FrontPage, guided by the
intranet team’s templates and graphics guidelines.
A document server handles documents in Microsoft Office and Adobe Acrobat formats.
Any part of the intranet that is database-driven can be updated through a Web interface.
The IT department manages the technology, and content owners update their relevant
databases.
TECHNOLOGY
Developers use Microsoft Visual Studio 6.0 for development and maintenance, Photoshop for
graphics, and FrontPage for handling HTML pages. The intranet runs on Microsoft IIS 5.0
Web server and Microsoft SQL 2000 databases, on three Windows 2000 servers.
USERS
There are around 4,300 users in Sweden (most of whom work in Stockholm) and
approximately 600 located at Sweden’s missions abroad. Users include political appointees
and civil servants who work as administrators, legal advisors, analysts, and secretaries.
Most of those working at the Government Offices draft and process government bills,
reports, and national legislation.
USER TASKS
• Access employee information, policies, handbooks, and law texts
• Search external news feeds and the Government Offices’ registry, and search for
and book library resources
BACKGROUND
The intranet began when e-mail and Internet access were simultaneously introduced in
1996; it consisted of a single start page that offered Web links and e-mail access.
In 1997, the ministries—separate since the 17th Century—became a single entity, and the
Permanent Secretary requested a common intranet for all ministries. Employees from IT,
information, library, and HR departments comprised the design group; they started the
project by studying users’ needs.
The team faced users who were still adjusting to the change—after all, things had been
done a certain way for 400 years—and who were in culture shock. “One of the first
comments from a ministry employee about the intranet was, ‘But how do we keep the other
ministries from seeing our information?’” says Lennart Fahlén, the initial intranet project
manager. While that attitude is no longer a problem, “it does illustrate the major shifts in
thinking that the organization has gone through, and is still going through—and not only
with regard to the intranet.”
The first full-fledged intranet was launched in 1998.
“What we think is rare, if not unique, is the fact that all of Sweden’s central ministries—the
highest level of the executive branch of the national government—as well as Sweden’s
embassies and foreign missions are united through a single intranet,” says Fahlén. Note that
the intranet doesn’t include the whole of Sweden’s central government. When the Swedish
constitution was created in 1632, Sweden’s executive branch delegated much of its
operating power to national agencies, unlike the U.S. or Britain.
In 2001, a redesign improved the individual ministry pages, added an index, and spiced up
visuals.
For the latest redesign, users wanted better search and more exciting visuals.
TIMELINE
• 1996: First intranet launched: a single page offers Internet links and e-mail access.
• January 1997: Ministries merge under one authority.
• 1997: Vision formed for a central, role-based intranet.
• 1998: Editorial board created to govern content and structure. Ministry intranet
editors begin extensive coordination.
• 1998: Launch of first full-fledged intranet.
• 1999: First intranet redesign creates a common structure and design for all
ministry pages.
• 1999: Intranet adds access to the government's registry, online training courses,
and law databases.
• 2000: Library databases and job postings move to the intranet.
• 2001: Intranet redesign clarifies information structure, improves the indexing and
search, and increases visual appeal. Organization-wide employee directory
launched.
• 2002: Design team adds intranet voice-mail management tool and online business-
travel booking.
• 2003: Organization-wide news feed and for-sale forums launched.
To create a new search engine, the redesign team got creative. “A decent search engine
was too expensive, so we worked on clarifying the structure, together with developing an
extensive index. This has proven to be a usable and fairly maintainable tactic, even if it
does take time,” says Jansson.
LESSONS LEARNED
Insights from Tracy Mitchell-Björkman:
Think big. “Even if the organization isn’t ready and all the necessary technology isn’t in
place, and even though the intranet team may be years ahead of its organization,
remember it takes time for ideas to develop and show their worth. The path is not always
straight.”
Think long-term. “Consider long-term maintenance—both editorial and technical—from the
beginning.”
SUMMARY
Many designers think that making sites accessible will hamper site aesthetics—and even
usability—for users without disabilities. On the contrary, considering accessibility when
designing often leads to interfaces that are not only accessible for users with disabilities, but
are attractive and easy for everyone to use. The London Underground intranet is evidence
of this phenomenon. By adding people with visual- or mobility-related disabilities to their
target-user group, designers created accessibility-driven designs that ultimately helped
every user. Two examples are giving all links concise names, and using scalable, rather than
fixed, font sizes. Using hidden links and a special accessibility mode vastly improves the
user experience for people with disabilities, yet it doesn’t affect the productivity of
employees who are not using assistive devices or software.
The overall goal of the London Underground’s intranet is to offer staff members up-to-date
information and ensure that all staff, including those with visual and mobility impairments,
have unfettered access to that information. The intranet designers were therefore highly
aware of their users—train drivers, station staff, and administrative office staff—and
potential accessibility issues. Designers linked all pages to style sheets, so people can
choose between the provided accessibility style sheet or their own style sheet. Also, the
fonts are not hard-coded, so users can take advantage of the browser’s function that lets
them increase (or decrease) text size.
The team took accessibility to a higher level by implementing an accessibility mode for
users with visual- or mobility-related disabilities. One feature, for example, lets users
change the page background and text colors. This makes for clearer viewing, and in some
cases makes otherwise illegible words readable. 11 The page design also gracefully resizes to
any window size.
11
For more information about visible colors for people with low vision, and information about good contrast for
all users, see Lighthouse International’s recommendations at http://www.lighthouse.org/color_contrast.htm.
Pictured: The Marketing & Planning main page as viewed with large fonts. The page
resizes gracefully, and users with low vision can take advantage of the browser’s
features for changing the font size.
Using the accessibility mode is far better than creating a completely separate text-only site
for users with disabilities. It also complements the current site, and adds no clutter or
confusion whatsoever for sighted users. The first link on every intranet pages is a hidden
link with an ALT tag. Although invisible to the typical user, people using screen readers will
hear the link first, and have the option of switching to the intranet’s accessibility mode.
Users can also use a shortcut key, “Alt-X,” to access accessibility mode.
Any user can access accessibility mode via a visible link in the quicklinks bar, though an
interstitial page first explains what accessibility mode is, to reduce help-desk calls from
people who think something’s wrong with their display.
The link labels, which are concise and meaningful, are an especially useful feature for
screen-reader users. The designers avoided commonly used but unnecessary words, such as
“click here” and “go now,” which reduces useless chatter for users listening to links being
read. This also helps people using screen magnifiers scan for the phrases they’re looking for
more quickly.
Accessibility mode also hides banners and the main navigation, streamlining screen-reader
users’ navigation options. Graphics-intense applications also got an accessibility translation.
For example, on the intranet’s calendar, green, yellow, and red dots represent confirmed,
tentative, or canceled events, and all have ALT tags with those terms so screen-reader
users don’t miss out.
Font size is fully adjustable. Using Internet Explorer’s built-in font-size capabilities, the
design team created pages with fonts that change size relative to the page’s base size. This
feature works whether users are in accessibility mode or not.
Most content, including menu links, is textual; intranet pages only uses graphics to help
reinforce a message. This improves accessibility as well as page-download time. Because
people using screen readers often encounter difficulties accessing content in frames, the
team has a “no frames” policy for all pages.
Accessibility and usability elements don’t end there. With more than 23,700 pages on the
intranet, having a consistent look and feel for all pages helps users tremendously, though
the intranet design team had to work very hard to achieve this. The layout on all pages is
consistent, but the top banner and menus are color coded for each department, helping
users to quickly tell where they are. Today, the team is working on reorganizing the intranet
by tasks rather than by department.
At many organizations, finding images for presentations and publications can be a struggle.
To address this, the intranet offers a graphics Image Library, and users can submit their
Pictured: The Image Library features graphics for use in publications and
presentations. Users can submit their own images, and the search features make this
library accessible.
Pictured: Results page from an Image Library search. The images are clear, obviously
named, and include descriptive ALT tags for visually impaired users.
CONTENT MANAGEMENT
The intranet has over 23,700 pages and more than 100 content publishers.
Intranet content is served via ASP, with template elements stored centrally in a global
library. Only the intranet team has access to the templates, which are designed using
Macromedia Dreamweaver.
Users with permission to publish can only do so to predefined site areas. The intranet team
maintains those permissions via FrontPage 2000 settings; all content creators use it.
Content creators get development server access for uploading content, which they can
make live whenever they choose. (The organization is planning to migrate to content
management software.)
The search engine is Microsoft IndexServer, though London Underground plans to replace it
with MondoSearch.
TECHNOLOGY
The intranet is hosted in-house on a Microsoft Windows NT 4.0 server using IIS 4.
The intranet team uses JAWS software 12 to test page accessibility for the visually impaired.
12
JAWS is a popular screen-reader software application. It is produced by Freedom Scientific,
http://www.freedomscientific.com/fs_products/software_jaws.asp.
USERS
Of the 12,000 London Underground employees, approximately 6,500 have regular access to
the intranet through networked PCs. That will increase with imminent thin-client monitor
installations in many of the 255 stations managed by London Underground; only fourteen
lack network access. (Note there are twenty additional stations, which London Underground
doesn’t manage.)
The intranet team is experimenting with new methods to extend the intranet to staff
members without frequent PC access. A pilot project enables intranet access for 400
operations staff at an Acton Town Internet café. In the future, the remote intranet access
could be extended to PDAs, Internet kiosks, or an extranet.
A small number of London Underground intranet users have visual impairments.
USER TASKS
Users often use the intranet to:
• Locate people or personnel information via the phone book
• Read news, press releases, staff bulletins, and organization notices
• Access commonly used forms and letters
• Peruse the restaurant’s lunch menu
• Get PC help
• Access publishing guidelines
• Find reference material, including standards and procedures, manager’s daily
reviews, and safety information
• Examine train timetables, see which trains are in service, and view station
refurbishment schedules
For HR-related activities, users can:
• Request annual leave
• Enter timesheets
For projects, London Underground employees can:
• Reference key milestones
• Find project contacts
13
For more information about the W3C WAI see www.w3c.org.
In September 2003, the intranet team began preparing content for migration to a CMS.
TIMELINE
• 1995: London Underground intranet created under IT directorate; volunteers
maintain content.
• 1999: Previous intranet style guide created. Pages, graphics, and navigation
dissimilar across the intranet.
• 2001: Intranet oversight moved to communications directorate. The new motto is:
“Content is king.” Publishing structure reorganized, content creators trained.
• October to December 2002: Moved to new template suitable for many screen sizes.
All content cut and pasted into new ASP pages. Template changes now applicable
site-wide.
• January 2003: Standardized navigation added to every page, including search box,
quicklinks, and a one-level-deep sliding menu to replace the existing JavaScript
expanding menus.
• May 2003: “Accessibility mode” work begins with new templates and navigation.
Content creators get new guidelines to facilitate more accessible text.
• June 2003: Migration from Microsoft Index Server search engine to MondoSearch
begins. All pages get titles, meta-data descriptions, and keywords, and are slotted
in a predefined category. Search engine results immediately improve.
• July 2003: Current site navigation implemented: fixed left-hand menu (variable by
directorate) and context-sensitive menus on right.
RESULTS
The intranet grew from a few hundred pages in 1999 to over 23,700 today. The initial 2001
redesign particularly boosted content-author participation. Today, the intranet receives
70,000 site visits per week, and continued rollouts—especially to users without a PC at
work—should increase uptake.
Getting there required some tough love. The intranet team—only two people—centralized
template design, nudging would-be amateur graphic designers to focus exclusively on
creating and improving content. At the same time, the team encouraged management to
include intranet activities as part of employees’ job descriptions, and to authorize ongoing
training for all content creators that emphasizes writing easy-to-scan documents, putting
important information at the top of the page, and creating descriptive hyperlinks.
Clarity carries over into each page’s “you are in” breadcrumb bar. The information is
generated by the names of Web server folders and files, driving content creators to keep
things simple, and enforcing good housekeeping. As an added benefit, it also improves
search engine efficiency.
Content creators now have the tools they need to keep site content fresh and usable, plus
an Image Library full of pre-approved images.
One especially useful new feature is the broken links e-mailer. Whenever a user receives a
“page doesn’t exist” error after clicking an intranet link, a behind-the-scenes e-mail is sent
to the relevant content contributor. “Since the introduction of this feature, the error page
has gone from being the most frequently viewed intranet page—at 21% of total page
views—down to below 1% of page views,” says Oatham.
To maintain the site, the intranet team constantly analyzes the most visited pages, using
the information to populate the quicklinks toolbar.
The intranet team’s approach is working. Average site visits per week have jumped from
1,000 in 2001 to 70,000 today. “We attribute this to changing the homepage daily; well-
thought-out, up-to-date content; and enhanced usability,” says Shaw.
Accessibility work also paid off, but for more than just visually impaired users. “There is also
a visible link to the accessibility mode for people not using screen readers and this mode
has been useful for people dialing in from outside the network as it gives faster download
time,” says Oatham. As so often happens when designing more accessible software, other
users—in this case, mobile ones especially—also prize the new functionality.
Moving forward, the intranet team plans to integrate four company intranets into one
intranet that will be available across the Transport for London Group. “The London
Underground intranet is by far the largest and oldest of all the intranets in the Transport for
London Group,” says Oatham. “We hope to apply a lot of our knowledge and lessons learned
to this new project, to avoid making the same mistakes again.”
SUMMARY
The silverorange intranet platform has proven to be an attractive and very easy-to-use
system. In fact, designs from silverorange have made the top ten in not one, but two
Nielsen Norman Group intranet design annuals. The silverorange designers created the
intranet platform iteratively employing a combination of usability methods, including field
studies, basic usability tests, card sorting, and heuristic evaluations. Even this excellent
intranet, however, wouldn’t just work perfectly right out of the box for the NCR-IRAP. The
design team, consisting of NCR-IRAP and silverorange employees, needed to do research
with the specific users and target the design accordingly. In fact, by studying the NRC-IRAP
server logs, the team discovered that few employees were using the old intranet tool, and
some had even begun developing pirate sites to meet their needs. The silverorange team
helped deploy an intranet tailored to NRC-IRAP’s needs, before it was too late, ultimately
producing yet another award-winning design.
NRC-IRAP employs more than 400 people, including a network of field agents—Industrial
Technology Advisors (ITAs)—who operate throughout ninety communities across Canada.
ITAs work independently or in teams to assess and enhance clients’ technology growth
potential. Their mobile work environment can make keeping in touch with clients and
coworkers a challenge, but the intranet facilitates this important communication. Users can
post items on the intranet, including messages, tasks, events, checklists, work reports, files,
and news. Other custom item types are available too, including frequently used forms. All
items can have file attachments and allow for threaded conversations.
The Post a New Item link is always visible in the left-side navigation and leads to a simple
form for creating a new posting. Using basic drop-down menus, users can assign an
importance level to a message, and can relate messages with projects and folders. The
easy-to-use editor, which looks similar to the familiar Microsoft Word interface, allows even
users who do not know HTML to add links and basic formatting to the message. Required
fields are indicated with yellow stars, and effective tips—such as What do priorities mean?—
help prevent errors before they occur. By selecting other item types from the right-most
Pictured: A simple form for adding a new posting. Similar pages with additional fields
can be used to create other item types, such as tasks, events, and checklists. The
simple “WYSIWYG” editor allows users who don’t know HTML to add links and basic
formatting to their post.
More ambitious users can set rules that will inform them of updates through e-mail or other
notifications. Front-page alerts, for example, keep users apprised of any intranet activity
since their last login. These alerts are like e-mail alerts, but appear on the user’s front
intranet page. Users can subscribe to different ones or choose only alerts for particular
users. The NRC-IRAP intranet’s core consists of a set of tools and work areas called forums.
Users access their forums by clicking the Subscribed Forums or All Forums links in the left-
hand navigation bar, or by using the search tool, which includes results from forums.
Content pushing, a persistent theme on this intranet, eliminates noise and ensures that
people see the information they need—crucial for a site with 145 forums. This allows the
same intranet to be used by many different types of users with different tasks, from client
communication to high-level management work. For example, a user working on three client
Pictured: The NRC-IRAP intranet is divided into forums that can have any number of
members and folders. Users can belong to any combination of forums, depending on
which teams they’re working with, and they see only their own forums.
Each forum has its own main page with a list of members, content folders, and other
management functionality. Users can also search by forum-only, a very nice feature—
especially for larger forums. Users can also change the order of the folders in the forum list.
Any user can create a forum, and either become the owner/moderator or designate
someone else to fill that role. Owners determine content and folder managers; they also
control access rights—granted to either groups or individuals—and can grant read-only
access, and add, delete, or change members’ access levels.
The left-side navigation and top-horizontal menus are available on every page of the
intranet. These and breadcrumbs help users navigate effortlessly. The keyword search
appears as a plain, open field on every site page as well.
Users can view the calendar tool, which is always available on the left-side menu, by day,
week, or month. The tabs to select the views are obvious and provide both text and icons
for quick scanning. Users can easily choose the month and year from drop-down lists. They
can also easily add a new event. For jam-packed calendars, the application provides filtering
tools that show only a certain type of item, items from a specific forum, or items assigned
to a particular person. For example, a user could show only his or her own assigned tasks.
The NRC-IRAP intranet had to work in both of Canada’s official languages: English and
French. This challenge proved minimal: it was accomplished through a French technical
translator’s expertise and through the silverorange intranet platform, which is
internationalized and multi-lingual.
Another challenge: like all Government of Canada websites, the NRC-IRAP intranet must be
compliant with the clearly defined set of Common Look-And-Feel Guidelines set by the
Government of Canada Treasury Board. 14 Designers customized the silverorange intranet
platform to meet those look-and-feel guidelines. Adhering to them wasn’t oppressive, say
the designers. “We learned that we could still be creative and expressive. And, as opposed
to constraining users, the CLF guidelines and corporate branding actually made our tools
easier to use and saved us time and money,” says Loewen.
14
The guidelines can be found at http://www.cio-dpi.gc.ca/clf-nsi/index_e.asp.
CONTENT MANAGEMENT
The NRC-IRAP intranet is a custom-developed intranet based on the silverorange intranet
platform version 3. Additional technology includes PHP and SQL.
The intranet CMS differentiates between two types of content: user-generated and articles
and content from outside the organization.
Content tools include both WYSIWYG and code-view HTML editors, multiple languages per
article, a check-in and check-out system, and multiple-author capability.
NRC’s senior management went a step further than the Common Look-And-Feel Guidelines,
mandating a common look and feel for all of NRC’s sites. The silverorange intranet platform
was customized to meet all of those guidelines, and reflect NRC-IRAP branding.
TECHNOLOGY
Using Adobe Photoshop, silverorange developed NRC design concepts and graphics
elements.
The silverorange intranet platform runs on Dell servers with Microsoft IIS, Microsoft SQL,
and PHP4. The search engine was custom developed by silverorange. Additional in-use
technologies include XHTML, cascading style sheets, and PHP. The silverorange software is
internationalized and multilingual.
USERS
Over 400 NRC-IRAP employees work at the national office in Ottawa and in ninety different
Canadian communities, with 260 field agents often operating independently or in small
groups at client sites across Canada.
BACKGROUND
In 2001, an audit by the NRC-IRAP communications department revealed that fewer than
10% of IRAP employees used the intranet. Yet most employees said their tool of choice
would, in theory, actually be an intranet. Follow-up testing revealed employees weren’t
Luddites; intranet usability was poor, leading some users to even “develop ‘pirate sites’ to
meet their needs,” notes Loewen. That’s no surprise since IRAP’s field agents, scientists,
and engineers—known as ITAs—work across Canada, evaluating clients’ technology needs,
then lending their skills. They also value technology for trading ideas and information. “Each
ITA is a knowledgeable guide who works in-person and on-site to lead you to the resources
best suited to your situation. Your ITA will help you set priorities and establish the most
direct route to achieving your goals,” says Loewen.
For example, ITAs helped find technical solutions for Frantic Films, which develops software
for animating fluids ranging from water to tar. “NRC-IRAP provided us with technical
expertise when we wouldn't otherwise have been able to afford it,” says Ken Zorniak, the
company’s CEO.
“IRAP is around to say ‘let's get this idea off the ground.’ And even if an idea doesn't lead
you exactly where you wanted to go, it still leads you to something else,” notes Hadi
Husain, director of research and development for Zenon Environmental Inc., another NRC-
IRAP client.
TIMELINE
• January to March 2002: Intranet development strategies formulated.
• April 2002: Usability testing begins.
• June 2002: Design requirements finalized.
• July 2002: Developers begin coding website.
• October 2002: Intranet beta testing begins.
• December 2002: Deadline for compliance with NRC-wide common-look-and-feel
policy.
• January 2003: New intranet goes live.
RESULTS
The redesigned intranet gives users what they need: a way to easily collaborate with a
geographically distributed workforce.
One surprising result from the redesigned intranet was that a common look and feel made
the intranet tools easier to use, and clarified some working processes, ultimately saving
users’ time.
The new NRC common-look-and-feel standards helped clarify and simplify the team’s
intranet redesign approach, ultimately saving time and money. “With the new standards
that conform to the official languages, groups gained the ability to collaborate privately in
the language of their choice, publishing in both official languages only when they complete a
project and need to share the information across the entire organization,” notes Loewen.
Previously, IRAP translators ensured that any content postings appeared in both English and
French. Eliminating this translation requirement for private collaborative forums not only
saved money, but also enabled a more ad hoc, fluid intranet work style.
Whereas NRC’s organizational structure was the basis for the previous intranet, the new
intranet emphasized collaboration in its terminology. “Card sorting showed us that users
work better with an intranet designed around tools to help them collaborate, rather that the
organizational structure,” says Loewen. For example, they relabeled “Projects” as “Forums,”
which is closer to in-house lingo and refers more explicitly to community and
communication. When users said that they didn’t understand the meaning of “Make a new
post,” the design team renamed it “Post a new item” (“Afficher un nouvel article” in the
site’s French version).
The new intranet improves several existing features, including search, user and forum
creation wizards, and WYSIWYG functions. Users get management tools for forum posting
and folders, and for personalizing side menus with their subscribed-to forums. They also get
three views of forum postings: the default tree view, chronological listings, or a preview
mode that shows the first three lines of each post. Users have access to My Personal Forum,
a shared space open to whomever they choose. Common uses for this forum include project
collaboration and even sharing holiday photos with workmates. The goal is to reduce stress
on the e-mail servers.
Users have embraced the new intranet. As one user noted in the communications
department’s regular user surveys since the redesign, “the ability to utilize forums as an
interactive space for program and policy management has been extremely beneficial and ...
helped to strengthen communication lines and ensure efficient information dissemination
across the regions where we deliver programs.”
Management support has also been a crucial redesign success factor. “We needed support
from management to encourage employees to try the intranet and new ways of working.
Now, more employees are using the intranet, and are beginning to move away from e-mail
and collaborate more efficiently to accomplish key business processes,” says Loewen.
LESSONS LEARNED
Insights from Lorrie Loewen:
SUMMARY
Consistent with its goal of facilitating communication, the Senate Republican Conference
(SRC) intranet is available for staff members nationwide on multiple devices. The inventive
features, exhaustive content, and consistent navigation all make this a winning government
intranet.
SRC’s intranet enhances communication and research possibilities for all fifty-one senators
in their Capitol Hill and state offices. There are more than 2,300 registered intranet users,
including senators, their chiefs of staff, administrative personnel, and interns.
The intranet is whimsically named TrunkLine, a nod to the longtime Republican Party
mascot, the elephant. The straightforward homepage offers a balanced combination of
features and news. The center column, On the Floor (an allusion to the U.S. Senate floor) is
updated daily with recent news from the White House, Department of Defense, Majority
Whip’s office, and other offices. The Announcements area, including significant speeches,
events, and television spots, is updated weekly.
The left-side navigation (Legislative Shop), the Google search box, and the top horizontal
navigation are available on every intranet page. In the upper right of each page, including
the homepage, is a simple open search field that lets users search for a bill by its number or
name.
The homepage’s right-hand column, In the Gallery, lets users click and view press releases
and previous items from the Recent News area.
The user’s name in the homepage’s upper right corner links to a form that lets users enter
their contact information. The field labels are understandable and the form itself is relatively
brief. Users can also input their interests and affinities so that other users can search by
those criteria.
The Policy Papers link leads to Republican Policy Committee papers organized by month and
year. Users can choose the month they’re interested in from a drop-down list, or view all
papers at once. A brief introduction helps users locating the papers they’re looking for. Each
paper is available in PDF format.
The Leader’s Calendar has a legible, predictable layout, and includes information such as
when the Senate will next convene and which items it will debate or vote on. The calendar
also shows an especially vital piece of data: how many items have been “hotlined.” Hotlines
are brief statements about critical upcoming votes. Hotlined items can be accessed on
BlackBerrys and Palm Pilots, as well as on the intranet. In fact, TrunkLine users can log into
the intranet on PDAs and two-way pagers from any location and read the recent news and
announcements, or browse the archives. Although most TrunkLine users are based on
Capitol Hill or in senators’ state offices, they’re not restricted to office access, which makes
the intranet especially convenient.
The intranet also supplies a Member Voting Record, with multiple ways to search and
compare or report votes made or missed by senators. The archive includes all Congressional
sessions back to 1981.
Another unique feature is the intranet’s database design. Database information is laid out to
transfer easily to wireless devices on multiple platforms and to increase the number of
contributors, even if they’re not Web-savvy. For example, staff members in the Majority
Whip’s office and the Republican Policy Committee (RPC) can update sections of TrunkLine
daily without knowing HTML.
When it comes to everyday tasks, the intranet is extremely accommodating. For example,
legislative correspondents and chiefs of staff use TrunkLine to search information that
comes from Senate offices, the White House, the Republican Policy Committee, the
cloakroom (the Republican Secretary’s Office for Senate floor management), the Majority
Leader’s office, and the Majority Whip’s office. Press secretaries access TrunkLine to retrieve
talking points for the media and to stay updated on television and radio interviews (offices
can save audio files to TrunkLine). Many staffers use TrunkLine’s Key Staff Directory, which
includes all TrunkLine users, to find contacts within a particular Senate office or committee,
or to locate specialists by issue or subject.
CONTENT MANAGEMENT
A product from GSL Solutions, SiteDirector, handles content management. Among its
features is the ability to restrict content authors’ changes to their own intranet areas.
To change or upload content, authors use a pre-existing, Web-based template, pasting
information into text boxes, filling in vote data, or inserting links, pictures, video, or audio.
“This form of content management was custom developed so that each section that is
managed does not look identical to any other section. Different offices have different
preferences for how and what they would like to communicate, and we want to ensure true
‘ownership’ for each content manager,” says Aaron Broughton, information communications
manager for the SRC. The intranet team customizes the content management templates to
suit each individual department’s unique workflow. Content owners include staff from the
SRC, the Republican Policy Committee, the Majority Leader, the cloakroom, the Joint
Economic Committee, and all fifty-one Republican senators’ offices. Each is responsible for
its own content.
The content management template was jointly designed by IT representatives from each
office.
TECHNOLOGY
The intranet runs on four Compaq Proliant Web servers, running Microsoft IIS on a mix of
Windows 2000 and 2003. The application software is Cold Fusion MX.
USERS
There are more than 2,300 registered TrunkLine users, ranging from senators and their
chiefs of staff to administrative personnel and interns.
USER TASKS
All users:
• Read recent news
• Read the Whip Alert, which contains summaries of Senate floor proceedings (the
whip is the Senate’s second-ranked Republican)
• Find talking points on a variety of issues
• Access fact sheets
• Reference archives for any of the above material
• Use the Key Staff Directory
• Search for bills (proposed legislation) by number
• Find issue or subject specialists
• Search senators’ cast and missed votes
Legislative correspondents and chiefs of staff:
• Search information originating from Senate offices, the White House, the
Republican Policy Committee, the cloakroom, the Majority Leader’s office, and the
Majority Whip’s office
Press Secretaries:
• Retrieve talking points for the media
• Keep up to date on television and radio interviews
BACKGROUND
The SRC launched TrunkLine in 1995. “TrunkLine was created to remain functional over
multiple platforms, and to store data in a secure, traditional database format,” says
Broughton. It was designed to attract new users without their having to know HTML, and to
make it easy for them to update information on a daily basis. The database-driven approach
also makes it easy to repurpose information for a PDA or two-way pager.
Redesign means constant evolution, says Broughton. One ongoing challenge, however:
“time and resources,” he says. There are only two full-time staff members for TrunkLine
support, design, updates, training, and marketing.
One surprise during development, says Petty, was “the high demand for customization for
each application.” In fact, when the different leadership offices were ready to add
information to the site, they first wanted to improve their office’s content-input processes.
“They asked for us to help streamline their process. It was good to learn the process and
build a back-end content management workflow to meet that need,” he says.
TIMELINE
• 1995: Joint Senate Republican intranet created.
• 1996: First intranet redesign.
• 1997–98: Additional intranet features and applications added.
• 1999: Major redesign.
• 2002: Major redesign.
• 2003: Latest redesign (three months from start to finish).
LESSONS LEARNED
Insights from Tim Petty:
Real-time pays. “Users always appreciate exchanging information as fast as possible.”
Good word of mouth increases users. “Plan for more users than you might think.”
A website is never finished. “Build a website that can be easily expanded to
accommodate new ideas.”
Query users. “For design inspiration, always ask users what they want, what format they
want it in, and give them what they want.”
SUMMARY
Employees at Ontario’s Workplace Safety and Insurance Board (WSIB) appreciate their
intranet, CONNEX. Before it existed, employees had to hunt through many different sources
and types of media to find the answers they needed to do their jobs. With CONNEX, staff
members can now access numerous tools that simplify their work, as well as current
information from a variety of sources, in one clean package.
The homepage, My WSIB, contains information of interest to all staff, such as corporate
news and messages, job postings, and recent publications. Designers, upon learning that
finding employee phone numbers was a common task, placed the telephone directory on the
homepage’s upper-left side. Using it, employees can search for a person’s phone number as
soon as the intranet launches. Search criteria include first name, last name, and location;
they can also search for employees by phone number. Users can also opt for advanced
search features, or generate a phone list for a particular team or working group. Below the
search-by-person area, links let users find a particular office location. Given that WSIB has
fourteen different offices, this is an especially helpful feature.
The intranet is the main source for HR information, such as policies, vacation request forms,
and the employee assistance program. The most frequently accessed content on CONNEX
relates to the PeopleSoft Integrated Financial Systems software. CONNEX provides a
gateway to the application, along with resources to help staff submit and approve expenses,
generate cost and budget reports, and more.
In addition to basic corporate information, news, and general support, the intranet also
offers applications that directly enhance core business tasks. For example, claims
adjudicators can use a tool to help with one of their everyday tasks: determining average
earnings. Before this tool was created, adjudicators had to search many different
information sources, making the task time-consuming and labor intensive. Policies,
procedures, and guidelines were scattered across hardcopy manuals containing hundreds of
documents. Letters, forms, and worksheets lived in various electronic databases. Lists of
“helpful tips” and FAQs didn’t even exist.
To repair this process, the intranet team worked with different business areas to gather the
most current and approved content, policy and procedure documentation, relevant
background material, and online worksheets. They then designed a tool—integrated with the
Pictured: The tool for determining average earnings links to current policies and
information.
Pictured: A tool for finding service codes and fees. This simple tool replaced sixteen
Excel spreadsheets and the myriad headaches that arose from having to search them.
Another example of how the intranet consolidates multi-source information is the Managers’
Page. This page encapsulates all things management-related, such as processes and forms
for training, job reviews, and pay ratings. The page also links to any legal information
managers might need and offers links to magazines to help keep them well informed on
management issues.
The intranet designers conducted not one, but several usability tests, understanding the
need for iterative testing and design. After a detailed investigation of users’ needs, the
designers fashioned imaginative tools aimed at simplifying or eliminating previously painful,
time-consuming processes.
CONTENT MANAGEMENT
The CMS is a Lotus Notes application that was designed in-house. Ten content owners,
drawn from HR, communications, administrative services, and specialized claims, have
access to the application and can post, format, and edit content. Once they’ve implemented
the forthcoming Content Contributor area, the intranet team expects to recruit more content
contributors. “We have been very cautious about opening the floodgates so far,” says
information resources manager Carolyn Archer.
TECHNOLOGY
The intranet portal software is Plumtree 4.5WS, which interfaces with a Microsoft SQL 2000
Enterprise edition database. There are four servers: a Web server, database server,
gadget/application server, and search server. Internet Explorer 5.5 is the standard browser.
The intranet team designs pages using Macromedia Dreamweaver 4.0 and PhotoShop 6.0,
and develops applications on Lotus Notes 4.6. For metrics, the team analyzes CONNEX Web
server logs using an Access database that was built in-house and analyzes intranet use by
page, document, and user group. WebTrends software provides other statistics, such as
page hits.
USERS
Approximately 4,300 WSIB users perform more than 700 distinct jobs in fourteen Ontario
offices.
USER TASKS
• Read the latest corporate news and updates
• Use the phone directory
• Read the weekly job postings
• Read HR information, request vacation time, and seek assistance for training
• Submit expenses for approval
• Generate cost-and-budget reports
The redesign team faced a number of challenges; some persist. For example, many
employees still don’t consider CONNEX an essential business tool, making it difficult to
procure needed technical resources or content-owner buy-in.
WSIB’s existing technology infrastructure is also complicated, perhaps partially a legacy of
government frugal-spending. “Ideally, the intranet should provide a seamless gateway to all
tools of the trade, but the costs of trying to integrate mainframe-based legacy systems and
off-the-shelf applications in a highly security-conscious environment has limited our success
in this area,” notes Murphy.
Given those constraints, the redesign largely targeted low-hanging fruit, she says, and
because of needed software upgrades, developers spent most of their time on the software
conversion, leaving “only limited time available to work on design improvements.”
Other complications included the “limitations of the Plumtree product,” says Murphy. “The
rather rigid gadget-column structure imposed by Plumtree makes for busy-looking pages.
To combat this, we expended a lot of resources developing the cleaner-looking Employee
Services page and have since used this model to develop pages that appear ‘gadget-less,’
while still conforming to the Plumtree infrastructure,” she notes.
As the rollout progressed, WSIB moved from Netscape 4 to Internet Explorer 5.5. “By
upgrading and standardizing the browser for all users, the WSIB is able to better control the
user experience,” notes Murphy.
After an initial round of changes, the intranet team conducted one-on-one usability sessions
with WSIB users. “The responses were generally positive in that users liked the design
changes and saw the value of the simplified navigation and improved search function,” says
Oakley.
One surprise finding, however, was users’ strong resistance to technology. “Users don’t
want to find answers on an intranet, they want classroom training,” says Murphy. She
attributes some of that resistance to users’ limited PC skills and comfort only with Lotus
Notes and mainframe interfaces. Others had a high threshold for learning—it had to be vital
to their job before they wanted to take the time.
Another surprise: after usability testing, participating users had much better intranet
familiarity. While usability evaluations should never be conducted to educate users, they can
be educational for two reasons: 1) the test sessions encourage users to try things they
might otherwise never try, and 2) at the end of the sessions, just before users leave, the
test facilitator can explain some of the functionality. “Interestingly, many of the usability
participants found the session extremely educational and went away with a better
appreciation of how CONNEX could enhance their work experience,” says Murphy.
TIMELINE
• November 2001: First CONNEX pilot, combining content management and portal
efforts, begins in a regional office with twenty teams and 430 employees.
• May 2002: CONNEX rolled out to entire organization.
RESULTS
The redesigned portal gives users quick access to policies and procedures. “It has become a
virtual desktop file cabinet for staff—no more need to stockpile forms in desk drawers,” says
Arnold Sooknanan, a knowledge services technical coordinator. The upgrade also fixed
several technical issues; improved the search engine, navigation, and information design;
and brought portal design in line with corporate branding.
The improved design is already having an effect: hits to CONNEX have doubled in the past
year. Based on a November 2003 user survey, intranet use among core users increased by
18%, and “user feedback and anecdotal evidence suggests intranet usage has gone beyond
the early adopters,” says Oakley. Management and staff now present more ideas for
content, demonstrating a growing interest. Employees also have new tools to facilitate their
jobs. The team’s design lessons will soon be applied to content. “We are also working on a
content contributor gadget for CONNEX that will include a link to the CMS, style guides, tips,
and templates. It will be an ‘everything you need to know to contribute content to CONNEX’
tool,” says Williams.
To aid the redesign rollout and test Plumtree’s collaboration features, the team had created
threaded discussions for enthusiastic early intranet adopters, who, as expert users, have
also touted the intranet’s benefits to others. That approach is now being applied to other
WSIB communities as well. Nurse case managers, for example, now have a professional-
practices page with threaded discussions. While not targeted at a specific WSIB rollout or
project, the informal, online community space allows individuals with similar interests and
day-to-day challenges to learn from each other—or just blow off steam.
Many November 2003 survey respondents detailed how the intranet now saves them time.
One user, handling a client’s spinal-cord injury claim, needed more information about
atypical symptoms. “I was able to find information [in CONNEX], which reviewed all this and
more, [and] reviewed further treatment options as well as success rates for these
treatments,” the user wrote. “There were even pictures available to demonstrate the client's
injury. This work took me less than five minutes.”
Another user fielded a call from a worker claiming he was entitled to expense his roundtrip
ride to a physiotherapist by taxi—the bus stop was too far; walking would aggravate his
injury. “I was able to verify this by using the [city] transit map in CONNEX, and I was able
to immediately reconsider my original decision with the worker still on the phone,” the
employee wrote. Still another user raved, “I wonder how I ever did my job without
CONNEX.”
Success stories validate the time and energy the intranet team devoted to the redesign. But
the team can’t stand still. “In some ways, the portal is becoming a victim of its own
popularity. Many users now feel that there is too much information on CONNEX and that it’s
becoming difficult to find what they’re looking for because of the sheer volume of content,”
says Oakley. The team plans a 2004 redesign to address those issues.
15
If you are looking for help on ROI, see these publications: Measuring Return on Investment, Gilutz, Nielsen,
www.nngroup.com/reports/roi; and Cost-Justifying Usability, Bias & Mahew, ISBN 0120958104.
REVIEW PROCESS
We posted the call for submissions on www.nngroup.com and on www.useit.com in January
of 2004. Submissions included: screenshots of the intranet, explicit descriptions of the
intranet’s design and how it works, notes about the design process (including usability
methods employed), detailed information about users and potential users, and the intranet’s
goals.
To judge the entries, we used a four-step process: 1) initial design reviews and numeric
rankings; 2) design sorting, followed by thorough design reviews to choose the top ten; and
3) follow-up interviews with the top ten.
16
The report about intranet usability is based on usability evaluations of 27 different intranets. Intranet
Usability includes guidelines about designing usable intranets, and is available for download at
http://www.nngroup.com/reports/intranet/guidelines.
Pictured: homepage
SUMMARY
The DOTnet intranet has a very clean look, with graceful color choices, clear
headings and categories, and easy-to-decipher links. Graphics are used appropriately
and sparingly. The personalization features help employees find the information
specific to them quickly. Some of these features include bulletin boards,
communities, chat rooms, and local news, weather, and traffic..
DOTnet also has several productivity-specific offerings. For example, the site’s Work
Tools section offers various applications and information sources people need to do
their work. The Communities are a nice way to present information, and allow access
restrictions for specified content for particular users. The community calendar,
Overall, data entry on DOTnet is simple. For example, the search feature is
presented as an open field in the upper-left, followed by a Go button. The login
function has two fields labeled Logon and Password. This simplicity is very good.
The DOTnet site also makes good use of information on several other government
sites. It’s smart to link to these, leading readers right to the source and not
duplicating data. The info-message that pops up every time you are leaving the
DOTnet pages, however, does interrupt your train of thought, is a bit annoying, and
can be an accessibility issue. A better option might be to note the source at the link,
so people know then that they are leaving the site.
There is a little too much text on some of the pages, and the clutter makes it difficult
to read. Some of the text is very small, and there is not enough contrast between
the text and the page background, which probably create accessibility issues for
people with low vision and motor skill issues.
Scoring
Simple Simple Consistent Visible Simple Limited Clear Clear
look navigation navigation search search (and well- labels links
across bar (or presented) (name
pages button) page text and
marks)
2 2 2 3 3 2 2 2
INTRANET
DOTnet is an intranet for all the DOT staff, providing features such as an employee
directory, library facilities, and electronic calendars, as well as role- and
organization-specific communities.
BACKGROUND
The U.S. Department of Transportation is not lacking for intranets: 10 out of its 11
operating administrations — such as the U.S. Coastguard and Federal Aviation
Authority — have developed their own systems. The DOT, however, is keen to
improve efficiency by sharing best practice across departments. They see the
introduction of a single, department-wide intranet as a way to achieve this aim. Last
year, the department hired a services company, Burke Consortium, to build a new
DOT-wide intranet to replace the existing system, which was built a year earlier by
the DOTs internal IS team.
As for the existing intranet version, few staff had been persuaded to use it in
addition to (let alone instead of) their own agency-specific systems. To be successful,
the new version had to look appealing and offer employees features they couldn’t get
elsewhere.
At the same time, the DOT didn’t want employees to regard DOTnet as a monolithic
system that didn’t reflect their individual needs. So, another priority was
personalization tools that let users adapt the system to their own requirements.
The third important goal was that the system be easy for the DOT IS department to
maintain internally, without ongoing service costs. The system design had to reflect
that goal, and the application needed a built-in CMS.
Not only did the designers have to complete the intranet in a short timeframe, but
they were also limited by some political decrees. For example, designers were
required to use the official DOT color scheme: blue and yellow. Further, the design
had to be sufficiently generic to not exclude or appear to favor any one of the DOT’s
individual agencies. An early prototype design featured a rotating logo that showed a
truck, then a plane. The DOT rejected this as too specific.
To be compatible with all the DOT’s workstations, the design had to be optimized to
work well with screen resolutions of 800 x 600 and older versions of Netscape. This
constraint limited the length of screen items such as form fields.
The application also had to comply with Section 508 of the Americans with
Disabilities Act, which specifies that all information presented on a public site must
be accessible to people with hearing or visual disabilities. “This makes it difficult to
include media such as video or audio because, for example, a hearing-impaired
person can’t benefit much from video on Web. You have to limit the number of
graphics to ensure the page is accessible to everyone,” says information designer
Matt White.
However, this constraint has also had the benefit of making it easier to create a
multilanguage version of the application, if required. “Though the application is all in
English now, because of Section 508 we give the ability to upload an alternate
version of every bit of content — which means we could put in a Spanish version at
the same time as the English version,” Matt says.
Following the initial meeting, Burke prepared a basic information design and the two
teams met and conferred again. Once the DOT approved and modified the design,
Burke started to prepare visual designs and functional templates, outlining what the
pages would look like and how they would work. The Burke team submitted three
designs to the DOT team, who in turn selected a combination of two designs, which
Burke used to create the final version.
DESIGN
To facilitate easy maintenance, the DOTnet design is entirely template-driven, with
around 30 templates in all. Most of the templates are three columns, with a few two-
column pages. Within these templates users can customize their screen layouts using
various arrangements of the two basic design modules: a single narrow column and
a double column.
Navigation, too, has been kept simple, with the aim of one-click access to most
areas. It includes a Home button and four tabs to take users to the main areas:
Employee Information, Employee Directory, Communities, and Calendar. Some
areas, such as Communities, provide sub-navigation. The My Dot area gives users
access to personal modules, such as a private calendar and library, plus personalized
weather, notes, and news.
PERSONALIZATION
Because the DOT consists of multiple agencies, one obvious approach would have
been to provide users with a personalized agency site view driven by their login, so
that coastguard users would see a coastguard view, and so on. There were two
reasons, however, why the DOT wanted to avoid this. First, the organization wanted
Users can customize their homepage by adding personal modules such as weather,
personal notes, and a calendar, and arranging them as they see fit. Screen layout is
customized using the My Modules option in the My Dot section.
In addition to this customization, community leaders and administrators can set the
screen layout for the site areas they are responsible for maintaining. For example,
the procurement community’s leader can arrange the Procurement Community
homepage. This type of customization is carried out from within the CMS.
USABILITY
The DOT planned to decide on the intranet’s content and structure simply using input
from its CIO team. “They didn’t see the need for much user testing, but we
convinced them we needed to go through one round of it,” White recalls. “Most of
the challenges didn’t come up until we gave the application over to users to look at.”
Around 20 test users were involved in the usability and functional testing, which
started in February 2001 on the first iteration of DOTnet. Most of the test users were
employees who’d expressed interest in the intranet project along the way; in cases
where agencies weren’t represented, the team asked for volunteers to fill the gaps.
They varied widely in their IT experience. “Some had used the old intranet quite a
bit, others didn’t even know what a scrollbar did. So the whole thing had to be very
easy to use,” Matt says.
Users were given several tasks to carry out using the CMS, which was seen as the
most complex part of the application. For example, users had to enter a news article
along with its headline and summary. The team designed the tasks to ensure that
test users would work with most of the intranet’s features.
The team tried to observe as many of the test users as possible as they worked
through the tasks, and got comments from all of them. “From that, we got a whole
slew of proposed changes to work through,” Matt says. “People were having trouble
understanding the method behind CMS — it was very foreign to them that they could
put content on the site themselves.” Burke incorporated the user feedback and
change requests from the DOT CIO team into a second version.
RESULTS
Because of the limitations of the DOT’s network infrastructure, DOTnet usage is still
restricted to the 50,000 employees in its Washington, D.C. headquarters, but the
aim is to make it available to regional offices and home workers via a virtual private
network. Burke has provided for this with features such as regional weather reports
based on ZIP Code.
DOTnet went live in June, and attracted three to four thousand users in its first
week. Although it’s too early to judge its ultimate success, community use appears
to be burgeoning, and one community already has 20 private groups within it.
TIMELINE
• November 2000: The project began.
• Requirements definition: 5 days.
• High-level information design: 7 days.
• Visual design (three design studies): 25 days.
• Functional template design: 18–25 days.
• Build prototype: 34 days.
• Testing and documentation: 16 days.
• Launch: 5 days.
• June 2001: The intranet went live.
LESSONS LEARNED
Burke Consortium is now applying the lessons learned from building DOTnet to
creating a general-purpose community tool. According to information designer Matt
White, they learned three specific lessons from the DOTnet project.
AVOID POP-UP WINDOWS
“While it worked for the DOT — because they wanted to maximize screen space and
do a lot of multiplexing — we don’t feel they are the most usable thing and we have
eliminated them in newer versions of our own tool.”
KEEP MENUS SHORT
Because long lists are difficult to manage, they often have to modify news items.
They learned from their focus groups that they needed to break longer stories into
more manageable chunks.
PROVIDE LOCALIZED SEARCH
DOTnet had just one general search engine, and although it could be categorized by
news, calendar events, surveys, and so on, users were still faced with a long list to
wade through. Burke now offers the option of localized searches in key areas, such
as a calendar search.
The intranet home page provides a comprehensive big picture of the Bank's online
resources, and consolidates corporate communications, both internal and external,
while maintaining an uncluttered look. The internal communications appear in the
middle section of the page, and external communications (Bank in the News: press
releases and press reviews) appear in the left-hand navigation. Employees can
suggest articles for each section; the Internal Communications team and Media
Relations team facilitate and prioritize the content. The advertising icons toward the
bottom of the left-hand column highlight items, such as annual meetings, that will be
posted for more than a day.
The intranet is the perfect place to advertise internal events and seminars. What
better way to ensure that all groups are included than to let people post their own
events? On the World Bank intranet, all Bank staff can publish their seminars and
events using the Kiosk tool. A Kiosk administrator monitors the entries to make sure
that the audience for the event is big enough that it makes sense to publish it for all
employees.
The services portal lets users browse by service category, by service provider, and
by headquarter services versus country office services. It integrates decentralized
service catalogs with the yellow pages, and lets units that do not have a service
catalog submit an entry into the yellow pages directly from the services portal. The
yellow pages administrator reviews and approves submissions for the yellow pages
catalog.
The designers chose templates with a standard and simple look and feel, light pages
that load quickly, and a consistent user experience. There is a prominent place on
the header for local branding, such as pictures and logos, while the rest of the
header components remain constant across the site. Most of the categories on the
left-hand navigation are optional, and there is room for free categories that are
specific to a particular group. Much of the content is data-driven, but in most cases
owners have the option to reject or accept content coming from an institutional
source.
For performance reasons, the designers chose to separate the people search from
the site search. Because the employee directory search is the intranet’s killer app at
many large organizations, it’s imperative that this feature is visible, simple, and most
of all fast. The site search combines a metadata search for frequently used
repositories with a crawl search that uses Google’s intranet search appliance for
uncataloged content.
The search results page repeats the search query, which is always a good idea. The
page is easy to scan, the title links to the full document, and the short descriptions
further describe the documents. The Hide Descriptions link is a nice feature, which,
obviously, hides the descriptions and lets the user see more results at once.
The breadcrumbs, standard navigation, and consistent page layout make this
intranet’s behavior predictable, but not boring. The bold colors and exciting pictures,
plus pertinent and ever-changing content make this intranet a place people will want
to return to when they conduct their everyday tasks.
Scoring (3 = best)
Simple Simple Consistent Visible Simple Limited (well- Home page
look navigation navigation search search presented)
and design text on pages
2.4 2.8 2.5 3 3 2.7 2.8
BACKGROUND
The Bank has had an intranet since about 1994, but started out by letting about 400
internal content providers around the world contribute on an ad hoc basis, using
their own tools and design ideas. “Everyone could do what they wanted: create
pages in HTML, Lotus Notes, and so on. Same for design — we had a few standard
templates, but that was pretty much it,” says Maria Dolores Arribas-Banos, team
leader and information management officer.
As the intranet grew in size and scope, it became increasingly cumbersome and hard
to maintain, and content became increasingly hard to find. In September 2001, the
Bank embarked on a three-year intranet redevelopment project, which would also
harmonize the internal and external sites. Although the technology department
In pursuit of its first goal, the Bank is now migrating existing intranet and Internet
content into a central CMS, with a dynamic publishing capability. As it introduced a
common technical platform and common look and feel, the Internet Working Group
(IWG) wanted to ensure both that content providers retained control over their
content and that departments and regional groups retained some individual identity.
“The templates we had before were very rigid. We wanted to provide some flexibility
and local branding,” Arribas-Banos says.
So, content creation will still be decentralized, but the IWG will centralize and
manage template management and overall design. Also, some content owners have
the same content on the intranet and external Web; the CMS should save them time
by making it easier to repurpose content.
One of the technical problems the team had to resolve was improving the search
facilities. “Before, you pretty much had to go to each individual repository to find
something,” explains Arribas-Banos. Now, the Google search engine lets users
search the whole intranet or narrow the search to a particular section.
All 10,000-plus Bank employees have intranet access, some from country offices
with less than optimal Internet connectivity. The intranet also has to serve mobile
employees as they travel throughout the world, and therefore has to work well even
over low-speed and mobile connections. This means, for example, a strict limit on
use of graphics. But, set against that constraint, the organization’s standard desktop
gives the design team the advantage of only having to develop for one browser:
Internet Explorer 5.0.
Requirements gathering lasted about six months, from July to December 2001, and
involved about 400 different content providers and users throughout the
organization. Satyam, the Bank’s development partner, created a detailed
questionnaire covering issues such as the goals, target audience, content type, and
workflow requirements for each section. The team sent this out to the main regional
coordinators around the world, who were asked to review it with the different
country webmasters.
The team learned some lessons while using card sorting to elicit requirements.
“Card sorting gives you some insight about how content should be organized, but
you have to be careful in how you use the results, because it may not be the case
that people really want it that way,” says Arribas-Banos. “We found the responses
would vary widely depending on the person’s background; depending on who you
asked, you would get a completely different organization, and when you played the
result of the organization they had chosen back to them, they didn’t always like it.”
The team addressed this issue by creating a flexible structure that lets users
navigate to the same content in different ways. Users can find data on Angola, for
example, by going to the data page and browsing by country, or by going to the
country page and browsing by data.
Using all this information, the team created an information framework that included
the overall site and navigation structure; basic template definitions; what approval
processes were needed; and any special requirements, such as specific workflow
processes.
They also specified a basic color palette and a page design framework, which they
called the C-clamp, consisting of a header across the top, left-hand navigation, and a
footer. In addition, local branding goes at the top left in the main menu bar, search
is always in the top right corner, and help and feedback buttons are mandatory on all
pages.
Once the information structure and workflow was established, the team started work
on building each section’s input and display templates, using either existing
templates or producing customized templates to meet departmental requirements.
“Some departments, like General Services, need very specific templates, so it was
very much demand-driven,” Arribas-Banos explains.
Before the designers started working on the site templates, they consulted with
content owners to come up with a preliminary content structure. Once the initial
design was set and the standard components were developed, they built a basic
Being able to specify the storyboards and page behavior in electronic documents is
particularly important, given that the Bank is working with an offshore design team.
Face to face meetings are almost impossible, and they carry out most
communications via email, phone, or video conferences.
Early on in the project, team members developed a migration plan setting out where
existing content should go — basically, they had to decide whether it should migrate
to the CMS or a document management system, or just be deleted. The final
migration stage is now underway and the aim is to complete the bulk of it by the end
of 2002. The data migration is proceeding in parallel with the portal implementation,
which includes the staff portal, projects portal, managers portal, and so on, plus
extranet applications such as the donors portal. This stage also includes training for
content providers, editing, and testing.
In January 2002, the team launched a pilot site, including news and events on both
the intranet and the external Web. By introducing the new system to users in small
steps, the team hoped to avoid the culture shock associated with a “big bang”
approach. “So we decided to go with a pilot and have the owners of those sections
bring the business on board, and this approach worked well,” Arribas-Banos explains.
Pictured: The previous home page design, which was too busy.
In October 2001, Satyam presented its first attempt at a redesign. However, several
of the problems identified on the previous intranet remained, so the design was
rejected, and it didn’t get as far as the Web and user communities. “It wasn’t fixing
any of the problems we had,” Arribas-Banos says. The page was still cluttered, with
almost the same amount of information as before. And, while the search option was
more prominent, it didn’t solve another existing problem: that most users didn’t
think to change the default search option — people search — resulting in frustration
and complaints.
Several further iterations resulted in the next version. “We liked this much better
and felt it was much clearer,” Arribas-Banos says. The search problem had been
fixed by having two separate boxes for people and site search, and the site had a
more professional-looking design, most of which has been retained in the current
version. In addition, the new version included a name for the intranet, Staff
Connections, and a new section, Kiosk Announcements, where staff can more easily
submit their own announcements, enhancing the sense of community. Because the
Bank wanted more regional input on the home page, the team introduced an In The
Field section to carry daily regional news. However, this turned out to be
impractical, and had to be dropped.
Even with the improvements to the home page, a number of user criticisms
remained. These included unclear priorities for the daily news; no way to highlight
items for longer than a day; and poor visibility for HR content, one of the site’s most
popular areas. The users also disliked the people image used in the top left corner
with the Staff Connection logo. Users felt that because the Bank has a multinational,
multicultural staff, the image should reflect this diversity.
In the latest home page design, the controversial photographic image has been
replaced with a neutral silhouette, and the logo was redesigned. To solve the
problem of being able to highlight items for a longer period, the left-hand menu
column can now include graphic buttons (such as Millennium Development Goals)
linking to special items of longer-term interest. But the page continues to evolve in
a process of ongoing development.
The latest design also addresses a longstanding issue by having content from the
Bank’s internal communications and external news departments appearing under the
same Bank’s World Today banner. User feedback showed that users did not see the
difference between the two sections, which both essentially cover news about the
Bank, and found them confusing. The solution is a compromise.
Pictured: The old services page, with its long list of services categories
and cascading menus.
In the new service portal, the number of service categories was reduced to nine, but
users have more ways of browsing them: by service category, service provider, and
headquarter services. Decentralized service catalogs will be integrated with the
central yellow pages. Units without a service catalog can already submit yellow page
entries directly from the services portal.
One of the problems the design team faced was providing central control over the
intranet’s structure and look and feel, while also providing a measure of local
autonomy. Setting the rules for the information framework, template definitions,
and page behavior upfront was vitally important. Before individual departments start
to look at page design proposals, they have already agreed on the basic ground
rules. Their own designers can be involved in the process, but must work with
design guidelines, such as a standard color palette. In developing the Bank’s World
Today section, for example, this meant much fewer interactions were needed
between the intranet team and the department, because the templates already
included the intranet’s standard components.
Principle feedback comes from the IWG Community, which any Bank employee with
any interest in the Web can join. The IWG Community distribution list currently
includes more than 600 people.
New proposals for the intranet are circulated to the IWG Community with a request
for comments. The intranet team also puts a link to any new pages on the intranet
home page, partly to get feedback and partly to alert users that a change is
imminent. “We might put up three mockups and ask them questions; we keep them
up there for maybe fifteen days or longer,” Arribas-Banos explains.
The intranet group can call on the Bank’s in-house usability team, which carries out
both heuristic evaluation and user testing for page designs as they evolve. “We do a
heuristic evaluation ourselves and then, once we're comfortable with the design, we
send it to the in-house usability team,” Arribas-Banos explains. “They will find the
most obvious usability issues and fix them; most of the problems you can fix right
away but others need more changes. Once the final templates are ready, we send
those to the team and they do an evaluation with real users.”
Team members initially focused the user testing on the input templates used by
content providers; they also extensively tested display templates. They carried out
tests with groups of three to five users, who were given a list of tasks to complete
and a questionnaire to fill out. One compromise the group had to make was on its
samples of test users. “It’s a challenge to get a representative group, because
people are busy, so you tend to end up working with the people who happen to be
wherever you are,” Arribas-Banos says.
TIMELINE
• November 2000: World Bank starts to look for new CMS; sends out
questionnaire to gather requirements from all content providers.
• September 2001: Work starts on the intranet metadata model.
• November 2001: Satyam starts work on page designs. Pages developed
on an iterative basis.
RESULTS
Before the project started, the World Bank hired a contractor to run out a baseline
assessment of the previous intranet, identifying indicators such as number of broken
links, time spent configuring subsites, how many consultants were hired to do site
design, and so on. When the current system is completed, the same indicators will
be measured to give quantitative results.
The intranet team also conducted a user survey when the old intranet launched and
the team plans to do the same survey once all content has been migrated into the
new version. The team also analyzes statistics of site usage, conducts surveys of the
organizational webmasters, and logs comments sent in by users via the feedback
button.
Though the site is still at the pilot stage, there are already informal indications that it
is achieving its goals, with an increased number of users reporting confidence in the
intranet. The improved search function has proved highly popular. “Search was a
huge win,” says Arribas-Banos. “People actually called us up to say how well it was
working, which was a pleasant surprise.”
The Bank also expects to make savings by using the CMS to more easily repurpose
content between the intranet site and the public Web site.
LESSONS LEARNED
Insights from Maria Dolores Arribas-Banos:
Change management is more challenging than any technical issue. “People
don’t like change. If you encourage them to participate by sending feedback, they're
more receptive to the new system.”
Involve content providers early on. “Content providers need to know the
capabilities of the new system and its potential before they can submit realistic
requirements. You have to go to them with a straw man and let them break it
apart.”
Go for process rather than perfection. “If you're aiming for perfection the first
time, you’ll never get anything done. Aim for continuous improvement instead.”
Get buy-in from decision makers. “Sponsorship and top management support
are vital.”
Plan for staff adjustments. “Don’t forget transitional activities like training,
ongoing support, and deploying staff whose skills are no longer used in the new
system.”
SUMMARY
The CG Central portal is designed to help project teams and individuals in the US
Coast Guard inform and be informed — critical tasks for military personnel, especially
in times like these, when the US homeland requires scrupulous protection.
The aesthetics are attractive, but not fussy. The Coast Guard seal at the top shows
the site’s official nature. The blue and gray color scheme is reminiscent of water and
creates a calm tone. Text is legible and photograph quality is quite good. Links are
obvious, indicted by bold, underlined text.
The homepage keeps morale and spirits high with the Features from the Field area,
which showcases various personnel and tells their individual stories, complete with
high-quality photographs. On any intranet, demonstrating what people and teams
are working on can be inspiring and educational.
The US military’s hierarchical nature helps keep this colossal organization steaming
ahead. On the homepage, a section cleverly named From the Helm includes the
Commandant’s Biography, a photo, and a link to Commandant’s Message, and helps
reinforce the command chain and remind people of the organization’s strong
leadership. The Leadership Voices also helps individuals work as a team with clear
goals and missions.
Links under the Organization Information section deal with administrative and
project areas.
Pictured: The United States Coast Guard Intranet homepage, before a user
logs in. It shows everything from news to leadership and military threat level.
The My Workspace tab gives users information that pertains to their daily life.
Assignments, alerts, and publishing are examples of areas important to individuals.
CG Central pulls information from a personnel file to give users alerts and
occupation-related information. Links to microsites also give users access to the
information they need most. Groups and units use microsites for discussion forums,
announcements, documents, checklists, and to conduct asynchronous online
meetings.
To post information on the intranet, personnel can use a very simple form with a few
clearly labeled fields.
The CG Directory tab breaks down the departments into an easy to search glossy.
Each unit has its local services, plan of the week, local announcements, directions to
the unit, and unit procedures to help give the user precise and up-to-date
information.
The My Unit tab gives users departmental information, services and benefits, and
duties pertaining to their position.
The CG Central pilot project has been very successful thus far. The Coast Guard
plans to extend it from the current 1,000 users to 40,000 users within a year, so
many more people will benefit from this comprehensive and practical intranet.
CONTENT MANAGEMENT
The US Coast Guard chose the BroadVision portal product because it offered content
management integrated with personalization and open standards.
TECHNOLOGY
CG Central is written in Java and currently runs on Oracle 9i and a Windows 2000
server. The US Coast Guard plans to migrate it to an Apache server running under
Solaris. The Coast Guard currently uses BroadVision’s FastSearch technology to
search the portal site only, but is introducing Google for whole-site search.
USERS
About 40,000 users access key US Coast Guard information using the Coast Guard's
portal. This includes all active-duty military enlisted personnel and officers, plus
about 6,000 civilians.
USER TASKS
• Access all essential Coast Guard information including: authoritative
doctrine, policies, and procedures (such as marine safety inspections, law
enforcement boardings, and fisheries patrols); mission essential applications
for reporting performance; the Readiness Management System; and current
content such as news, leadership messages, and strategic initiative updates.
• Receive alerts for subscription-based content.
• Search for information.
• Search for people, including advanced and sensitive searches such as:
a) Users can easily search for Coast Guard personnel by location and
title, such as an emergency medical tech in Kodiak, Alaska; a
qualified Law Enforcement Boarding Officer in Boston; or a First
Class Boatswain's Mate.
b) HR managers can use search for staffing assignments, easily
searching for a pilot, engineer, or female member to augment a
promotion board's composition, for example, or for other
specialists and operators to quickly build teams in local areas.
Such HR tasks used to require custom scripts, and a few days
would pass before programmers could respond; now the tasks take
minutes at most, seconds at best.
BACKGROUND
The 4,000 or so units that make up the US Coast Guard are dispersed around the
US, including Hawaii and Alaska, and on ships at sea in the nation’s coastal waters.
In the early 1990s, many of these units began developing their own intranets, which
were loosely connected on a wide-area network. “We had a decentralized WAN in
which there were a number of Web servers coughing up content in an unstructured
way, depending on what individual Web masters came up with,” says Lieutenant Tom
Shelton, project officer.
TIMELINE
• 2000: US Coast Guard leadership establishes the Coast Guard vision.
• Nov. 2000: A demo portal, including AltaVista search engine technology, is
shown to the US Coast Guard leadership to introduce the need for an
intranet portal to unify scattered information resources.
• May 2001: Another demo portal is introduced at the US Coast Guard’s
Innovation Exposition, demonstrating personalization and the content
management capabilities of BroadVision’s software.
• Mar. 2002: First round of funding arrives for the full-blown portal project.
• May 2002: Another portal demo at the USCG Innovation Exposition; the
demo includes a taxonomy benchmarked with the Air Force, and
BroadVision’s improved portal framework with collaboration workspaces.
• Dec. 2002-Apr. 2003: Joint application development with user
representatives.
• Apr. 2003: Development of CG Central Version 1 is frozen.
• May 2003: Testing phase/government acceptance.
• June 2003: CG Central Pilot goes live; users begin migrating to the new
system.
RESULTS
Since CG Central went live in June 2003, the Coast Guard has been gradually
phasing users in and moving slowly toward a fully operational system. Of the Coast
Guard’s 40,000 staff, about 5,000 profiled and unprofiled users are currently using
the system.
It’s still early to assess the Coast Guard’s goals of improving employee productivity
through the portal. In the longer term, however, the team plans to measure how
well the content provides mission support as part of its content management
framework. “At this point, I know we have some extreme time savers, such as faster
people search, faster information search, and fewer programming skills needed to
publish information,” says Stevens. “We will be working out a more realistic ROI
based on user behaviors, customer feedback, shutting down of several servers and
systems, and so on, and reporting our performance to the CG Readiness
Management System to ensure our system meets the needs of users afloat and
ashore.”
LESSONS LEARNED
Insights from Janet Stevens:
Publicize the benefits. “Project return on investment from small successes — the
leadership of any organization wants this information upfront and early on.”
Make it worth users’ while. “Reward users for participation and quality outcomes.”
Don’t turn to outside experts when you really need is internal knowledge.
“We hired consultants because we thought they were smarter than us. Actually,
they were only smarter than us for a couple of weeks. They didn’t have the
organizational knowledge we needed.”
SUMMARY
The New Zealand Ministry of Transport (MoT) intranet supports about 200 central
government workers. Letting employees post their own news content, and offering a
sound IA and fun style, all help to make the MoT intranet “the” place to be—and no
travel required.
At MoT, employees access and analyze information from many sources, then develop
and present policy papers and reports, and facilitate government policy
implementation through various transport-related agencies. In short, these workers
provide transport policy advice to the government; thus, MoT is an information-
based organization. And, because these people are working to ensure that New
Zealanders have the best possible transport system, the intranet had better be good.
Luckily, it is.
The look of the MoT homepage conveys a happy mood, with bright colors and
cheerful images. The theme image on the homepage rotates, depicting different
upbeat scenes, all about some form of transportation.
The Daily discovery area in the page’s far right column posts different fun facts about
transportation each day. An image usually accompanies the blurb, to bring home the
message. These trivia are not only fun, but actually teach employees facts about
their industry. And that can’t be bad.
Pictured: The MoT homepage has a rotating theme image, plus Alerts,
Announcements, and other news.
The Have Your Say poll at the bottom of the page allows employees to answer timely
questions. They can also see what their colleagues answered by clicking the view
results link. The question is repeated in a pop-up window, as is the user’s answer. A
bar chart quantifies all the answers.
Pictured: Users can view the homepage’s poll results. A simple graph makes
the answers visible at a glance.
If users wave their mouse over one of the bars, a pop-up appears showing the
percentage and actual number of votes for that category.
Pictured: A rollover with specific stats for the bar appears when users mouse
over it.
Alerts are important; they shouldn’t be displayed only on the homepage. Here, even
if users leave the homepage, they can still keep abreast of Alerts through pop-up
messages. For example, a message might tell users about a change to the internal
phone or voicemail system and specify the alert type (phone or otherwise).
Pictured: The News and Events tab offers content such as generic (default),
event, announcement, alert, and classified.
Because training is considered an event at MoT, training schedules are housed within
the intranet’s News & Events area. Users can view training by day, week, or month,
and can collapse the views to show more items with fewer details. By default, the
view shows the course name, the time it begins, and the price, plus additional
information when applicable.
Users can click an event to view details, then integrate the chosen events with their
Outlook Calendar.
Pictured: The Training Calendar displays the day, time, title, and price of
training classes at the organization.
Anyone can add items to the News & Events area. The input form makes this very
easy. Field labels are straightforward. Fields are the right size for the information
users are expected to enter. The drop-down lists for the calendars and times make
this selection simple. And, to avoid having the many content providers forgetting
important information, necessary fields are marked at required.
Two niceties are the checkboxes: Make this an all-day activity that doesn’t start or
end at a specific hour, and Make this a repeating event.
Pictured: Anyone can enter events in the Training Calendar. Simple and
required fields in this form make this process run smoothly for the person
entering and the would-be readers of the information.
Being a research organization, documents are of utmost importance. To make the
organization’s many documents accessible and possible to find, people post them in
the Tools & Resources tab in the Document List area. This allows users to browse all
site content using tags that are presented as navigation and column filters. Users
can see documents and sort them by many categories, including Type, (which also
shows an icon denoting PDF, PowerPoint presentation, and so on), Name, Content
Type, Date Created, and Created by. Having these categories increased the chances
that users will be able to find their desired documents. For example, they might
recall only the rough date when the document was posted. In that case, they can
sort by data and view document titles around that date.
Users can take several actions in this area as well, using a simple green toolbar at
the top of the page that contains four commands: New, Upload, Actions, and
Settings.
Pictured: The Document List area helps MoT employees do their research and
communicate it with each other. The list is sortable and easy to manage.
The MoT intranet makes it effortless to communicate research work and news. The
design team considered tasks and simplicity, while always promoting the
transportation theme in subtle and pleasant ways.
TECHNOLOGY
The MoT’s intranet technology platform has evolved from a Lotus Notes resource
library—containing a several databases populated with MoT manuals and policies,
email functionality, an instant messaging application, and two contact databases—to
its current platform of MOSS 2007 and Exchange/Outlook 2003.
The underlying technology for MoT’s intranet is Microsoft-based and consists of the
following components:
• Windows Server 2003 Enterprise SQL Server 2005
• Microsoft .NET Framework 3.0 and 2.0
CONTENT MANAGEMENT
Content Authoring
One person—a content publisher—manages the site’s content, with individual
business units responsible for their own content areas.
“Formal content updates are managed centrally (such as policies and procedures),”
says Wilkins, “With the nominated staff member from that area of the organization
updating content and providing signed off updates to the content administrator.
Content that’s more informal (notices, social events) is authored directly by the staff
member concerned. The informal content is frequently updated, giving a dynamic
site, whilst the formal business content is more stable.”
Changes are tracked via version control that is enabled across all document and
page libraries. This change management functionality is native to the CMS tool.
INTRANET TEAM
With only one dedicated internal resource, MoT has relied heavily on outside
agencies and expertise to plan, design, and build the intranet since 2005 when the
Communications Team initiated the intranet project.
The intranet project’s impetus was a result of two things: Claire Johnstone, MoT’s
General Manager of Corporate, engaged Murray Wills, a contract IT Manager, to
create an IT architecture and roadmap for MoT, and “a successful Treasury bid to
improve MoT’s IT capability to meet our responsibilities to the New Zealand public,”
says Denston.
In response, the Communications team hired an external consultant to provide MoT
with conceptual design and intranet strategy. The consultant completed the
requirements analysis and conducted user research. She also created the original IA
concept, which was later modified by Provoke Solutions and adapted to suit MOSS
requirements.
When the design and strategy consultant ended her contract, an internal MoT team
member took over ownership of the business requirements and project management
(with support from Hamish Denston, who at the time was the Communications
Team’s Webmaster).
When this initial phase was complete, MoT moved the project to its IT Department
and IT engaged Provoke Solutions, a company specializing in business-focused
software using Microsoft technologies. Provoke used these technologies to define the
functional specification, design and build the CMS solution, and extend the site’s IA
beyond the initial consultant’s design.
In addition to the Provoke team, Capiche Design won the contract to deliver the
visual design.
When the site’s beta release went live in October 2006, Denston assumed sole
responsibility for site management. He says he believes that the involvement of the
many participants in the site development process has ensured a level of quality in
the end product.
“The change in participants throughout the process has ensured every decision is
reviewed,” says Denston. “This has increased the time taken, but it does act
effectively to make sure all decisions are well thought out and appropriate—which we
believe makes the site more effective in the long run.”
Discover (the current site) was launched in May 2007, followed by a round of site
enhancements to improve interactivity. These enhancements included out-of-browser
Alert notifications via a Windows taskbar alert; online surveys, with results rendered
using Microsoft’s Silverlight; and extending MOSS OOTB Search functionality by
customizing search Web Parts and integrating the search with external data sources.
These enhancements were rolled out in August 2007, shortly after the site launch.
Goals
The efficiency and effectiveness of information flow is fundamental to MoT. The
intranet was designed to address disruptions to that flow and inefficiencies affecting
staff productivity.
“Staff were having difficulty locating and updating key documents (policies and
procedures) leading to lost productivity from long searches/browsing and to asking
colleagues,” says Denston. “Also, the email ‘chatter’ was damaging the usefulness of
email as a business tool.”
The goal for the intranet was stated as: “Ensuring users with differing needs, skills,
and experience are engaged, and the functionality enhances rather than challenges
their day-to-day work life,” says Denston.
The team’s specific intranet goals were to:
• Improve information flow throughout the organization by providing
accurate and consistent information for better cross-Ministry
communication and collaboration
• Improve information “findability” to reduce staff time spent looking for
information
• Provide a central repository for internal policies and processes and
improve access to business-critical information
• Reduce the risk of misinformation through human error in updating
multiple copies of documents
• Reduce the risk of misinformation through terminology that is meaningless
to the reader
• Support and strengthen the MoT culture and improve staff morale and job
satisfaction by having the intranet be a channel for staff interaction
• Align with the e-government guidelines (accessibility standards)
• Reduce the amount of email communication between staff by creating a
functional and attractive communal space
Constraints
MoT struggled with the usual list of project constraints: budget, timeline, and choice
of suppliers. “In terms of budget,” says Denston, “the Ministry are constrained by the
fact they are a government organization, and have a limited IT budget, and a
responsibility to the taxpayer to use funds wisely. The timeline for implementation
was reasonably tight due to the length of time taken for analysis and design, and
enthusiasm by the Ministry’s leadership to launch the intranet.”
USERS
MoT’s intranet supports a staff whose primary job function is to draft policy
documents and identify problems and opportunities in the New Zealand transport
sector. The majority of the site’s users are involved in researching policy options and
making recommendations to the Minister of Transport, Associate Minister of
Transport, and the Minister for Transport Safety.
USER TASKS
MoT’s design team conducted a “persona hypothesis” workshop and identified the
primary tasks the intranet should support. The workshops also generated user
scenarios that helped the team determine a short list of user tasks.
The scenarios included the following use cases:
• Respond to a Ministerial Inquiry about the number of aircraft fatalities in
New Zealand between 2001-2005
• Receive Alerts on modifications made to a document
• Write a new policy
• Draft letters responding to an insurance enquiry
• Post information about an upcoming social club event
• Email the HR policy manual to a staff member
Common tasks the intranet supports include:
• Access current and historical policies, Parliamentary bulletins, internal
news, Cabinet meeting times
• Search for documents and other information sources
• View organizational structure and identify personnel
• Access internal and external contacts (names, phone numbers, and email)
• Access internal policies and procedures (such as “How-to” documentation)
• Contribute to site content
• Subscribe to site update notifications
Pictured: The Tools and Resources tab, which is used to locate content. The
user, looking for “leave,” has selected Human Resources from the items
grouped by Business Unit.
Pictured: The document library filtered for Human Resources, with the
“applying for leave electronically” PDF highlighted.
Pictured: The Tools and Resources tab, which is used to locate content. The
user, looking for “leave,” has selected Manual from the items grouped by
Type.
Pictured: After users select an item from the Training Calendar, this screen
shows the available course details.
FEATURES
The Discover intranet offers many features, including:
• Browse and filter content by:
o Content Type
o Audience Type(s)
o Title
o Name
o Date Created
o Topic
o Transport Mode
o Origin
o Rights
o Ministerial Portfolio
o A-Z
o Author
o File Size
o Document Type
• Search
• Upload documents/content
• Alerts/Announcements/Events
• Classifieds
• Desktop alerts
• Quick Poll
• Tagging (controlled vocabulary)
• Contacts Directory
Community Tools
Although team collaboration tools are being planned for future phases, the intranet
already contains several popular community-building features. “The Alerts,
Announcements, and Classified functionality has been enthusiastically adopted by
users,” says Wilkins. “and has resulted in a significant reduction in internal emails
sent to large numbers of staff members.”
Different levels of announcements are distributed via the homepage, news section,
and taskbar alerts. Announcements can include alerts, general announcements, and
classified advertising. The intranet also contains MySite: an out-of-the-box
personalized space where staff members can upload personal documents and create
pages, blogs, and wikis. This content can be shared with peers.
“The MySite functionality has been adopted more by some users than others,” says
Wilkins, “but has not currently been actively promoted to users. When teamsites and
project sites are implemented, there will be more focus on MySite functionality also.”
Search Technology
The site uses MOSS search technology.
“In previous projects, we [the implementation team] have used other search
technologies such as MondoSoft and ISYS,” says Chandima Kulathilake, MOSS
Solutions Consultant at Provoke Solutions. “It was decided that the OOTB
functionality of Microsoft Search in MOSS provided the expected business outcomes
for search.”
“Since the intranet was being deployed on MOSS, the search capability of the
platform was evaluated and identified as the best solution for the business
requirements,” says Kulathilake. “The extensibility and ability to interface and
surface results from various other line-of-business systems provided a strong
argument for using the platform capabilities.” But, he says, the search tool needs
further refinement (such as clustering similar results). The team also plans to extend
search functionality to other areas, such as shared drives, and to address
opportunities to enhance search as user expectations increase with use.
Data Visualization
MOSS comes with a basic out-of-the-box survey tool. But MoT wanted one that was
more visually compelling and had more of a “fun factor.”
With the recent launch of Microsoft Silverlight (similar to Flash), Provoke Solutions
saw an opportunity to experiment with the new technology and meet MoT’s needs at
the same time. With cooperation from MoT and Capiche (for consistent visual
design), Provoke Solutions created a simple online survey tool.
The survey is displayed on the homepage. It asks users a question and they select
from the multiple-choice answers. On submission, the results are animated to display
a bar graph.
The poll fills a need for MoT by creating a collective voice for the user community.
It’s quick, simple, and fun. And, according to Denston, the survey is something the
staff can look forward to on a weekly or daily basis.
Redesign Goals
The primary redesign goals were to:
• Streamline the IA: Refine Discover’s IA (which was applied in phase
one) to better fit with current business-user requirements.
• Establish consistency: Review the content templates and metadata
model; identify a set of key content templates for business unit areas and
also add workflow for the templates through MOSS.
• Increase uptake: Increase the number of people using Discover by
creating a clean, simple, and visually interesting workspace.
• Distinguish work vs. play: Create a visual divide between serious
business content and more relaxed, “fun” aspects of the tool.
• Encourage collaboration: Offer employees the opportunity to take a
break, express their individuality and creativity, and interact with others
via features like Announcements and the Noticeboard.
• Create interest: Stimulate employee interest in information.
• Inform users: Push information that is new or important.
• Enhance the site’s aesthetics: Improve intranet uptake through visual
stimulation and greater design consistency.
• Enable out-of-browser message notification.
• Refine and re-envision content management: Streamline content
management tasks as much as possible. Encourage distributed authoring
for communication content to build a platform that will ease the move to
fully distributed ownership and content management in the future.
Usability Methods
The first consultant MoT hired provided business requirements and a conceptual
model for the site. This information, combined with insights from MoT’s internal
intranet team, provided the basis for Provoke’s redesign work.
Given budgetary constraints, behavioral research (usability testing, conducting
interviews, or observing staff using the site) wasn’t possible, so the Provoke team
chose instead to conduct a short workshop with the MoT project team to identify
primary personas. They created personas on-the-spot during the workshop. These
personas served as the team’s core usability research tool during planning.
“We began by identifying all the roles at the Ministry (based on job title),” says
Fugaz. “We then clustered similar roles and prioritized each cluster based on likely
intranet usage. For the priority clusters, we identified two primary user-types (based
on information-seeking behavior), identified user goals, and common task
scenarios.”
Time constraints dictated that the persona profiles that resulted from the workshop
were very basic, but they proved sufficient to help the IA identify a taxonomy and
navigation structure.
To augment the personas, the team relied on their collective knowledge and
experience, some field observations by Denston, and some research (including a
previous NN/g Intranet Design Annual). This data comprised the basis for the project
assumptions, and the team acknowledges that these assumptions will likely to lead
to the need for changes down the road. They have built that likelihood into the
system design, which helps compensate for the lack of upfront research.
“A lot of the IA work was based on assumptions,” says Fugaz, “so the tag-driven
system we’ve created allows flexibility for future iterations.”
“In terms of user navigation—pathways to information—the intranet relies on
appropriately tagged content,” he says, “While this requires a minute of upfront time
when uploading and tagging new content, we believe the benefits come later by
greatly enhancing the findability of content. Users can browse to content using a
variety of pathways, and via taxonomy which makes sense to each individual.”
Needs:
• Access to internal and external contacts
• Easy access to current and historical policies, Parliamentary bulletins, internal
news, cabinet times
• Easy search functionality generating accurate results
Needs:
• View organizational structure and identify personnel
• Access internal and external contacts (names, phone numbers, and email)
• Access internal policies and procedures (such as “How-to” documentation)
TIMELINE
Phase One—Project Planning and Design
(August 2005—October 2006)
August 2005: Intranet planning phase begins with one consultant scoping
intranet strategy and developing conceptual design
October 2006: Intranet launched, running on beta version of MOSS07, and
included the floor plan and org chart
RESULTS
The redesign’s primary results have been qualitative thus far. Based on feedback the
staff has received, the intranet has increased user satisfaction across the
organization.
“We’ve had overwhelmingly positive feedback from staff and higher uptake of the
intranet,” says Denston. “My observations show that staff are exploring the new
design and features—and as a result discovering information they initially missed.”
Denston says the redesign results go beyond just general satisfaction—they’re
having a positive effect on staff productivity as well.
Prior to the intranet, employees communicated to all staff or to a group of staff
members using email. The content of these messages ranged from time-sensitive
matters to mundane requests, such as someone looking for the location of a laptop.
The email volume was significant, as was the demand on staff time in dealing with it.
These emails have been replaced with the intranet’s Alerts and Announcements
features, and the notifications are now unobtrusive.
“This has been beneficial not only from a network perspective,” says Denston, “But
has helped to reduce the stress on staff of having a build-up of emails—that may or
may not be relevant—cluttering their in-boxes.”
Hamish Denston lists a few tasks users can do now that they couldn’t do before:
• Receive message notifications outside their browser (Windows taskbar
alert)
• Post messages to the whole Ministry without creating email “noise”
• Search for information and obtain weighted and indexed results
(previously, search returned a result set that was not sorted in any way,
which didn’t assist users in locating the information required)
• Contribute to online polls and surveys
LESSONS LEARNED
As can be expected from a complex development project, the lessons learned depend
somewhat on the team member’s role in the redesign effort. Following are insights
from various MoT team members.
SUMMARY
The New South Wales Department of Primary Industries (NSW DPI) is a government
agency that works with industry, rural communities, and other public sector
organizations to foster profitable and sustainable development. NSW DPI offers a
wide range of services, and the intranet helps enormously in supporting the very
diverse set of workers who deliver them.
The intranet, InSite, also helps to unify the four departments—Mineral
Resources NSW, NSW Agriculture, NSW Fisheries, and State Forests NSW—that were
unified to form NSW DPI in July 2004.
Just after the organizations merged, the intranet helped people to see where they
actually fit in to this much larger organization. Knowing the intranet was the ideal
platform to keep everyone informed of new department’s role and vision, the
intranet team worked quickly to get the site up and running.
Now under the Communications Branch, intranet team members immediately
populated the intranet with relevant content needed by the users. But the team
knew the communications could not be just one way, as staff had a lot of questions.
To ensure that employees felt heard and got their questions answered, the intranet
team added a form that let people submit questions and have them answered in the
FAQ area.
The exchange of ideas continues today, almost four years later. In the homepage’s
top middle section, there are tabs for Announcements, Events Calendar, and an RSS
subscription to Industry News. Users can also read archives or subscribe to news
types they’re interested in.
The homepage feature story, which appears in the upper left, changes at least twice
a week. Two scientists are showcased in this example, exalted for their latest
contribution to a trade magazine. This section usually comprises stories written by
staff members, enabling people to share with the whole organization what they’re
working on. Reciprocally, staff members reading the stories will learn more about the
different happenings at their organization.
The Staff Achievement Awards section appears just below that. This area encourages
people to nominate a colleague to be recognized—one more way staff can feel good
about themselves and their co-workers.
The homepage also displays, on the left, links to Media Releases. This is important as
it lets people within the department know what kinds of messages are being sent out
to the public.
Pictured: The InSite homepage of the government agency New South Wales
Department of Primary Industries offers stories and news that helps
employees keep each other informed and maybe even motivated.
On any intranet, it’s important to keep the news current and to ensure that a variety
of topics are covered. Having many news sources helps to alleviate this problem, as
does making it easy for users to submit news.
At NSW DPI, all staff members are encouraged to submit news and photos describing
what they are or will be working on.
The submit a news item appears on the homepage under existing news items.
Clicking it opens a clean, short form where people can add a story or an idea for a
story, plus upload related photos and images. The user’s name and email address
are required, so site editors can ask questions as needed when they’re editing the
story. The form allows users to enter the story right there, and browse to upload any
images. Clicking the Submit button at the bottom sends the information to the
Internal Communication Unit, where it’s edited and prepared for publication.
Pictured: A short and simple form enables all employees to submit a story
idea, or a story and accompanying photos.
All of the news and announcements are informative. Plus, the intranet allows users
to access their email over a VPN when they’re out of the office. The Webmail link is
under the Support Services tab, a good classification for the function. Once selected,
users are asked to log in with a username and password. At the bottom of the page,
there’s information about Help for users who are lost or simply forgot their password.
Pictured: People can check their email over the intranet via a VPN.
The intranet supports 3,500 staff at more than 120 locations throughout New South
Wales. These people hold a wide range of job roles, including: clerical and
managerial staff; field staff (such as mine safety inspectors, veterinarians, foresters,
and fisheries inspectors); operational staff (such as farm hands); scientists and
researchers (such as horticulturalists, entomologists, geologists, and chemists).
With all of these roles come many different types of tasks—far different than at more
traditional organizations. For example, some staff members need access to vehicles
to do their jobs. The Department maintains a fleet of vehicles at a few locations, and
staff members can book these vehicles for work-related travel. A simple form on the
intranet makes this possible.
The form is easily found in the intranet’s Administration section. The top of the form
asks for Driver details, where users type their names and choose a booking location.
The form lets administrative staff or other colleagues do bookings on behalf of
others, offering fields for both the Driver name and Your name. The Travel plans
section collects information about departure, return, and trip distance. The Vehicle
requirements and Special requirements sections allow users to specify the type of
vehicle they prefer, plus any other requirements.
Like the form for submitting news, all field labels are short, simple, and
understandable. There is only one column of fields; left aligning all of the labels and
fields makes the form neat and easy to scan. The section headings help users keep
their context as they answer the questions, as does the subtle yellow background
differentiating the sections.
At the end of the form, there is a Submit button (and a Clear button, which we don’t
usually recommend for forms, as users often accidentally clear their work). The
Submit button is visible and comes first (before the Clear button); when users click
it, the request is routed to the relevant fleet manager.
Historically, employees booked vehicles by calling their location’s receptionist, who
would take the details over the phone and enter the details into a fleet management
system. The new system is a good example of the intranet supporting work tasks
and helping to reduce costs.
Pictured: Users can book vehicles from the motor vehicle fleet. The form has
simple field labels that are left aligned, as is the single column of fields.
It’s not easy to make an intranet that works well and looks good doing it. That NSW
DPI achieved this was no accident. The intranet team designers wanted to use a lot
of white space so users could focus on the content. The team was disciplined,
keeping active white space on the intranet’s pages rather than cluttering them up.
The foundation for this discipline is at the template level; the template itself is
designed with a lot of white space. The team also published much documentation for
publishers, including guidelines on keeping pages “small” and eliminating non-
essential images. This is especially important considering that many of the staff are
in remote locations on slower connections.
Pictured: Much white space in the content templates ensures that the user’s
focus is on the content.
Designers also considered their typical users’ screen resolutions (800 x 600 and
1024 x 768) and designed accordingly. Through CSS and Javascript, the fixed-width
design changes automatically, depending on the width of the user’s browser.
The intranet’s role is as integral now as it was just post-merger. With an abundance
of news, plus very elegantly designed forms, people can effortlessly give and receive
information at NSW DPI. This exchange of ideas is all made possible through InSite,
the organization’s robust yet simple intranet.
TECHNOLOGY
Wireframes PowerPoint
Database PostgreSQL
Analytics A W Stats
CONTENT MANAGEMENT
CMS Technology
NSW has been using Squiz MySource Matrix to manage both its public websites and
intranet since 2004. NSW decided early on to use the same CMS for its public
websites and intranet, primarily to keep costs down. “Using the same system has
allowed us to share content and ideas, share knowledge and resources, and has
simplified publisher training,” says Needham.
Squiz MySource Matrix is an open-source PHP-based CMS developed by an Australian
company. It runs on a PostgreSQL database. The product is only about five years
old, but according to Needham, there is already a large user base within the public
sector. “The open source nature of the product means that it is constantly changing
and growing in complexity,” says Needham. “We upgrade the system about four
times a year, and each upgrade comes with new features that we try to figure out
how to take advantage of.”
Despite the advantage of using an open source solution, the downside to this
particular technology is that it can be somewhat difficult to use.
Content Authoring
With limited staff to manage the intranet, distributed publishing is key to keeping the
content up-to-date and relevant. “Like many large systems, the CMS is not an easy
application to use,” says Needham, “and tends to be overwhelming for people who
aren’t using it day to day, and who only need to perform relatively simple publishing
tasks.”
The department received training and implementation support from Squiz when they
first installed the system, but the training happened at approximately the same time
NSW DPI was created in the four-department merger. “There was a lot going on in
terms of communications and the need for integrated platforms,” say Needham. “We
were keen to start building sites, including an intranet, in the system in order to
have a centralized source of information, so we had to learn a lot about it in a
relatively short period of time.”
To address some of the system’s complexities, the department developed an
alternative interface, which is much simpler than the administrative interface, and
gives content authors access to perform routine content management tasks, such as
adding and editing HTML pages and publishing and updating files.
The department currently has approximately two-dozen content publishers in its
various branches. Most of the content publishers who are trained on the simple
interface are from the Corporate Services Division (finance, HR, library services,
asset management, IT, occupational health and safety, and so on). It’s their content
that is used most often, and impacts the operation of the other areas of the
department the most.
Needham and her colleague, Penny Wheeler, Web Content Officer, have also started
to train people from other areas of the department. “The people we train come from
a variety of job roles, including researchers, librarians, managers, and clerical staff,
but tend to be the latter,” she says. “We don’t have any dedicated intranet
publishers outside of the Internal Communications Unit. All of the people who have
been trained are doing intranet publishing in addition to their regular jobs. Once
people are trained, they are given access to specific areas of the content
management system to maintain content.”
“We also have comprehensive standards and guidelines on the intranet to guide our
publishers on accessibility, writing for the Web, using images, and structuring their
content,” says Needham.
The intranet is managed by the Internal Communications Unit (which is part of the
Communications Branch), and is staffed by two full-time employees: Needham and
Wheeler. A Website Administrator from the Communications Branch’s Web Publishing
section provides server administration and CMS support. “Due to the size of the
team, we are both required to work across a broad range of disciplines, such as
information architecture, usability, content management, design, and developing
technological enhancements,” says Needham. “The size of the team also means we
need to rely on other people in the department to keep the intranet content current.”
The intranet team resides in the same department as the team managing the public
website, and this proximity means the two teams have a close working relationship.
They share a CMS, rely on the expertise of the same developers, and, according to
Needham, “we often help each other out when we have big projects on.”
Pictured: The Forms index from Fishbowl, the former NSW Fisheries intranet.
Content was organized in Communities, which required users to know who
owned the content or resort to searching.
Pictured: The Forms index from the former NSW Agriculture intranet. The
navigation (on the right) was based on the organization structure and too
simplistic for the requirements of the larger, merged organization.
Immediately following the new department’s formation, a temporary intranet was
created to smooth information distribution during the transition.
It was during this time (September 2004) that the department decided on Squiz
MySource Matrix for the CMS—to be used by both the public-facing site and the
intranet. “The new system presented a huge learning curve for everyone involved in
its implementation,” says Needham. “By early 2005, a second iteration of the
intranet, using the new system, and combining much more of the information from
the legacy intranets, was launched.”
The new site that was being built out of the legacy intranets was constructed without
much consultation with users. This was because there wasn’t much time to devote to
usability, and what time the team did have was being directed mostly to learning the
new CMS and the huge task of content migration. As a result, the site’s design and
navigation was developed mostly from concepts borrowed from the legacy intranets,
and ideas from intranets outside the department and publications such as Nielsen
Norman Group’s Intranet Design Annual.
Developing a New IA
Migrating content from the legacy sites presented the team with the problem of
where to put all the content. “The structure of the site had become unworkable,”
says Needham. “Not only were we getting complaints from the users, but we were
having trouble finding a home for the content we were migrating into it. It became
clear to us that the navigation was not going to work in the long-term, so we decided
to redesign it.”
Once the initial content migration challenge was complete, the team could focus on
involving users in the redesign process. “We put a call out for volunteers to be part
of an ‘Intranet Reference Group’ that would take an active role in reviewing and
redesigning the navigation, as well as providing an ongoing source of focused user
feedback.”
The group’s members participated in a virtual focus group (via a blog), card sorting,
and user testing activities, and contributed to helping the design team create the
site’s new IA and navigation. The ideas that were generated from the Intranet
Reference Group sessions were integrated into the new design, which was launched
in July 2007.
“The virtual focus groups were a real success story in the redesign,” says Needham.
“It allowed us to involve a broad range of users, and to keep the costs to a
minimum.”
According to Needham, this latest iteration of the intranet, called InSite, provides
“much more intuitive navigation, greater integration of corporate applications, a
strong recognizable design based on the department’s new corporate identity
standards, and is part of a family of branded internal communication vehicles—which
includes InBrief, a weekly email newsletter, and Inside DPI, a printed staff magazine
produced three times per year.”
Pictured: The navigation and overall IA of the old intranet (version 2) was a
constant source of complaints from users.
Pictured: Topic page from the second iteration (version 2) of the intranet. The
inefficient “flyout” navigation on the left was a major usability problem. The
new version has local, contextual navigation that expands to two levels.
Pictured: The new intranet has a strong, recognizable design based on the
department’s new corporate identity standards, and is part of a family of
branded internal communication vehicles.
Pictured: Sample topic page (Human Resources). The team made a concerted
effort to avoid structuring content based on the organization structure. This
was particularly important in a post-merger environment, where the
organization structure was not well understood and was likely to change
frequently.
USERS
The intranet supports 3,500 staff at more than 120 locations throughout New South
Wales, in a wide range or roles including:
• Clerical and managerial staff
• Field staff (including mine safety inspectors, veterinarians, foresters, and
fisheries inspectors)
• Operational staff (such as farm hands)
• Scientists and researchers (such as horticulturalists, entomologists, and
geologists)
USER TASKS
Using the intranet, staff can:
• Read internal news, media releases, and industry news
• Submit news and photos to keep the homepage fresh and relevant
Design
• Simple, clean design (lots of white space and emphasis on hyperlinks)
• Consistent design across all pages
• Minimal use of graphics (no gratuitous images)
• Resizable text
• Standards compliant design (including CSS-driven layout)
Search
• Search available from every page
• Search the intranet, staff directory, or Internet from one field
• Search results include “best bets” to help users quickly locate relevant
information
Content
• Distributed publishing
• Comprehensive intranet design standards and guidelines for content
contributors
• Department-wide news and announcements (with archive) and RSS
subscription service
• Seamless integration with major corporate applications, including
purchase requisitions, travel bookings, vehicle bookings, and Webmail
• Content owners identified on every page to enable quick, targeted
feedback via a link to an email address
• Simple, easy-to-use forms
• A-Z index and site map to assist users in finding content
• Key contact lists for content topics
• Web 2.0 integration (Google maps) for office location maps
Collaboration Tools
“We don’t currently have any collaborative areas,” says Needham. “Some teams use
Lotus Notes teamrooms, but we have a project looking at using blogs and forums to
support geographically separated teams and to foster communities of practice.”
Data Visualization
Because one of the department’s primary roles is to lead the response to agricultural
and animal emergencies, such as exotic disease outbreaks, the intranet provides
access to Front Gate, an interactive mapping system. As Needham notes, “this
system was specifically designed to support emergency planning, response, and
recovery operations, as well as ongoing regulation and compliance activities.”
Front Gate lets users generate an array of customized maps and reports—
incorporating a wide range of data—for any area of the state.
Search
The intranet template has a multi-search field available at the top of every page. The
same field can be used to search the intranet, staff directory, and the Web (via
Google). The NSW intranet uses the search module that comes packaged with the
CMS, Squiz MySource Matrix. It’s limited to searching content contained in the CMS,
but there are a range of information repositories the intranet draws on. “We are
currently looking at implementing a Google Mini search appliance to search the
intranet and other information repositories,” says Needham.
The department regularly tracks search logs, and in an effort to improve search
results, it applies log information to adjust the metadata included in the most
relevant content items.
Pictured: Search box available from the top right of every page on the
intranet. Users can search the intranet, staff directory, or the Internet (via
Google) by simply changing the tab at the top of the search box.
Pictured: Sample search results page. “Best bets” (pages that best match the
search query) are highlighted in yellow.
Pictured: Keywords are entered into the CMS to improve search results.
Search terms are also monitored in the search logs; popular terms are added
to relevant content items in an effort to further improve search results.
Redesign goals
The primary redesign goals were to:
• Address fundamental issues with the navigation
• Provide more consistent page layouts
• Provide a flexible IA that will grow with the site
• Improve search
• Improve access to content
Constraints
A Small Team
“The biggest challenge was probably a lack of resources,” says Needham. “With only
two members in the intranet team we were often stretched for time. Somehow we
managed to develop the new intranet, which involved reviewing the existing intranet
with the Intranet Reference Group, developing the new IA, developing wireframes
and prototypes, building new templates, conducting user testing, migrating content,
all while maintaining the existing intranet. It meant we had to focus on the most
visible and used content first.”
CMS Hurdles
The complexity of the CMS also presented a considerable challenge for the team.
“We had trained a handful of people from outside the Communications Branch to use
it, but it proved too difficult for people who weren’t using it often,” she says, adding
that this “had a huge impact on the speed of the content migration.”
Making a Case for Task-Based Navigation
Moving from an inward facing organizational-based navigation to a user-focused
task-based navigation also proved to be a hurdle for the team in working with
content owners.
“We consulted heavily with content owners following the navigation review,” says
Needham. “Convincing them that organizing in a user-oriented way, rather than by
who owns it, has been a significant challenge.’
Usability Activities
The design team looked at as many intranets as they could find for ideas and
inspiration before embarking on the redesign. “In developing the design of the site,
and deciding on how to implement some of the major functions, we looked to other
intranets for ideas,” says Needham. “Whenever we can, we like to see the intranets
of other organizations, and talk to other people who manage intranets about what
they are doing, and how they have solved particular business problems. The Nielsen
Norman Intranet Design Annuals are also a major source of inspiration.”
But they also looked inward to review what was and wasn’t working on the current
site.
The second intranet (v2) was built very quickly and without user input. The team
was focused on integrating assets from the four department sites into one difficult
CMS.
Pictured: Ideas were borrowed from the intranets of the former agencies for
the second intranet (v2).
After about a year, Needham says it became increasingly obvious that people were
having trouble finding content. “In particular,” she says, “the global navigation
labels—Communities, Industry, and Resources—seemed to cause confusion for
users. Whilst Communities, for example, was well understood by the staff of one of
the former agencies, it didn’t resonate with staff that had come from the other
agencies.”
Pictured: Communities was well understood by staff from one former agency,
but it didn’t resonate with staff from the other agencies.
The team was also struggling to find a home for all the content that had been
inherited from the four legacy intranets. Although there was much content that was
of value to users, as Needham says, “It was just too hard to find.” The navigation
was the main cause of the confusion.
asked to take the columns into a new worksheet and regroup them in a way that
made sense to them. They were also asked to name the groups.
Participants were allowed to put the items in more than one group or to make sub-
groups as needed. There were but two simple rules: there are no right or wrong
answers, and ignore the current groupings on the site.
When the users were through, the team analyzed the sheets to determine patterns
and trends and then returned the results to the blog and opened it up to feedback
from the group. “Again, the discussion on the blog provided a lot of insights, and
gave us a great starting place to start to explore options for the navigation,” says
Needham.
Pictured: The team used Excel spreadsheets to conduct card sorts with a
virtual focus group of 30 staff members.
suggest alternative models (but to also provide a clear rationale if they did so). Their
only direction this time? Avoid the organizational chart as a basis for their model.
“Over the course of two weeks, we did about six design iterations until it felt like the
group had reached a consensus,” says Needham.
Pictured: An early “site map” illustrating the placement of content within the
proposed navigational model.
Pictured: One of the Intranet Reference Group tasks was to test an HTML
prototype of the proposed new navigation with another staff member. Group
members were given instructions on how to conduct the test, and provided
with a script that included a range of user tasks.
The user group members reported their findings on the blog. The designers gained
insights, “but nothing that sent us back to the drawing board,” says Needham.
The design team made changes based on the test results and sent the user group
back into the field. This iterative approach resulted in far fewer issues reported in the
second test. The user group and the design team agreed that they should proceed to
implement the ideas in the final prototype.
Pictured: The local (left hand) navigation now expands to one level, rather
than using “fly out” menus.
their content to feature on the homepage. It now has a good mix of news and
announcements, navigation, and quick links. In addition to a feature story and
headlines, we have ‘spotlights,’ which are used to feature new tools or content, or
promote other projects and initiatives going on in the department.”
She has also taken steps to ensure that the site’s navigation and homepage are
protected by policy, so that it’s difficult for people to exert their influence to make
changes to the site that are not user-centered.
TIMELINE
July 2004:
New department formed
Interim intranet (v1) concept approved
Interim intranet (v1) launched
September 2004
New CMS implemented
January 2005
New intranet (v2) launched
February 2006
Intranet Reference Group formed
February 2006—April 2006
Intranet (v2) reviewed, including:
Analysis of usage statistics and search logs
Content audit
Card sorting
Usability testing (using scenarios and task analysis) of proposed navigation
and IA
Development of wireframes
User testing of prototypes
RESULTS
For Needham, the redesign’s most noticeable result is the reduction in user
complaints to the helpdesk. “Anecdotally, we have taken this to mean that staff are
finding information easier to find, and the changes to the homepage have satisfied
the needs of more areas of the department for a ‘presence’ on the site,” she says.
“Feedback after the redesign has been overwhelmingly positive. A number of staff
have commented that they find the site much easier to navigate, and content much
easier to find.”
It’s probably too soon to tell whether the redesign has had a dramatic affect on
usage statistics. Needham says she regrets that the team didn’t collect more
benchmarking metrics, so they could measure the impact of the changes going
forward.
The new navigation is “much more user-centered” as a result of the user research,
she says. “Improved supplementary navigation, including the site map and A-Z
index, provide users with multiple ways to access content quickly.”
LESSONS LEARNED
Lessons learned from Kate Needham and Penny Wheeler:
Focus on key content. “Identify, and concentrate your efforts on, the most
valuable (most used and visible) content first. Doing so will build trust in the
intranet, and the redesign team, and provide the momentum and enthusiasm
you need to continue to improve the site.”
Improve continuously. “A redesign never finishes. There is always
something that can be done to improve an intranet.”
Look to other intranets. “Look for opportunities to interact with other
intranet managers and to see other intranets, as they are an endless source
of ideas and inspiration.”
Involve users and test with them often. “Involve users as early and often
as possible in the design of the site, and ensure that you consult users from
as many different areas of the organization as possible. Test your design
decisions as often as you can, with as many users as you can.”
Communicate with content owners. “Be ready to defend your decisions.
We had quite a few content owners who found it difficult to cope with the
move to task- and topic-based navigation, rather than the organizational
structure style of navigation they were used to. Keep content owners
informed of major decisions that might affect their content.”
Communicate with sponsors and users. “Manage the expectations of the
project sponsors and users. Prepare the users for major changes the site
before they happen.”
Collect metrics. “Remember to collect some metrics before a redesign, so
you can measure the impact of the changes.”
For user research, think beyond the box. “The Intranet Reference Group
and virtual focus groups conducted via the blog were far more successful than
we could have imagined. Think outside the square when it comes to user
research, especially if time or money is limited.”
Manage your time wisely. “Make sure you allow enough time for the
redesign process. Break the redesign into phases—don’t try to do everything
at once.”
Interrogate technology options. “Make sure that the technology used to
create the site supports your vision.”
SUMMARY
The goal for JPL’s intranet team was to build a site that was more functional, more
easily edited, and better-looking. The primary goal was to enhance the user
experience on the site by helping users find the information they need. On the way
to that goal, the technical side of the intranet team joined forces with the Office of
Communications and Education (OCE). By partnering with a team well versed in
communicating, the team could better tackle the problem of keeping content current.
The team also made a technical move to using SharePoint, which simplified content
update methods and let content editors make changes more easily.
A side effect of working with the OCE was an added focus on the site’s visual
presentation. The site, which had been previously designed by engineers, looked like
it had been designed by engineers. The team brought in an outside design team to
build a better-looking intranet, based on the knowledge that a clean design can
greatly enhance a site’s usability.
By joining forces, the Office of the Chief Information Officer, the OCE, and the
outside design firm of Moore Boeck were able to tackle the challenges the previous
site presented and make great steps forward in creating a better intranet.
At JPL, content creation is distributed; the site’s only editorial workflow is focused on
the homepage. Additions to the homepage require approval from one of a few
reviewers, each of whom can approve or reject content and route approved content
to the appropriate site areas.
All news stories require approval. Stories can originate from anyone at JPL or directly
from the OCE. The OCE team then edits the stories and routes them to JPL Downlink,
JPL in the News, Upcoming Events, or Announcements Web areas of the homepage.
One of the most unique aspects of the site is the Quick Find tool built into the site
search. The site search suffers from problems common to many intranet site
searches: it doesn’t always pull the best documents or information to match users’
queries. The team is continually adjusting the backend to make the tool work more
successfully. As an enhancement to the search, the team uses Quick Find, which
The Quick Find functionality works for information about people as well as other
types of content. The tool searches information in both its Yellow and Red Pages.
JPL’s many service organizations are listed in the Yellow Pages; its Protective
Another creative feature on the site is the use of maps, created through Google
Maps, to convey information about the corporate campus as a whole as well as about
specific campus buildings and resources.
Pictured: Campus maps don’t just show building locations, but include
information about bus stops, facilities at each location, and even available
conference rooms in each building. (image courtesy NASA/JPL-Caltech)
The team decided it was important to provide mobile access to the site, so it started
by designing a mobile site accessible on the iPhone, with plans to expand support to
BlackBerry devices as well. As team members started building a mobile site,
however, they realized that rather than making miniature webpages for a small
mobile screen, they could design a better experience by building specifically for the
platform. So, information about JPL available to employees on the iPhone is built as
an app for the phone, rather than as a mobile website.
The team tried to focus on providing the most useful information for mobile users,
such as person lookup, daily news, maps, menus, bus schedules, and conference
room information. It’s important to consider what information is of most importance
to mobile users versus users who are sitting at a computer to access information.
Pictured: An iPhone application lets users access intranet content on the go,
providing access to a subset of site content. (image courtesy NASA/JPL-
Caltech)
The team continues to come up with new ways to display information in a meaningful
way and to help users get to the information they need quickly and efficiently.
Creative solutions to known problems, novel methods of displaying information, a
new focus on presenting up-to-date and changing information, and a much-improved
visual design all work together to help the JPL site provide an improved user
experience to employees.
Future Plans
Now that the team has developed all the key navigation, Quick Find, search, and
look and feel elements, it plans to expand the feature set. It’s also looking to other
areas within JPL where the site can add value. “We are looking at supporting
projects, line organizations, work groups, interest groups, and other OCIO [Office of
the Chief Information Officer] service areas,” says McWatters.
TIMELINE
The JPL intranet has been in a state of continuous evolution, with incremental
rollouts since it began. One major exception was switching between hosting
platforms from the Sun portal platform to SharePoint. This transition took more than
a year to complete.
Constraints
If time is the universal constraint, budget is a close second at nearly every
organization. Although tight budgets make site enhancements difficult, often the real
challenge is just getting enough money to keep abreast of the inevitable ongoing
changes needed to just keep the site current.
“Budget is always an issue,” says McWatters. “There is always a hope by
management that an intranet once set up will be able to just keep running with
almost no resources.”
USERS
JPL has an extremely diverse workforce that includes all the usual roles found at any
large organization. In addition, the site serves a workforce that includes world-
renowned scientists and engineers. The key activities at JPL are highly technical, but
the ordinary activities of any company with 5,000 employees must also be fully
supported by the organization’s intranet.
USER TASKS
One of the most common uses for the intranet portal is to find: people, buildings,
conference rooms, phone numbers, documents, maps, information, services, and
tools to support people both as employees in general and in their work-related roles,
including scientist, engineer, and so on. The other common site use is to discover
what’s happening at JPL.
DESIGN PROCESS
The JPL intranet’s design has been evolutionary, and that evolution has been fed
along the way by user feedback and testing. The JPL team used the following
methods to ensure that user-centered design would drive the design process:
• Solicit feedback from users
• Conduct usability testing
ACCESS
The JPL intranet homepage is the default homepage for every computer provided to
JPL employees. Users can access the intranet from outside the firewall via a VPN
application or a browser-based VPN.
TECHNOLOGY
The JPL intranet portal runs on SharePoint and an additional server supports extra
features such as Quick Find and the interactive maps. In keeping with SharePoint’s
farm terminology, the tech team develops on a development farm, tests on a test
farm, and deploys to the production farm. They also use source control repositories.
All user-generated trouble tickets are tracked in a Remedy system.
The site’s Quick Find capability utilizes AJAX technology.
CONTENT MANAGEMENT
Content management on the JPL intranet is handled through SharePoint. Permissions
govern who can update the content and a versioning system is in use.
The only part of the site with a real editorial workflow is the homepage
Announcements section. Anyone at JPL can submit homepage Announcements; the
following workflow governs that content:
• The user submits content
• Multiple reviewers are notified via email
Search
As mentioned earlier, the JPL intranet relies heavily on both search and the Quick
Find feature to aid users in getting directly to the content they seek. Finding the
technology to support search is a process, and as many teams find out, it’s an
ongoing process.
“For evaluating different search solutions we have a “bake-off” (taste test),” says
McWatters. “First, we analyze our search logs to come up with a list of 20 common
queries. We enlist about 20 users and have them submit these common queries to
the different search products and have them rate the results for each query.”
They ask the users to rate the results based on how close to the top they feel the
ideal result was for them. “At the end, we have them play with additional queries of
their choosing and again rate the results,” he says. “There are differences in extra
features between the offerings—such as the ability to refine a search—and we ask
them to rate how valuable they found those features.”
This type of continual improvement is one of the best methods to refine search.
What JPL and other teams have learned (sometimes the hard way) is that users want
effective search and making search effective is a process that must be supported
over time, not a one-off project.
• Alerts. The JPL intranet pages include an alert system that can pop up an
alert without requiring users to refresh the page. Physical and computer
security personnel can initiate these messages in emergency situations,
without requiring the intranet team’s intervention.
• Weather and traffic. The intranet homepage displays current weather
and traffic. There are links to get more detailed weather and traffic
information, but because the information displayed on the front page is
current, users rarely need to click for more.
• News feeds. The site offers dozens of JPL-related external news feeds
(RSS) focusing on NASA, business, science, and technology.
Pictured: The intranet’s graphing capabilities. This example shows power usage
compared with the previous year. (image courtesy NASA/JPL-Caltech)
ROI
The familiar refrain of “we don’t measure ROI in hard numbers,” applies to the JPL
team, too. Sometimes a useful site is just a useful site—and that’s enough.
“We have not been able to justify the ROI in hard numbers,” says McWatters. “We
tried the usual if X people do these things Y times per day and it used to take Z
amount of time and now it is ZZ% faster, we are therefore saving $XX, but we
haven’t found this argument to be particularly convincing to upper management.”
LESSONS LEARNED
McWatters shares some of the many lessons the JPL team has learned in developing
the redesigned portal:
SUMMARY
With diverse, thorough content and unusual and fanciful features, the intranet for the
Saudi Commission for Tourism and Antiquities (SCTA) far exceeds its goal to involve,
include, and attract all employees.
The homepage gives an overview of the intranet’s content and varied information,
including news, tools, weather around the country, and event photographs to help
draw users in. Specifically, the center column offers various types of news, including
the President’s Word section at the top, which includes a summary of and link to the
SCTA president’s letter to the organization. Below this are the top news items,
followed by Articles posted by employees. This combination of news from the
president, internal news, and news and announcements written by employees
themselves makes the homepage inclusive of and appealing to all.
Users can access eServices—the various tools they need—via the set of icons that
appear toward the bottom of the center column.
More amusingly, in the upper left, the photo library section shows one of the latest
photos that an employee posted. These pictures are related to antiquities and tourist
attractions. Employees can click through and see more photos. The Media Library, in
the lower right, links to videos. Also in the lower right, the Comics section links to
comics written by employees. All of these sections add up to some entertaining
intranet moments. Another rewarding topic relates to spirituality: The Prayer Time
area in the middle of the left rail shows the times for praying each day.
Given that the intranet is written in Arabic and most text is read from right to left, it
makes sense that the main navigation menu appears on the right side of the page.
The logo appears in the upper right, rather than left. Also, section headings, tab
labels, and text blocks are flush right (when not centered).
The intranet’s eServices area offers a very extensive set of tools and applications
that help employees do their work. People with various jobs and in different
departments alike can find the tools they need here. And, as new tools are created,
they are also added to this list. This consolidation of items facilitates sharing
applications and tools between teams, and makes it easy for employees to find the
To learn about what is happening with colleagues from around the organization,
employees can click through from the homepage to the social news section, where
they can post their own news items and related images, and view, comment on, and
rate other items. Content might relate to work, such as success stories and
To post new material, users click a link on the homepage. This opens a form that lets
users title their item, write a description, and attach a file. Once the intranet content
administrators approve it, the content will be posted.
Pictured: Users can fill in a simple form to post content on the intranet.
Comics have become very popular in recent years, and SCTA employees are trying
their hand at not just reading them, but creating them. The organization considers
this sharing part of team building and fun, and encourages sharing and commenting
Pictured: Employees can post comics and funny stories, and comment on these
on the intranet.
The Media Library houses sets of media that employees post (after the media is
approved by the content administrators). Employees can use the folder on the right
to view different categories; they can also post comments about each item, adding
and sharing knowledge and thoughts.
Employees use the employee directory to find and learn about their colleagues. They
can also update their own profiles easily; once the HR department approves the
change and updates the main HR database, the information is posted on the
intranet. This helps the organization keep its systems up-to-date and ensure that the
HR and intranet databases match up.
In the profiles, the standard information about the employee appears on the first
tab, while other information is stored in subsequent tabs to keep clutter at bay.
An editable form with the user’s information pre-populated makes it easy to edit
personal and job information. Users can also add a photo or avatar to their personal
profiles.
The main page for a sector within the organization displays information important to
that group, such as: a welcome from the president, events, projects, document
library, eServices, media library, important links, and various other elements
available on the homepage. In this case, however, the elements are targeted toward
the particular sector.
Department pages also offer similar types of content, but targeted to each particular
department.
The SCTA intranet designers succeeded in striking that very delicate balance
between making the intranet a pure productivity tool and making it whimsical and
interesting. It’s beyond difficult to do this while maintaining a consistent personality
throughout the design, but they certainly achieved it here.
BACKGROUND
The SCTA intranet came about when the organization decided to replace its weekly
employee newsletter, which focused on news and social events. In the early days of
the organization, the newsletter was sent out to all employees. It was designed and
created using adobe Photoshop and was sent to employees as a pdf file, with all
information on a single page. Although it contained all the weekly news and social
events, some news took longer to publish; in those cases, the newsletter was
published every two weeks. This publication method wasn’t timely, and yet it was
time-consuming to prepare. With this as the main channel for communication, the
idea of intranet started to percolate. Replacing the newsletter with an online portal
meant the organization could encourage employee engagement by giving them the
tools to contribute content updates themselves. And, with an intranet in place, what
took weeks to gather, design, and publish could now be published in seconds.
INTRANET TEAM
Pictured: The SCTA intranet team (from left to right): Hossam Almujallai, Anas
Alsolai, Majed Alshedi, Abdullah Aljehani, Massar Almassar, Ali Abdulwahed,
Mohammed Almazrooa, and Waqas Chaudhry.
GOVERNANCE
Ownership
The intranet is managed by different departments within the organization, but mainly
by the Media department. The Information Technology department is responsible for
monitoring and maintenance and for supporting all technical and design issues. The
Human Resource department manages all employee operations on the site. All
departments manage their own related content and sections based on their job roles
and responsibilities.
USERS
The SCTA intranet is used by all of the organization’s employees, meaning everyone
can access content and post articles and replies. One of the team’s main goals for
the intranet was to allow all employees to engage at all levels as much as possible.
So, the team made most of the content open for all, with very few levels of
permissions.
Some parts of intranet are used only by specific employees because those areas are
tied to their job responsibilities. For example, all employees can change their job
profiles and their information on the intranet, but only one or two employees can
access all employee changes and approve those changes to actually update the
employee profiles.
ACCESS INFORMATION
Item Status
URL
On the SCTA internal network, users access the
intranet via http://intranet
Default Status
The intranet is the default homepage when
users open a web browser on their office
computers
Remote Access
Users can access the intranet remotely (outside
the network) using www.tawasol.gov.sa and
must enter their network username and
password to log in
Design Approach
SCTA partnered with several companies and organizations so it could study their
intranet designs and functional implementation. The SCTA team conducted site visits
TIMELINE
INTRANET TIMELINE
Milestone Date Milestone Description
September 25, 2010
Begin intranet business requirements analysis
October 17, 2010
Develop interface design requirements
November 20, 2010
Begin portal development
March 26, 2011
Complete interface design and portal
development
Begin usability testing
June 20, 2011
Launch
TECHNOLOGY
TECHNOLOGY
Category Technology Used
Web Server Hardware and
IIS 7.0 and Windows Server 2008 R2
O/S
HP Blades
Bug Tracking/Quality
SharePoint Trace Logs and the Unified
Assurance
Logging Service (ULS)
Design Tools
Adobe Photoshop
SharePoint Designer
Microsoft Expression
Site Building Tools
SharePoint Platform
Microsoft Visual Studio 2010, C#
Search
Microsoft FAST Search 2010
SEARCH
To ensure the best possible search results on the intranet, SCTA used a high-
performance search engine called SEEK. Using this engine, the team hopes users will
Pictured: The SEEK search engine in action. Users can search and find
information or articles across the intranet.
SITE USAGE
Overall Stats
Total number of visits
287,349 visits
Daily Averages
Average number of daily unique visitors
60 users
SUMMARY
With just three months to improve the site and move to SharePoint 2010, the
WorkSafeBC intranet team had its hands full. The WorkSafe Network (WSN) supports
3,000 staff throughout British Columbia. The organization works to support workers
throughout the province and keep worksites safe.
Armed with surveys telling them what employees wanted in an intranet—as well as
plans and ideas of their own—team members set out to give employees access to
information and a way to communicate with one another.
One of the site’s big wins was organizing content by topic or task, rather than by
organizational structure. This has made it much easier for employees to find the
information they need.
The site consists primarily of two main parts: corporate content and team sites.
Corporate content is the information of value to all employees, aimed at a broad
audience. Team sites can be used for groups, teams, or projects to help members
communicate and collaborate. They can be used for a finite amount of time, such as
during work on a project, or can be ongoing, such as for a team.
The homepage features news stories in a carousel at the top center of the page. The
carousel design does a nice job of letting employees see the headlines of all items,
rather than just giving them a next and previous control to move through content.
Employees are also invited to submit a story idea with a prominent link at the
bottom of the news headlines list. The team manages content centrally, which lets
team members gather and aggregate news and information from around the
organization.
Further news stories are highlighted below the carousel, and each headline is
accompanied by the date it was published as well as the number of comments
associated with the story. The site already has more than 5,000 comments on its
2,000 news stories, showing an active employee community.
Tabs give users quick access to other current information, including events, offers,
kudos (employee recognition), and blogs. A calendar of events, weather information
(important for employees traveling to work sites), and links to popular site areas
Pictured: The homepage collects all the latest information from across the site,
featuring news, blogs, events, and performance metrics.
The site is no longer organized by department, but now departments and teams have
their own pages—in the Our Organization area of the site navigation—to
The site’s strength lies in the many ways it provides opportunities to connect
employees to one another. Employees can give recognition to colleagues for work
Webcasts help keep employees who might be working in remote areas of British
Columbia informed and connected. Providing presentations as webcasts encourages
employees to watch and learn from events. Brief summaries explain what the video
The site offers content beyond the normal forms and policies. For instance, the
Health and Wellness area is a popular addition featuring information on staying
healthy—exercise, diet, ergonomics, and stress management. Users can also view
recorded Lunch and Learn sessions and information about Return to Work and
Employee and Family Assistance. Information includes both internal and external
events, such as the Vancouver Sun Run, a local road race.
Pictured: The Wellness Tracker helps employees manage their progress in the
in-house wellness challenge, encouraging employees to stay fit and healthy.
Little details like a Lost? icon help the site constantly improve. If users can’t find
what they are looking for, think content is in the wrong place or has the wrong
name, or need information updated or deleted, they can click the icon to open a
comment window. In this way, feedback is integrated into the design. The team also
takes such opportunities to do some recruiting: commenters are asked if they want
to take part in future user studies. This not only recruits users, but also informs
Pictured: The Lost? feature encourages feedback when employees have trouble
finding information on the site, and also acts as a method for recruiting users
for future usability research.
Challenges
Achieving the project goals and making the necessary changes weren’t always easy.
The team overcame several challenges during the WSN redesign, including:
Timeline: The first challenge was an extremely tight, non-negotiable
deadline to create the new design, bring it online, and make sure it
worked. That deadline was three months. “By comparison,” says
SharePoint Developer Chris Datcu, “a project of this size at most other
organizations would take six months.”
Limited resources: The limited timeline was further complicated by
resource constraints. “CIS didn’t have a separate team to assign the
project to,” says Kuzik. “We had to implement the upgrade ourselves,
on top of our existing workload.”
Every new content request the team received had to be formatted for
both the old system, which was still operating, and the new system, so
the content would be available when the new version came online. “We
also had to go back and mine two years’ worth of old content,” says
Trevor Seguin, Web Publisher, Corporate Internet Services, “all of
which had to be uploaded into the new WSN environment. This wasn’t
just cutting and pasting, either. We had to copy a thousand pages,
along with thousands of documents and document libraries, then
reformat the content and recreate all of the links. Some content could
be moved in batches, but there were a lot of pages that had to be
handled individually.”
Technology challenges: In addition to the daunting challenges of a
limited timeline and resource constraints, the team ran into some
technology issues as well. “There were also some issues with the
upgrade that didn’t become apparent to us until late in the project
because our intranet environment is unique,” says Kuzik. “CIS had to
work closely with Microsoft to resolve these problems.”
Ultimately, with the help of WorkSafeBC’s IT department and several
other supporting departments—and after putting in many long days—
the team succeeded in launching the new version of WSN on time.
Pictured: The WorkSafeBC intranet team (back row, left to right): Trevor
Seguin and Laine Dalby; (middle row, left to right): Chris Datcu, Lauralee
Kuzik, Sharleen Gairdner, David Lesjak, and Glenda Troup; (front row, left to
right): Joanna Gould and Terence Little.
GOVERNANCE
Ownership
The CIS team is part of the Marketing and Communications department, which lets
the team centralize all publishing and thus make changes quickly and easily, with a
focus on quality control. It also helps prevent content duplication.
“Our team’s ownership of WSN helps to prevent duplication of content and ensure
content adheres to our editorial style guide, brand, and is validated by our subject
matter experts,” says Kuzik.
Site and content responsibilities are shared across several groups: The CIS team
manages additions and updates to corporate content; the Business Technology
Support Services team (BTSS team) manages the creation of team sites; and team
site administrators manage team site content.
USERS
WSN supports approximately 3,000 full-time and temporary staff and contractors,
spread across the province of British Columbia, Canada. WorkSafeBC staff carry out
a variety of activities, such as helping workers file injury claims, conducting safety
inspections at worksites (ranging from urban restaurants to isolated logging camps),
and developing new tools and programs to support employers in their efforts to keep
their employees safe.
ACCESS INFORMATION
Item Status
URL
http://wsn/Pages/Default.aspx
Default Status
WSN is set as each user’s homepage, but it is
not bookmarked
Remote Access
Some staff can access WSN remotely (including
a select group of managers, some IT staff, and
others) using the organization’s VPN protocol
Shared Workstations
During some in-house training sessions,
workers will occasionally access WSN from shared
workstations in training rooms at the head office
and in regional offices. The head office’s
“Technology Hotspot” area is a walk-in support
center with shared terminals where staff can
access WSN and view some of the latest
technology products used at WorkSafeBC.
Design Approach
The first step in realizing the new design was to ask site users where they thought
improvements were needed.
“When we came to the conclusion that we would need to enhance the intranet, our
first step was to conduct a survey of WorkSafeBC staff to find out what they thought
WSN needed,” says Kuzik. “Nearly a third of our workforce—800 people—responded
to the survey, providing us with a number of suggestions. They requested everything
from blogs to a wiki, to the ability to comment on news stories. Over the years, staff
had also sent us feedback on their own. This gave us another list of suggestions,
challenges, and relevant issues to take into consideration.”
The CIS team created its own list of ideas for WSN enhancements as well. “These
came up during our regular team meetings, where we would discuss issues such as
how to fix web browser compatibility problems, or what kind of system we would
need to put in place to vet comments submitted to our news stories,” she says.
Some decisions about the site’s needs were made during the redesign’s early stages.
The team asked for input from staff and the management team about the proposed
architecture for WSN, and enlisted people from other departments to help with
usability testing.
PROJECT TIMELINE
Milestone Date Milestone Description
February 1999
Launched BoardNET, WorkSafeBC’s first
corporate intranet. BoardNET was an HTML-
based site designed for collaboration and
communication with support for WinNT 4.0 and
IE 3.0.
November 2004
BoardNet transitioned to The WorkSafe
Network (WSN), a redesigned site that was
implemented on SharePoint Portal Server
2003. The main reasons for the upgrade were:
o Improved content management
o Consistent organization
o Better look and feel
o Improved search function
o Improved integration to better reflect
WorkSafeBC’s new organizational
structure
o Ability to organize business processes
by tasks
o A simpler publishing process
The site’s new functionality included:
o Employee self-service
o Job postings
o Forms
o Office maps
o Calendar of events
o Cafeteria menu
o A “get answers” tool
o User alerts
January 2005–September
By this point, approximately 300 team sites
2009
had been created to share:
o Documents
o Procedures
o Tutorials
o Departmental material
SEARCH
The team chose to use SharePoint 2010’s out-of-the-box search functionality as a
simple and easy solution to its search needs. SharePoint’s search lets users search
by scope (WSN, team sites, people, or all internal and external websites) or to define
advanced search criteria and search by word, exact phrase, language, type of
document, and properties.
Pictured: One of the organization’s performance indicator graphs from the WSN
homepage, where users can find several graphs that track different
performance areas.
LESSONS LEARNED
Chris Datcu, the organization’s SharePoint consultant, shares some of the lessons
the team learned during the project. “Over the years, our experiences redesigning
WSN have reinforced a number of lessons that are helpful to keep in mind:” These
lessons include:
Gather feedback early. “Follow a design workflow where you get
early feedback and approval from the clients/SMEs, so you know what
features are needed and what the priorities are.”
Put usability first. “Always evaluate the usability of the intranet
during the design phase. Get typical users from the organization to
test different functions to make sure all parts are self-explanatory,
easy to use, and easy to find.”
Plan your migration in detail. “Do a proper analysis of your old and
new intranet platforms so you don’t run into integration problems
when migrating from one platform to another.”
Using the intranet: The International Monetary Design team: The IMF intranet was designed by
Fund (IMF) is an organization of 188 member consulting firm Threespot in close collaboration with
countries working to foster global monetary the IMF project team, comprising members from the
cooperation, secure financial stability, facilitate Technology and General Services (TGS) Department
international trade, promote high employment and the Communications Department’s Internal
and sustainable economic growth, and reduce Communications team.
poverty around the world.
In-house members: Archana Kumar, former
Headquarters: Washington, D.C. Internal Communications Chief; Camilla Andersen,
current Internal Communications Chief; Deb Reilly,
Number of employees the intranet supports: Chief of Information and Knowledge Management
Approximately 5,000 Division; Hari Maddineni, Chief of SharePoint Intranet
Company locations: IMF has offices in more Section; Begoña Nuñez Allue, Communications
Officer; Hélène Faurès, IT Project Manager; Sonia
than 100 countries.
Dwyer, Enterprise Information Architect; Rajitha
Locations where people use the intranet: US Devineni, Business Analyst; Graham Dwyer, Senior
headquarters, as well as offices and travelling Communications Officer; Aissata Sidibe,
staff in 188 member countries. Communications Assistant; Padraic Hughes, Chief of
Media Services Section; Scott Merker, Designer; Vera
Rhoads, User Experience Specialist; Shishir Bhandari,
Technical Lead; Joshua Sampson, Solutions Architect;
Vijay Challa, SharePoint Architect
SUMMARY
Even well-designed intranets stay that way only when there is a plan in place for use
and growth. That’s what the International Monetary Fund (IMF) discovered as its
intranet grew and expanded over time. The organization found itself in need of a
makeover to incorporate new technologies, update a now-dated design, and
generally clean up the clutter that can creep onto any intranet site.
A lesson learned from the previous project was that the need for intranet governance
is critical to an intranet’s success. Sites cannot maintain themselves. Growth can
quickly get out of hand. That’s why a key part of the IMF’s redesign was to create an
intranet governance structure to plan for and maintain future growth.
Previously, there was no central ownership of the site or overall strategy for
maintenance. Responsibility was shared, with the Communications Department
(COM) taking care of the homepage and news, IT controlling the technology, and
departments and other groups managing their own sites.
The team created the Intranet Council, consisting of nine members from different
departments representing all the departments at the IMF. The Council’s work started
when the redesign was finished: its job is to sustain the gains made in the redesign
by developing and enforcing guidelines and standards, and managing the growth of
the site.
The team worked with Threespot (a digital agency) to do initial user research, create
wireframes and designs, write functional specifications, and create the governance
framework. The project used a variety of user research methods to make sure the
Categories are clear and distinct. The user’s current location, Services &
Resources, is indicated by a thick blue underline.
The About Us and Collaboration landing pages include a Yammer feed. Yammer is
integrated throughout the site as a way to actively engage employees in
conversation. Integrating social content in the main site, rather than requiring users
to go to a separate tool to communicate with one another, is a great way to
encourage participation. The Yammer feeds show current conversations as a way to
keep people connected to one another.
There are 208 Yammer groups at IMF, with Yammer web parts that allow both
reading and posting integrated into team sites. When new team sites are created,
the intranet team encourages the team to create a Yammer group and include a feed
on the site. Feeds can be created based on groups, company, an individual, or even
a keyword.
Although some employees started using Yammer, its use is not yet widespread
within the organization. The intranet team is currently planning to do a campaign
around the use of Yammer and other social tools and features to further increase
engagement, communication, and collaboration.
The site contains a lot of video content, but the previous design lacked a central
location for it, which caused many user complaints. The site’s videos now have a
Departments have their own sites and content, but the sites are integrated into the
main intranet’s structure. Each department has its own header, but follows a similar
Department pages have their own header, but follow the intranet’s general
structure. Each departmental site has a persistent link to the main intranet
homepage, Intranet Home, on the left side of the top site navigation.
The team realized that, in creating the new site, change leadership was essential and
it worked closely with stakeholders and departments to keep them informed and
involved. One big change was for content owners, who were used to having a
dedicated space on the previously crowded homepage. Communicating a new plan
Goals
The project’s overarching goals were threefold:
• Deliver a user-focused design to meet the business needs of IMF staff
• Make the intranet not only a useful tool for staff, but also an engaging
place where people would come to get information and share views
• Bring the intranet in line with current intranet best practices and
technologies
Specifically, the organization wanted to achieve several tactical improvements with
the new intranet:
• A less cluttered and more organized homepage
• Easy access to resources that employees need for their daily work
(based on their own preferences)
• A sound IA and clear visual hierarchy
• Uniform branding across the intranet so users would have a consistent
browsing experience
• Modern intranet features to provide personalization, increase staff
participation, and improve information findability
• A governance structure to ensure that the intranet will continue to
grow and be maintained in a controlled and sustainable way with
future growth in mind
Challenges
Every project has its challenges, and the IMF’s intranet redesign is no different. The
organization struggled with basic project challenges related to timeline and
technology, but also experienced some organizational challenges as they had to
convince content owners and stakeholders that some content house cleaning would
The intranet team (left to right): Camilla Andersen, Graham Dwyer, Begoña
Nuñez Allue, Hari Maddineni, Aissata Sidibe, Hélène Faurès, Jamie Colucci
(Threespot), Rajitha Devineni, Joshua Sampson, Deb Reilly, Shishir Bhandari,
Phil Gosier (Threespot), Vijay Challa, Scott Merker, Hallie Wilfert (Threespot),
and Archana Kumar. Missing from photo: Sonia Dwyer, Padraic Hughes, Vera
Rhoads, Anna Rappoport (Threespot), James Early (Threespot), and Paul
Zolandz (Threespot).
GOVERNANCE
Ownership
Prior to the redesign, the IMF intranet had no clear owner. Various stakeholders
owned (or controlled) different parts of the site, with COM at the forefront controlling
the main areas of the homepage as well as the news and notices pages, and the IT
department controlling all the technology, software, and applications software, as
well as the IA and search engine and interface.
“Other departments or groups requested to have their content posted in various
spaces on an as-needed (often as-demanded!) basis,” says Begoña Nuñez Allue,
Communications Officer, “which is why the homepage had grown in a rather chaotic
way.”
In addition, each individual department managed its own websites within the
intranet. “This decentralized approach lacked cohesiveness and communication
among the parties,” she says. “In particular, it lacked a group or a body that would
The Intranet Council was formed to coincide with the launch of the new intranet, so it
did not influence the project. “But we hope it [The Council] will help us keep our new
intranet tidy and up-to-date and ensure that it continues to meet the evolving needs
of our users,” says Faurès.
USERS
All IMF staff members use the intranet, and it is set as the default homepage on all
IMF computer browsers (although staff members can change this). The intranet is
the key communication vehicle for conveying important information to all staff.
Some common uses of the intranet include:
• Read IMF-related news and notices, and learn about events
ACCESS INFORMATION
Item Status
URL
• http://www-
intranet.imf.org/Pages/IntranetHome.aspx
Default Status
• The intranet is set as the default homepage on
all staff members’ computers, but they can change
the default.
Remote Access
• Many IMF staff members work and access the
intranet remotely on a regular basis. Remote
access is provided through Windows Terminal
Server (Citrix) from any computer or through SSL-
VPN from IMF computers.
• The organization is currently working to give
iPad users access to mobile-friendly intranet pages
and applications.
Design Approach
There were certain aspects of the intranet design that the team knew had to be
addressed—urgently—such as updating the look and feel, and decluttering the
homepage. However, in order to gain in-depth knowledge of what other areas had to
be targeted and what the project goals should be, the team did a lot of research in
the project’s early stages.
An early survey, conducted by IMF’s partner, Threespot, was aimed at finding out
the staff’s preferences for the intranet: what they liked about it and what they didn’t,
what they would like to have on the new site, and so on.
The survey received what Nuñez calls “an incredible response,” with more than 36%
staff participation. “It allowed us to collect a vast amount of data from employees
INTRANET TIMELINE
Milestone Date Milestone Description
1996
• First IMF intranet
December 2011
• Redesign project kick-off
January 2012
• User needs analysis complete
April 2012
• Wireframes complete
July 2012
• Usability testing
July 2012
• Outreach: presentation of designs to all IMF
staff, intranet news article, presentation of
designs to stakeholders
August 2012
• Designs final
November 2012
• Functional specifications complete
December 2012
• Technical specifications complete
January 2013
• Start of development activities, including:
o Develop/implement new designs for 11
pages provided by Threespot.
o Apply new branding and styles to the
rest of the 200+ pages in the homepage
site collection.
o SharePoint 2010 upgrade of the
homepage site collection (remediation
activities of components that were
broken after the visual upgrade).
April 2013
• Start of quality assurance (QA) testing
May 2013
• New intranet ready for user acceptance testing
June 2013
• Launch of new design
TECHNOLOGY
On the technology front, the organization recently upgraded from SharePoint 2007 to
2010. SharePoint 2010 came with new social features such as tagging, which the
organization will rollout and promote in the near future.
MOBILE
IMF staff members can access an anonymous (no authentication necessary) mobile-
friendly intranet site from their Blackberry devices. The mobile site includes intranet
news, notices, events, a Communication Toolkit, people search, and resources for
working remotely. In addition, three departments currently have a mobile-friendly
version of their departmental page.
The Blackberry-only approach was not intended to be the mobile endgame. “When
we started working on the intranet redesign, our intent was to implement a
responsive design using HTML5 and CSS3,” says Faurès. “However, we had to give
up due to incompatibilities between Internet Explorer 9 and SharePoint 2010.
Therefore, the team is currently at work on a custom intranet site for iPad users,
with a target launch date of spring 2014.”
At that time, the team will most likely retire the Blackberry site.
This iPad-friendly version of the intranet will provide more available content as new
iPad-friendly intranet sites and applications are launched. The first iPad-friendly
application to go live will be eReview, a workflow application used to review and clear
documents.
The jump from Blackberry to tablet devices makes sense as interest and usage of
tablet devices has increased among the organization’s business clients. The IMF
made the decision to support iPad devices a few years ago, and it now supports
approximately 1,700 (IMF-provided) iPads and 500 personal iPads, and expects to
add 1,000 more in coming months. With so many staff on-the-go and increasing
demand, a decision was made recently to give every professional staff member an
iPad, doubling the number of iPads in use across the organization. There is also
SEARCH
The IMF chose FAST Search for SharePoint 2010 for its intranet because it is rated as
a top-tier search engine and is designed for the SharePoint platform. The decision to
use FAST was made after reviewing other highly rated enterprise search engines.
“We know that no enterprise search engine is a ‘set-it-and-forget-it’ tool,” says Sonia
Dwyer, Enterprise Information Architect. “They all need to be configured to match
the content being searched in the organization.”
To address these required configurations, Dwyer explains the customizations the IMF
team has made to FAST:
• Search scopes: Enterprise search guides users to different content
sources through the following defined scopes, which are presented as
filters above the search box on all intranet pages:
o All Sources searches across all content sources below
o Intranet searches on intranet content
o IMF.org searches on IMF public site
o People searches on SharePoint My Sites
o KE Documents searches on Knowledge Exchange Documents (a
collection of selected country reports, research papers and IMF
publications)
• Content sources and prioritization: “Content sources are treated
and weighed equally by the search engine,” says Dwyer, adding that
the search engine does not prioritize content sources differently. Role-
based, or “user-context,” search is planned for the next year.
• Crawl rules: “We have in total about 42 different rules for content
inclusion and exclusion to make searches more accurate and exclude
‘noise’ from SharePoint items,” Dwyer says. “Crawl rules are updated
as needed.”
• Custom metadata/managed properties: “We have in total about
62 configured SharePoint managed properties for all content sources
to improve search results and content retrieval,” Dwyer says.
“Managed properties are also used for Advanced Search to ensure that
users are searching IMF metadata fields for very specific searches.
Every time a new content source is added, we need to map the
crawled properties to managed properties.”
• Relevance tuning: “FAST Search Server 2010 for SharePoint
provides flexibility for tuning relevance in several ways,” she says.
“Relevance is not absolute and perceived relevance differs greatly
among users. As part of the longer term intranet renewal, we are in
the process of centralizing and elevating key information on the
intranet in parallel with efforts to ‘upskill’ staff on content management
best practices.”
SUMMARY
Understanding the true work that employees do and giving them the freedom and tools to
do it is the backbone of the Saudi Food & Drug Authority’s intranet. The designers of
“Bawabaty” ( ) ﺑﻮاﺑﺘﻲwhich means “my portal” in Arabic, made the intranet highly
customizable. The team considered the needs of the 2,000 people in 32 different branches
that the intranet supports. These users — including administrators, content authors who
have permissions to write only, content authors who can write as well as approve content,
and end users — have varied requests and desires. Thus, designers made 70% of the
homepage customizable via widgets. In this area, employees may move, add, or remove
widgets as they desire.
Moving widgets is simple by clicking the move (cross) icon in the upper left corner of the
widget, then just dragging and dropping it to the position in which they want it to appear.
The icon looks like the oft-used move symbol, which makes it easy to decipher. As a widget
is dragged, a transparent version of it is displayed to make the action obvious. Once
dropped, the widget falls into its new position, and the widget that held the position
automatically moves out of the way and down to the next slot on the page.
Common barriers to customizing pages on intranets include:
• Discovering it’s not possible to customize
• Not finding the method to customize
• A complex UI that’s hard to use and gives little feedback when trying
But none of these issues are present on Bawabaty. On the contrary, this interface makes it
easy for employees to test and investigate layout options for the homepage that best suit
their needs.
To remove a widget, users click the X icon in the upper left of the widget. Employees are
asked to confirm widget removal, which is a nice safety feature to help prevent errors.
People may add widgets easily via the yellow icon in the far upper left corner of the
homepage. Clicking it opens categories of widgets the users may select from.
Besides the “non-fixed widgets” that employees may choose to use, designers created “fixed
widgets” as well. These comprise the most important content that everyone needs, like
news, announcements, and all internal services. The page is arranged in sections with
borders and backgrounds so users may easily scan for the information they are looking for.
Image 6. SFDA Intranet: Fixed Widgets. The sections (widgets) in the top part of
the homepage are not moveable, evident by their lack of the move icon.
58_SFDA_06_home_live.png
Image 7. SFDA Intranet: e-library Widgets. The e-library on the SFDA intranet
houses shared folders and a document library. 59_SFDA_07_eLibrary_live.png
Widgets that are less work related are also available, such as Special Offers. Employees may
sort the offers using filters on the right.
Other non-work related tools on Bawabaty are weather and prayer time. These appear as
shortcuts in the upper left of pages, in the topmost blue bar. In this same area, users may
also change their location to display information related to that location.
Designers made it easy to get started when browsing using the menus by offering only three
top-level navigation choices: Home, My Services, and e-Library. These appear in the right-
most part of the blue horizontal bar second from top of page. The site’s search is in the far
left of the same blue bar.
Bawabaty keeps employees updated in a number of ways. For example, users may see news
items in the news list, and filter those items.
Image 11. SFDA Intranet: Notifications Center Emails. Hovering over the first
icon, the envelope, in the Notification Center displays a list of the most recent unread
emails, including the sender and subject. 63_SFDA_11_NotificationCenter_live.png
Image 13. SFDA Intranet: Notifications Center Notebook. Hovering over the
third icon, the notebook, in the Notification Center displays a list of tasks to do.
65_SFDA_13_NotificationCenter_live.png
The Photo Gallery is a visual way to stay abreast of happenings at the organization.
Employees may also learn about one another through their profile pages, which collate and
display the latest information from various systems (e.g., Human Resources). Employees
may search for each other via the Employee Directory widget by various criteria, such as
first name, last name, phone number, or email address — and they can do so in either
Arabic or English.
Image 16. SFDA Intranet: Employee Profile. The Employee Profile page on the
SFDA intranet combines the most current information from various sources.
68_SFDA_16_employeeDirectory_live.png
To locate other information, users may search Bawabaty via the search field in the far left of
the global navigation bar. The results page displays a clear title for each result, a short
Image 17. SFDA Intranet: Search Results. Search results on the SFDA intranet
display a title, description, link and icons. Filters on the left allow users to refine the
results. 69_SFDA_17_Search_live.png
Flexibility and function are uniquely combined in this intranet. Employees may work the way
they choose to, while being highly supported by this solid design.
BACKGROUND
When SFDA was established ten years ago, it created an intranet that helped employees
complete their daily tasks. This early intranet included a document center, news, and a few
services. At that time the intranet was serving approximately 200 employees and its
offerings were sufficient.
Recently, however, the SFDA expanded its number of branches and services, and the
employee count has grown significantly. The organization now has more than 2,000
employees distributed across 30 branch locations across many cities in the Kingdom of
Saudi Arabia. As a result of this expansion, the intranet had become crowded with many
links, documents, and services, none of which were organized. It had become difficult for
employees to access the information they needed and the search function was not returning
useful results.
Top management decided it was time to improve the intranet, to keep it in pace with the
organization’s expansion.
Image 19. SFDA Intranet: Old Homepage. The old SFDA intranet homepage as it
looked before the redesign. 71_SFDA_19_oldIntranetHomePage_old.png
SFDA project team members and management (top row, left to right): Falah AL-
Mutairi, Faisal Alturaif, Bander Al-Johani, (bottom row, left to right) Mohammed
AlMutairi, Abdulaziz Al-Fakhri, Fahad Alquait, Fahad Alanezi, and Abdulaziz Alsughyyer.
USERS
The intranet is integrated with Active Directory. Since every employee exists in Active
Directory, every user can access Bawabaty according to his group and department
permissions. Each group and department has private content, which is kept from those
outside the group. The publishing team can target content for specific groups.
ACCESS INFORMATION
Item Status
URL • http://bawabaty
• The same URL is used for both desktop and
mobile devices since the intranet uses a
responsive design.
Default Status • Users choose whether or not to bookmark the
site. It is not required as a user’s homepage.
Remote Access • Users can access Bawabaty remotely via VPN.
Design Approach
When the SFDA management team decided to create a real intranet portal to replace the old
intranet, they assigned a project team and gave them their full support. They also defined
the project goals as follows:
• Help employees do their work and improve productivity
• Help employees find content quickly and easily and improve usability
• Ensure information is accurate and up-to-date
• Provide efficient access to content and tools
• Create a consistent user experience
• Create a consistent look and feel
• Align intranet content with business workflows
• Facilitate collaboration across groups and departments
• Empower content providers to manage their own information
• Follow intranet standards
• Create better categorization
• Promote best practices across the site(s)
• Eliminate wasted clicks
• Create tools that are easier to learn and use
• Enhance knowledge sharing
The key to achieving this comprehensive list of goals was to do a lot of research and find
ways to gather feedback from users. To that end, the following activities were conducted:
PROJECT MILESTONES
Milestone Date Milestone Description
January 2007 • Launch of first SFDA intranet
August 2013 • Create vision document and requirements
analysis, conduct usability studies to inform
design of new intranet
October 2013 • Project begins
December 2013 • Design phase
February 2014 • Implementation
March 2014 • Deployment
May 2014 • Develop content
June 2014 • Launch and go live for new intranet
TECHNOLOGY
TECHNOLOGY
Category Technology Used
Web Server Hardware and OS • Five servers (see hardware architecture
diagram below)
• Windows Server 2012 Standard
Bug Tracking and Quality • Team Foundation Server (TFS) quality
Assurance assurance
Design Tools • Photoshop
• Dreamweaver
Site Building Tools • Visual Studio 2012
• SQL Server 2012
• SharePoint Designer 2012
Content Management Tools • SharePoint 2013
Search • SharePoint 2013 Search (embedded FAST
Search)
SFDA-INTRAWFE1 SFDA-INTRAWFE2
SFDA-INTRADB1 SFDA-INTRADB1
SFDA-INTRAOWA1
1 TB SAN
Image 24. SFDA Intranet: Server Architecture. This diagram shows the hardware
architecture design of the SFDA intranet. The site relies on two servers for the web
front and indexing services. A SharePoint farm (with NLB) configuration was
implemented to provide highly available services. Microsoft SQL 2012 servers are
connected to SAN storage and used to host the database. Windows Server 2012
Standard edition (clustering) technology is configured for SQL that provides the
services with redundancy and continuity in case of failure.
76_SFDA_24_hardware_architecture_diagram.png
MOBILE
The SFDA team chose to employ a responsive design to lower their development efforts and
administration overhead, and to provide a unified user experience regardless of how users
access the site.
The fixed widgets are the only widgets available on mobile devices, since they comprise the
most important part of the intranet, and employees don’t need non-fixed widgets when out
of the office. All other site features (besides non-fixed widgets) are available.
Users can access Bawabaty from their mobile devices, only through VPN.
SEARCH
One of the reasons the team chose SharePoint 2013 as the intranet platform is because of
the powerful search engine it provided. “We adapted this out-of-the-box search engine and
it has provided the intranet with rich search features such as content categorization and
filtering, indexing, a friendly relationship with Microsoft Office web apps, support for Arabic
language content, as well as great search results, that can be displayed based on content
permissions,” says project manager Mohammed AlMutairi.
LESSONS LEARNED
The SFDA team shares a few lessons learned:
• Share the vision and goals with team and stakeholders.
• Communicate with stakeholders early.
• Get support from senior management for content development and integration
purposes.
• Invest in user experience design. A successful design leads to intranet
success.
• Make sure the site serves user needs. Employees will be interested in visiting
the intranet frequently if information is helpful and tools aid productivity.
COMPANY TEAM
The Swedish Parliament Design team: The core in-house team consisted of
three people, with a further 10–12 project members
Headquarters: Stockholm, Sweden who changed over time depending on the project
Company locations: Stockholm, Sweden phase and the work being done. The internal team
worked mainly with the digital agency Creuna and
Locations where the intranet is used: Mainly in together they formed a big project team. The
Stockholm, Sweden, but also when members communications agency Futurniture had a smaller
travel or are in their hometowns. role in the project.
Annual sales: N/A Project sponsor: Karin Hedman, Head Of
Information Department and Intranet System Owner
Intranet team members shown here (back row): Janna Palmgren and Anna Elding;
(middle row): Angelina Fredriksson, Karin Hedman, Paul Lernmark, Katja
Engelhart, Ingeborg Granlund, and Lars Gustavson; (front row): Birgitta Elgemyr,
Jessica Stringer Bodin, Katarina Willstedt, and Åse Karlsen.
Goals
The goal of the redesign was to create a usable and accessible intranet that would transform
the existing information-heavy site into an intranet that could serve as a practical tool for its
users, as well as:
• Be an effective tool for both users and content contributors
• Promote cooperation and a sense of belonging
Challenges
The design team was fortunate to have an adequate budget and timeline for the project
(one year), but it faced many challenges working with the content for the new site. “We
started working on the content too late,” says Stringer Bodin, “or rather, this work didn’t get
going fast enough even though we started early.”
The redesign required wholesale changes to the content. Everything had to be rewritten and
edited to fit the new design and accommodate the requirements of the new templates in the
CMS. Stringer Bodin explains some of the other challenges the team faced, such as how to:
• Emphasize relevance. “Create an intranet in which all the target groups
perceived it as relevant to just them.”
• Change the content to match the new concept. “It takes time to learn to
think in new ways!”
• Get all the target groups involved. “It was particularly important to
involved the MPs, so that the project could monitor whether we were headed
in the right direction and test proposed solutions.”
• Gain support and acceptance internally. “We were doing something that
was very modern and different compared with the previous version of the
intranet, but also compared with other systems and digital services.”
• Support mobile devices. “It turned out that the project came about just at
the right time and there was a secure solution for mobile devises at the time
of the launch.”
Homepage
Image 2.
Swedish Parliament Intranet: The New
Homepage. 147_Swedish-
parliament_02_home_live.png
Image 6.
Swedish Parliament Intranet:
Content Page (Plain Swedish Information).
151_Swedish-parliament_06_plain-swedish-
page_live.png
Image 1.
Swedish Parliament
Intranet: Chamber
Calendar. 152_Swedish-
parliament_07_chamber-
calendar_live.png
Image 1.
Swedish Parliament Intranet:
People Directory.
153_Swedish_parliament_08_people-
directory_live.png
Image 2.
Swedish Parliament Intranet:
Global Search. 154_Swedish-
parliament_09_global-
search_live.png
Image 3.
Swedish Parliament Intranet:
Mobile View of the Homepage.
155_Swedish-
parliament_10_mobile-
home_live.png
A visualization of the target groups and their needs for the Swedish Parliament
intranet.
When the redesign project kicked off, the first thing the in-house project team did was to
inventory all the pages and functionality available on the existing (old) intranet. For each
function and page, team members analyzed the metrics from the previous year (2012). This
analysis showed which functions were most used, which were trending and which were not
used at all. This information let the team prioritize the most important functionality and gain
a holistic view of the content.
Prioritizing Needs
Prioritizing the initial tasks wasn’t difficult. With all the research material they had in hand,
team members knew a lot about the top tasks they wanted to focus on, and which were less
important and could be given lower (if any) priority in the new design. They also wanted to
liaise with content owners to ensure that the new intranet would have the right content and
functionality to meet user needs.
One critical need emerged early on: users wanted intranet access on their mobile devices
and from locations outside the Riksdag, rather than only on their computers at work. This
need was especially important for MPs, who are often on the move.
Comprehensive Surveys
The Swedish Parliament partnered with Creuna, a full-service digital agency, for the
redesign effort. When the Swedish Parliament Administration kicked-off the project, it asked
Creuna to conduct a survey to evaluate the organizational needs that the new intranet
would have to meet. Team members explain how the survey was carried out:
• In-depth interviews: “We conducted in-depth interviews with
representatives of the different target groups. We realized quite quickly that it
would be a relatively extensive study as the operations are complex and the
conditions of the target groups completely different. The Swedish Parliament
(like many other organizations in the Swedish public sector) has a good
understanding of the need to meet the needs of users in various digital
channels, and it was important to carry out thorough groundwork. The in-
house team also understood the importance of achieving broad support within
the organization, and this was something an extensive interview study could
also contribute to.” (Katja Engelhart, UX Lead)
• Extensive preparations: “Before Creuna could even start writing the
interview guides, they were given training about the work of the Swedish
Parliament, including plenty of background reading and a number of
preparatory discussions with key persons in different parts of the
organization. It was important that we understood the operations and
processes in order to be able to ask the right questions.” (Birgitta Elgemyr,
Web Editor)
“The Swedish Parliament uses a number of technical terms and concepts;
there are many traditions and routines. The training we were offered made us
better prepared to lead the interviews and gave us a good basic
understanding of part of the task ahead of explaining and clarifying on the
intranet. If this was complicated for us, it would naturally also be difficult for
new employees and MPs.” (Engelhart)
Examples of the design elements used for information and basic functionality on the
intranet.
ACCESS INFORMATION
Item Status
URL
• http://intranatet.riksdagen.se/
Default Status
• Users with older operating systems have the
intranet as the homepage in their browsers,
and the intranet automatically starts when the
computer is switched on. The organization
would prefer the intranet to be the default
homepage for all users, but most people have
Windows 8, in which the intranet is not the
homepage and auto start is not possible.
Windows 8 users have an intranet shortcut in
the taskbar.
Remote Access
• Users can access the intranet remotely via VPN
on all devices that Riksdag provides (but not
BYOD). Most users’ work equipment includes a
laptop and an iPhone; some also have an iPad.
Users that are often on the go (such as MPs)
use the site remotely, as do officials working
from home or in other places.
Note: There has been a noticeable increase in
traffic to the intranet from mobile devices since
the redesign launched. In the first month,
mobile traffic increased 4%; as of this writing,
the increase is now almost 15%.
PROJECT MILESTONES
Milestone Date Milestone Description
1998
• First intranet implementation in Lotus Notes
2000–2007 Previous redesigns:
• 2000: Lotus Notes update: New homepage
• 2005: Lotus Notes update: New homepage;
users could choose between different
presentation options
• 2007 redesign: First web-based intranet, with
a greater user focus
2011–May 2012
• Preliminary study for new and redesigned
intranet
November 2012
• Start of new intranet project
March 2014
• Launch of the new redesigned intranet
Post-Launch Following its launch, the team continued its efforts to
improve the new intranet. Some improvements had
been given lower priority during the project, yet still
needed to be addressed. Other parts were shown to
need improvement during usability tests (conducted
after the launch). Among the post-launch activities
aimed at addressing these various needs included:
• May 2014: Post-launch usability tests
• June 2014: Homepage is redesigned with
improved calendar and intro blocks at top of
page
• November 2014: “I want to...” feature
redesigned
Overall redesign time frame: 17 months (not including preliminary study and
post-launch work)
Contributors
Content can be generated from contributors across all parts of the Swedish Parliament. For
example, the MPs are mainly users, but the party secretariats sometimes provide input to
the calendar.
The intranet has two specific content contributor groups:
• Content owners: All managers at the Swedish Parliament Administration
who have content on the intranet are responsible for its accuracy and are
considered content owners.
• Appointed contacts: Contacts in the administration are appointed by
content owners to manage content. The contacts can initialize changes, as
they know what’s going on in their field of expertise and can answer questions
coming in from the organization. Approximately 35 appointed contacts exist in
the organization and report to the content owners.
Contribution
Content ideas are generated through many channels across the organization:
• Brainstorming: The intranet team encourages the contacts in the intranet
network to come up with ideas for improvements and news of interest to large
user groups or a specific organizational group.
• Intranet inbox: Anyone with access to the intranet can also email the
intranet inbox, which is monitored during office hours.
• Calendar: The calendar for internal groups and networks in the Swedish
Parliament is widely used and has many contributors. Anyone can send in
suggestions for new calendar items via an intranet form.
• Feedback links: Content ideas are also generated through the “Was this
information of help to you?” function. This often includes content that users
would like to see or suggestions for improvements to content.
• Intranet network: Seventeen of the appointed contacts and content owners
are representatives in the intranet network group. This group was formed to
help the team improve the intranet over time.
Training
Four web editors work on the intranet; one of them is responsible for training new contacts
and content owners. A contact person and content owner should understand the intranet’s
purpose and goals, its overarching concept, and what is required.
The team provides a 1–2 hour training session for content owners and contacts. Very few
content contacts are allowed to publish on the intranet; those who are get an additional 2–3
hours of CMS training as well. If there are new contacts that need to learn how to publish,
the team provides one-to-one training and teaches them exactly what they have to learn to
process their content. The number of appointed publishers is deliberately kept low to help
maintain high-quality content, consistency, and usability.
Content Guidelines
The team monitors developments related to usability and accessibility on an ongoing basis,
and follows the findings of the NN/g surveys, as well as those of GDS in England.
Headings
Headings should be short and pithy; use introductions/extracts to clarify or go into greater
depth.
Guideline no. 105, Priority 1: Create headings with heading elements
• Headings should be real headings, not just captions. For example, it
doesn’t work to write “Seminar in the Riksdag” as a heading. Instead try to
write what the seminar is about: “Seminar on men’s violence against women.”
• A heading should be active. This means that there should be a subject that
is doing/thinking/planning something. Write “The Riksdag debates the budget
bill,” rather than “The budget bill is debated in the Riksdag.” Think about
writing headings in the present tense as a rule.
• Aim to write headings that are as short as possible when you write for
the intranet. The goal should be to write headings of no more than one line,
even on the latest news page.
• Think about the message in the heading, so that the heading and extract
text don’t have two different messages.
• Try, if possible, to highlight something interesting. Think about how to
get the user to want to read more. Include interesting details.
Culling Content
From the very start of the project, the new site’s content and content quality was a priority.
The team had to decide what to keep, what to leave behind, and how to handle content they
decided was important enough to include on the new site. “We worked on the basis of the
concept and list of priorities that we drew up at an early stage of the project,” says Web
Editor Birgitta Elgemyr. This laser focus on content planning paid off: the new site provides
users with a better, more cohesive experience.
“We went from having a disjointed intranet to a coherent one,” she says. “Earlier it was
important to have shorter pages, but with the redesign we wanted to keep the content
within each subject together in a completely new way.”
Making quality content a focus of the new site design meant the team had to find effective
ways to uncover gems in the rough.
“When we met the content owners during the project, many of them hadn’t looked at the
content on the old intranet for a long time,” says Web Editor Katarina Willstedt. “When we
worked together on the content, we discovered that many things were no longer relevant
and didn’t fit the new concept or objectives for the new intranet.
“We also didn’t want it [the new site] to be a storage space for old material ‘that may be
useful some time’ or offer the same services as other channels,” she says.
So, if content didn’t really have a target group, the team simply got rid of it. There was no
longer room for text that merely filled empty space.
“We were forced to rethink and remove material that was no longer used,” says Willstedt.
Not everything was published before launch, as the team decided to port the low-priority
content later. That content proved to be that last box you find in the basement six months
TECHNOLOGY
TECHNOLOGY
Category Technology Used
Web Server Hardware and
• Windows servers
Operating System
Bug Tracking/Quality
• Redmine
Assurance
• nUnit för automatiserade tester
Design Tools
• Adobe Photoshop
• Axure
• Paper, Post-Its, white boards
Site Building Tools
• Visual Studio
• ReSharper
• Grunt
Content Management Tools
• EPiServer CMS 7
• SharePoint 2013 (calendar and user
profiles)
Search
• Apache Solr
Version Control
• Subversion
Build Server
• TeamCity
Front-End Framework
• Twitter bootstrap
At the beginning of the project, the team evaluated three different platforms: EPiServer
CMS, SharePoint 2013, and WordPress. During the evaluation, team members examined
The team also reviewed specific functions that it had identified as important — such as text
and image management — and evaluated operational and licensing costs. Ultimately, the
team chose EPiServer CMS for content management and SharePoint for specific functions,
such as handling editorial calendars.
Defining Success
The Swedish Parliament had many goals for the new intranet, but above all, the intranet
had to be effective in helping users carry out common tasks. Specifically, the new site had
to make it easy for users to:
• Find people
• Find the information they need
• Understand all information on the intranet
• Follow what’s happening at their workplace
With these goals in mind, the team conducted user tests before and after the launch and
also asked users about their overall experience with the intranet to gauge its success.
In the test conducted before the launch, the team uncovered a list of things
to improve on the intranet, including changes to the UI and editorial content
(especially micro content). The results for these items in the post-launch test
were much better. It was easy for users to find people by the work they
performed, and all test participants successfully finished the test tasks. The
team also tested the information structure with satisfying results. For
example, the name of the “I want to…” (Jag vill…) section was perceived as
an odd choice at first, but users also liked that it was different from other
section names and easily remembered.
The tests also showed that mobile use of the intranet is rising steadily. “We can also see
which functions are used the most, and that what we need to work further with and refine,”
says Stringer Bodin. Another interesting finding was that the top tasks on the new intranet
do not differ significantly from those on the old one. The big difference, of course, is that
these top tasks have been simplified so that they are easier for users to perform.
This shows the KPI framework used by the organization. KPIs are described on the left;
indicators that can be measured are in the middle; and the right column shows the
measurement method. Everything that is measured relates to the impact objectives.
Swedish-parliament_36_KPI.png
A few key metrics and their visualizations on an Excel sheet. Note: It appears that
everything is going sharply downward, but most people are on holiday in July, which
accounts for a natural dip in intranet usage and feedback.
LESSONS LEARNED
Members of the Swedish Parliament team and its design partners share lessons learned
from the project:
Process
• Educate external partners as thoroughly as possible. “We decided to
concentrate on carrying out an extensive pre-study in several steps and
consisting of several components, and to teach our partners about the
organization and the internal processes. We benefited greatly from having
done this during the rest of the project.” (Karin Hedman, Head of Information
Department/Intranet System Owner)
• If you hire consultants, keep them close to the process. “The Swedish
Parliament is an organization with complex operations, and participating in
the survey of needs would have helped me to gain a deeper understanding of
work procedures, conditions, etc. I was lucky enough to work with one of the
long-time web editors and that was critical for my understanding the
operations of the organization and the intranet. It is important to have
someone who knows how the organization works and can explain things when
you’re a consultant. It’s been positive that we have worked in such close
cooperation with the clients; we became a project team consisting of us from
Creuna, the core team from the Swedish Parliament Administration, and other
consultants.” (Fredriksson)
Content
• Cull content; it is a critical task. “It was good that the in-house team had
such a clear focus on culling the content and focusing on what was important.
This made the task easier for us as consultants.” (Fredriksson)
Teams
• Whenever possible, locate team members in one location. “If possible,
make sure that the team can work from a common location. Through most of
the project, we sat in two different locations in Stockholm. If we’d been sitting
together, it would have been easier and quicker for us to bounce questions off
each other.” (Lernmark)
• Don’t underestimate the power of a supportive team environment.
“The ability to create commitment and loyalty in the team is critical. We
succeeded with this! This meant that certain shortcomings could be overcome
as we worked as a team, and we wanted to make things work! We really
managed to create a high level of team spirit: ‘We’re going to bring this off!’
We made time for coffee breaks together, to talk and do things together, to
discuss. Our team had a linear organization, where everyone was included,
which is typically Swedish. We worked without prestige, with our objectives in
focus.” (Stringer Bodin and Palmgren)
An Iterative Approach
• Keep reassessing. “We tried to improve our work methods all the time. We
changed things on the basis of our experiences; some improvements emerged
during the retrospectives, but also in other ways. We worked according to
scrum and this was a success factor for the project. With scrum, we were able
to prioritize and reprioritize throughout the project. The more we learned and
developed, the easier it was for us to see what needed to be done and
developed. Some things that we thought were important during the planning
stage turned out not to be so important when we started to see and test the
whole concept. This gave us a flexibility throughout the project, and some
user stories remained in the backlog and were later rejected.” (Stringer
Bodin)
• Work as efficiently as possible. “Once the design concept was agreed
upon, we tried to work as efficient as possible in the design process. No
unnecessary time was spent on sketches and prototypes. We drew things on a
whiteboard and took photos of what we’d drawn. We rarely had formal design
or prototype deliveries, as is customary. Sometimes it was enough with a
specification of what needed to be developed in the user story, and then for
the art director and interaction designer to work closely with the developers
during the implementation instead. When we needed to test different
alternatives or to seek buy-in in the organization, we still made prototypes
and design sketches though.” (Engelhart)
• Practice nimble design/small iterations, which are more effective
than big design sweeps. “Start by developing a scaled-down version of a
new function. Test it on users, analyze data from statistics tools, and then
decide what the next step should be. This way, you avoid going too far and
devoting time to functions that aren’t used or don’t support the users.”
(Fröberg)
COMPANY TEAM
Tourism New Zealand is the organization Project team (internal): Deborah Gray, Project
responsible for marketing New Zealand to the world Owner; Sue Parcell, Project Sponsor; Irina Winsley,
as a tourist destination. In a fiercely contested Project Lead; Brighid Kelly; Matt Moore; Alison
global tourism marketplace, Tourism New Zealand Dorrington; David Brem; Christine Adair
is responsible for ensuring New Zealand remains
attractive as a visitor destination internationally. Design team (external) Datacom: Katrina
Through the 100% Pure New Zealand campaign, MacDonald, Project Manager; Matt Swain,
the organization’s team of approximately 160 staff in SharePoint Practice Lead; Chris Zhang, SharePoint
15 offices takes New Zealand's story to consumers, Architect; Bryan Nimo, Brand and Digital Designer;
the travel trade, and the global media, while working Trudy Evans, Content Strategist; Keshwal Prakash,
with the industry in New Zealand to ensure they Test Analyst
deliver on the campaign’s promises. Tourism New
Zealand is funded by the New Zealand Government.
Headquarters: Auckland, New Zealand
Company locations: Tourism New Zealand has 15
offices across the globe, including in the US,
Europe, South America, Asia, Australia, and New
Zealand.
Locations where people use the intranet:
Employees at all Tourism New Zealand locations
use the intranet.
Annual revenue: N/A
THE INTRANET
Users: Approximately 180 people use the intranet.
The user population is very diverse in terms of age,
time at Tourism New Zealand, English proficiency,
locations, role types, and usage types.
Mobile approach: Responsive web design
Technology platform: Office 365 (SharePoint
online)
Team members shown here (left to right, top row): Sue Parcell, Deb Gray, Brighid
Kelly, and Irina Winsley; (left to right, bottom row): Matt Moore, Dave Brem, Alison
Dorrington, and Christine Adair.
BACKGROUND
The old TNZ intranet was rapidly becoming irrelevant for the organization’s users. It was
inaccessible on mobile devices and outside the TNZ network. Intranet pages were too
visually busy and hard to read, with too much text and scrolling. The result was that people
were struggling to find information, and content managers were struggling to keep the
content up-to-date. Some people did not even know there was an intranet.
The company needed a new intranet, but it also needed a new approach that would meet its
staff member’s mobile-first needs. The following business goals were outlined for the
project:
• Enable collaboration. Create a collaborative environment that supports the
organization’s mission, vision, and values and supports knowledge-sharing
across TNZ by connecting people across the organization, regardless of their
location or device.
• Create a hub. Make the new intranet a single, intuitive point of access to
TNZ tools, systems, and information.
Homepage
Navigation Highlights
1. Main categories. Site content is arranged under three main categories: What’s
happening, How do I, and Who we are. What’s happening includes news, events
calendar, media updates, presentations, and research; How do I includes
procedural instructions for completing work-related tasks; and Who we are
includes information about the organization.
2. Megamenu. The megamenu design gives people quick access to information.
The menus are arranged with bold categories followed by indented subcategories
to help people understand the hierarchical structure and find what they need.
The team made sure to use plain language for all labels, avoiding unexplained
abbreviations or meaningless jargon to make sections as clear as possible.
3. Local navigation. The side of the page displays the user’s current location. The
main section is highlighted with a gray background and bold text. Subsections
are listed beneath, matching the order of the subsections in the megamenu.
GOVERNANCE
The Corporate Affairs team is the overall owner of the TNZ intranet. Because this team is
responsible for TNZ’s internal and external communications, it is very well equipped to be
the driving force behind the intranet. The team is comprised of a good mix of
communications skills and technical, business, usability, and IA knowledge — all of which
are essential for driving the intranet forward. However, the intranet is more than just a
communications platform. So, to ensure the intranet’s ongoing value as a key internal
business tool, the organization’s intranet governance group also includes representatives
from the HR, IT, and Digital teams.
Three Corporate Affairs team members also played key roles on the intranet development
project team: the business owner, the project lead, and the communications/user adoption
lead.
ACCESS INFORMATION
Item Status
URL https://tourismnz.sharepoint.com/
Default Status The intranet is set as each user’s homepage.
People can’t change this setting.
Remote Access The intranet can be accessed remotely on any
device; the Corporate LAN is not required.
TIMELINE
PROJECT MILESTONES
Item Status
2001 • Developed the first company intranet on the
Shado platform
2005–2006 • Redesigned the intranet on the Shado
platform
July 2014 • Set up a project team for the intranet
redevelopment project
December 2014 • Supplier (Datacom) selected for the intranet
redevelopment project
January 2015 • Began working on developing the new
intranet on the SharePoint Online (Office
365) platform
July 2015 • Launched the new intranet on the
SharePoint Online (Office 365) platform
Culling Content
One of the critical pieces of creating great new content is to take a deep dive into the old
content before porting it over to the new site. The TNZ team conducted a full audit of the
existing intranet content (all pages and documents) and captured its findings in the “Master
Content Migration” document. All content was then reviewed and prioritized by the content
owners. Content evaluation criteria included content age, relevance, quality, length, and
usage; all of these factors were used to make decisions regarding which content to keep,
leave, or merge in each topic area.
The intranet team provided a template for content managers so that they could codify the
new content that would be required on the new intranet. That template contains fields for
key information (including meta data) and also includes brief editorial guidelines.
TECHNOLOGY
Category Technology Used
Web Server Hardware and • Office 365/SharePoint Online
Operating System
Bug Tracking/Quality • JIRA
Assurance
Design Tools • Adobe Creative Suite
• SharePoint designer, Visual Studio
Site Building Tools • SharePoint designer, PowerShell for
SharePoint
Content Management Tools • Office 365/SharePoint Online
Search • SharePoint Enterprise Search for Office 365
Other Functions • Yammer
• The API of Time and Date service is used to
provide real-time world clocks for all TNZ
offices
ROI
BEST PRACTICES
TNZ team members share some of the best practices they’ve learned through the redesign
process:
• Be strategic about change management. “Change management is a
crucial part of the intranet development project. A strategic approach to
change management is important for making sure all users are informed
about the project and are involved from the earliest stages whenever
possible.” (Deborah Gray)
• Governance is what keeps the new intranet running smoothly. “A good
governance framework is the key for ongoing intranet maintenance and future
growth. It enables the decision-making and planning processes for the
intranet, provides support for the intranet team, and assists with the smooth
running of the intranet.” (Sue Parcell)
• Get people involved and keep them involved. “Incorporate all staff
throughout the process to get a better understanding of your users and their
needs, as well as help all staff to be a part of the process, part of the
change.” (Brighid Kelly)
• Keep it simple. “Keep it simple. Simplicity and fun are key to user adoption.”
(Matt Moore)
• Use photos to your advantage. “Pictures are worth more than thousands of
words. Use them effectively.” (Irina Winsley)
• Plan for mobile first, but don’t stop there. “For internal users, think
mobile-first, but not mobile only. Today people use many different devices to
handle daily business processes. Start with mobile first by placing mobile
devices at the heart of the design and development strategy, and then grow
outward to a desktop-friendly version.” (David Brem)
COMPANY TEAM
Anthem is working to transform health care with Leadership: Peter Lobred, Staff VP Enterprise
trusted and caring solutions. The company's health Communications; Ramesh Aki, Director II
plan companies deliver quality products and Technology; Mike Berry, VP HR Service and
services that give their members access to the care Solutions; Sanjeeva Kodimala, Director I
they need. With over 73 million people served by its Technology; Christian Jansen, Director Corporate
affiliated companies, including nearly 40 million Communications; Brendan McGarret, Manager II
within its family of health plans, Anthem is one of the Technology.
nation’s leading health benefits companies.
Design and development: Amanda Aszman, Corp.
Headquarters: Indianapolis, IN, US Comm. Specialist Sr.; Andre McMillan, Software
Architect; Anthony Francisco, Developer Advisor;
Company locations: All across the US
Arlen Vargas, UX/UI Designer Lead; Barbara
Locations where people use the intranet: Howrey, Systems Analyst Sr.; Brian King, Developer
Employees at all Anthem locations use the intranet. Advisor; Calvin Grier, Security Analyst Sr.; Cole
Smith, Systems Analyst; Daniel Smith, Scrum
Annual revenue: Approximately $90 billion USD in Master; Devi Shailender, UX Designer; Dinesh
2017 Bandari, Developer Sr.; Doug Glaze, Developer
Advisor; Emily Gosselin, Initiative Project Leader;
Harsha Kakumanu, Developer I; Jenn Minder, Staff
THE INTRANET VP, Communications; Joe Moro, Developer Advisor;
Users: All Anthem associates and the majority of Kamalakar Peta, Developer; Leslie Williams, QA
the company’s contractors use the company’s Lead; Mary Katherine Lane, Systems Analyst Sr.
intranet, Pulse, on a daily basis. Anthem’s intranet is Advisor; Prashant Baliyan, Content Developer; Raja
designed to provide users with an experience that Raja Chozhan Velayutham, Developer; Rajani Saini,
aids both in daily tasks and personal needs through Systems Analyst; Rajvi Jariwala, Developer Advisor;
its advanced SSO HR portal. The intranet is used Raviknth Kolagatla, Front-End Developer; Shiva
for both internal and external customer service Ram Krishna Pandla, QA Analyst; Sourav
needs and was designed as a one-stop-shop. Mohapatra, QA Analyst; Srikanth Narala, Front-End
Developer; Subhashree Mishra, QA Analyst; Suresh
Mobile approach: Responsive web design Loganathan, Developer Lead; Tim Schluttenhofer,
Scrum Master; Veera Vantipalli, Developer;
Technology platform: Oracle WebCenter Suite 12c
Vengadessane Sittanandam, Performance Analyst;
Vikas Reddy Yelguru, Developer; Whitney Kelso,
Administrative Assistant II.
Team members shown here (top row, left to right): Peter Lobred, Ramesh Aki, Mike
Berry, Sanjeeva Kodimala, Christian Jansen, Brendan McGarret; (second row, left to
right): Amanda Aszman, Andre McMillan, Anthony Francisco, Arlen Vargas, Barbara
Howrey, Brian King, Calvin Grier; (third row, left to right): Cole Smith, Daniel Smith,
Devi Shailender, Dinesh Bandari, Doug Glaze, Emily Gosselin, Harsha Kakumanu;
(fourth row, left to right): Jennifer Minder, Joe Moro, Kamalakar Peta, Leslie Williams,
Mary Katherine Lane, Prashant Baliyan, Raja Raja Chozhan Velayutham; (fifth row, left
to right): Rajani Saini, Rajvi Jariwala, Raviknth Kolagatla, Shiva Ram Krishna Pandla,
Sourav Mohapatra, Srikanth Narala, Subhashree Mishra; (bottom row, left to right):
Suresh Loganathan, Tim Schluttenhofer, Veera Vantipalli, Vengadessane Sittanandam,
Vikas Reddy Yelguru, Whitney Kelso.
BACKGROUND
In 2016, Anthem embarked on a project to create a new, customized intranet that would
not only inform and educate users through communication technologies, but also aid in their
day-to-day tasks. As a company in the health care industry, it has numerous customers who
rely on accurate information on a minute-to-minute basis. Anthem therefore required a
best-in-class system that would empower its internal associates to serve customers with
great care, accuracy, and commitment. Prior to Pulse, Anthem used an intranet called
WorkNet, which had become outdated and cumbersome. Anthem needed a new solution
that would serve its current needs as well as provide a foundation for its needs for many
years to come.
As with any project, the new Anthem intranet came with its own set of obstacles, but none
that proved too difficult for the team to overcome. A dedicated and diversified team of
Anthem associates from several enterprise areas set out on a multifaceted mission to create
a best-in-class intranet experience for each and every user.
Starting small was the name of the game when the idea for the new intranet—Pulse—first
came to be. The Anthem team knew it had to aim high, but it also knew that taking on too
much would surely mean delays and unavoidable mishaps so it kept even the team size
intentionally small. This small but mighty group soon adopted the adage: No idea is a bad
idea.
Anthem has many different business areas with needs that deserve attention and
consideration, so the Pulse team was comprised of diverse individuals representing each of
the functional areas. One of the team’s first tasks was to brainstorm project objectives,
which it did through a series of sessions. Because the intranet had not been updated for
more than 10 years, identifying needed changes was rather easy. The question was: Which
changes were of the highest priority? And, as a follow-on: Which approach would be best to
implement those changes? The team clearly had enormous opportunity and potential for
success, but to achieve it, a strategic and methodical approach was needed. The team could
not rely solely on the input of its members—especially within such a large organization—so a
Pulse Ambassador Committee was formed made up of volunteer associates from across the
company to aid in specific tasks, including surveys, focus groups, and early adoption
testing. As the project progressed, the Ambassador Committee, along with the Pulse
Steering Committee, proved invaluable in validating appropriate solutions and processes.
The Anthem team used an Agile approach throughout the entire Pulse creation process, and
continues to use it today as the site evolves. Agile lets the team pivot quickly without being
too disruptive. During primary development, regular backlog grooming sessions and daily
Scrum calls helped keep the team on task, connected, and engaged. And, in an effort to
continue to listen to Pulse users post launch an internal suggestion box was set up.
Feedback received through this mailbox has helped the team identify what users like, don’t
like, and find most relevant. The team has also been able to keep a running list of
suggested features that may be added to the site as it evolves. The team has found that
being open to suggestions from the user base is extremely important and valuable.
Homepage
Pictured: Anthem’s New Pulse Intranet Homepage. News, access to tools, and a
lovely color palette make the new Anthem intranet homepage supportive and pleasant.
Homepage, Highlights
The Anthem intranet homepage offers personalized news and a customizable apps list so
users can easily see what’s important and access what they need each day.
You can’t help but notice the intranet’s color palette—light blue, royal blue, grey, and
black—along with judiciously used punches of color (such as green for an elevated stock
price). The palette creates a calm vibe and supports the content without taking attention
away from it.
To ensure that everyone can find the intranet easily, all Anthem associates have Pulse set
as the homepage in their web browser, and a shortcut icon to Pulse is on their computer’s
desktop.
Pictured: Anthem Intranet Dashboard Icons Wizard. Clicking on the site tips
wizard icon on most Pulse pages gives users helpful tutorial content, which is
particularly useful for an expanding company that regularly adds new associates.
Pictured: Anthem Intranet Events Dashboard. Each users’ events are listed in
their dashboard calendar.
Pictured: Anthem Intranet People Finder Dashboard. The People Finder is a killer
app that allows users to search for colleagues.
Pictured: Anthem Intranet People Search. This shows a search for people results
in a scrollable list of rich results.
Pictured: Anthem Intranet Favorites Dashboard. Users can add bookmarks to any
pages or search results pages on the site.
Pictured: Anthem Intranet Global Navigation. The megamenu makes it easy for
users to scan all the options in each top-level category.
Pictured: Anthem Intranet Mobile Employee Profile. When using a mobile device,
employees can access all the information in employee profile documents.
Pictured: Anthem Intranet Employee Profile Organization Chart, List View. The
org chart can be displayed as a list on Pulse.
Pictured: Anthem Intranet Tools. Tools & Resources for Anthem’s wide variety of
job roles are consolidated in one section of the Pulse intranet.
Pictured: Anthem Intranet Community Search. Users can search for any topic to
see if a related community exists.
Community, Resources
Pictured: Anthem Intranet Comment Function. Employees can like and comment
on news.
Pictured: Anthem Intranet Company Page. The company page houses key
information about the organization.
Getting Buy-In
Change management was a focus throughout the Pulse creation process. To ensure the
project would be a success, the Pulse team formed a Change Management Workstream
early on that met regularly. Key milestones and touch points were identified up front, and
these helped guide the project and keep it on track. Because people had been using the old
platform for so long, the team knew there might be adoption—or even acceptance—issues.
To combat this, the team kept the site intuitive and simple, and also developed a series of
communications that were delivered to users pre- and post-launch.
Because associates were eager to experience Pulse and the team didn’t want to operate in a
complete vacuum, it offered a series of interactive Pulse Sneak Peeks leading up to launch.
Associates were able to experience Pulse in a virtual setting with limited functionality over
the course of three in-depth interactive sessions. After launch, the team ran an eight-week
Get to Know Pulse series that focused on different Pulse areas and offered helpful tips along
the way.
The team also called on the Pulse Ambassadors to help out on launch day. These employees
served as Pulse experts who could help answer associates’ questions. And, of course, the
ambassadors were given early access to Pulse to help prepare them for their duties.
The team also created a comprehensive Site Wizard to help associates through the adoption
process. Because Pulse has so many potential users, the team wanted to try to avoid having
too many people contact the help desk or email the Pulse inbox with their questions, as
those channels would likely become overwhelmed. The Site Wizard proved to be a helpful
tool and is still active today.
ACCESS INFORMATION
Item Status
URL https://pulse.antheminc.com
Default Status By default, all Anthem associates have Pulse set as
their homepage and cannot change this setting. A
shortcut to Pulse is placed on each associate’s
desktop.
Remote Access Associates can access Pulse from anywhere using
two-step verification for security (log-in credentials
and a one-time passcode sent via a preferred
method, such as to a phone). Some Pulse content
is not viewable outside of the Anthem network to
ensure proper site security. However, applications
such as HR transactions and expense reporting are
externally available through Pulse.
Shared Workstations Some corporate offices provide shared computer
facilities to be used during breaks. Although not
widely used, Pulse is accessible via these
workstations.
PROJECT MILESTONES
Milestone Date Milestone Description
November 2005 • Launch of WorkNet
September 2014 • Collaboration (commenting and liking)
added to WorkNet’s news articles;
homepage refresh
May 2016—April 2017 • Redesign of Pulse (v.1): branding overhaul,
IA, new features
April 2017 • Launch of new design
April 2018 • Redesign of main header, footer, and
primary navigation, including reducing
header height by half, consolidated profile
photo section, and introduction of sticky
navigation
• Mobile responsiveness and accessibility
improvements to main page template
July 2018 • Enhanced photo upload tool, including
cropping and resizing, and an upgraded UX
• Configurable widgets
September 2018 • Launch of Pulse (v.2)
Overall redesign timeframe: 1 year
TECHNOLOGY
Category Technology Used
Web Server Hardware and • Web Tier: IBM HTTP Server
Operating System
• App Tier: Oracle WebLogic Server 12c
• Operating System: Redhat Enterprise Linux
Server release 6.8 (Santiago)
• Hardware: AMD 64
• Database: Oracle 12c RAC Enterprise DB
Bug Tracking/Quality • Bug Tracking & QA: JIRA Atlassian
Assurance
• Monitoring: Splunk, CA APM, Wily
• Documentation: Confluence Atlassian
Design Tools • Architecture Design: Microsoft Visio 2013
• UX Design: Adobe Photoshop, Balsamiq,
InVision
Site Building Tools • Eclipse, Oracle JDeveloper 12c, Web Storm,
Microsoft VS Code, Atom IDE
Content Management Tools • Oracle WebCenter Content 12c
Search • Google Search Appliance (GSA)
Other Functions • App Tier Caching: Oracle Coherence
Caching 12c
• Web Tire Caching: Apache Module Caching
Technology Migration
The Anthem team’s technology migration progressed as follows:
• Migrated legacy application from unsupported technology (Oracle Content
Server 10g) to the next-generation intranet platform (Oracle Content Server
12c) by launching automated content migration and enhancement.
• Upgraded and migrated legacy application from Windows platform to Linux for
better security and performance.
• Introduced architecture transformation foundational framework to replace the
third-party licensed products with more reusable components in an Agile
System Development Life Cycle (SDLC).
• Replaced Google Search Appliance (GSA) with Elastic Search as an enterprise
search solution as GSA was scheduled to reach the end of its life support at the
end of 2018.
MOBILE
ROI
Aside from the obvious benefit of Pulse providing Anthem with a much-needed intranet lift,
significant ROI was also realized shortly after launch. From an IT perspective, the new
intranet allowed for the decommissioning of 20 stressed servers and reduced significant cost
and complexity of Oracle operational support, including reduced infrastructure risk and
outdated OS and DB web applications.
The launch of Pulse also allowed for single sign-on capability and previously unavailable
external access to more than 130 specific Anthem apps, which users can now manage and
access simply and securely. Pulse also proved to be an immediate win in terms of associate
engagement, which rose by more than 250% for Pulse content. Also, the Pulse team was
able to expire more than 120,000 pieces of outdated WorkNet content.
Overall, the team has been extremely happy with the performance and new abilities that
Pulse provides.
LESSONS LEARNED
The Anthem team learned many lessons during the Pulse project, and it shares two key
lessons here:
• Launch slow, but fail quickly. “If you have the time, use it. Launch slow, but
fail quickly. Don’t feel rushed to move on to the next thing. Respect your
timeline, but also demand perfection, if not close to it. If something isn’t right,
fix it. Always act with your end users in mind and don’t be clouded by your own
curse of knowledge. Just because you know how something works and realize
what value it adds doesn’t mean the end user will. Additionally, make sure that
your team is made up of diverse individuals who really care about the product
and realize the impact it can have. Give everyone a voice. From end users to
project testers to those on your development and design teams, everyone has
great value to add. Simply allow them to add that value with their voice,
perspective, and opinion.”
• Pay close attention to change management efforts. “Change management
is especially important if an organization has a lot of diverse users. Ease your
audience and users into the adoption and do not just drop the new system on
them. The Pulse team found that seeing is believing, so don’t be afraid to give
glimpses into the current state and vision for the final product. Lastly, once
live, don’t leave users on their own. Continue to support them and make sure
that they feel a sense of ownership and ask them for their input. Make sure
they know you value their input, but the team can’t do everything.”
COMPANY TEAM
Dynacare is one of Canada’s largest, most The core project team: directly involved in
established health solutions companies. It serves the planning, design, and launch of ConneXe
healthcare solutions to more than 10 million comprised five team members: Mario
Canadians, offering services that include essential Fantozzi, Business Owner/Project Lead;
medical testing, insurance solutions, corporate Tricia Gill, Project Manager; Sandra
wellness programs, advanced genetic testing, and Bhikram, Business System Analyst; Mara
digital health solutions. MacKay, Project Coordinator; John Neves,
SharePoint Specialist.
Headquarters: Brampton, Ontario, Canada
Some of these team members also took on
Company locations: 200+ laboratories, health additional roles during the project phase as
service centers, transport depots, and corporate follows.
offices
Design: Mario Fantozzi
Locations where people use the intranet: Canada
Leadership: Naseem Somani, CEO; Mario
Annual revenue: N/A Fantozzi, IT; Tricia Gill, IT; Sandra Bhikram,
IT; Arun Thomas, IT; Donna Pascal, HR;
Scott Hickey, Corporate Communications;
THE INTRANET Andrea Price, Corporate Communications;
Ingrid Huss, HR; Ana Andreasian, IT; Peter
Users: The intranet’s 3,000 users range from Parsan, IT
clinicians and laboratory technicians to couriers,
frontline staff, and those in operational and Development: Mario Fantozzi, IT; John
departmental roles such as HR, customer service, Neves, IT; Sandra Bhikram, IT
maintenance, finance, and quality assurance. Users
Support: Mario Fantozzi, IT; John Neves,
share core demands for items such as policy
IT; Melanie Wells, Branding; Lissette
documents, company news and insights, and HR
Edward Copperi, Branding; Andrea Price,
and finance information; however, there are also
Corporate Communications–Content;
distinct intranet use cases relevant to only some
Andrew Munday, Corporate
user types or departments. For example, specialist
Communications–Content
staff uses the intranet on desktop devices to locate
subject matter experts to collaborate on healthcare
challenges, while couriers rely on mobile access to
coordinate operations with their team and stay
aligned with company objectives.
Dynacare team members shown here (top row, left to right): Arun Thomas, Mario
Fantozzi, Andrea Price, and Andrew Munday; (second row, left to right) Scott Hickey,
Donna Pascal, Ingrid Hess, and Sandra Bhikram. Unily team members shown here
(left to right) Emma Horder, Jason Liang, and Paul Seda.
BACKGROUND
In 2015, Gamma-Dynacare formally changed its name to Dynacare, repositioning itself as a
health solutions company. This new identity spoke to the company’s intention to expand its
scope within the changing Canadian healthcare landscape.
The company required an aggressive digital transformation strategy to support its ambitious
growth plans, part of which involved implementing a new, more powerful intranet platform
that could support collaboration, communication, and cultural goals.
Goals
The intranet that resulted from this initiative, ConneXe, was built around four pillars:
• Share knowledge: Provide employees with easy access to organizational
updates, policies, forms, and more.
Challenges
Key project challenges included the following.
• Full multilingual support: When the team discovered that not all of the
widgets included in the chosen intranet platform had multilingual capabilities,
it had to find another way to provide a true multilingual UX for both the
English- and French-speaking employee communities.
• Office 365: The company had an existing investment in Office 365 that had
to be leveraged in the new intranet.
• Seamless UI regardless of user roles: The design team had to figure out
how to provide a seamless experience for both union and non-union
employees, specifically on the Benefits page (which is different for each
group). And, along with that, the team had to find a way to ensure proper
access for both groups through Active Directory groups functionality.
Digital Workplace
The Dynacare vision was to have ConneXe be at the center of the digital workplace—a
digital destination where employees can start their day and find the tools they need to do
excel at their job. At the core of this vision was the desire to create an intranet that would
connect all employees, regardless of device, and thus increase collaboration, ease
information access, and improve every employee’s quality of life.
ConneXe was designed to be that digital toolbox, and it comprises many key features.
• Messaging: integrated Outlook Online email
• Productivity: integrated Office 365 Online productivity suite of applications
• Document management: SharePoint
• Collaboration: functional team sites and integrated WebEx
• Communication: a CMS, corporate news publishing capabilities, blogs, etc.
• Business applications: personalized user dashboard for company apps and
Office 365 apps
• Crowdsourcing: integrated Dynacare SoapBox (an employee ideation
platform) and Achievers (a rewards and recognition platform)
• Connectivity: integrated employee directory and rich user profiles, including
a skills repository
Pictured: Dynacare Legacy Intranet Homepage. This shows the Dynacare intranet
as it looked prior to the most recent redesign.
Homepage
Pictured: Dynacare Intranet Apps and Tools. ConneXe’s customizable Apps and
Tools menu ensures that critical business tools are no more than a click away.
Search Highlights
Because it is both predictive and highly responsive, ConneXe’s search experience
returns results right as the user begins typing. ConneXe’s global search provides
quick access to all content across the intranet, with results broken down into four
handy categories that make it easy for users to find what they need.
1. Search results: Search functionality is integrated with Dynacare’s SharePoint Online
environment, which allows users to search for content on the intranet and SharePoint from a
single search box. Results for intranet content, site-specific content, office-related results, and
people all display in a set of easy-to-scan results.
Pictured: Dynacare Intranet News. Users can skim, scan, and engage with
Dynacare news easily with ConneXe’s reader-friendly article templates.
Pictured: Dynacare Intranet Who Does What. The Who Does What business
overview page is dedicated to giving users a simple overview of the core Dynacare
business functions.
Pictured: Dynacare Intranet Team Site Page. Each team site landing page outlines
what the team does, introduces leadership team members, and provides links to
critical department tools and documents.
Mobile
A Research-Based Approach
The team’s design approach was multipronged and included several detailed research steps,
but the first step was to make the case for change. The team used a variety of analytical
tools to accomplish that goal, including Net Promoter Score, employee feedback surveys,
and Google Analytics to complement anecdotal feedback it was hearing from employees.
This data helped the team assess the current state and gain insights into the areas that
required improvement.
Team members also defined four strategic pillars to help them determine which employee
portal capabilities were critical to enhance ConneXe. These pillars later evolved into a list of
five capabilities critical to achieving the team’s vision for the new intranet:
• Communication
• Social networking
• Productivity
• Access to knowledge
• Effective collaboration
All of these early assessment and vision-building activities provided a solid foundation for
the project, but the through line for the project’s success emerged through one key activity:
including users in the design process. The team engaged a cross-functional team of
employees from all levels, geographies, and lines of business to participate in bimonthly
design-thinking workshops. The internal team collaborated with KPMG, a national lead
partner for Microsoft services, to help lead and facilitate these stakeholder workshops
alongside the Dynacare business owner/project lead. These workshops helped the team
finalize the vision and intranet strategy, and contributed to a better understanding of
employees’ goals and priorities.
Other design and assessment research activities included:
• Defect log review: By reviewing current state support-defect logs on the
existing ConneXe platform, team members were able to gain a good
understanding of its pain points and ensure that they designed a new
experience that addressed the service gaps. This analysis revealed that the
existing system lacked a sophisticated, intuitive, and user-friendly CMS; it
also lacked the flexibility to build web parts. Other findings revealed the costly
impact of custom development and the high cost of support maintenance.
• Net Promoter Score (NPS): NPS was implemented and measured on a
quarterly basis. This data included crowd-sourced comments from employees
noting ConneXe areas they wanted to see improved. The primary takeaway
from this analysis was that employees wanted to see team sites developed for
each of their functions to promote collaboration, teamwork, and knowledge
sharing.
Adoption/Buy-In
The Dynacare team did not experience any significant challenges with user adoption or buy-
in to the new site. Team members attribute that outcome to several factors.
GOVERNANCE
Ownership
Corporate Communications, HR, and IT jointly own ConneXe. This joint ownership
arrangement blends and supports the building of an exceptional employee experience and
corporate messaging objectives—all of which are enabled through the use of the best tools
and technology.
ACCESS INFORMATION
Item Status
URL www.connexe.dynacare.ca
PROJECT MILESTONES
Milestone Date Milestone Description
December 15, 2015 • First company intranet launched: A custom-
developed SharePoint 2010 on-premise site
with third-party hosting
January–December 2016 • Resolved break of and fixes for current
SharePoint intranet
• Developed intranet strategy and
governance model
April–August 2017 • Launched quick-win enhancements to the
existing SharePoint intranet, including:
weather widget, Twitter feed, Must Read
web part, Soapbox Ideation widget
integration, and I Would Like To quick links
• Conducted ConneXe stakeholder workshops
to finalize the vision, strategy, employee
voice, ideation, and prioritization activities
September–December 2017 • Designed the ConneXe UX through
wireframes
January–March 2018 • Explored the market through the ConneXe
RFP process
April–May 2018 • Held vendor demos with five companies
June 2018 • Received Unily proof of concept
July 2018 • Selected final platform and approved
business case
August 2018 • Held project kick-off and lab workshops
January 2019 • Achieved launch-ready intranet and
completed user acceptance testing
February 2019 • Trained end users, held marketing and
communications launches, and released
teaser videos
February 28, 2019 • Go-live launch date
Overall project time frame: 6 months
Culling Content
In order to move good content from the old platform to the new one, the team reviewed
previous intranet content and selected items to transfer or cull based on relevance. Old
TECHNOLOGY
Category Technology Used
Web Server Hardware and • Windows Azure
Operating System
• Office 365 Platform
• SharePoint Online
• OneDrive
Bug Tracking/Quality • Service Now
Assurance
Design Tools • Unily tools
SEARCH
Elastic search is integrated into the Unily intranet product, but it also passes queries along
to integrated data sources, such as SharePoint, to retrieve results.
Filtering is enabled across various search experiences, and all filters are responsive to the
content being searched, such as filtering by department in the people directory or filtering
by file type in the document center. In many cases, the complexity of filters is dynamic to
the content being searched. So, for example, the department filters are supplied by all the
potential departments and are listed against user profiles in the identity management
provider. Other filters, such as article tags, are built manually and have simple options to
increase usability and reduce complexity.
ROI
Dynacare requires that each business case put forward for approval stand on its own merit
by generating a positive rate of return. The intranet team was thus required to demonstrate
this in building a business case for this project. Since launch, keeping track of how the new
intranet is performing is an ongoing exercise in tracking both hard and soft metrics; both
forks continue to show that the new platform is moving in a successful direction.
Page views are tracked monthly to measure employee engagement. Since launch, average
monthly page views have increased by 17% over those of the previous intranet. This means
that more users are viewing content beyond the homepage.
Story views are also measured to determine the degree to which employees are engaged
with the organizational updates and insights that are being published. One dramatic
example of an increase in this type of engagement is with news stories. In 2018, four news
stories were viewed more than 400 times. The number of stories has already doubled in just
the first four months since the new intranet launched.
Best Practices
The Dynacare team’s list of best practices might seem simple on its face, but this list
represents a critical, detailed approach to developing a great, usable intranet platform that
will serve all employees:
• Assess the current state: understand your organization’s digital workplace
maturity level, how employees work to help identify the gaps, and the
appropriate tools employees need to do their best work.
• Establish a digital workplace vision.
• Create a capabilities-based digital workplace strategy.
• Align organizational objectives to strategy.
• Engage stakeholders from across the business to better understand the tools
that people need to get their work done.
• Select the right digital toolbox based on your business drivers and strategic
priorities: messaging, productivity, collaboration, communication, business
applications, crowdsourcing, connectivity, and mobility.
• Determine which tools will be part of the intranet, and which tools will be
outside of the intranet and part of the larger digital workplace environment.
• Design appropriate governance, operational policies, and management
systems to support the success of the intranet post-launch.
• Build change management practices into the project plan to ensure that users
embrace this new way of working and that they are ready for the change that
is coming.
• Develop marketing and communications plans to help create excitement
about the launch.
• Provide sufficient training to all users; include both front-end and back-end
user training.
• Measure success and adoption through reporting metrics.
COMPANY TEAM
The Norwegian Government Security and Service The platform was designed and implemented—and
Organization (Departementenes sikkerhets- og is continuously maintained and enhanced by—a
serviceorganisasjonm, or DSS) provides shared flexible group of internal and external resources.
services to the central government in Norway,
including the Prime Minister’s Office, 15 ministries In-house team: The internal team handled project
and embassies, and consulates, as part of the management, concept design, UX, IA, tech
Ministry of Foreign Affairs (MFA). supervision, dialogue with intranet editors, user
research, search, and visual design. Team
The main purpose of DSS is to provide synergy for members: Hilde Kari Sundet (project lead), Petter
the ministries with cost-effective and reliable Thorsrud, Torbjørn Vagstein, Stig Nappen,
shared services, which include cleaning, security, Shanmugathas Asaipplillai, Mette Haga Nielsen,
switchboard, and postal services, as well as Kristine Brodahl, Rune Løvnæseth, David Rooke.
running computer systems and handling
government publications. External resources: External resources were used
for interaction design, UX, visual design, EPiServer
The Department of Digital Services web section CMS, and SharePoint search implementation. These
provides web services to the ministries, mainly included consultants from: Creuna, EpiNova, and
providing support for the external website PuzzlePart: Ingrid Håland, Stig Kulvedrøsten, Vidar
www.regjeringen.no (government.no), the Olsen, Martin Falck-Ytter, Carl Lundblad, Bjørn
norway.no portal for MFA, and a number of smaller Tennøe.
sites, along with the intranet platform.
Ministry representatives: In addition to the
Headquarters: Oslo, Norway project/team members, the involvement of the
ministries’ intranet editors has been (and still is)
Company locations: DSS (750 employees) and crucial to the platform’s development,
most ministry employees (5,200) are based in
maintenance, user support, and further
Oslo. Roughly 1,800 employees are located in
development.
about 85 other countries worldwide (in 110
embassies and consulates).
THE INTRANET
Users: Approximately 7,500 Depweb/common
platform users, of whom 6,700 also have access to
a ministry-specific intranet.
Core team members shown here (back row, left to right): Torbjørn Vagstein, Stig
Nappen, Mette Haga Nielsen, Rune Løvnæseth, Shanmugathas Asaipplillai; (front row,
left to right): Kristine Brodahl, David Rooke, Hilde Kari Sundet, Petter Thorsrud.
BACKGROUND
The first common intranet platform for the ministries was launched in 2007, as a direct
result of a major upgrade to the Norwegian Government’s external website
(www.regjeringen.no/www.government.no), which united the many ministries under one
public platform.
Prior to this, there were 15+ unique ministry intranets with more than half a dozen different
technologies and platforms, each “owned” by the respective ministry’s ICT department.
However, because the ministries were experiencing increasing costs and upgrade issues,
they were open to seeking common solutions. This coincided with a need to reduce local ICT
staff and use DSS services to strengthen its position as the leading supplier of services to
the ministries. DSS is a public agency; although it is owned by one ministry, it offers
services to all ministries.
The experiences from the regjeringen.no project clearly indicated that offering a single
platform to all ministries offered many potential benefits, and it was natural to try to
leverage the external site’s technology solutions. DSS has therefore sought to standardize
both the technical platform and its use of suppliers for all web solutions and services offered
to the ministries. This helps DSS reuse solutions and optimize resources and competencies.
The intranet’s previous version had common functionality and design guidelines, but each
intranet was hosted as a separate instance, necessitating the need for separate servers and
licenses for the CMS and search engine, and in some cases, local hosting inside a specific
ministry’s firewall.
Since its origin in 2007, the intranet’s goal has always been twofold:
• Help employees find relevant information and tools to do their jobs efficiently
• Offer news, background information, and socially-oriented content to help
foster a common culture and a good working environment
The new platform is hosted as one instance, which results in savings on licensing, hosting,
development, and maintenance. It also allows for central editorial and tech support,
common guidelines and page templates, and the ability to share and localize common
Challenges
The team encountered many challenges in undertaking a project of this size and complexity,
including:
• Meeting everyone’s needs: Unifying the requirements and priorities of 15
different ministries into a single coherent platform was the project’s single
biggest challenge. Originally slated for release in late 2016, the project launch
was delayed for two main reasons:
o The platform architecture was redesigned to offer one centrally hosted
application, with content sharing and reuse of a common search. This led to
several challenges, including the need to solve access rights and
network/firewall challenges, as well as to agree on common content and
metadata models.
o During the development process, additional user needs were identified and
met, leading to scope creep, delays, and budget problems.
• Creating an all-encompassing search: Early in the process, the team
decided that rather than set up an intranet-specific search, it would create the
first iteration of an enterprise search covering all important sources, including
SharePoint resources and document management and archiving systems. The
first version of this search covers all content on the intranet and (common)
SharePoint platforms with rights management; it is designed to include
document management systems’ content and other sources at a later stage.
Aiming to create a system that would index and search SharePoint resources
meant that the teams responsible for SharePoint functionality, UX, and local
SharePoint hosting and maintenance had to be consulted and included in the
project. In the long run, this proved useful for all teams, but getting there
took time.
• Deciding what to do about specialized functionality: The previous
platform had a lot of specialized functionality that had been developed over
the years. The intranet project was originally intended to remove some
specialized functions, but the opposite actually happened. Almost all special
functions had to be reimplemented on the new technical platform, and new
functionality was also added, including prefilled forms (with personal and
organizational info) for ordering services, a new course portal, and a module
for producing HTML documentation from Microsoft Word files.
Platform
Homepage
Homepage, Highlights
The intranet homepage of DSS itself offers links to common tasks and user-created
bookmarks that expedite DSS employees’ work. The homepage keeps employees informed
with a selection of news, links to more news, and a wall feed where employees can post and
react to messages.
1. Intranet name: The intranet’s name is the first item in the upper left of the DSS
intranet homepage. Some ministries and DSS itself have intranet names that add an
“i” before ministry acronym (such as iDSS and iLMD for the Ministry of Agriculture),
while others chose catchier names, such as FINTRA for the Ministry of Finance and
Arena for the Ministry of Knowledge.
2. Search: The intranet search appears as a white field on the right. The juxtaposition
between the white field and blue background bar help make the field visible. This
search field is common across all intranets at DSS.
3. Waffle menu: A black button with the waffle icon and the label Gå til (Go to)
appears to the right of search. This menu makes it easy for users to access other
relevant platforms, such as shared SharePoint workspaces.
4. Edit button: For those users with editing rights, the Edit button appears in the far
upper right corner. Clicking it gives them access to the CMS for creating and editing
content based on their rights.
5. Logo and organization name: On the far left of the black bar that spans the width
of the page appears a small lion logo followed by the full name of the department.
6. Global navigation: The global navigation appears on the far right of the black bar.
7. Bookmarks: A drop-down list of bookmarks is on the far left of the white bar that
spans the width of the page. Mine snarveier (My shortcuts) includes both user-added
items and standard shortcuts set by the site administrator.
8. Top News: Two top news items appear at the top of the page in the I fokus (In
focus) section. Each has an associated photo, clear title, date, summary, and number
of comments and likes the story has garnered. Selected items, such as important
articles, and the news list offer links to the full news listing.
9. News list: To the right of the top two news items is a list of six other recent news
stores, each with simply a title, date, and number of comments and likes for each.
10.Feed: Below the news appears the Oppslagstavle (Bulletin board) feed, where
employees can post, like, and comment on messages. This offers a way for engaged
employees to correspond with—and potentially inspire—each other in a public way.
11.Common links: The center of the homepage houses the Enklere hverdag (everyday
tasks) section with links to some of the most commonly used tools and resource
pages on the intranet and on external websites.
12.System status: It’s important for employees to know when IT systems are having
issues. Driftsstatus og informasjon (system status and information) shows a green
link and checkmark when systems are all working as expected. A yellow or red line
Pictured: Norwegian Government Intranet Tools. Users can scan the list of tools
or search for the one they want.
Pictured: Norwegian Government Intranet Mobile Menu and Search. The menus
and search feature collapse under icons on mobile to save screen real estate.
Pictured: Norwegian
Government Intranet
Search. Search
suggestions and results
are targeted based on
user affiliation and
rights.
Pictured: Norwegian Government Intranet Search Best Bets. Best bets are like a
search results insurance policy.
Pictured: Norwegian Government Intranet Search Filters. The search results are
organized in tabs, each named for a different content source.
1. Tabs: Tabs just below the search field include those for all results, employees,
intranet/extranet, collaboration rooms, user guidelines/knowledge base, the HR
portal, and the user’s SharePoint homepage. Less important content sources are
placed in a menu to the right of the tabs. The first tab on the SERP is for all
results, which includes results from all content sources.
2. Selected tab: The selected tab is obvious: the text is blue instead of
light grey, and the tab is underlined.
3. Facets: All tabs (except “all results”) have facets for that content source.
4. Clickable metadata: In addition to the clickable result title, the SERP
includes other clickable metadata that lets users start a new query. For
example, a search for a colleague by name will return a result for that
person. Within the result’s summary is a clickable link to the person’s
department, and users can quickly view the person’s department
colleagues by clicking the department name.
5. Sort: Results are initially sorted by relevance, but a drop-down menu
just below the tabs allows users to sort the results by date or
alphabetically.
6. Preview: For documents housed in the collaboration room, the search
provides a document preview. This appears on the right side of the SERP
when the mouse hovers over the result. Seeing the document can give
users an idea of what the document is about without having to open it.
From the preview, users can also follow or share the document.
Pictured: Norwegian
Government Intranet
Organization Chart Section. The
org chart enables users to home in
on a section of the ministry, right
down to particular employees. The
links on employee names lead to
their profile documents.
GOVERNANCE
DSS provides a wide range of services to the various ministries. The common external
internet platform for the ministries (www.regjeringen.no) has been DSS’s responsibility
since 1995. In 2007, during the site’s major redesign and technical upgrade, the ministries
were deeply involved in design and implementation. This process led the ministries and DSS
to look more closely at the plethora of independent intranet platforms that the ministries
ACCESS INFORMATION
Item Status
URL intra.dep.no: This URL directs users to the
homepage of the ministry or organization where
they are employed.
Default Status The homepage is the start page in standard
browsers installed on the users’ desktop. Users
cannot change the homepage, but they can use
other nonstandard browsers that do not have this
homepage as the default.
Remote Access The sites may be accessed remotely via VPN.
Windows 10 clients use Direct Access for seamless
access. ADFS is used for authentication.
Mobile access to the intranet is handled by
MobileIron/Web@Work to ensure secure access to
internal systems. Intranet use on mobile is
relatively limited so far, but has proven to be very
useful in specific situations for some users.
PROJECT MILESTONES
Milestone Date Milestone Description
Late 1990s • First ministry intranets were hosted by
individual ministries and did not share a
common platform
July 2007 • First common intranet platform for the
ministries
2010 • Upgrade CMS and new version of EpiServer
January 2016 • Recent redesign project start date
February 2017 • Internal launch of the new platform (first
version) for intranet editors
• Content production on new platform starts
March 2017 • Launch of the Depweb extranet, the first
site on the new platform
May 2017 • Launch of DSS intranet, the first intranet
site including the Finn :D enterprise search
August 2017–March 2018 • Launch of Ministry intranets
2018 • Launch of new releases every month based
on usability testing and stakeholder needs
• Some core functions (organization maps,
search suggestions, etc.) have been
released since the first launch, based on
user demands and research
TECHNOLOGY
Category Technology Used
Web Server Hardware and • Operating system: Microsoft Windows
Operating System Server 2012 (64-bit)
• Virtual servers: VMware ESXi, 6.0.0,
8934903
• Servers: VMware HP ProLiant DL380 Gen9
Bug Tracking/Quality • Jira
Assurance
• Confluence
• SharePoint collaboration rooms
Design Tools • IA and wireframing: Axure RP Pro, Adobe
XD
• Photoshop
Site Building Tools • Visual Studio 2017 v15.7.4
• Octopus Deploy 3.4.13
• TeamCity 2018.1
• .NET 4.6.2
• node v4.6.1
• npm v2.15.9
Content Management Tools • EPiserver CMS v11
Search • SharePoint 2013
Other Functions • Matomo (statistics and search logs)
Technology Evaluation
The regjeringen.no project experiences pointed to the potential benefits of offering one
platform to all ministries, and it was natural to reuse that external site’s technology
solutions. DSS is now seeking to standardize the technical platform and suppliers for all web
solutions and services to enable reuse of solutions and to optimize resources and
competence.
In 2006, when a platform consisting of EPiServer CMS, FAST ESP search, and TM Core Topic
maps relational engine was chosen for the external site, the main criteria were:
• Platform and components should be technologically mature and offer the
necessary functionality with a good user (editor) interface
• Platform and components should come from suppliers of a certain size, with a
good probability of market survival and strong representation in Norway
MOBILE
The design team decided to use a fully responsive design, adapted from the regjeringen.no
project. All intranet content is available on mobile, but the element sequence and placement
may be changed. All employees who use Mobile Iron can use all intranet services. The
search experience is not quite ideal; limitations in SP 2013 make it too costly to build a
responsive search. However, this will be remedied as part of a SharePoint upgrade.
Users have not expressed a strong need for mobile access, and most ministries have not
been very active in promoting it. That said, there is a growing use—especially on
tablets/pads, which some people are using as an alternative to portable PCs in meetings and
other out-of-office situations. Serving these users, and those using iPhones or Android
smartphones, is considered important, as the use and usefulness of these devices is steadily
increasing.
ROI
Applying Metrics
Despite the challenge of measuring exactly what success means, the organization
recognizes that great strides have been made with the intranet redesign, with benefits that
include:
• Reduced costs
o Common platform: Hosting all of the intranets on a common
platform has greatly reduced costs; the savings on licensing alone
amounts to roughly $30,000 USD per year.
o Improved accessibility: The importance of providing the best
possible usability and accessibility has permeated the project from the
start. While providing good usability and accessibility is an obvious
target for any site (intranet or internet), accessible websites are now
mandated by law in Norway and site owners can be fined for
noncompliance. The project hired accessibility experts from Funka to
ensure high-quality accessibility. And, because the platform in under
constant development, Funka now conducts regular accessibility
checks and all new functionality is tested for accessibility. DSS sites
now have a strong reputation as examples of good accessibility, which
in turn makes the sites friendlier for all users.
• Time savings:
o Pooling resources: Pooling development and maintenance resources
means that each intranet site is kept up-to-date for a fraction of the
cost of updating each site as a separate instance.
o Content sharing: Content sharing and collaboration among editors
saves time for the ministries, providing increased quality for less cost.
o Enterprise search: Having an intranet with good enterprise search
results saves time for all employees, allowing them to find needed
content and helping them perform tasks more efficiently.
Since launch:
• Trends in relevancy
• Trends in precision
• Queries per month
• Average query length per month
• Average number of terms per query per month
• Trends in abandoned queries
• Trends in zero-result queries
Previous month:
• Number of queries per search tab per day
• Unique users per day
• # of queries per user, per day
• # queries per 25 most popular topics
• Recent trends in query terms, with content suggestions
• Top 10 abandoned queries and zero-result queries
Last three months:
• 25 most popular topics per month
Lessons Learned
• Be specific with specifications. “The intranet team could have been more
precise when specifying tasks sent to developers, potentially saving time and
cost on superfluous meetings. Using Scrum/Agile methods, the development
team of three felt that only one product owner responsible for specifications
was insufficient. More team members should have worked with stakeholders
and users to specify the design details and new functionality. Also, staff
members of the team changed a lot during the development period. Skills and
knowledge were not always on the required level, and this caused delays in
the process.”
• Don’t overlook training. “Some editors wanted more training and courses
to adapt to the new platform. The needs for training vary a lot. It is a
challenge to satisfy all needs when time, money, and resources are limited.
However, the concept of ‘open house’—where intranet editors and DSS team
members get together on a regular basis to go through new concepts and
functions, and work on content—has proved to be an excellent platform for
sharing knowledge, defining best practice, and helping each other.”
• Sometimes functionality can change culture. “In the new intranet
platform, employee search was a part of the enterprise search (Finn :D).
Previously, employee search was a unique search function with its own
specific interface and functionality. Introducing an entirely new search
concept caused some resistance, as users of the old version were used to
certain tools that no longer existed. These users particularly missed being
able to create lists of employees that could be easily pasted into Excel for
further use. This was considered to be out of scope for the new search
project, but it is very likely that as part of the post-launch development
activities an alternative search display will be developed to meet these
requests.
“The old employee search was mainly directed at finding people in your own
ministry, with a different search for all ministries, with limited information.
The new Finn :D search made all ministry employee information available to
everybody, and this challenged the culture in the ministries.”
Best Practices
• Identify opportunities and change direction if you need to. “In the
initial phase of the design process, the scope was to upgrade and redesign the
intranets, without changing the concept of separate intranets. Enterprise
search and shared content between extranet and intranets was not within the
scope of the project, and budget and deadlines were set accordingly.
However, after seeing results from insight and research work, and wishing to
fulfill requests from stakeholders (in the ministries), it was decided to widen
the scope of the redesign process to get a platform that would serve users
better, and save resources in the long run. More funding was provided and
deadlines extended, all in collaboration with management and stakeholders.”
• Work lean. “During development, we used Prince II, Agile, and Scrum
methods, with releases every month. Intranet editors had access early on,
allowing for user testing and dealing with requests from the very start. In the
process, we used insight, research, and analytics (metrics, KPI) to adjust and
improve. We also arranged frequently user tests, often on smaller groups for
easier administration. This proved to be very helpful in the process of
achieving a user-friendly intranet. After launch, it was user tested and
improved a dozen times.”
• Create opportunities for collaboration. “Previous experience from the
regjeringen.no project had indicated that regular ‘open house’ meetings
where all editors could meet DSS team members (an, in some instances,
external consultants involved in the project) to go through new concepts and
features, and work together on concrete content production and problem
solving, had been extremely useful. Throughout the intranet development
period, open house meet-ups were held biweekly (or weekly), so that editors
got accustomed to the platform and could get mutual help in creating good
content.”
• Don’t try to reinvent the wheel. “In general, reusing design, concepts,
technology, and methods from previous projects (most notably the
regjeringen.no process) was deemed successful, and also caused great
savings in terms of money and time to target.”
Team members shown here (left to right): Stéphanie Spiegel, David Mimran, Fred
Fath, Renée Luque, Helga Leifsdóttir, Annie Paprocki, and Eric Hahn.
BACKGROUND
Pictured: iSeek’s homepage balances global and local content with the aim of making
all staff members feel at home regardless of their work location.
Pictured: iSeek’s drop-down menus, duty station menu, and mobile navigation are
fully responsive so users can find exactly what they need on any channel.
Pictured: Clear guidelines for submitting content are available to staff members to
ensure content meets iSeek’s quality parameters and publication standards.
Pictured: iSeek’s global contact directory makes it quick and easy to find a colleague’s
email address, phone number, duty station, and more.
AppCatalog Highlights
Recently created to help staff move toward a single set of shared tools, facilitate increased
productivity, and support collaboration, the Unite AppCatalog shows the full suite of digital
Pictured: A searchable database of all available jobs is fully integrated into iSeek so
staff members can find positions at other UN offices.
Pictured: iSeek’s business card application allows staff to customize their own
business cards, starting with a standard template.
Pictured: One of the most popular iSeek features is Classifieds, which allow the UN’s
global workforce to buy and sell to each other. This is particularly helpful as staff
members regularly move to new duty stations.
Classifieds Highlights
iSeek Classifieds offer a safe, user-friendly space for employees to sell items or start looking
for a new place to live. The platform is safe because users know they will be selling, buying,
Pictured: iSeek includes pages for sports, games, and clubs to build community,
promote health and wellness, and provide outlets for employees who share common
interests.
Data-Driven Design
The team supports its design decisions with data gathered through qualitative and
quantitative methods. For example, the iSeek team ran regular global surveys in 2015,
2018, and 2019 to assess user satisfaction and identify areas for improvement. They also
listen to staff during the frequent (once per day on average) team-led trainings, as well as
in communications meetings and other forums. Further, they frequently seek feedback and
support from the iSeek Focal Point Network.
In addition to all of these active-listening activities, in 2019 the iSeek Team ran focus
groups and usability tests, and conducted interviews. This helped the team learn more
about what users want—and what they don’t.
Google Analytics is also used to track user behavior, page views, and sessions.
This data, drawn from a variety of sources, cumulatively helps the team assess the
effectiveness of various types of content or internal communication campaigns.
Information Architecture
There were four primary IA requirements:
• More information presented above the fold to give better exposure to
announcements and events, classifieds, jobs, and essential UN policy, which
were among the top features according to usage statistics.
• More exposure to emergency information, the staff directory, and the user’s
team information in the top menus.
• Footer should appear on every page and be filled with essential links (Toolkit)
categorized by themes.
• Site should include news feeds to departmental homepages in order to better
disseminate information.
Adoption/Buy-in
In addition to gathering innovative ideas from staff and management about the intranet
they would like to see, the findings from the 2015 and 2019 research initiatives lent weight
to the iSeek team’s vision for the redesigned site as a go-to place for staff information that
was user friendly, easy to navigate, and had a more modern look and feel.
Ownership
In other organizations, HR or IT may own the intranet, but at the UN, the Department of
Global Communications manages it. And, as the name implies, that department comprises
communications professionals who are primarily focused on creating awareness of the
organization’s work and priorities. Because the iSeek team is situated in this environment, it
can attract talented internal information specialists, with skills in information management,
graphic design, website development, translation, and communications. So, this ownership
model is beneficial because the focus is on effective communication, resulting in a less
“corporate” intranet. The challenge with this placement is that the team is located outside of
the management department’s decision-making process.
ACCESS INFORMATION
Item Status
URL iseek.un.org
Content Management
The iSeek team manages articles via an editorial calendar. Once a submission is received,
the calendar manager and editors vet the content for accuracy and rules compliance, edit
and translate it, and give it a spot in the calendar.
The editorial calendar is used to manage global articles—which appear on every local
iteration of iSeek—as well as local articles that are managed by local teams in different
departments or duty stations and that appear only on their iteration of iSeek. This allows for
greater flexibility and helps increase the feeling of belonging for sub-entities whose staff can
read global articles as well as articles that concern only their duty station/entity.
Other types of content are managed according to type:
• Events and announcements can be managed either by Focal Points or by staff members
who have permission to post these on behalf of their entity.
• Classified ads, a popular iSeek feature, are posted by individuals, including staff from
other entities that have requested an account.
Maintaining Quality
As iSeek’s popularity has increased over the years, staff member content submissions have
also increased—though this content does not always fit the quality parameters. To address
this, rules and guidelines are offered to staff members to help improve submission quality,
and iSeek team members are always available to give advice (in person, by phone, or
email) to those who want to write for iSeek. Rather than turn down contributions, the team
tries to encourage contributors to improve their text. This approach helps foster the feeling
that everyone belongs to the vast community of UN staff members around the world and
iSeek is an inclusive platform.
A comprehensive page on the intranet offers specifics on content requirements. Following is
an example of the requirements for story posting:
TECHNOLOGY
Category Technology Used
Web Server Hardware and • iSeek is hosted on an internal Drupal farm,
Operating System which is managed by the UN’s corporate IT
department
Bug Tracking/Quality • Jira
Assurance
Design Tools • Adobe Creative Cloud
MOBILE
iSeek became been available on mobile devices (smartphones, tablets) and any computer
browser in 2014—a year before the major redesign. Currently, about 10% of traffic comes
from mobile users.
Accessing the intranet remotely was an essential feature for a tool serving an international
organization with staff located all around the world. Since iSeek went mobile, all staff
members have been able to access it from wherever they are, without being tethered to a
local network. This also opened the door for intranet access for employees traveling and
telecommuting. In addition, mobile access impacted content contributions, as it made the
ability to post remotely a reality. Editors and contributors can now create and edit content
on the go. And they can respond to requests to add new content even more quickly.
Mobile access is not only a convenience and an efficiency for the team, but it also provides a
pillar of business continuity in times of crisis or emergency. For example, in an emergency,
the iSeek Team can alert staff and update them about developments without having to be in
the office.
SEARCH
Filtering
iSeek has several different search applications whose filter mechanisms depend on content
metadata. In most cases, the intranet uses a combination of faceting and keyword
searching. For example, the classifieds search has multilevel facets for category and
location, while the jobs search has six different facets. iSeek search results include filters for
all normalized metadata fields whenever possible.
Search Relevancy
Making sure the search tool returns relevant results is an ongoing challenge on any intranet.
On iSeek, search relevancy is maintained through various means, including expiring old
content automatically and offering powerful faceting tools along with keyword search,
particularly within applications such as jobs and classifieds.
Search relevancy is also being actively improved through a new UI that will provide a more
intuitive filtering process.
ROI
Measuring Success Through Metrics
LESSONS LEARNED
The iSeek team members have given their lessons learned a lot of thought. They’ve tried
hard to figure out what worked and how to benefit from it, and what didn’t and how to learn
from it and do better in the future. Among these lessons are the following.
• Evaluate what “business” you’re in. “The Deputy Secretary-General—the
UN’s number two—launched the iSeek platform as a vehicle for internal
communications, but over time, because of the lack of means and the loss of
management engagement, the focus of the team became to manage the
intranet. Between then and now, iSeek has come to support more and more
staff—over 90% in 2019—and is gaining recognition from the highest levels of
all departments. By being at the epicenter of all internal communications and
recognized so by the office of the Secretary-General and management, its
staff is in a position to create the assets all departments use to promote the
priorities of the UN. This positions the iSeek staff as much more than an
intranet support organization, as they should be, given the intranet’s role in
furthering the mission of the UN.”
Best Practices
Content
• Allow for distributed content ownership. “Allowing for content autonomy
over individual areas helps generate pride and create community amongst
contributors. iSeek provides the platform and governance, and then news and
stories originate from all over the world, enabling fresh and interesting
content to be generated daily.”
• Make it personal. “Like a standard intranet, iSeek provides tools and
systems at users’ fingertips, but iSeek’s human-centered content provides
staff with a sense of meaning and belonging. By featuring a mix of global and
local personal stories, along with the accompanying images and videos, the
intranet serves to connect people and provide a window into the human
aspects of this distributed organization. With some staff working in harsh or
extreme environments, the platform unifies staff under a shared mission.”
Management
• Move from a product-orientation to service-orientation. “When iSeek
first launched, the team was almost entirely responsible for creating and
sourcing stories. Now, stories are created and submitted through a more
distributed model and iSeek is being used to shift toward having an active role
in building awareness, oversight, maintaining guidelines, and providing
training and education. The platform has been transformed into more of a
two-way communication tool.”
• Stay lean. “The iSeek team’s flat hierarchy and ability to reach out within the
UN has enabled it to move fast and innovate.”
In addition to those listed below, we thank co-authors Candice Goodwin, a journalist and
usability consultant (2001-2003 Intranet Design Annuals), and Mathew Schwartz
(penandcamera.com) (2004-2007 Intranet Design Annuals) for their essential work.
Kara Pernice is Senior Vice President at Nielsen Norman Group and works with clients to
derive UX strategy and designs that meet business goals. With more than 20 years of
experience in management and user experience (UX) research and design, she has led
many major intercontinental research studies, authored a variety of research reports and
hundreds of guidelines, and coauthored the book Eyetracking Web Usability. The Wall Street
Journal called Pernice an “intranet guru.” She has lectured around the world on a wide
range of topics, and her client work spans many businesses and industries. Before joining
NN/g, Pernice gained invaluable experience pioneering UX and building and managing UX
teams in an assortment of development environments and established several successful
user experience programs. A champion for usability, Pernice chaired the Usability
Professionals’ Association 2000 and 2001 conferences, and served as 2002 conference
advisor. She holds an MBA from Northeastern University and a BA from Simmons College.
Amy Schade is a Director at Nielsen Norman Group with more than 20 years of experience
in usability, user research, and website design and development. She has led research,
authored reports, and taught courses on the usability of intranets, mobile websites and
applications, responsive design, emerging design patterns, email newsletters, and
ecommerce. She co-authored the Intranet Information Architecture report and has co-
authored the Intranet Design Annual since 2010.
Schade works with clients large and small in industries including telecommunications,
ecommerce, nonprofits, government, education, and publishing, including extensive work on
corporate intranets. She has conducted worldwide user research, including longitudinal
studies, remote studies, accessibility studies, and eyetracking research, running studies in
the US, Canada, Europe, Asia, and Australia.
Before joining NN/g, Schade worked as an information architect. She previously held a
variety of positions in advertising and web production. She holds a master’s degree from the
Interactive Telecommunications Program at New York University and a BA in
communications from the University of Pennsylvania.
Patty Caya (www.pattycaya.com) is a freelance journalist (writer and editor) and an
award-winning digital media producer. In her business writing, she specializes in topics
relating to usability (including social media and mobile design) and the business and
technology of the web. She has co-authored the Intranet Design Annuals for NN/g since
2008. She wrote and edited the report, Mobile Intranets and Enterprise Apps, and the 1st
and 2nd editions of Social Features on Intranets: Case Studies of Enterprise 2.0. She
authored the 3rd, 4th, and 5th editions of the report on intranet portals and contributed to
the Application Design Showcase (2nd Edition).
For more than a decade, Caya has split her time between journalism projects and web
consulting. She is an experienced content strategist and interaction designer. She has
consulted for many of Boston’s top interactive agencies, leading web and intranet
development projects as well as usability testing, research, and design initiatives. Her client
roster spans a wide range of industries and includes leading national brands alongside
mission-driven nonprofits. She has a BFA from New York University’s Tisch School of the
Attendees learn from NN/g experts and invited industry peers, leaving with practical skills
that can be applied immediately.
With more than 40 courses available, there’s something for everyone. Courses are taught in
areas such as: research practices, design processes, working with stakeholder and product
teams, among other things.
• Certification — Our certification program helps UX professionals quickly gain skills
and credibility. By taking 5 courses and passing related exams, practitioners earn
NN/g UX certification and badge, a recognized credential in the industry.
• In-house Training — Many of our courses can be taught at your location and
customized to fit your unique needs. In-house training is ideal for teams that want to
758 [email protected] A Leading Voice In The Field of User Experience Since 1998.
spread user experience perspective throughout a large group and those working on
large projects that need to kick start the creative process and head in the right
direction.
• Consulting — Our experts are available for custom consulting. Our services include
but are not limited to: Guiding critical design decisions to improve the bottom line
• Design Reviews and Competitive Analysis (starting at $38,000 USD)
• Usability testing (starting at $20,000)
• Benchmarking (starting at $45,000)
Publications and Content
Over the years, our experts have developed a comprehensive body of knowledge and UX
resources. We’ve taken the results of our decades of research and distilled it down into
actionable guidelines, best practices and proven methodologies.
Articles and Videos
Over the years, we have created one of largest and most comprehensive sources of free
user experience content and research insights.
• Articles — Each week we publish new articles on current UX topics available to
practitioners around the world at no cost.
• Videos — In addition to our free articles, we produce a variety of short topical UX
videos posted to our YouTube channel weekly.
Reports
Our research library contains more than 60 published reports and books addressing a
variety of topics including but not limited to the following:
• Doing UX in Agile Environments
• UX Design for specific audiences (e.g., children, college students, seniors, people
with disabilities)
• Information Architecture
• B2B Websites
• Corporate Websites
• Ecommerce UX Design
• Marketing Email and Newsletters
• Intranets
• Non-Profit Websites
• University Website
Shop for reports here: https://www.nngroup.com/reports
Our Free Newsletter
Nielsen Norman Group’s Weekly Newsletter includes summaries of our latest research and
insights published each week. To subscribe: https://www.nngroup.com/articles/subscribe