We hear a lot about the need to break down silos, to look outside of the usual venues for innovative ideas, and to embrace new points of view. In this day and age, we have access to more information from more sources than ever before. At first glance, it would seem that the task of collecting different ideas and points of view would be easier than ever.

Unfortunately it doesn't always play out that way. Because there is so much information out there, the new challenge is in filtering out what is relevant from what is not, and this task is as daunting as finding new information used to be. Think about this the next time you search for information. How are you determining the relevance?  What are your filters? I do believe that people need filters to help them to cut through all the daunting information out there.  However, what I'm finding is that it is now the filters that are limiting the diversity of the ideas and points of view, rather than the desire to seek out what is new.

Filters are useful to the extent that they are used to focus the mind to recognize relevant information. But how often do you notice when people are using irrelevant filters? For example, if a certain author or expert provided useful information in the past, their point of view may be less likely to be questioned in the future. It becomes a shortcut that is intended to save time, but can result in blind following and group think. As I've said before, there is no excuse for not thinking about what you are doing. Especially in the realm of innovation, every problem is unique and a new filter must be created for every query for new information. This doesn't need to take a lot of time, but it does require that you stop and think before blindly accepting or dismissing new information or sources.

What filters are you using as you make decisions about new ideas or points of view? If you ask yourself if they are relevant to your current task at hand, you may be surprised at your answer.

This weekend I read a fascinating article by Columbia professor Dr. Robert Jervis in the Boston Globe.  He wrote about the way our brains make connections, how these connections inform our decisions, and how this process could have contributed to the incorrect decisions the CIA has made when drawing conclusions about terrorist threats.  He made two points that were of particular interest to me.

The first point is his assertion that humans are very good at recognizing patterns and making connections that are relevant to our world view.  In the work I've been doing, I would call this a linear connection.  The second point is that once humans reach a conclusion, they are not very good at questioning their initial assumptions.  They tend to disregard or manipulate data that could call their conclusions into question. (I'm sure we've all had frustrating experiences with this human trait.)

After reading the article, I was struck by the similarities between the problems the CIA is experienceing, and th eproblems many companies have when trying to innovate.  And as is often the case with companies it became clear that, while I'm sure the CIA has plenty of good problem solvers among their ranks, I would bet they are lacking people with good problem-posing skills.  Successful innovators are very good at questioning assumptions, making non-linear, synesthesia-like connections, and posing new problems.  These people are more open to finding the path that reconciles the data they have, rather than paying attention only to the data that reconciles the path they have chosen.  Sound familiar?

All of this then made me question one of my own assumptions.  I believe that people who can make relevant (as opposed to random) connections between seemingly disparate ideas have a heightened ability to make cognitive connections.  I have imagined this very physically, as a brain with more physical connections being made. But is it really this way?  Maybe these people lack the ability to make the well worn connections that others make, resulting in the need to make new connections more often.  Or maybe it's not physical at all.  Is it due to a difference in the way we perceive information, or a tendency to suspend judgment until all data is reconciled?

I don't have an answer as to why this happens, but as I work to build models to objectively select people with good problem posing abilities I'm realizing that the need to identify and nurture their skills is broader than I had anticipated.

We've talked about the difference between the innovation process and the development process in terms of the results they are expected to achieve; the innovation process being used to identify market relevant opportunities for innovation, and the development process being used to efficiently and reliably get offerings into the market.  We've also talked about how different people, and different thought processes lend themselves to achieving these goals. 

What we haven't talked about is how the different processes should enable people to best do their work.  This is where we often see culture clashes in companies who try to standardize performance objectives based on discipline when they should be targeted to the overall objectives they are tasked with achieving.  Let's see how this plays out by examining some common process elements and seeing how they differ between the innovation and development processes.

The complexity of the development process can best be defined by the sheer number of tasks, functions, and people that must be managed.  It is often a project manager's sole job to coordinate and keep track of everything that must happen.  This person also communicates the interrelations between the tasks required of different functions so that the team can proceed toward the goal.  For this reason, quality of work is evaluated based on whether or not the team members complete their required tasks efficiently and according to schedule.  There are well defined parameters for the completion of tasks to hit project milestones.  In fact, every task is planned and scheduled before the project starts, and the project operates under the assumption that when all tasks are completed, the project is done.  As can be expected, the planning process is very involved, but this typically happens once, when the process is being initially determined.  After that, most projects are similar to the first and can follow predictably along the same steps. So, it can be said that the purpose of the development process is to ensure that human error can be engineered out of the system.

The complexity of the innovation process can best be defined by the fact that the team typically has no idea what the tasks should be at the beginning of the project.  This team is guided by an overarching goal, and needs to be flexible and creative enough to do whatever tasks are necessary to collect the information that will help to achieve it.  The fact that a set of tasks worked on the last project may be useful knowledge, but it is certainly not a roadmap for the next project which will have a different overarching goal.  For this reason it is difficult, if not impossible, to map a process step-by-step for a person outside the work process to plan, manage, and communicate.  Quality of work is evaluated on whether or not each person is able to construct logic and create solid rationale leading to recommendations, making sure to voice any logic breaches that come up so that the team can step back and address them.  Milestones are certainly helpful, but they are more useful for the team to structure their thinking, and less useful to determine tasks.  At the end of the day, it can be said that the purpose of the innovation processes is to ensure that intuitive leaps are made transparent, able to be evaluated, and that recommendations can be presented in such a way that the rest of the organization can make use of them.

Think about how your company's development and innovation processes.  Are they different?  Do they try to achieve different goals while using a similar process?

I've been reading several articles lately that discuss different processes for innovation.  They typically center around a few main themes; ethnography, rapid prototyping, open innovation, and other ways to connect market insight with opportunities for new offerings.  And yet when I talk with clients who have tried similar processes, I get mixed responses regarding the results.  Most can point to isolated events that would not have occurred without the new process, but none can say that these processes have increased their ability to consistently connect opportunities for new offerings with the market they are intended to satisfy. 

I'm actually not surprised when I hear this.  Over the past few years I've come to the realization that there is a big, pink elephant in the room regarding innovation processes.  That pink elephant is the fact that some people are better at making non-linear connections between disparate disciplines than others.  Why does this typically go unsaid?  Because the perceptual skills required to make these connections are difficult to identify, define, and measure, let alone codify into a bullet-point job description.  However, everyone perceives the world differently, and better descriptions of process will not turn a linear thinker into a non-linear thinker.

Think of it this way.  No one would argue that everyone has different levels of physical ability.  I can swim, but if I was standing next to Michael Phelps, we wouldn't need to be near the water for anyone to guess who could swim faster.  That's because physical differences are observable, definable, and we can easily measure the results of the output.  Differences in perceptual skill are invisible, but that doesn't mean they aren't real.  The problem is that most organizational processes have been designed to take the human variable out of the system.  In terms of development and other day-to-day processes I think this is a good thing.  But it just doesn't work for developing breakthrough innovations that will connect with the market.

In the next few posts, I'll be reviewing best practices I've developed to identify the right types of perceptual skills for innovation, and connecting them to different disciplinary skills.  For now, start noticing how different people in your company perceive the world around them.  You may be surprised at what you see when you really start looking.

Most organizations have mastered the ability to deliver their products and services reliably and efficiently.  Remember the 99% lists?  As consumers we've come to expect excellence, and companies that don't deliver above and beyond this excellence won't last very long.

Organizations themselves also take these skills for granted.  I'm often reminded of this when I'm working with clients to develop innovation processes.  Many of the people within companies become frustrated that the organization's capacity for change is so low. 

At this point, it's helpful to step back and really think about what your development and manufacturing processes are expected to do.  If you work in a business where 99.9% isn't good enough (most organizations), then expecting the current process to accomodate breakthrough innovation is just not realistic.  Alternatively, expecting that the outcome of the innovation process will be products and services that fit neatly into existing systems is equally unrealistic.  Innovation efforts that implicitly carry either of these expectations will most certainly fail.

Innovation processes require room for experimentation, trial and error, incorporating unpredictable human elements, and all the other things that would bring current development and manufacturing processes to a screeching halt.  It's far better to separate each process, and let each one be what it needs to be.  Your innovation process should result in the identification of new opportunities that can be delivered in multiple ways.  Some may be able to work with slight modifications to existing processes.  Others may require completely new processes. 

Your innovation process should deliver market relevant opportunities.  Your development and manufacturing processes should deliver offerings to the market reliably and efficiently.  The real organizational challenge is managing expectations within the organization for what each process should deliver, and establishing the right connections between them (more on how to do that later).  But don't expect one to deliver on the expectations of the other.