Introduction
When people think about creativity, they often imagine:
• artists,
• musicians,
• designers,
• painters,
• filmmakers,
• or writers.
Meanwhile, creativity is one of the most important skills in the IT industry.
Interesting, right?
Because at first glance software development may seem highly logical, technical, and structured. And of course — partially it is.
But if we look deeper, programming is actually constant problem solving.
And problem solving is deeply creative process.
Every day engineers create:
• architectures,
• abstractions,
• workflows,
• interfaces,
• systems,
• optimizations,
• and solutions to problems that often never existed before.
This requires much more than technical knowledge alone.
Creativity is not chaos
I think one of the biggest misconceptions about creativity is the belief that it only appears in spontaneous or artistic environments.
But healthy creativity usually needs structure.
What’s interesting is that limitations often increase creativity rather than reduce it.
For example:
• tight deadlines,
• hardware limitations,
• accessibility requirements,
• business constraints,
• or legacy systems
can force teams to think in completely new ways.
Sometimes the best ideas appear exactly because ideal conditions do not exist.
And honestly — this happens very often in software development.
Different types of creativity
Another fascinating thing is that creativity looks different depending on role inside the team.
Developers may express creativity through:
• architecture,
• abstractions,
• algorithms,
• optimization,
• debugging,
• automation.
Designers may express it through:
• interfaces,
• user experience,
• branding,
• visual systems,
• customer journeys.
Product managers may express it through:
• strategy,
• prioritization,
• problem framing,
• communication,
• business thinking.
Even QA engineers use creativity while discovering unusual edge cases and unexpected user behaviors.
So perhaps creativity is not single skill.
Maybe it is ability to connect things in ways that create value.
Fear kills creativity
I think creativity is deeply connected with psychological safety again.
Why?
Because creativity requires experimentation.
And experimentation naturally includes mistakes.
In unhealthy environments people stop:
• sharing ideas,
• taking initiative,
• proposing improvements,
• asking “stupid” questions,
• or trying unconventional approaches.
Why?
Because fear appears.
Fear of:
• judgment,
• rejection,
• criticism,
• failure,
• embarrassment.
This slowly creates emotionally defensive teams.
And defensive teams rarely create innovative things.
At some point people stop thinking:
"“What could we build?”"
and start thinking:
"“How do I avoid negative reaction?”"
This changes entire energy of collaboration.
Creativity and ego
Another interesting paradox is that ego can both help and destroy creativity.
Healthy confidence allows people to:
• experiment,
• explore ideas,
• take initiative,
• express themselves.
But excessive attachment to ideas creates rigidity.
Sometimes people defend solutions not because they are best — but because they are emotionally attached to them.
This is why emotionally mature creative process requires flexibility.
You must be able to:
• create ideas,
• share ideas,
• improve ideas,
• and sometimes abandon ideas.
Without taking it personally.
And honestly — this is much harder than it sounds.
Boredom and space
Modern IT environments are often overloaded with:
• notifications,
• meetings,
• messages,
• deadlines,
• context switching,
• and constant stimulation.
But creativity usually needs mental space.
Some of the best ideas appear:
• during walks,
• in the shower,
• while skateboarding,
• during workouts,
• while travelling,
• or simply while resting.
Interesting, right?
The brain often solves problems when we temporarily stop forcing solutions.
This is why balance becomes important.
Overworked minds usually become reactive rather than creative.
Creativity and collaboration
I think one of the most beautiful things in teamwork is collaborative creativity.
Moments when:
• designer inspires developer,
• developer inspires product owner,
• QA engineer notices opportunity nobody else saw,
• customer feedback changes entire direction positively.
In healthy teams ideas flow between people instead of competing with each other.
And this creates something much bigger than individual contribution.
Unfortunately ego, hierarchy, and poor communication often block this process.
Sometimes best idea in the room comes from quietest person.
But psychologically unsafe environments prevent these ideas from surfacing.
Creativity requires observation
Another thing worth mentioning is that creativity is deeply connected with observation.
Creative people often notice:
• patterns,
• inefficiencies,
• emotions,
• behaviors,
• contradictions,
• opportunities.
This is why curiosity matters so much.
If you stop observing, questioning, and exploring, creativity slowly decreases.
At some point work becomes purely mechanical.
And while systems and routines are important, completely losing curiosity may slowly reduce emotional engagement with craft itself.
Final thoughts
I think creativity in the IT industry is much more important than many people realize.
Not only for innovation.
But also for:
• communication,
• leadership,
• problem solving,
• collaboration,
• adaptability,
• and emotional resilience.
Because creativity is not only about building products.
It’s also about finding healthier ways of thinking and working together.
Perhaps creativity is not exclusive talent reserved for artists or “gifted” people.
Maybe it is natural human ability which grows when:
• curiosity is supported,
• fear is reduced,
• perspectives are respected,
• and people feel psychologically safe enough to explore.
And maybe the most creative teams are not the loudest or smartest ones.
Maybe they are simply environments where people feel safe enough to think differently.
Soft Skills series
Part 6 of 32. Read more on the Empatalk blog or take the Communication DNA survey at empatalk.app/survey.
Sources and further reading
• Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly. https://doi.org/10.2307/2666999
• van Knippenberg, D., Nishii, L.H., & Dwertmann, D.J.G. (2020). Synergy from diversity: Managing team diversity to enhance performance. Behavioral Science & Policy. https://doi.org/10.1353/bsp.2020.0007