Why normalising failure is essential for technological innovation

Historically great leaders in technology have intuitively grasped the underlying psychology of creative teams. And now academics are able to explain the patterns of behaviour. Let's look a one key aspect, that of goal orientation, and what this means for supporting and managing creative teams.

Understanding Learning-Goal vs Performance-Goal Orientation

Psychologists identify two distinct orientations toward achievement. Performance-goal oriented individuals focus on demonstrating their competence and avoiding failure. They prefer clear tasks with predictable outcomes and tend to play it safe when facing uncertainty.

Learning-goal oriented individuals focus on developing their skills and understanding. They embrace challenges, view failures as learning opportunities, and actually perform better under uncertainty because they see it as a chance to grow.

The people drawn to software development, systems engineering, and technical innovation are overwhelmingly learning-goal oriented. This isn't coincidence, creative work requires exactly the mindset that learning-goal oriented people bring naturally. They are the type of people who take chances on out-of-the-box ideas and learn more from failure than success.

But here's the crucial point: these two types require completely different management approaches. Interrupt learning-goal oriented people for a "quick meeting" or impose a new bureaucratic process and you'll see their shoulders slump and their motivation drain away. Even the fun and social Friday drinks can be a frustrating imposition if they're in the middle of a breakthrough.

While traditional command-and-control management works reasonably well for performance-goal oriented people who crave clear direction, it actively demotivates learning-goal oriented individuals who need autonomy, intellectual challenge, and the freedom to experiment, exactly what Edison, Oppenheimer, and Taylor provided instinctively.

The Psychological Safety revolution

The concept of psychological safety was first defined by Carl Rogers in the 1960s as essential for creativity to flourish. But it took Amy Edmondson's research in the 1990s to prove its importance for team performance.

Edmondson made a breakthrough discovery while studying hospital teams. She expected to find that better teams made fewer mistakes. Instead, she found the opposite: the best teams reported more errors. Further investigation revealed that better teams weren't making more mistakes, they were more willing to discuss them openly, leading to faster learning and superior performance.

This research found its most famous application when Google launched Project Aristotle to understand what made their best teams effective. Initially, they looked at composition factors like educational backgrounds and personality types. They found no correlations.

What they did find was that the best teams had two characteristics: conversational turn-taking (everyone spoke roughly equally) and social sensitivity (team members were good at reading each other's emotions). Both are aspects of psychological safety, the belief that one can speak up without risk of punishment or humiliation.

At Xerox PARC, Bob Taylor's famous beanbag meetings exemplified this approach. These weren't simply casual gatherings, they were carefully designed forums that minimised hierarchy and encouraged open and equal participation. One person would present their work while others listened from identical seating, eliminating the subtle power dynamics that could stifle honest feedback.

Taylor also pioneered techniques that transformed potentially destructive conflicts into collaborative problem-solving sessions. When team members clashed over technical approaches, Taylor would ask each person to articulate the other's position until they could explain it to that person's satisfaction.

The research around psychological safety validates what Edison, Oppenheimer, and Taylor had practiced instinctively: creative teams need environments where people feel safe to experiment, fail, and learn together.

Modern applications: Netflix and Amazon's humanistic approach

These principles aren't historical curiosities. Google's Project Aristotle findings have been baked into the approaches used by the most successful technology companies today, though with different emphases and implementations.

Netflix famously prioritises "talent density", surrounding high performers with other high performers and giving them extraordinary freedom to do their best work. Their culture deck emphasises psychological safety, learning from failure, and treating adults like adults. Reed Hastings learned these lessons from his previous company, Pure Atria, which became "overly cautious, risk averse and hierarchical" as it grew.

Amazon's approach differs in implementation but follows similar principles. Their "two-pizza teams" ensure systems thinking isn't lost in large hierarchies. Their "Day 1" mentality maintains the experimental culture that drives innovation. Jeff Bezos famously said that "developers are alchemists and our job is to do everything we can to get them to do their alchemy."

Both companies understand that creative work requires different management approaches. They've systematically designed environments that enable learning-goal oriented people to thrive, just as Edison did at Menlo Park 145 years earlier.

The specific practices vary, Netflix's keeper tests, Amazon's two-way door decisions, but the underlying principles remain constant: provide context, normalise intelligent failure, and create psychological safety for experimentation.

How to Normalise Intelligent Failure and Systematic Learning

Perhaps the most crucial aspect of managing creative teams is changing the relationship with failure. In creative work, failure isn't the opposite of success, it's a prerequisite for it.

This requires cultural change that starts at the top. Leaders must model failure normalisation by sharing their own mistakes and the lessons learned. Edison's approach of celebrating "ways that didn't work" provides a historical template.

Create systems that encourage experimentation while containing blast radius. Amazon's "two-way door" decisions can be reversed if they don't work out. Some teams use tools like Netflix's "Chaos Monkey" that deliberately introduce failures to test system resilience.

The specific technologies may evolve, but the fundamental needs of creative people, for psychological safety, intellectual challenge, collaborative relationships, and meaningful work, remain constant.