Archive for the ‘Government Service Excellence’ 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.

Employee Innovation Program Considerations

Tuesday, June 15th, 2010

By Robert Sibley

On June 14th Stockwell Day announced an Employee Innovation Program to incent public servants to find cost savings in government.  The program would see public servants with a “creative or practical idea” receive a cash award of 10% of the cost savings, up to $10,000.

Directionally, this is positive movement for the GoC.  No matter the discipline, aligning rewards to the behaviours you are seeking is a classic management approach.  Without a profit motive, and particularly given the heightened political risk of failure (see previous post Failing Forward), public servants often have little incentive to push forward ideas for improvements that might lead to cost savings.  This costs the public service dearly.  If you also layer on the fact that with a knowledge based economy it is invariably at the employees’ discretion whether or not they want to contribute their knowledge for the betterment of the organization, it is important to stack as many cards as possible in favour of the employee wanting to contribute what they know.

While the Program is directionally sound, running internal innovation programs can be very challenging.  Here are a list of issues Mr. Day and the Pilot Departments will have to consider as their Programs become operational:

Resourcing: one of the biggest challenges with internal innovation programs is how to free up the right resources to work on new initiatives.  In my experience, these programs create what I call “incremental work packages” to the organization which create a burden often seen as surplus to an individuals’ “9-5″ job.  Each department will need to come up with a strategy that balances the need to free up resources from their current tasks with the need to complete what was originally planned.  Similar to aligning behaviour through incentives, ensuring the contributing to Innovation Program work is on the performance scorecards of resources, and those who own them, is one approach to finding the necessary resource support.

Intra-preneurship is not one size fits all: related to the above, not all individuals who have a great idea are fit to lead its implementation.  Conversely, not all great implementers are creative minds.  Any internal innovation program needs to take into consideration the skills required to pull the idea off.  This may mean, in some cases, that the idea submitters’ involvement in the implementation is not in a leadership capacity.

Governance: while the notion of an innovation program conjures up images of amazing ideas being submitted in terms of their quality, clarity, and alignment to organization objectives, this is often not the case.  Usually, ideas submitted have not had the benefit of time to be fully thought through, and they often miss the mark in terms of their ability to satisfy the organization’s objectives.  A Governance process that uses criteria to evaluate ideas and make portfolio decisions is important to ensure that investment dollars flow to the right kind of idea for the organization, that the organization has a good distribution of ideas, and that the ideas where possible related to one another to amplify their benefits.

Process: as I’ve said before, Innovation is both a product of a process and a process itself.  While an idea often requires random creativity, the implementation of the idea requires an innovation process that is disciplined.  Discipline doesn’t necessarily mean rigid, but structured enough to ensure that an organization can practice and habituate.  There needs to be rigor behind the execution but notional flexibility to ensure the implementation can move in the direction it needs to to realize the benefits originally sought.

The Right Incentive: given the size of government, as well as individual departments within government, the potential for large cost savings for good ideas is significant.  Capping the incentive amount protects the government, yet it could also limit the amount of creativity.  In the public sector context, the reward needs to outweigh the career risk of failure.  There is a risk that a $10K reward cap may limit the ideas to smaller improvements as the reward may not justify the risk of trying to implement larger ones.  This is where leadership in the department needs to step in and begin to change the culture to one that is more tolerant of risk.

Robert Sibley is Director, Service Innovation at Systemscope and can be reached at sibley@systemscope.com

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