OVO Logo
OVO Views
Conversations about Innovation
May 2007 - Vol 1, Issue 11
In This Issue
Sign Up
Quick Links
Greetings!
OVO logo

Welcome to the OVO innovation newsletter.

For our May issue we'll turn our attention to the task of organizing a successful innovation initiative.

While there are a host of processes, tools and techniques to help your organization become more innovative, we find most often that the real challenges to becoming more innovative are based on culture, organization and motivation. So before we worry about processes, software, techniques and other "downstream" enablers, let's consider defining the scope and responsibilities of an innovation initiative in a charter, examine who is responsible for innovation and how that responsibility is managed, and identify some early staffing needs for an innovation team.

Taking these steps will help your innovation initiative get off the ground more quickly and with more success.

In our last newsletter we noted that there are a number of innovation conferences in the spring, and that one of the largest - the Front End Conference - was rapidly approaching. We attended the Front End conference in Boston May 9 - 11, and can provide the following brief recap, for those of you unable to attend.

What we liked

If you have the chance to hear Gary Loveman from Harrah's talk about innovation in the gaming industry, we'd highly recommend it. Probably one of the best talks about innovation and using all the tools at your disposal to offer new services, track trends and create a valuable experience.
Also impressive was the keynote by Dustan McCoy from Brunswick on sustaining ingenuity. Brunswick has done a lot of work understanding customer wants and needs and using that information to create innovative new products.
We always like to hear what Rob Shelton (author of Making Innovation Work) and Jeneanne Rae (from Peer Insight) have to say about their work. Rob has a lot of experience and ideas about measurements and metrics for innovation, and Jeneanne's Peer Insight team is a leader in service innovation thinking.

What we felt could be better

Many of the presentations focused on what went right in an innovation initiative. Very rarely do we hear about what went wrong, yet innovation generates more failures than successes. There needs to be more emphasis on what fails (and what was learned from the failure) as well as what succeeds. Almost every speaker talks about "what worked" in their innovation effort. Did everything work perfectly? What didn't work? When you failed, what did you learn? How much of what we are hearing is "survivor bias" and how much is really what happened and what was intended? Many great innovations were unintentional accidents or resulted from years of "failure" before the success. Let's hear more about the failures and the learnings that came from those failures.

Give the consultants more voice

The Front End, like many conferences, prefers to hear from end customers who talk about one project or issue that they faced and addressed. For good reasons, the conferences often blanch at having consultants speak, concerned the topic may become a sales medium rather than an information channel. However, most consultants have great breadth of understanding of the issues that are common across companies, and those that are unique to certain firms or industries. I think having more presentations from consultants could offer a much more valuable insights. I suspect most attendees can determine when the speaker is "selling" them and when the speaker is providing valuable information. An easy way to weed out the consultants who offer only boilerplate sales material is to allow the attendees to "vote them off the island", so that the firms must provide great insights or they don't get to speak again.

Growing numbers of software vendors

This was the third time we've been to the Front End conference, and each year the number of firms providing idea management, idea capture, idea generation, product portfolio and other types of software grows. Competition is a good thing and indicates that a lot of firms believe there is value in the space. The exhibitors from software vendors ranged from SAP, one of the largest software firms in the world, to smaller one and two man shops. The range of offerings and capabilities is enormous, and indicates a growing opportunity to move from in-house developed spreadsheets and idea databases to more robust, collaborative third party software to fill virtually any need in the idea to product process.

All about the process

Finally, one other take away is that innovation is all about the process. Many firms at the conference expressed the fact that they have plenty of ideas. They lack a method to carefully consider the ideas and move them through a regular, defined process and a way to transition them to new product development or new service development.

One of the biggest problems with innovation in many firms is related to a classic economics theory called the "tragedy of the commons". This article will NOT require an advanced degree in economics, but will tell an interesting story and relate it to some of the challenges in creating an organized innovation approach.

Tragedy of the Commons

The economic concept called the Tragedy of the Commons relates to the days when each small town in England had a "commons" or a shared area for grazing animals that was available to the townspeople. The Commons was jointly owned and each person could graze their animals there. Of course, since no one owned the commons, it was in each person's interest to graze as much as possible on the commons rather than on their own lands, so a useful resource for everyone quickly fell apart into demands by each townsperson for more and more grazing rights, to the extent that the commons were overgrazed and ruined. This, at least, is my interpretation. You can read more about the Tragedy of the Commons here. Note also that Aristotle defined this problem as "That which is common to the greatest number has the least care bestowed upon it"

What's sheep grazing go to do with innovation?

Ok, so you are thinking, what's this commons tragedy got to do with innovation? The last point is the clue - "That which is common to the greatest number has the least care bestowed upon it."

Where innovation is concerned, everyone in the firm wants to participate. After all, who in your firm will claim that they are not innovative? What happens, however, is that everyone claims to be innovating, but the pressures of making the quarter, delivering the products and services and meeting customer expectations squeeze out innovation as a priority. So while everyone wants to be involved, no one is responsible and there are too many other demands on these teams. Innovation is simply too important to be left to chance. Many times you've heard "what gets measured gets managed". In this case, when everyone is innovating but no one is measured on the results, little innovation gets done effectively.

What can be done to avoid a "commons tragedy"? Better definition of the innovation responsibilities and tighter evaluation and measurement of the outcomes. In many cases, we recommend a central innovation team to provide common processes and tools, and to provide visibility for ideas and oversight of the innovation capability of the firm. While many teams "can" innovate, at least one team should be measured on the innovation results.

Innovation is happening now

In most businesses, innovation is happening every day, simultaneously in R&D groups, product teams and business functions. After all, if your firm isn't innovating, it's probably stagnating or even dying. The problem isn't with the innovation effort, but with the coordination, collaboration and links back to strategic intent. A centrally organized and managed innovation team doesn't remove the need and importance of innovation in the different teams within the business, but can help organize and sponsor innovation and align the outcomes to strategic needs.

Tragedy Avoided

The problem with the commons tragedy is that any responsibility that is too widely distributed becomes increasingly less and less important to any specific team. While innovation can, and probably should, happen across your organization in different teams and business functions, it needs to be measured and managed in the same way that other important processes are managed. Otherwise, the result will be a lot of churning for little innovation value.

What's your purpose?

In many firms we speak with, an individual or team has received the direction to "make the firm more innovative". This is a reasonable and worthwhile goal. In most cases, however, few people are able to define what this directive means in terms of budgets, resources, impact to the organization or outcomes.

Being a good employee and wanting to move ahead quickly, the innovation manager plunges in and begins creating ideas and capturing them. He or she publicizes the fact that the team is generating and capturing ideas. Soon, managers and leaders within the business bring opportunities, problems and challenges that require innovative, creative thinking to solve.



That's a good thing, right?

It is absolutely a great response when the innovation team is recognized as a place to think creatively and begin to create new ideas that will change the market. However, we often discover little definition or scope to the ideas that are presented, and no filter or clear set of priorities to help determine which ideas to work on, or where the innovation team's responsibilities begin and end. When this lack of definition is present, the team hops from one "good" idea to another as they are presented, generating new ideas and developing them, only to be directed to yet another topic or idea. After six months or so, the management team shows up and asks what benefit the innovation team is generating, and what they've got to show for the investment. What they have is a grab-bag of ideas that have been partially investigated, with little alignment to the strategic needs of the business.

Developing a Charter

Since innovation is a word that has as many definitions as there are employees in your organization, and since there are few examples of well-defined innovation processes, we encourage our clients to define an innovation charter. This is a document that calls out the roles and responsibilities of an innovation team, and defines the scope and priorities of the team. The charter helps the team define its role and relationship to the rest of the organization - where innovation is taking place anyway - and define clearly what it will, and won't, do. The charter allows the team to define its span of influence and the priorities and types of ideas it will consider, and its role in generating, evaluating and implementing ideas.

We already know this stuff

This "charter" business seems relatively straightforward, but in our experience this concept trips up innovation initiatives more quickly than just about any other issue. Why? Innovation has been done in organizations as an informal, occasional activity and has never been defined or considered an ongoing activity. There are many definitions of innovation within the organization, and everyone wants to be involved. Therefore, there are no clear guidelines, expectations and roles for innovation, and left to their own devices, each function or product group will define innovation differently. Only by creating a defined innovation charter and establishing what is - and what isn't - important and what the team's role is will the team be effective.

Charter Definition

The good news is that it's never too late to create a charter and impose the intent of the charter on the innovation approach. A good charter will include the following items:
  1. Mission of the team
  2. Purpose - what is the team supposed to do
  3. Alignment to corporate strategy
  4. Scope - where does the span of control begin and end
  5. Impact - what impact will innovation have on the business
  6. Customers - who are the customers of the innovation initiative
  7. Priorities - how will the team prioritize its work

With these items in place, the team can communicate its relationship and responsibilities and make better decisions about which ideas, trends or topics to pursue and which to reject.
Now we reach what is probably the most important aspect related to starting an innovation initiative - choosing the "right" people to define and begin the process. Since innovation often starts out as a "bolt on" to existing organizational structures and processes, few people will form the innovation team and those within the team will need to work closely with existing teams and processes to achieve early success. The small team needs people with broad capabilities who can add a lot of value quickly, and often in a one to many situation.


One Riot, One Ranger

My favorite story along these lines deals with a small town in Texas in the 1800s. There was a fight brewing in the town and the mayor was concerned it could breakout into a shooting war between two families. The mayor telegraphed the head of the Texas Rangers and asked for assistance. A few days later the train pulls into town and one Ranger gets off the train. The mayor, pleased that the Rangers responded, asks, "where's the rest of your men?" The Ranger replies, "one riot, one ranger".

The story illustrates that a few people, appropriately applied, can make a big difference. When we look at building and staffing an innovation function, we encourage our clients to start small and identify volunteers who are genuinely excited about innovation, who can think outside the box, who can work collaboratively with others, and who understand how things get done within the business. Each of these attributes is important.
  1. Volunteers - we want people who are excited to work on innovation and willing to go beyond the "9 to 5" mentality
  2. Big thinkers - we want people who aren't limited in their thinking and are willing to challenge the status quo.
  3. Collaboration - innovation teams need to foster collaboration, and they need to be excellent communicators and collaborators themselves
  4. Process oriented - innovation teams need to define and shepherd ideas in a process and encourage the generation, evaluation and conversion of ideas into new products and services


As you can see, this is a tall order for a small team. People who are excited and engaged in innovation and willing to work hard to make innovation succeed are necessary. This often means picking people more for their interest, enthusiasm and capabilities than for their seniority or position in the company.

Roles

Generally speaking we see three critical roles:
  1. Trend gathering and synthesis - this role is responsible for understanding what is happening in the market, the trends that are demonstrated, the met and unmet needs of customers, and organizing that information as inputs to various teams for consideration and for brainstorming
  2. Idea process and data management - this role is responsible for defining the "flow" from idea generation to eventual handoff to a product team or business unit, and establishing the systems, tools and databases necessary to enable the process
  3. Idea Champions/Consultants - this role is responsible for shepherding ideas through the process and working with teams to obtain their insight and feedback. The champion or consultant may also offer ideas and services as an in-house consultant to other teams


Filling these roles with people who demonstrate the key attributes defined above, combined with defining a clear responsibility and charter document, will go a long way toward establishing an effective innovation initiative.

If you'd like to discuss how OVO can work with you to improve your innovation strategies, ideation sessions, innovation processes or software, contact us today at our website or (919) 844-5644 x789. If you enjoyed this innovation newsletter, please pass it along to your friends. If you wish to unsubscribe, please see the link below.

Sincerely,


Jeffrey Phillips
OVO

phone: 919-844-5644 x789

Forward email


OVO | 220 Horizon Drive | Suite 117 | Raleigh | NC | 27615