The Innovation Myth: Why Your Process Map Is Holding You Back

Most organizations treat innovation like a mechanical output, assuming that plugging a design thinking recipe into a team will automatically produce a breakthrough. This is a system error. In their conversation, Dr. Tessa Forshaw and Rich Braden explain that innovation is not a rigid map, but a cognitive state managed through intentional mindset shifts. Relying on standardized innovation recipes creates innovation hesitation, a psychological drag that stops teams from working through ambiguity. By separating innovation from the idea of innate talent or rigid process, leaders can unlock latent creative capacity. This analysis helps practitioners who feel stuck in the process trap move from checking boxes to building genuine problem solving capabilities.

The Hidden Cost of Recipe Based Innovation

Most professional environments treat innovation like a software deployment: follow the steps, run the script, and get the result. Braden and Forshaw argue this is a category error. By selling design thinking as a replicable stamp of authenticity, organizations teach their teams that innovation is an external artifact rather than an internal skill.

The result is a widening gap between an individual's actual creative capacity and their perceived ability. When a team hits the ambiguity of a novel problem, they see a threat instead of an opportunity. This triggers a cognitive reflex, a drag on the system, that causes them to retreat into the safety of the recipe.

"Design thinking and other creative problem solving processes are essentially like thinking strategies full of steps that they want you to take... that kind of process is often sold to businesses as this like replicatable, you know, confirmed stamp of authenticity and validity process that if you do these things you will be creative."

-- Dr. Tessa Forshaw

The Aerodynamics of Problem Solving

To move past the recipe trap, Forshaw compares innovation to the physics of flight. This systems thinking approach shows why teams often stall: they focus on one phase while ignoring the others.

• Lift (Divergent Thinking): The phase of generating abundance and new connections.
• Weight (Convergent Thinking): The phase where ideas are evaluated and distilled.
• Thrust (Executive Function): The discipline of planning, focus, and momentum.
• Drag (Innovation Hesitation): The psychological caution that prevents the system from getting airborne.

The system fails when teams treat these as sequential steps rather than interconnected forces. If you prioritize lift without weight, you get chaos. If you prioritize thrust without lift, you get rigid, uninspired output. The competitive advantage lies in the ability to modulate these forces in real time, rather than following a static map.

Why Immediate Pain Creates Lasting Moats

Braden notes that many engineers and designers fall into the trap of designing for their own definition of cool, ignoring the reality of the end user. The transition to a learn from others mindset is uncomfortable because it requires surrendering the expert ego.

"I started as a software engineer and suffered from this for quite a while where I designed the coolest, most incredible things except that was my view of what those cool, incredible things were and not someone else's. And so I had to learn through some painful experiences that I was less important and they were more important."

-- Rich Braden

This discomfort is the primary filter for competitive advantage. Most teams abandon the process when it gets difficult or requires talking to strangers. Teams that persist through this friction, treating it as a necessary part of the process rather than a failure, build a moat that others, who are still looking for a painless recipe, cannot cross.

The System Responds: Mindset as a Forcing Function

The most non-obvious insight is that you do not need a new process to change your output; you need a new mindset to change your input. Braden and Forshaw describe mindsets as forcing functions. By explicitly choosing a mindset, such as iteration, learning from others, or divergent exploration, the team aligns their focus before the work begins. This prevents the friction that occurs when team members approach a problem with conflicting agendas.

When a team adopts a mindset uniformly, they shift from defending individual ideas to navigating the system together. This is the difference between a group of people playing the same song and a jazz ensemble improvising within a shared structure.

Key Action Items

• Audit Your Innovation Hesitation: Identify the specific moments in your projects where the team defaults to caution instead of exploration. (Immediate action)
• Adopt Single Mindset Sprints: For the next two weeks, assign one specific mindset to a project phase. Do not attempt to solve the whole problem; just practice the mindset. (Over the next 14 days)
• Decouple Process from Outcome: Stop using design thinking as a checklist. Instead, view your existing background as your toolkit. Apply your existing skills through the lens of a chosen mindset. (Ongoing)
• Build Self Efficacy Through Small Wins: Do not try to boil the ocean. Solve one small problem using a deliberate mindset shift. The goal is to prove to yourself that you are capable of the process. (Next 30 days)
• Normalize Failure as Data: Reframe past project failures as necessary iterations rather than wasted time. This builds the psychological resilience required for long term innovation. (12-18 month horizon)