Archive for the ‘Web Channel Management’ Category

Web Renewal Series: Building a Foundation for Success

Wednesday, August 25th, 2010

by Denise Eisner

Our last post on web renewal examined the different flavours for large scale transformations of a departmental web site. While there are various types and combinations of renewal strategies – content, information architecture and technical – planning their implementation as distinct projects with a beginning, middle and end typically should be regarded as an ominous sign. Treating web renewal as a project means the foundational pieces needed to support the web in a sustainable fashion are weak or perhaps nonexistent. We’ll look at the relationship of web renewal efforts with those pieces to illustrate the optimal path to web renewal success.

Part 2 – Renewal through Constant Change

For large organizations, delivering a web product that is useful and meaningful requires constant change, since the needs and expectations of your users are constantly changing. Large scale overalls of your web presence are sometimes required if you need significant change in direction. The value gained from these exercises, however, will slowly erode if the structures that support the web presence are lacking.

We’ve drawn three simple diagrams to help illustrate why changing your look, content and technology may only get you so far. The first diagram shows an ever expanding gap in your service offering if you take a lights-on approach to your website. The second one shows a similar scenario of service gaps if web renewal projects are carried out in isolation from the management of your foundational structures. The final illustration should be the goal of any organization management a web presence, with the right support in place to evolve alongside the client needs and expectations.

Graph 1

Graph 1

Graph 2

Graph 2

Graph 3

Graph 3

Continual Improvement through the Web Maturity Model

The foundation required to properly manage a web presence can be measured against our Web Maturity Model, which encapsulates a sustainable foundation through seven pillars, each of which plays a critical role in effective Web channel management. The pillars are defined as follows:

Governance – Governance structures define decision-making authority and accountability, typically in the form of persons or groups (committees, boards, working groups, etc.) and are responsible for addressing issues of budget, capacity and ongoing sustainability.

Strategy and Planning – Strategies and plans for the web demonstrate that the organization is making efforts to use the Web effectively, manage and control costs, ensure compliance with relevant statutes and policies and improve service delivery as well as internal business processes.

Roles and Competencies – Developing an effective Web site requires many different competencies and skills working in concert, including:

• Specifying who does what in a given process;
• Specifying the boundaries between different functions in a given process; and
• Specifying accountability for the activities in a given process.

Research-Driven Design – There is increasing recognition that effective Web sites reflect an in-depth understanding of the site’s users and their needs, and that effective Web management requires a commitment to undertaking appropriate research to inform design efforts.

Performance Management – A performance measurement framework defines the means by which the organization will measure success against defined outcomes. The framework should specify which metrics will be used for each outcome, and how the results will be obtained.

Web Standards and Guidance – Almost all federal Web sites are expected to comply with a number of Acts and federal policies, i.e. Common Look and Feel. In addition, standards and guidance should be developed for information architecture, editorial, visual design, IM and technologies.

Technology – The operating systems, applications, programming languages, standards and tools that underpin the organization’s Web development and publishing activities are planned, implemented and evaluated in accordance with desired business outcomes.

Together, these seven components can give your organization the footing it needs to keep pace with the ever-changing needs and expectations of your users and produce a web product that truly delivers. It’s more than just a “web renewal project”: it’s about a program of web management.

Our next post in this four-part series will look at sustainability in web channel management as an antidote to the resource-intensive web renewal project.

This blog was written by Denise Eisner with support from Alexandra Katseva and Kellen Greenberg.

Web Renewal Series: 6 Departments, 3 Consultants, 4 Blogs

Monday, July 26th, 2010

by Kellen Greenberg

Recently my colleagues Denise, Alex and I met up at the local diner to catch up on our projects. Over eggs and coffee we realized that despite us working on Web-related projects in six different departments, the issues, challenges and at times high stress levels faced by our public sector clients are very similar. We decided to put together a series of blogs to pull together some of the important lessons learned from this aggregate of projects.

This series of Web Renewal blogs is designed to help the Federal Government continue in its quest to deliver meaningful web content to Canadians.

Part 1 – More Than One Piece to the Puzzle

All six of the Web Renewal projects we were working on tackled seemingly similar challenges under similar labels: Web Renewal, Web Renovation, Web Transformation. However, when we lifted the rock to see what these projects were really about, we were presented with a host of different challenges. The rubric of “Web renewal” (or something similar) is being used as an umbrella for what we’re seeing as four different types of project:

  • IA Renewal: Often the stepping stone to a deeper problem, clients are looking to fix a broken Web experience by cleaning up their navigation and underlying information architectures.
  • Content Integration: A lot of our Government clients are still working hard to clean up their footprint on the Web. We’ve helped several organizations forge ahead with taking their 200+ websites and streamline them into a single, cohesive Web presence.
  • Content Renewal: This type of work involves taking all of walls of policy text from your website and turning into useful, findable, readable, meaningful Web content. If only people would spend more time and money in this area!
  • Technical Migration: Moving from one technical platform to another. The panacea of managing and delivering content through a Web Content Management System (WCMS) (or a shinier newer one), often gets embedded with cleaning up content and navigation.
  • None of the above: In some cases, the issue being manifested on the Web is rooted in issues that have very little to do with the Web. Absence of organizational vision or direction, poor leadership, misunderstanding of client needs, or complicated policies and operations can all be brought to the surface by trying to make a usable Web experience. However, just because the website is unclear, doesn’t the mean the problem is with the Web.

What’s the point of all these definitions? Fixing a large GC website can have many different facets to it, and moving forward towards a fix requires a good understanding of what the true problems are, a solid project plan and the support of senior management.

Mixing up the right Web Renewal cocktail from the outset can save a lot of pain and frustration down the road. If you’re looking onto a similar type of project for your organization, here are a few quick notes about how to best shape your project and avoid shooting yourself in the foot.

  • Content Integration and Information Architecture work are a natural fit together.
  • Content Integration and Content Renewal are also a good pairing.
  • Content Integration, Renewal, and IA can all be done at once too, but it’s a big project.
  • Content Renewal on its own or combine with other things is a lot of work. It’s incredibly valuable and necessary work, but a lot of it.
  • Technical Migration is just different. Doing this in lock-step with the uprooting your IA and content can be extremely challenging.

Our next post in this series will focus on some of the foundational pieces often overlooked in Web Renewal projects that can make or break its success.

This blog was written by Kellen Greenberg with support from Alexandra Katseva and Denise Eisner.

Website Rx: content audit

Thursday, July 22nd, 2010

By Denise Eisner

Do you find yourself looking at your organization’s website and wondering: why can’t we just throw it all out and start over? Wouldn’t that be better than working with stale content that no one reads? Or that was architected by previous management who have moved on?

We’ve yet to see a government department act on this impulse, which is fortunate. Starting from scratch undoes months of work and means throwing the baby out with the bathwater. There’s likely some nugget of good content lurking here and there, and more importantly, some relevant thinking about audience segments, content types and tasks. So what is the logical next step for an ailing site?

A web strategy is always a good start. It has the benefit of setting a direction that then guides all future development. Another more hands-on effort (which can occur simultaneously) is a content audit. An audit involves conducting an inventory, identifying ownership and then having owners make decisions about their contents’ future.

Environment Canada recently used a content audit approach to sift through 100,000 pages. They ended up with a much leaner content repository that now stands at a third of the original. By getting rid of the stale content, the relevant content is easier for users to find

During an audit, you want owners to make decisions about their content. No owner willing to step up? Archive the content and take it off the site. No owners willing to make decisions? Give them plenty of notice (and gentle reminders) and explain the end goal (better site management, satisfied users, etc.) but give them a deadline you’re ready to act upon. As in, you’ll remove the content unless they decide. And do so. A reaction sets the stage for a fulsome discussion of the content value relative to the goals of users and desired business outcomes.

If you’re looking at a site with more than 500 pages, this is a full-blown project, requiring a dedicated coordinator and one or more other team members to talk to content owners and catalogue the results. The effort in days will depend on the number of pages, owners and complexity of the site structure. You’ll need well-written criteria to make content decisions and a communications plan to articulate the project to various stakeholders. Management should regularly be apprised of your progress and alerted of any issues or risks requiring their action.

A content audit sounds like tough medicine but it’s the most effective way to deal with sites that have lost their way, without throwing the good pieces in the trash by accident.

Denise Eisner is a consultant in the Government Service Excellence practice. Follow Denise on twitter

MANAGING INFORMATION IN THE PUBLIC SECTOR
April 26-27, 2010
- Architecting for the E-Record, presented by Linda Daniels-Lewis. Read More

Procurement - Talk to us about
TBIPS and SBIPS! Read More