Encouraging Creativity

For two decades, I’ve seen engineering teams tackle incredible challenges. And I've noticed a pattern: the speed of innovation isn’t about having a few brilliant brainstorming sessions. It's about building a culture where creative thinking is woven into the everyday fabric of how we work. It's about making creativity a habit, not a special occasion.

How often do brilliant ideas generated in brainstorming sessions never see the light of day? We invest time and energy in these events, but true innovation is often the accumulation of many small, incremental improvements. And those improvements come from teams where people feel safe to explore, experiment, and even fail without fear of reprisal.

So, how do you move beyond the occasional "innovation day" and build a genuinely creative engineering team? Here’s what I've learned, distilled from successes (and a few hard-won lessons) over the years.

The Problem with “Trying” to be Creative

Let's be honest: telling people to “be creative” is often counterproductive. It feels performative, and it puts pressure on individuals to conjure up brilliant ideas on demand. It's like asking someone to feel inspired. Inspiration doesn't respond to commands.

Many of us fall into the trap of equating creativity with radical, "blue sky" thinking. While that's important sometimes, it overlooks the power of combinatorial creativity - taking existing ideas and remixing them in new ways. This is far more accessible and sustainable.

As the quote suggests, many more people could be doing great work, but often don't actively choose it. It’s not necessarily a conscious decision not to be creative, but a lack of structures and permission to explore.

Shifting from "Innovation Events" to Everyday Practices

Here are some practical strategies that have worked for me:

• Embrace "Small Bets": Encourage your team to spend a small percentage of their time (I’ve seen 10-20% work well) on side projects or explorations that aren’t directly tied to current sprints. This is about allowing them to tinker, learn new technologies, and pursue "what if" scenarios. This feels less risky than a full-blown innovation initiative and yields a steady stream of potential breakthroughs. Providing dedicated time for these pursuits also fosters intrinsic motivation and a sense of ownership, combating the demotivating effects of purely task-driven work.
• "Post-Mortem" with a Twist: We all do retrospectives to learn from failures. But also conduct "success retrospectives." What seemingly small decisions contributed to a successful outcome? This shifts the focus from avoiding mistakes to understanding what enabled success, fostering a positive learning environment.
• The "Yes, And..." Rule: Borrowed from improv comedy, this simple rule encourages building upon each other's ideas instead of immediately shooting them down. It creates a safe space for brainstorming and collaborative problem-solving. It’s surprisingly effective even in highly technical discussions.
• Dedicated "Learning Time": Protect time for developers to explore new technologies, read articles, or attend workshops. This isn’t just about professional development; it's about refueling the creative engine. A stagnant mind rarely produces innovative solutions.
• Rotate Roles & Responsibilities: Breaking up the monotony of repetitive tasks is crucial. Encourage team members to shadow each other or take on new areas of the codebase. This exposes them to different perspectives and challenges, sparking new ideas.

Addressing Motivation and the “Un-Bore” Factor

Boredom is the enemy of creativity. Engineers are motivated when they understand why their work matters. Regularly share customer feedback, demonstrate the value of their contributions, and connect their tasks to the bigger picture.

Furthermore, providing autonomy and ownership over solutions is paramount. Micromanagement stifles creativity, often stemming from pressure to deliver or fear of failure. Trusting your team to make decisions and own their work unlocks their potential and fuels engagement. Challenge and growth are also critical; ensuring everyone on the team is constantly learning prevents stagnation and keeps work interesting.

The Long Game

Building a truly creative engineering team isn’t a quick fix. It’s a cultural shift that requires consistent effort and commitment. It requires leading by example – demonstrating curiosity, embracing experimentation, and celebrating both successes and the valuable lessons derived from failures as learning opportunities.

As the opening quote suggests, focusing on doing great work—work that expands possibilities—is the ultimate driver of creativity. It’s about creating an environment where people are inspired, motivated, and empowered to bring their best ideas to life.

Key Takeaways:

• Embrace Small Bets: Dedicate a portion of time for exploratory projects.
• Foster Psychological Safety: Create a safe space for experimentation and learning from both successes and failures.
• Empower Autonomy: Give developers control over how they solve problems and encourage ownership of their work.
• Connect to Impact: Ensure engineers understand the value and purpose of their contributions.

Start small – encourage one team member to dedicate 10% of their time to a side project this week.