Creativity Is a Spice (Even for Engineers)

Engineers love to insist we're not creative. Then we rewrite the same Flink job five different ways before lunch and call it "just work." Technical creativity is the most-used, least-credited tool we have. It runs in two modes, and most new leads only know one of them.

Problem mode: break your own pattern. Pattern recognition is the gift. Your boss calls an "emergency" meeting and you feel the déjà vu before he finishes the sentence, because you've seen this exact shape five times. Good. The trap is what comes next: you reach for the same fix you always reach for, the quick patch on prod instead of fixing the pipeline that keeps generating the patch. So break it on purpose. Take a move that works in one place and try it somewhere it has no business being. Give the hard feedback at the incident, while it's bleeding, instead of filing it for the quarterly review where feedback goes to die.

de Bono called the antidote the Creative Pause, and there's nothing to it. Fighting on five fronts? Stop for a minute. My youngest tech lead physically cannot do this. The second a voice goes up in the corridor he's already sprinting toward it. I keep telling him the same sentence: don't chase the yelling, take the pause, then choose. To a new lead who only feels useful while doing, the pause feels like negligence. It's the opposite of negligence.

And before you "brainstorm" it with the whole team, don't. Not by default. The research is annoyingly clear that people produce better ideas alone than in a room full of people waiting to talk. Let them think first, then bring it together.

Build mode: structure is a creativity tool, not the enemy of one. A whiteboard and a spreadsheet are where a messy problem turns into a solvable one. Rotting legacy component, stability issues, a stack of support tickets, a six-month rewrite plan, and a team that's understaffed and never owned the thing. Put every factor on the board. Score each one for impact and effort, out loud, until the shape of it is finally visible. Now you can show the stakeholder who only ever sees his own slice, and you can gently block the well-meaning people charging in to "help" while quietly making it worse. I've been that guy. That's how I know to watch for him.

We got handed the title "engineer," and somewhere that became permission to walk in straight lines and follow old runbooks. Wrong lesson. The only thing actually worth banning is running the same approach a sixth time and expecting a different number on the dashboard.