Editor | On 07, Mar 2018
Every business problem is inherently complex. And inherently needs to address intangible â€˜emotionâ€™ issues. Solving complex problems necessitates getting the problem back to a first principles level. The overall TRIZ, Systematic Innovation and TrenDNA processes are intended to help problem solvers do exactly that. The downside of both processes is they demand a certain learning overhead. An overhead that circumstances may mean is unacceptable. The COBRA+ process is intended to fill the gap. It too ensures problem solvers tackle the issues theyâ€™re trying to address back at the first principles level. Figure 1 describes the basic steps of the process:
The process is also template-based in order to swiftly enable problem solvers to work through a logical complexity-embracing sequence of steps without a long learning curve. The overall process forms a cycle, and as such, allows a problem solver to undertake as many iterations as might be necessary to achieve an â€˜appropriateâ€™ solution. The test for what might be classed as â€˜appropriateâ€™ is contained within the process.
A first iteration around the COBRA+ cycle typically begins with C for Compass.
Compass is all about making sure we know where weâ€™re heading. Irrespective of where we think we should be heading, TRIZ tells us that all successful solutions head towards an â€˜Idealâ€™ end state in which all the intended stakeholders receive all the outcomes theyâ€™re looking to achieve with no negative consequences. Put into lay-person terms, every system evolves to a â€˜free, perfect and nowâ€™ evolutionary end point. As may be expected, this end point is more theoretical than practical. From a practical perspective it will typically entail solutions that deliver useful functions â€˜by themselvesâ€™: the ideal software updates itself; the ideal team manages itself; the ideal advertisement targets itself, and so on. The usual manner of interpreting the Compass part of COBRA+ is to encourage problem solvers to think about two â€˜idealâ€™s: one the ultimate â€˜idealâ€™ solution, and then the other the pragmatic â€˜idealâ€™ we wish to achieve in the current scenario.
Next up comes O. O is for Outcomes. When weâ€™re discussing situations involving humans and weâ€™re thinking about â€˜outcomesâ€™, we need to consider both tangible and intangible sides of the story. If weâ€™re smart we should also think about what each of the different stakeholders present within a situation are looking to achieve, and what the people around those stakeholders are trying to achieve. Then, as if weâ€™re not already making life difficult for ourselves as problem solvers, we also need to consider how those outcome needs alter at different stages of the story. The Fast-Moving-Consumer-Goods sector spends a lot of time thinking about â€˜Moments of Truthâ€™, critical moments when, in their case, consumers make decisions about the products being sold to them. In their world, there are basically two Moments of Truth â€“ number one, did the consumer select their product off the supermarket shelf, and number two, when they got the product home and used it, did it work? In other industries, the number and type of Moments of Truth is likely to be rather more complex. The COBRA+ outcome-mapping job, if weâ€™re to do it right, requires us to identify the tangible and intangible outcome needs of each of the stakeholders at each of the Moments of Truth. Taken to the first principles level, the job is easy, and we simply fill out this template:
The time-consuming part is creating one of this tables for each stakeholder at each Moment of Truth. So that we end up with something like the image reproduced in Figure 3.
Next up comes B for â€˜Butâ€™. Hereâ€™s the part of the process where we deliberately force ourselves to run towards the things that will prevent us from achieving all the things weâ€™ve identified we wish to achieve in the previous C and O stages of the process. â€˜Butâ€™ is a short-cut for â€˜yes, Butâ€™. Or we could call it â€˜Barriersâ€™. Itâ€™s about identifying all of the things that we perceive might prevent us from achieving a successful solution. Hereâ€™s the first part of the COBRA+ process where we explicitly start to think about complexity and complex adaptive systems. Normally (i.e. if we hadnâ€™t accepted our business challenge was a complex one) we would be encouraged to go and find the â€˜root causeâ€™ of our problem.
Once we accept that a situation is complex, we have to accept that there is no such thing as a root-cause. The links between cause and effect in a complex system are often remote and inter-connected. The strong likelihood is that the outcomes our system currently delivers are emergent and that what they emerge from is a â€˜conspiracy of causesâ€™. Once weâ€™ve identified each of the â€˜yes, butâ€™sâ€™ preventing us from achieving the outcomes we want (versus the ones we might currently be getting), the heart of the â€˜Bâ€™ stage of COBRA+ involves us mapping the relationships between each of the â€˜yes, butâ€™ statements weâ€™ve been able to identify. Hereâ€™s another important feature of complex systems: itâ€™s not so much the things that determine the behaviour of the system as it is the relationships between the things. The way the process works here is we map the â€˜betweensâ€™ by asking the question â€˜which of the other â€˜yes, butâ€™ perception statements does this one lead to?â€™ We need to answer this question for each of the â€˜yes, butâ€™ perceptions weâ€™ve been able to list. Then we can draw a map of what weâ€™ve done. The map should end up looking something like this:
…which can appear a little intimidating at first (although this particular map is for a somewhat more complex problem than most). What will inevitably appear, however, is at least one loop. And because the map has been constructed based on a list of â€˜yes, butâ€™ statements, those loops (actually only one in this example â€“ in other situations, there may be more) will define the vicious cycle (or cycles) that are preventing us from achieving our desired outcomes. At this point we have found something important: the critical part or parts of the â€˜conspiracy of causesâ€™ that will prevent us from getting to where we need to be. Actually, weâ€™ve also identified something else that may turn out to be important. Looking at the above map, notice the box â€˜Qâ€™ which has multiple arrows pointing to it. This is what we call a â€˜Collectorâ€™. It is one of the important things â€˜drivingâ€™ the vicious cycle. If we combine the idea of loops and collectors, we can also notice that the boxes labelled â€˜simple truths beat complex liesâ€™, â€˜Brexiteers more passionateâ€™ and â€˜Big Beastsâ€™ are not only in the vicious cycle loop, but theyâ€™re also Collectors. This is trying to tell us that, as we transition from problem definition to solution generation, these are the most important areas for us to focus our attention on. In a complex situation, everything is, of course, connected to everything else, but nevertheless, when weâ€™re looking to change the system (hopefully for the better), we need to start somewhere. This â€˜yes, butâ€™ map is designed to navigate us to those places.
We still havenâ€™t solved anything at this stage in the process, but we do now know what the important problems are, so we can begin the transition to solution. This brings us to the R part of COBRA+. R stands for Resources. The job in this part of the process, then, is to make a search for anything (knowledge, things, processes, people, measures, etc) that is either in or around our current system that we might be able to bring to bear to help us to improve the system. In theory, this is the simplest part of the process. In practice it can often require us to do some deep thinking about what we already have that we might not recognise we have. The best heuristic to keep in mind when making this search for Resources is that any time we allow ourselves to add something new to a system, weâ€™ve just made it worse. In that weâ€™ve taken it further away from the â€˜Idealâ€™ we identified in the C-stage of COBRA+. Hereâ€™s another heuristic: 99 times out of a hundred, the resources needed to solve the problem are already there in or around our system, they just havenâ€™t been recognised as resources. Or â€“ important point â€“ they have been things that weâ€™ve viewed as harmful things rather than things that will help us to get to where we want to be. Lack of money, competitors and the person that arrives at meetings apparently intent on disrupting everyone are all things that are easily classifiable as negative things, but as far as our search for Resources is concerned, theyâ€™re also likely to be some of the best opportunities we will have to solve our problem.
Now we arrive at A for â€˜Andâ€™. This is the part of COBRA+ where we do all of the heavy-lifting in terms of solution generation. There are numerous way to do this idea generation job. The simplest, now the C, O and, particularly, B stages have told us where weâ€™re trying to get to and whatâ€™s stopping us, is to simply brainstorm solution ideas. The next simplest is to look to the world of TRIZ and this book and make use of the 40 Inventive Principles. The most effective way is to make use of the Business Matrix since it will allow us to prioritise which of the 40 Principles to use. The â€˜Andâ€™ process, therefore, makes use of the Conflict Abstraction Template (CAT) â€“ Figure 5. The way we start the job of using this template is to equate the â€˜thing weâ€™re trying to improveâ€™ box at the top left of the picture to our Compass â€˜ideallyâ€™ statement. And the thing stopping us are the most important of the â€˜yes, butâ€™ perceptions as defined by the â€˜yes, butâ€™ map from the â€˜Bâ€™ stage of the process. Once weâ€™ve translated this â€˜specific problemâ€™ into the generic improving and worsening parameters offered down the sides and across the top of the Matrix, we can start looking up the relevant Inventive Principles at the intersections between the relevant rows and columns. Then, when we have these Principles, we can begin generating a list of â€˜Andâ€™ solution clues. In true TRIZ (and Design Thinking â€˜divergenceâ€™) fashion, our target here is to generate as many solution clues as possible.
The SI team in-house heuristic is â€˜diverge until it hurtsâ€™. As a minimum, we force ourselves to generate at least five clues from each of the offered Inventive Principles. If weâ€™re feeling particularly motivated, the five will become ten. Or twenty. Thereâ€™s rarely a downside to generating â€˜too manyâ€™ ideas. Forcing ourselves to generate lots of ideas forces us to put aside consideration of the quality of those ideas and to get â€˜out of the boxâ€™ and start thinking about more radical solution directions. The ultimate idea being that, once we start the process of converging on the solutions we might actually consider taking forwards, we will be looking at combinations of the solution clues weâ€™ve generated. A radical clue on its own is rarely going to give us a â€˜silver bulletâ€™ solution, but a radical clue in combination with some of the other clues, is very likely to give us the breakthrough weâ€™re looking for. The â€˜Andâ€™ process is largely a divergent one, but after weâ€™ve â€˜diverged â€˜til it hurtâ€™, thereâ€™s a need to start doing the convergent job of identifying the solution clues (and combinations thereof) that will give us a first insight into how weâ€™re going to solve our problem.
This, finally, takes us to the â€˜+â€™ stage of COBRA+. This is the place we close the loop back to the initial Compass heading we defined. It is all about examining the appropriateness of the insights and solutions that have emerged from the â€˜Andâ€™ solution generation stage. â€˜+â€™ is all about the comparison of where we trying to get to versus where our new solution has got us. Itâ€™s the place where we decide whether we need to go through the whole COBRA process another time, or whether the solutions we have are â€˜good enoughâ€™. There are a number of criteria that â€˜+â€™ expects problem solvers to examine in order to make the decision about whether weâ€™re finished or whether we need to do more work. The typical â€˜+â€™ questions are:
If the answer to any of them is â€˜noâ€™, then we really ought to go back to â€˜Câ€™ and conduct another iteration, either refining our initial Compass heading, or re-defining the problem in terms of where we are experiencing our â€˜noâ€™. A likely scenario for example, is that we enter the â€˜+â€™ stage of the process with a solution that we think is the best thing weâ€™ve ever dreamed up in our lives, but, unfortunately, when we are forced to think about the question, â€˜do we possess a critical mass of resources to successfully execute the solution?â€™ we realise we do not. Now the new problem is either a new Compass heading that focuses on how we might acquire that critical mass of resources, or how we rethink our beautiful solution such that it is achievable with our existing resources.
If weâ€™re operating in true Design Thinking mode, there is no limit to how many times we might find ourselves looping around this COBRA+ process. In reality, what weâ€™re doing is very brain-intensive and therefore energy-sapping. The heuristic in the SI team when weâ€™re working on real problems is â€˜go around the loop once and get a â€˜goodâ€™ solution; force yourself to go around a second time and you get a â€˜greatâ€™ solutionâ€™. Ultimately, it all depends on how much time and energy you have, recognising too, that in a complex environment, you canâ€™t â€˜knowâ€™ what the right solution is until youâ€™ve tested it with your full spectrum of stakeholders. And, again in Design-Thinking and â€˜minimum viable demonstrationâ€™ modes, youâ€™re looking to do that as soon as you possibly can. I.e. the stakeholders are the ultimate arbiters of the first â€˜+â€™ question of â€˜is the solution good enough?â€™ and they can only meaningfully answer that question when weâ€™ve given them something to play with.
As with many things in life, it is often easier to grasp a process by seeing a tangible example rather than by reading abstract theory. The first place youâ€™ll find that is in the forthcoming Business Matrix 3.0 book, where COBRA+ plays quite a big role in the context of complex business problems.