An Industry Canada Perspective

Background Document for a Round Table Discussion

Public Policy Forum

October 6, 1998

Presented by: Kevin G. Lynch, Deputy Minister, Industry Canada

Contents

A. Introduction

B. Factors Demanding Innovation

C. One Department's Approach

D. Challenges Encountered Along the Way

E. Looking Ahead

Annex: A Case Study of Innovation in a Government Setting: Strategis

Abstract:

Many external factors call for innovative behaviour on the part of organizations that wish to continue serving their constituencies effectively. Innovation in a government setting is essential to continuous improvement and to a greater focus on outcomes. To encourage innovation and risk-taking in government, we need to ensure that we have frameworks and incentives in place to support innovation, properly integrated risk and innovation strategies, real empowerment and trust in our people, and a persistent focus on client requirements.


A. Introduction

Clearly, the demands placed on public service managers have changed dramatically over the last ten years. To quote Lawrence Strong's Advisory Committee Report on Senior Level Retention and Compensation:

"Citizens are demanding greater accountability, improved service, greater openness, enhanced accomplishments and, above all, results."

These demands have heightened the pressures on managers in the government to be more innovative personally, and to promote innovation and risk-taking behaviour across their organizations. The question is: Are we providing public servants with the frameworks and toolkits to innovate, which means, inherently, to take risks? Or, rather, have we changed our objectives without adequately realigning incentives? Employees, be they in the public or private sector, will respond rationally to the incentive frameworks within which they work.

B. Factors Demanding Innovation

C. One Department's Approach

In response to these various pressures for organizational and service innovation, Industry Canada has introduced a number of major changes, designed to encourage "new ways of doing things". Some examples:

D. Challenges Encountered Along the Way

Given the demands for change, the initiatives above set out a number of ways we, in Industry Canada, have responded. Other departments have many different initiatives underway, all responding to the same pressures for innovation.

In what follows, we set out some of the challenges encountered in our movement towards becoming a more innovation-based organization.

In sum, becoming more entrepreneurial and innovative represents a major cultural shift. Many impediments have been removed to a new way of doing government business, but some that remain lie in our evaluation and incentive systems. They underpin many of the processes, rules and regulations that tend to inhibit innovation and risk-taking. At the same time that clients are expecting change, and public servants are being encouraged to deliver new ways of doing government business, employees, at times, wonder whether the "underlying frameworks" have been changed sufficiently to support innovation.

E. Looking Ahead

A clear, consistent and new approach to innovation and risk-taking is crucial to shape the sort of behaviour we want in the public service of the future.

Excessive risk-aversion can stifle progress and establish bureaucratic gridlock. It can result in significant underachievement, even harm, not to mention wasted resources. Excessive risk-taking is no better. The challenge is to reach a happy medium. But who gets to make that judgement? How do we handle the "second-guessers" with 20/20 hindsight? How do you create an evaluation system that is flexible across very different fields of government activity? Where is the "right" balanced "tolerance zone" between risk-aversion and risk-taking that is part of our framework and is accepted politically?

The case study of Strategis provided in Annex A is an example of where we feel our achieving the balanced "tolerance zone" was impeded by the traditional audit approach which focussed on processes and controls from a project management perspective, rather than highlighting innovative management, portfolio approaches and results achieved. (December 1997 Auditor General's Report, Chapter 23, Systems Under Development). Had Industry Canada applied a process-oriented management approach to a dynamic project such as Strategis, it would have created impediments to the timeliness and usefulness of the required information, and, we believe, undermined the ultimate success of this initiative.

There is also a concern that the timeframe of some results audits may be shorter than the time required to achieve the public policy objectives. The outcomes of some public sector initiatives typically take longer to emerge than those of the private sector. It follows, therefore, that public service auditing must be compatible, in its timeframe, with the time required for public service initiatives to achieve the desired results. Public service auditors, therefore, cannot necessarily appear on the scene as soon as those in the private sector. If they do, there is a risk that audit approaches and standards are developed prematurely, and are applied before there is a solid understanding of how things actually work best in newly emerging (technology) areas.

For us to truly adopt an outcomes-orientation (i.e. less concern with process, rules and regulations, and activities and outputs), a greater tolerance for risk-taking and more support for managerial innovation are required. To some extent, this shift in attitudes, values and culture can be facilitated by training and development, by drastically changing some of our evaluation processes (for instance, the manner in which we monitor and assess our performance), and, perhaps most important of all, by "walking the talk" as leaders.

We need to develop incentives and frameworks that foster shifts in values and attitudes, so that the resulting behaviour of public service managers is what we expect of them from an innovation and risk-taking point of view. Being inherently rational, people respond to incentives. Creativity and risk-taking can be encouraged in many ways, however the wrong incentives are certain to generate the wrong behaviour.

There are unrealistic expectations among many stakeholders and the public for a perfect public service with no "horror stories". We talk about the need to widely communicate our "success stories", but, too often, the focus is on "problems"—to blame rather than to celebrate success. Celebrating our successes in an open, visible manner helps us all to feel pride in what we do, and motivates public servants towards change and growth.

In short, we must ensure that we have a risk management strategy that mirrors our innovation strategy. The key is that the strategies are integrated and that one considers both the upside and the downside. Risk entails not only potential loss, but also potential gain. And our strategy has to be one that fosters empowerment and trust in our people; one that contributes to shaping a climate in which managers can be entrepreneurial; one that frees staff to concentrate on WHY (i.e. intended impacts) we are doing things, or the intended results we are trying to achieve, rather than HOW (i.e. process) we are doing things. In very basic terms, this means a willingness to accept mistakes.

And we must never lose sight of the fact that client service and client satisfaction are key to any organization's success. Clients must drive public-sector innovation. But this is a two-way street, and requires a greater acceptance of failure, and a greater understanding of the differences between the public and private sector cultures, incentive systems, and operational realities.


A Case of Innovation in a Government Setting: Strategis

Annex to a Background Document for a Round Table Discussion

Public Policy Forum

October 6, 1998


Strategis—A Case Study

Innovation and change are inherently risky. Strategis was initiated by Industry Canada in 1994. It was—and still is—a key element of Industry Canada's new way of doing business based on redirecting and realigning the service content and delivery mechanisms in IC. A multitude of new ideas were brought together, new models and concepts were developed for client services, and these ideas were implemented through advanced technologies.

New product/service development strategies are often highly unpredictable—neither the flow of development nor its end points can be specified with any degree of precision. Creativity lies at the heart of such programs—the creativity of organizations, and the talents, vision, inspiration and instincts of the individuals who work there.

With Strategis, the Department started small and knowingly confronted the risks of rapidly changing technology to develop new relationships with business and consumer clients. Calculated risks, new team-oriented ways of working, rapid, much faster cycle times, competitive internal business case resourcing mechanisms, and a less ponderous management structure were all intentionally used, in order to be at the forefront of the new, fast-moving Internet medium.

It was recognized at the outset that realistic assessments of potential risks and benefits were essential. Twelve months of intense study of client needs, Industry Canada capabilities and technological opportunities preceded the decision to embark on the family of Strategis projects. The danger of paralysis through analysis was ever present and fully recognized. In the end, a multitude of project proposals were considered, some projects were undertaken, some were not. Of those undertaken, some carried a greater degree of risk than others, but no one could say at the start which ones would succeed and which would not.

Managing innovation while minimizing risks was a key challenge. Since we were dealing with new concepts and new technologies, management processes needed to be adaptive rather than prescriptive. Good judgement and diligent management oversight guided the evolution of this innovative project more than the strict adherence to policies and procedures that may or may not have been appropriate. Priorities, objectives, scope and resources were adjusted, in response to evolving difficulties and emerging opportunities, through regular senior management reviews. Certain projects were terminated when it became clear that potential risks outweighed potential benefits, while others were expanded to take advantage of new opportunities.

The perspective taken in measuring success can cultivate a healthy environment to foster innovation and judicious risk taking, or it can become a serious disincentive to change. From a program perspective, Strategis has been a success. It was designed to help Canadian businesses, and from the usage statistics and client feedback, it is clear that we have hit the mark. Strategis and a number of its individual products are the recipients of a wide range of industry awards.

From the perspective of individual projects within Strategis, there were some clear successes and some clear failures. This was to be expected, since at the start, client requirements could only be identified in general terms and technological complexities could only be roughly estimated. Singling out specific failures, with 20/20 hindsight, and without full appreciation of the context and circumstances of key project decisions could do great harm to staff morale, and create a disincentive for risk taking. Our management challenge have been to extract the lessons learned, without associating a stigma of failure on the individuals involved.

Program Audits have a significant impact on how organizations and individual managers respond to risk management challenges. The Strategis Audit conducted by the Auditor General in the Fall of 1997 focused mostly on the management process, rather than on the results achieved. Our performance was measured against Treasury Board's "Enhanced Framework for the Management of Information Technology Projects" of May 1996. While this framework was developed with great care, it relates to large IT projects and is not in our view, an appropriate benchmark for Internet based information publishing projects. Strategis was also faulted for not following the structure in TB's guide for "Creating and Using a Business Case for IT Projects".

From the outset, Strategis, and all its sub-components, were managed on a business case approach. Emphasis was placed on timeliness, because speed counts, and on clarity, since efficient communications was essential for effective decision making. We feel that this less cumbersome approach to project planning and management has served the Strategis development effort very well. Traditional IT project management methodologies would have been impediments to the timeliness of required transformation.

Notwithstanding these shortcomings, the Audit Report did provide useful suggestions for improvements and for reducing risks. However, its approach of measuring management processes against inappropriate benchmarks reduced the credibility of the report in the eyes of project managers and diminished the beneficial impact of useful observations.

Moving from innovation to operation called on a different set of management challenges. As Strategis has become more structured and formal (with some 8,000 daily clients) it is now necessary to adopt a more structured approach to its operation and maintenance. However, new product and service developments will continue on an innovative track in order to support judicious risk taking.

Our challenge will be to implement steps to provide more stringent quality assurance and business planning, and to involve our clients even more closely, but in such a manner as to not bureaucratize the current innovative dynamic and responsive processes that are working well and providing "real time" feedback. We believe that in this way, Strategis will be best able to continue to advance and evolve to meet the changing requirements of Canadians.