Skip page content

Oxenrider on Synergy / The Center for Creative Teamwork

Oxenrider on Synergy: A Unique Name and Logo

Oxenrider is an uncommon name, a Fourteenth Century trade designation. My ancestors were road builders using teams of oxen to move trees, earth and rocks for road construction. Just as modern day highway contractors are often seen in their pickup trucks, my ancestors rode their teams of oxen to their work, carrying the tools of their trade; thus, the name and my affinity to this quaint metaphor and the logo created for this blog. You could say leading and working with teams is in my “DNA”.

The Center for Creative Teamwork: Seminars and Products

cctlogoThe Center for Creative Teamwork (CCT) is my consulting, publishing and seminar business. For many years, CCT has been the partner of Hillsdale’s Dow Leadership Center to deliver special programs to address customer needs. When Hillsdale exited the executive education business, CCT took over all Executive Education seminars in order to provide uninterrupted service to our customers. Click on the CCT icon at the lower left of this blog to learn more. Read the whole story…

CRCA: The Solution(s)

Screen shot 2010-10-20 at 11.40.05 AM

The Solution is the course of action the team chooses to address The Root Causes and solve the problem. It becomes the strategic objective targeted by The Tactical plan.

The Solution step identifies and describes the strategic direction that will solve, resolve or eliminate the problem. Since problem solving requires a change in thinking or process (different from the thinking and process that created the problem) there will, by necessity, be some level of innovation, creativity and risk in any viable course of action.

The outcome of The Solution Step is the creation of a viable way to eliminate The Surface Problem at the root cause.

To create a solution, review The Alarm, The Expectation, The Surface Problem statements, and The Root Cause diagram.

The probing question I often pose to a team to find a solution is: “If you could, without fear or limits, offer any suggestions to address the root causes to this problem, what would be your suggestions? I also like to advise teams: “Never allow fear, flak, or finances to prematurely eliminate a viable option.

Introspection and dialogue by and between team members are the primary sources of solution generating. Interviewing people for ideas can be useful to some extent, but the primary source of creative solutions will come from the team members themselves who have been intensely involved in the work of problem solving. The creative idea or solution usually comes after a period of intense involvement and commitment. Encourage team members to trust and rely on their own creative insights and solutions.

Generate creative ideas by repeating the cycle three times: Ask for ideas, record on a list, ask again and expand the list or solution ideas. Experience with Creative Root Cause Analysis (CRCA) has demonstrated time and time again that the most creative, innovative and viable solutions are generated in the second and third rounds of solution generating. Challenge team members to probe their subconscious. Encourage individuals to avoid self-censoring and express all that comes to mind, even ideas considered silly or impractical. All ideas are to be suggested without critique.

To facilitate repeated cycles of inquiry, the asking of additional probing questions is usually helpful. Challenge the team to generate a list double in size to the initial list of ideas that resulted from the preceding response to the probing question. The greater the number of options generated, the greater the likelihood a viable and innovative solution will be identified.  Accept and record all ideas without critique. Remember, critical judgment applied too soon stifles creativity. You can eliminate weak or poor ideas later, but if you never get an idea on the table because someone held back, it can reduce the results.

Once the team has exhausted all ideas for possible solutions, the task is to reduce the long list to a short list of viable solutions. Team members discuss, clarify, combine, critique, and integrate ideas. Allow the discussion to take a positive approach and develop the best ideas. It is not necessary to eliminate ideas; simply focus on developing viable solutions. The most viable ideas will continue to attract the team’s attention; others will fall by the wayside for lack of interest. At this stage, it is important to anticipate new problems a solution could generate.

Through discussion, the team works to combine, divide, stretch, and mold new ideas. This is the point at which synergy has the greatest benefit. Through discussing several ideas, an entirely new idea may emerge. Continue the discussion and refinement until a short list of three to five viable courses of action remain.

Prioritize the short list. In most cases, the number one priority item will be the selected solution. If not, the team can select a solution or multiple solutions. This solution will become the expectation against which its success or its problems will be measured.

Manage time pressures. Sometimes, it is best to take a break and get away from the problem. At other times, a break would disrupt the thinking flow. Pressure is nearly always the enemy of creative problem solving.


Screen shot 2010-10-20 at 11.48.58 AM

CRCA: Root Causes (Visualize and Analyze)

Screen shot 2010-10-19 at 8.55.22 PM

Visualize The Root Causes

Screen shot 2010-10-20 at 11.24.29 AM

The Systemic Categories become the roots on the diagram and the verified causes in each category become the tributary roots. Visualize the root causes by recording all of them on the root cause diagram. This rendering is important for perception, and often generates further insight into the problem. While this may appear to be time consuming, the visualization of the category roots with the contributing factors is a powerful tool to drive The Solution Step of the process. Read the whole story…

CRCA: Root Causes (Categorize Causes)

Screen shot 2010-10-19 at 8.55.22 PM

Once The Root Causes have been verified, the next task is to systematically organize them. As a team, group The Root Causes together by like themes, patterns, and similarities. When completed, category names should be determined that will represent the main contributing (primary) roots to the problem. There are no predetermined category titles or number of categories in this method. Some root cause diagrams will have two categories; others three; still others, four and five. The categories will become the titles of the systemic roots on the diagram. Read the whole story…

CRCA: The Root Causes (Verify Causes)

Screen shot 2010-10-19 at 8.55.22 PM

In generating a long list of possible causes, it is understood that many of these will not be valid. The next activity after generating this long list is to pair down the list of causes to a “short list” that only contains actual causes. Read the whole story…

CRCA: The Root Causes (Generate a Long List)

Screen shot 2010-10-19 at 8.55.22 PM

Root Causes are the factors that fuel The Surface Problem. They are the source of the problem condition and the tributary events that bring about the problem. Read the whole story…

CRCA: The Surface Problem

Screen shot 2010-10-19 at 8.33.19 PM

Poorly or ill-defined problems lead to poor solutions. The accurate definition of a problem is essential for effective problem solving. A Surface Problem is an obstacle that blocks the Expectation. This condition is unacceptable. “Surface” implies that the problem is immediate and observable, but the entire problem is not visible. In some terminology, the Surface Problem might also be called the symptom. The cause of a Surface Problem can be a single or multiple, less visible source. The Surface Problem is the difference or the gap between expected results (Expectation) and actual results (Alarm). Read the whole story…

CRCA: The Expectation

Screen shot 2010-10-19 at 8.17.50 PM

In root cause problem solving, the Expectation is the anticipated outcome or result. It is the assumed or explicit benchmark that triggered the Alarm. It is the strategic focus of a viable solution. The Expectation is also the standard of measurement that will be used to define the problem. It may also be understood as a desirable situation or event with desirable consequences. Read the whole story…

CRCA: The Alarm, Part 2

Screen shot 2010-10-19 at 7.45.22 PM

Too many alarms are an indication of more than one problem. However, the team may also identify symptoms or even root causes at this time. Accurate alarm descriptions may be facilitated by a thorough consideration of What, Where, When, How, Who. The following questions may prove useful: Read the whole story…

CRCA: The Alarm, Part 1

Screen shot 2010-10-19 at 7.45.22 PM

An alarm is an indicator of a possible problem. It is a signal or “red flag” that warns or alerts the team of potential difficulties. Problem solving is reactive. Therefore, problem solving is nearly always activated by some kind of alarm, which is the first recognized indication that something may be wrong. Read the whole story…

CRCA Team: The Story Behind the Logo

Screen shot 2010-10-19 at 2.19.49 PM Read the whole story…