Category: Business Operations

GTEC 2010: Igniting Government Transformation!

One of the hottest tickets at this year’s GTEC! – rapid-fire innovative thinking on transformational topics from Systemscope experts and client partners.

Nine (9) Ignite presenters shared thought-provoking and challenging stories about various aspects of government transformation – giving a quick window into a variety of trends that are fueling government transformation. Using 20 slides that advanced every 15 seconds, this intense and unique format kept everyone glued to the topics.

  • Goodbye Librarians… As the amount of digital data and information is growing at a dizzying pace, Linda Daniels-Lewis (Senior IM Consultant, Systemscope) notes it’s getting harder to pinpoint the best information sources. The traditional boundaries of collections management, electronic records management, data stewardship, digital preservation, and digital asset management are beginning to blur – what is the role for digital curators?
  • Five Myths About Performance… Performance Dashboards That Is – Everyone thinks they want a big, beautiful dashboard, but not every organization can handle it. Denise Eisner (Senior Consultant, Systemscope) exposes the dirty myths and offers some salient truths about web performance management in large organizations.
  • Clocks And Clouds: Process Analysis In the Post-Modern World – Clocks are neat, orderly systems that can be solved through reduction; clouds are an epistemic mess, highly irregular, disorderly, and more or less unpredictable. Kellen Greenberg (Director, Integrated Process Management, Systemscope) explains why knowing the difference makes a difference in effective process modeling.
  • $#*! My Dad Says About Business Architecture is Steven Karam’s (Partner and Government Service Excellence Practice Lead, Systemscope) refreshing and provocative look at the trials and tribulations of Business Architecture in the Government of Canada. It also reveals an easy entry point for GC organizations looking to use Business Architecture as a means to linking strategic IM/IT investments to policy and organizational outcomes .
  • RACIs – The Rosetta Stone For Your OrganizationDenis Barbeau (Partner and Strategic Business Consulting Practice Lead, Systemscope) describes how RACI diagrams are used as a foundation in organizational transformation, all the while fostering high levels of engagement, a common understanding of roles and responsibilities, and a consistent vocabulary that mitigates organizational ambiguity.

Systemscope also welcomed two exciting guests to its Ignite session: public policy entrepreneur, open government activist and negotiation expert David Eaves to talk about Open Data: Release the Power Within! and Ron Surette (DG of Information Technology Branch, Library and Archives Canada) who expanded on his theme GC: We’re Going Paperless! … Write That Down.

Back to GTEC 2010 Overview

GTEC 2010

Systemscope returned to GTEC October 5, 2010 with three informative workshops from our consultants paired with innovative public servants. New this year was a fast-paced, provocative Ignite-style session as well as two other workshops showcasing how public sector leaders are using new approaches and methods to address the persistent challenges within Government Transformation and Performance.

Presentations Now Available!



Workshop 1


Igniting Government Transformation:  With Ignite-style presentations from Systemscope experts and client partners David Eaves and Ron Surette, DG of Information Technology Branch, Library and Archives Canada.

Workshop 2


You Can’t Handle The Truth: Management of Performance: With Gina Smith, A/Executive Director of the IT Project Review and Oversight Division, TBS, and Stephen Karam, Systemscope Partner and Practice Lead – Government Service Excellence.

Workshop 3


Everything’s Different, But Has Anything Changed?: Realizing Efficiencies Through Organizational Transformation: With Victor Abele, DG of Citizen Service Strategy, Service Canada, Denis Barbeau, Systemscope Partner and Practice Lead – Strategic Business Consulting and Stephen Karam, Systemscope Partner and Practice Lead – Government Service Excellence

Performance Management at the CRTC

The Canadian Radio-television and Telecommunications Commission (CRTC) website supports the organization’s regulatory activities by providing timely access to public proceedings documents and general interest content particularly suited to consumers of broadcasting and telecommunications services. Its most frequent visitors are representatives of the two industries it regulates, who need the site content for research purposes and to participate in regulatory proceedings.

In the spring of 2009, Systemscope delivered a Performance Measurement Framework and an accompanying research program to support monitoring and reporting on the CRTC site’s performance. The Framework outlined performance indicators with respect to user experience, content and web operations.

Using the Framework as a guide, the Commission worked with a Systemscope analyst to benchmark its existing site performance to understand traffic patterns to the site among new and returning visitors, and then use analytics to improve the user experience.

Case Study – CRTC Performance Management

Yanks Look to Gov Being the Platform for Open Data

by Denise Eisner

Full disclosure: I am a dual citizen of the U.S. and Canada, so any hint of favourtism toward the U.S. approach to open data should be taken with a Memphis-rubbed rib in one hand and a Sam Adams lager in the other.

Open Data is the mantra within government, both here and abroad. In the U.S., government employees, non-profit organizations, developers and community activists are working together on a myriad of data mashups that take rich public data and put it into useful interfaces and onto the platforms people are using. Students with no budgets but seemingly endless spare time are publishing extremely practical applications, while tech start-ups are challenging the notion that data sitting in a dusty archive doesn’t have tremendous value: in fact it can have market value that then translates into new job creation, or what we now call “stimulus.”

The open data fervour reached fever pitch last week at the Gov 2.0 Summit in Washington D.C., where several hundred of the aforementioned groups both from the U.S. and abroad came together to talk about open data, citizen engagement and a slew of related topics. It kicked off with the clarion call by O’Reilly Media’s CEO Tim O’Reilly that “government should think of itself as a platform, to let others build on to deliver additional services to the public.”

With government as “the caretaker for vast stores of information in our national libraries, archives, research laboratories and museums” points out Carl Malamud, founder of Public.Service.Org, those in and outside that conference room should “finish the open gov revolution.” They need open data standards, and need to enforce them. Giving the government’s data to small groups, he says, can turn many small facts into one big truth.

The trouble is that the open data revolution to date has produced a lot of sexy looking government websites, but as Ellen Miller of the Sunlight Foundation notes, not a lot of good data. Data errors and omissions have hobbled many of the U.S. government’s efforts to date. Bloated IT projects with no accountability have undermined efforts to give value to citizens, something that the U.S. government’s CIO is addressing with a deadly serious IT scorecard process that actually halted 30 projects that were in the works and cancelled 12 outright.

What’s the answer? Mr. O’Reilly has it right that government should be the platform, and I would add that the line stops there. Governments should not decide how citizens want their data, but give it freely in formats that can be used across devices and services. ESRI’s president, Jack Dangermond, encouraged government to publish maps as a shared service, one where the data sets are free for anyone to overlay with other data and gain new insights. Developer/blogger Kathy Sierra spoke passionately about creating the killer user, not the killer app. And June Cohen of the powerfully inspiring TED Conferences reached out to the audience to “harness the power and wisdom of crowds.”

David Eaves, the sole Canadian presenter at the Gov 2.0 Summit, stole the show with a fast-paced monologue describing open data successes, all built using available government data. We’ll see David soon at the GTEC conference here in Ottawa as our guest.

As the FCC’s Chairman Julius Genachowski stated, “it’s the public’s data, not ours.”

Denise Eisner is a senior consultant within the Government Service Excellence practice. Follow Denise on Twitter.

The Fallacy of the Innovator’s Ambition – A Call for Tinkerers

Innovation and Transformation.

Wow. Just saying those words conjures up images of wildly successful business models that disrupted industries, technological prowess that stole market shares, visionary products or services that relegated competing and highly capitalized companies into shells of their former self, and even the creation of mega-millionaire pop star phenoms overnight.

How can people tasked with transforming or innovating in their respective organizations perform under this kind of weighted expectation? Indeed, they probably don’t.

I just finished reading a book called “The Upside of Irrationality: The Unexpected Benefits of Defying Logic at Work and at Home” written by Dan Ariely. In it, Ariely, a professor of behavioural economics at Duke University, recounts a number of experiments he has crafted which lend insight into human behavior at work, and at home. One of these insights is particularly relevant when considering the often daunting task of transformation and innovation.

Ariely ran several social experiments to test an individual’s inclination to donate to a cause. He varied, however, the stimulus presented to individuals to elicit a behavioural response. One group of individuals were given a broad stimulus request such as “help the millions of people below the poverty line in Africa” (in our context this would be the dazzling innovator’s ambition) while others were given a specific, and personable, stimulus such as “help Andy, a young boy living in poverty, this is his story”). No surprise, that those in the latter experimental group donated more than those in the former.

What this tells us is interesting. In the face of a large scale problem, people can’t identify with the problem nor contemplate how their small actions contribute to a solution, so they balk under the expectation and don’t act. But, broken up into more personable, and less sizable problems, people will persevere and perform – they will react with a feeling that they can indeed make a difference. The transformation and innovation buzz – the discourse surrounding innovation’s criticality to organizations and the examples used to define what they mean – has done a disservice to the people who are tasked with doing the transformation and innovation. It has placed sizeable expectations on them, increased the distance between today and the goal, and placed the yardstick so high that taking the first step en route to improvement seems futile. The mumblings of “where do I start?” are audible.

The broad domains of service and product innovation, new product development, service transformation and service improvement – call them what you will – need a new image. In almost all cases, transformation or innovation represents “incrementalimprovements to ” or the introduction of something “different”. Indeed, when you look at the synonyms for transformation or innovation, words like “alteration”, “modification”, and “deviation” are supplied which provide a more palatable ambition to strive for. These ambitions are more practical, and more achievable. What is required to succeed is discipline in terms of business analysis rigour, strong leadership of people, direction underpinned by thoughtful road-maps, and the execution of plans. Individuals viewing their ambition in these small steps will look back on their efforts and realize that, from where they started, they have more than likely made significant transformation progress. The significant barrier of a huge expectation will have been removed.

For the Government context, this is a worthwhile thought exercise. Innovation in the public sector context is difficult, oftentimes due to the consequences of failure and the lower tolerance for risk. But this is likely a function of the ambition of innovation being akin to those dazzling examples which I referenced above. Well of course, when viewed in that light, failures can be big because the goal was commensurately large and virtually unattainable under the best of circumstances. When considered in a more more practical context, innovation and transformation efforts can become the byproducts of a disciplined approach to “tinkering”. Yes, tinkering.

So, this is a call to tinker. Tinker with your processes. Tinker with your assumptions. Tinker with your business model. Tinker away in a planned and disciplined way, and when you’re done tinkering, add the tinkerings up. And then tell me about your transformation success story.

Systemscope Volunteer Day: Riding with the Tour for Kids

by Denise Eisner

I’ve done charity bike rides before, including two Boston-NY AIDS Rides in the nineties. That ride lasted three days, covered 434 kilometers and four states, and had the best support crew ever, some in drag. It was the hardest thing I had done in my life, and it represented the kind of challenge that makes you realize that your true potential lies in what you can do, not what you can’t. More importantly, everyone gets a healthy dose of the real big picture.

This year I was again reminded of the big picture on my Systemscope Volunteer Day, when I participated in the Tour for Kids, a cycling odyssey through the rolling hills north of Toronto.

Tour for Kids exists for one reason only — to help children and their families impacted by cancer. Through the generosity of sponsors, the dedication of dozens of volunteers, and the 500 riders who participate, 100% of the donations raised go directly to three camps that let kids with cancer be kids, and heal their hearts and souls toward a full recovery. The ride this year has raised more than $1.2 million, putting a lot of smiles on the faces of children and families that face the daily rigours of cancer.

The challenges faced by a young person with cancer have a strong parallel to the ride. On the ride you face many battles, some small (potholes, flat tires, road kill, rain, heat, cold) and some large (more hills than you can count, aggressive drivers, hail and lightning). There are moments when you want to dismount and throw the bloody bike into the ditch. There are glorious moments when the scenery is breathtaking and your lungs are pumping and everything is working. Then you get a flat. So it goes.

But through it all, you have the support of people around you. On the ride, I had the support of 459 strangers, dozens of volunteers and one wonderful husband. Some were riding 100 kilometers like me, others were going for 160 and the truly possessed rode 200 clicks per day. At the end of each day, we came together for our carb-rich dinner and tear-producing presentations from parents, kids and the professionals who work with these amazing kids at the camps and Sick Kids Hospital in Toronto.

Denise Eisner finishes the Tour for Kids, August 2010

Denise Eisner finishes the Tour for Kids, August 2010

The programs supported by Tour for Kids receive no government money. Government gives the bricks and mortar health care, but the Tour is the emotional top-up that these kids and their families need to keep going. It’s a cause that demonstrates what determination, passion and a common goal can achieve, whether at work or in our personal lives.

We help people like Marisa, shown in this video. God bless her and all the 10,000 kids and their families in Canada braving cancer. You’ll see me back on the Tour next year!

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

Web Renewal Series: Building a Foundation for Success

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

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.