What Actually Happens When You Run a CPS Workshop
I've facilitated dozens of creative problem solving sessions across tech companies, nonprofits, and government agencies. The theory looks clean on paper. The reality usually involves a room full of people who would rather be anywhere else. The method itself isn't complicated, but executing it without turning into a waste of everyone's time requires a level of discipline that most facilitators skip. The process breaks into a few distinct phases. You start by clarifying the actual problem, not the one people assume they have. Then you generate data through structured ideation. After that, you develop strong solutions and finally plan actionable steps. That sequence matters. People who jump straight to brainstorming usually come up with variations of what already exists, which is predictable and useless.
01 Creative Problem Solving Participant Optimist Leaders
This framework is designed specifically for people who are tasked with leading others through unstructured challenges. The "optimist" part isn't about forced positivity. It refers to a documented cognitive bias in leadership where people tend to overestimate the probability of favorable outcomes. That tendency can be leveraged during the idea generation phase to push past the initial filter of "that won't work." I've seen teams stuck for hours on a solution that was viable within 20 minutes once the facilitator explicitly told them to list every possibility without judgment. Here is how the actual workflow runs in practice. First, you define the problem statement using what I call the "framing loop." You write the problem once. Then you ask five people to rewrite it in their own words. If all five versions mean the same thing, you are ready to move forward. If they diverge significantly, you do not proceed until you understand why. I spent three weeks on a project last year because a client team couldn't agree on whether their problem was a staffing issue or a process issue. We resolved it by mapping every decision point on a whiteboard and tracking where delays actually occurred. The staffing hypothesis was wrong. Once the problem is locked, you enter the idea generation phase. This is where the optimist leader technique becomes relevant. You set a timer for fifteen minutes and require each participant to produce at least thirty ideas. The volume requirement forces the brain past the obvious answers. Most people run out of reasonable ideas around number ten. Numbers eleven through thirty are where the actual creativity shows up. I usually hear groans at this stage. They stop after about three sessions.
The next phase is solution development. You take the generated ideas and apply criteria to evaluate them. The standard approach uses feasibility and impact as two axes. Ideas that score high on both go into the execution pipeline. Ideas that score high on impact but low on feasibility are archived. I recommend archiving rather than discarding because a second project often has different constraints that make the previously infeasible option workable. I keep a running document of archived ideas and review it quarterly. About twelve percent of archived ideas eventually become viable solutions when conditions change. Data collection during the process should be minimal but intentional. You do not need hours of interviews or elaborate surveys. A single structured session with five to eight people who actually interact with the problem produces more useful information than weeks of peripheral research. I ran a problem solving exercise for a logistics team once where the entire diagnostic phase took forty-five minutes. The warehouse manager described the bottleneck in two sentences while walking me through the facility. Something I would have paid a consultant twenty thousand dollars to tell me. There is a significant pitfall that beginners in this method keep falling into. They treat the optimist leader component as motivation rather than methodology. The optimism framing is a tool to suspend the inner editor that kills ideas prematurely. It is not about cheerleading. When I work with teams that misunderstand this, the ideation phase produces sanitized suggestions that everyone already agrees on. Those suggestions are useless for anything beyond a team building exercise.
Get the Full Details
Another counter-intuitive finding from my experience is that the most effective problem solvers in these sessions are often the quietest participants. The dominant voices in a room will naturally claim the easy ideas and steer the conversation toward familiar territory. I deliberately seat introverted participants closer to the facilitation area and give them structured turns to contribute before open discussion begins. This simple seating arrangement has consistently produced higher quality solutions in my sessions. The data supports it, though I have never bothered to publish that finding formally. The planning phase is where most CPS programs fail. Teams generate good ideas and then drift into endless meetings about implementing those ideas. The solution is to convert each selected idea into a single page action plan before the session ends. One page. Problem statement, proposed solution, required resources, timeline, responsible party, and success metric. No exceptions. If a participant cannot fill out one page during the session, the idea is not ready for execution. That constraint has saved me from committing to half a dozen projects that would have fazed out within three months anyway. The method has clear limitations. It does not work well for problems that require deep domain expertise that cannot be acquired through group ideation. Medical diagnostics, structural engineering failures, and regulatory compliance issues often need specialists rather than creative thinking sessions. I have tried to apply CPS frameworks to architectural safety reviews and it produced nothing useful. You need engineers for that, not ideation workshops. The framework works best for organizational problems, process inefficiencies, and product development challenges where multiple perspectives genuinely add value.
Training materials for this approach are widely available but most of them are padded with filler content. The core methodology can be understood in under an hour of focused study. The application takes years of practice. If you want to learn the fundamentals, look for resources that emphasize the framing loop and the idea volume requirement. Those two components are the ones that most people get wrong and they are the ones that matter most. Everything else is implementation detail. I recommend starting with a small problem you can solve in a ninety-minute session. Do not attempt this method on your most critical organizational challenge as your first use. The learning curve is steeper than the materials suggest. A controlled practice run with low stakes will reveal your personal gaps as a facilitator before you embarrass yourself in front of senior leadership. That happened to me in 2019 and I have been careful since. The participant guide that accompanies most formal training programs is adequate but generic. The real value comes from adapting the framework to your specific organizational context. A healthcare environment requires different constraints and evaluation criteria than a software company. The underlying structure remains the same but the application shifts considerably. I modify my templates for every industry I work in because the default versions assume a business context that does not apply universally.
One final note about measuring success. The standard metric people use is whether the team produced a solution. That metric is wrong. The correct metric is whether the team developed the ability to tackle the next problem without external facilitation. A successful session leaves participants with a repeatable process they can use independently. If they walk away dependent on you for the next challenge, the session failed regardless of whether the immediate problem was solved.
