Brain Hacks for Enticing the Unicorn of Creativity
Adrianna Gugel
·
Chief Product Officer & Co-founder
October 18, 2024
About this blog
  • Unicorns of Creativity: Creativity isn’t a rare gift—everyone has the potential to be creative, especially in software development.
  • Wizards vs. Engineers dynamic: “Engineers” rely on structured thinking, while “wizards” bring spontaneous, intuitive insights; both are essential for innovation.
  • Lessons from Innovators: Some of the greatest minds in history have used creative approaches like balancing focus and relaxation, showing that fostering creativity is key to achieving groundbreaking results.
  • Neuroscience-Backed Brain Hacks: By balancing divergent and convergent thinking, leaders can foster creativity in their teams through intentional practices that create space for both structured problem-solving and spontaneous insights.
  • Unlocking Innovation: When "wizards" and "engineers" work in harmony, teams are better equipped to solve problems, innovate, and push boundaries.

Our society idolizes creativity. And no wonder why – just look at how creative ideas have shaped the world since literally the dawn of time. But the way I was taught about these achievements led to the belief that there are simply “creative people” and “non-creative people” in the world – and girlie, you either have it or you don’t. To me, creative people were like unicorns – I saw them in movies and books, but I never actually met one, and I certainly was not one. In college I did a technical degree and I was taught to structure my thoughts and approaches in a fairly regimented way as the goal was not creativity; the goal was accuracy. So it wasn’t until a few years later when I was entering the world of software development that I realized I had it all wrong. Unicorns are everywhere if you know how to find them.

The Creative Magic of Software Development

Software is all about building something from nothing, and the only boundary is what you can imagine. As an engineering leader, I’m sure you know this better than anyone – while perhaps not the backbone, creativity is the lifeforce of the software world. Working arm-in-arm with software engineers has shown me that creativity is a moment in time, not a permanent state. And no matter how much we want it, creativity can’t be forced.

But how can you intentionally foster the right conditions for creativity? The answer lies in understanding the neuroscience behind how we think, because here’s a secret: I know someone that lives in the magical land of unicorns, and you do too: Wizards. 

Wizards and Engineers: The Neuroscience of Two Thinking Modes

In the realm of cognitive science, different types of thinking are well-documented. A few years ago, a mentor of mine introduced me to the concept of “wizards and engineers”. It was a total game-changer for me. Here’s what she said:

“Inside your brain there are wizards and engineers hard at work helping you problem solve and processing experiences into learnings. Generally it’s the engineers that help you with the daily grind – they are methodical, diligent, and get shit done through the combination of effort and skill.  But you also have wizards – they are spontaneous and wacky, brainstorming off the wall ideas based on intuition and lived experiences. Engineers often get irritated by the wizards, believing they create chaos and disrupt their efforts by provoking racing thoughts and distractions, so they try to shut them out whenever possible. But it’s the wizards that whisper in your ear while you’re vacuuming or taking a shower, giving you a seemingly out-of-nowhere “aha!” moment resulting in a new idea or that solution you’ve been searching for. The key to harnessing creativity is making space for both wizards and engineers to have equal influence on your life as they need one another to help you accomplish the greatest things.”

These two different types of thinking have been comprehensively studied. One of the most popular models comes from psychologist Daniel Kahneman’s Dual Process Theory, which describes two systems of thinking:

  • “Wizard Mode” = System 1 is fast, automatic, and intuitive—ideal for generating creative, spontaneous ideas. It allows you to make leaps, envision possibilities, and approach problems in unexpected ways.
  • “Engineer Mode” = System 2 is slower, more deliberate, and analytical—perfect for logical problem-solving and execution. It’s focused, structured, and necessary for refining ideas and bringing them to life.

These two systems map closely to another popular model in creativity research: divergent (wizard) and convergent (engineer) thinking. But even more intriguing is the way these thought processes correspond to brain activity. Neuroscientists have identified two major networks in the brain:

  • The Default Mode Network (DMN), which is active during rest and mind-wandering. This network is closely linked to creative, spontaneous thought, making it the brain's "wizard mode."
  • The Task Positive Network (TPN), which engages when you're focused on a task. This network governs structured problem-solving, reflecting the "engineer mode."

Thanks for the lecture, Adrianna, but what does all this mean for me as an engineering leader? It means it’s possible to trigger creativity. Every software engineer already embodies both modes of thinking in different situations, but most feel more comfortable in the structured realm of engineer-thinking. But as a leader you can foster the right environment through intentionally shifting between these modes of thinking, which can lead your team to new breakthroughs.

How Past Innovators Have Harnessed the Genius of Creativity

What do Thomas Edison, Alan Turing, and Albert Einstein have in common? Aside from their revolutionary contributions to science and technology, each of these innovators deliberately created conditions that fostered their creativity. 

Thomas Edison, for instance, would take short naps while holding metal balls in his hands with a notepad by this side. The moment he began to drift off, the balls would drop, waking him up. He would immediately jot down any ideas that had surfaced in that twilight state between wakefulness and sleep – a time when the brain is free to wander creatively.

Alan Turing used a different strategy. He’d follow periods of intense, focused work with mindless physical activities like long runs or cycling. These moments of relaxation allowed his mind to make connections he couldn't see when focused. Some of his most brilliant insights came to him during these periods of rest.

Albert Einstein, on the other hand, embraced daydreaming and playing the violin. He’d regularly take long walks while letting his mind wander to impossible thought experiments, like imagining riding alongside a beam of light.  And when he encountered difficult problems he’d turn to playing music, believing that music helped him relax and stimulate new connections in his subconscious to form: “I often think in music. I live my daydreams in music. I see my life in terms of music."

These innovators understood that creativity doesn’t just come from hard work; it needs space to breathe. But that doesn’t mean you need to institute mandatory nap hours or form a company band (though, hey, if it works, go for it). Different things work for different people, and as an engineering leader, your job is to create the space where your team’s wizards can work their magic. So, how do you do that? That’s where brain hacks come in.

Brain Hacks: Get those wizards working!

The wizards-and-engineering mindset has fundamentally reshaped my approach to leadership. It’s not just intuition, it’s genuinely backed by neuroscience. Here’s the process I use, and it has transformed how me and my team work.

Some Traditional Methods to Spark Creativity (Oldies but Goodies!)

  • Psychological Safety: Create a space where your team feels comfortable letting their minds wander, even during working hours.
  • No Dumb Ideas: Encourage “silly” ideas – they might spark someone else’s “aha” moment.
  • Have Grace: Creativity isn’t always immediate, and that’s okay. Give yourself and your team permission to let ideas emerge when they’re ready, and normalize it’s okay if they don’t.

The Simple, Neuroscience-Backed Process for Unlocking Creativity

  1. Timeboxed Intro (5-15 min)

Start with a brief discussion about the problem, goals, and constraints. Let your engineers get to work understanding the limits and planning, while the wizards are listening in the background.

  1. Stop Talking About It

No joke – stop. No decisions are being made today. Schedule a follow-up. Now it’s the wizards’ turn to work their magic.

  1. Give It Time (1 hr to overnight, or even over the weekend)

Ideally, you'd take a break to let your mind wander; but let’s be real, that’s not always possible within the workday. Even if you can’t fully step away, simply letting the problem sit in the background gives your wizards the space they need to work while your engineers handle other tasks.

  1. Rubberduck It (Optional)

This one should be familiar to you! If you have time, try talking out loud about the problem – even if no one responds. It often helps bring clarity, and you create space for both engineers and wizards to contribute.

  1. Keep Calm and Carry On

Circle back to the topic after the wizards have had their space. Whether they’ve produced or not, it’s okay. Life happens on a timeline, so get the best you can and move forward.

  1. Repeat

The more times you follow this process, the more it works.

Trust the process. Neuroscientists and cognitive experts developed these steps, and they work. You know it too: you’ve likely recognized moments in your own life where you’ve followed a similar process and seen results. 

Embrace Both Your Inner Wizard and Engineer

Creativity is the lifeblood of software development, and while I once thought unicorns of creativity were rare, I now know they exist in all of us. Just like the magic that happens when you build something from nothing in code, unlocking creativity requires both structure and freedom. Whether it’s giving your team the time to let ideas simmer or allowing wizards and engineers to work in harmony, you’ve got the tools to foster an environment where those elusive sparks of innovation become reality.

If you take these steps, you’ll be well on your way to building a team that can innovate, solve problems, and push boundaries – whether the wizards are working their magic or the engineers are getting things done.  

Let Flux Help Shoulder the Engineering Load, So You Can Lead with Creativity

But let’s be honest: balancing the wizard-engineer dynamic alongside the demands of engineering leadership is no easy feat. And the more time you spend in your “engineer” mindset – handling the nuts and bolts of daily operations – the less space you have for the kind of creative thinking that drives innovation. The same goes for your team.

This is where Flux can help. We built our platform to take on the heavy lifting of “engineering” thinking: managing structured, methodical tasks like code evaluation, risk identification, and prioritization. By automating these processes, Flux frees up your time and mental bandwidth, allowing you to tap into your wizard mode more often – dreaming up new solutions, fostering a culture of innovation, and leading your team to breakthroughs that would have been impossible if you were buried in the weeds of day-to-day management.

So, lead your team with creativity - let us help and watch the magic happen!

Adrianna Gugel
Chief Product Officer & Co-founder
About
Adrianna

Adrianna Gugel is the CPO and Co-Founder of Flux. With 15+ years of product management experience and a proven history of launching new products and strategic partnerships, Adrianna’s unique blend of business acumen and technical understanding allows Flux to bridge the gap between ideas and achievable results.

About Flux
Flux is more than a static analysis tool - it empowers engineering leaders to triage, interrogate, and understand their team's codebase. Connect with us to learn more about what Flux can do for you, and stay in Flux with our latest info, resources, and blog posts.