De Bono Lateral Thinking Exercises

What Actually Happens When You Try These

I used to run De Bono Lateral Thinking Exercises in team workshops at a logistics company. The results were mixed, but not for the reasons most people expect. The exercises themselves work fine. The problem is almost always how they are delivered and what expectations are attached to them. Edward de Bono's framework isn't about creativity techniques in the traditional sense. It's a set of structured interruptions to vertical thinking. Vertical thinking is linear, deductive, and relies on existing patterns. Lateral thinking is about entering a new pattern. That distinction matters because people confuse the two constantly.

De Bono Lateral Thinking Exercises

The core idea is simple enough. You deliberately disrupt your normal approach to a problem using tools like random entry, challenge, movement, and concept fans. These are not prompts for brainstorming. They are mechanical interventions designed to force your thinking out of established pathways. That's why they feel awkward at first. You are supposed to feel awkward. Here is how I actually ran them. Pick a problem your team is stuck on. Not a big vision statement. Something specific and annoying, like why the return authorization process takes three business days from submission to resolution. Write it on a board. Then apply one tool and only one tool. Don't layer them. People tend to stack methods and end up with noise instead of signal. Random entry is the most useful tool for beginners. You pick a random word from a dictionary or use a dice-based word generator. Something like "bridge." Then you force a connection between bridge and the return authorization problem. This produces terrible ideas at first. That is normal. The point isn't to find the right answer immediately. The point is to break the assumption that the problem only has one obvious framing.

Challenge is different and more controversial. You take something accepted as given in your process and mark it for examination. For example, the rule that a returned product must be physically received before a refund is issued. Most teams treat that as a fixed constraint. Challenge asks whether it is actually necessary or just historically convenient. This tool produces the best structural changes but also the most pushback from people who built their roles around the existing process. Movement is the step after challenge. Once you have identified something worth questioning, you don't just argue against it. You move toward a new position. The trick is that the new position doesn't have to be logically derived from the old one. It just has to be workable. In practice I found that teams skip this step and stay stuck in critique mode for the entire session. Movement forces forward momentum. I encountered a specific edge case that still comes up. A client tried to use random entry on a safety-critical problem involving chemical mixing procedures at a manufacturing plant. The random word was "feather." The team started generating ideas about gentle application and light touch. This was completely useless for the actual problem and dangerously misleading. The workaround was to introduce a filter step. Before any random entry idea is considered, write down the hard constraints of the situation. Safety regulations, physical limitations, regulatory compliance requirements. If an idea violates a hard constraint, discard it immediately. Hard constraints are not there to be challenged in a lateral thinking exercise. They are the boundaries within which you operate.

Another common pitfall is treating concept fans as a replacement for the other tools. Concept fans are useful for expanding outward from a solution. You take your current approach and ask what higher purpose it serves, then generate alternatives at that broader level. The mistake people make is applying concept fans before they have a clear starting point. It generates vague possibilities instead of actionable paths. Use concept fans after you have a working idea, not before. There is a specific type of problem where these exercises reliably fail. Highly technical debugging scenarios where the answer depends on reading logs, tracing state, or checking configuration files. Lateral thinking exercises assume the problem is poorly framed. Sometimes the problem is well framed and the data is simply incomplete. In those cases, applying random entry or challenge wastes time and creates frustration. Use systematic debugging methods instead. The exercises are not a universal problem-solving toolkit. They are a specialized intervention for when framing itself is the bottleneck. The exercises also struggle in environments with strict hierarchical decision-making. If the person who approves changes is not in the room and has a record of rejecting ideas that deviate from standard procedure, the team will self-censor during the exercise. The ideas generated will be safe and predictable. This defeats the purpose. The workaround is to run the exercise in a documented format where outputs are preserved and reviewed separately from the immediate approval chain. Give participants some protection from career risk.

For implementation, I recommend starting small. A single thirty-minute session with four to six people is sufficient. Larger groups produce more ideas but also more social dynamics that dilute the exercise. Write the problem statement clearly at the top. State which tool you are using. Timebox the activity to fifteen minutes per tool. Do not let discussion extend beyond the timebox. The structure is what creates the constraint that forces lateral movement. Without structure it becomes a regular meeting with a random word attached. Available resources online include PDF workbooks and slide decks from various training suppliers. De Bono's original publications like Lateral Thinking and Use of Lateral Thinking contain the foundational material. Many companies create their own facilitator guides based on those texts. The exercises themselves are not proprietary. The specific formatting and workshop structures are what vary between providers. If you are evaluating whether to adopt this approach organizationally, budget for roughly six to eight hours of facilitation across two sessions for a first implementation. The first session covers basics and runs a single exercise on a low-stakes problem. The second session, two to three weeks later, applies the tools to an actual current challenge. Running both sessions in the same week produces shallow engagement because participants have not had time to internalize the mechanics.

The main downside worth noting is that the exercises produce a high volume of low-quality output in the initial rounds. About seventy percent of ideas generated in the first pass are irrelevant or trivial. This is by design. The method requires volume to break patterns. Teams unfamiliar with this often interpret the low quality as failure and abandon the exercise prematurely. Expect the first output to be poor. Skip the refinement phase entirely on the first pass and move to the next tool. There is also a fatigue factor. Running more than two tools in a single session reduces the quality of participation noticeably. Attention drops and people start giving performative answers instead of genuine attempts at pattern disruption. Keep sessions short. Two tools maximum per sitting. When vertical thinking is adequate and the problem is well-defined, these exercises add nothing. If your team routinely faces ambiguous problems with no clear root cause and multiple valid interpretations, the exercises are worth the effort. The return on investment shows up most clearly in strategy sessions, process redesign projects, and product development discussions where the default approach has become routine.

A practical tip that is not in most guides: record the problem statement and the tools used in a shared document. Track which tools produce the most useful output for your specific type of problems. After six to eight sessions you will see patterns. Some tools consistently generate better results for certain problem categories. This personal data is more valuable than any generic guide. The exercises require a facilitator who understands the difference between criticism and movement. A facilitator who jumps in to evaluate ideas during the exercise kills the process immediately. Participants need to generate without judgment for the full duration of each timed segment. Evaluation comes only after the idea generation phase is complete. This is one of the hardest disciplines to maintain in practice. If you want a starting point for implementation, begin with a single problem your team can agree on. Use random entry once. Record everything. Review the output honestly. Decide whether the disruption in thinking was real or superficial. That single session will tell you more than any description of the method.