The Case for Slow Thinking in Engineering Teams

But when it comes to decision-making, speed can be deceptive. The fastest thinker in the room isn’t always the best thinker. The loudest voice isn’t always the wisest. And when teams rush to close decisions, they often sacrifice quality for the illusion of momentum.

That’s why we need to make space for slow thinking.

The Seven-Second Rule

In my current team, we’ve adopted something we call the seven-second rule.

At the end of an explanation or proposal, we deliberately let seven seconds of silence hang in the room. It feels awkward at first — seven seconds is surprisingly long when you’re sitting on a call together. But that pause creates space.

It gives quieter voices time to step in. It allows people to formulate a question they might have otherwise let pass. And it stops us from filling every gap with more words, which often just buries the real insight.

Some of the best contributions in our discussions have come in that silence. Without the seven-second rule, they would have been drowned out by momentum and noise.

Why Fast Thinking Dominates

There are good reasons teams default to fast thinking. Meetings often reward the first person to speak, creating pressure to respond quickly. Culturally, we tend to prize decisiveness over deliberation, so speed is mistaken for confidence. And when psychological safety is fragile, people hold back unless they’re certain — which means valuable perspectives never reach the table.

The result? Teams converge too quickly, missing alternatives that could have been stronger.

Psychologists Daniel Kahneman and Amos Tversky famously described two modes of thought: System 1 (fast, intuitive, automatic) and System 2 (slow, deliberate, analytical). System 1 is efficient but prone to bias. System 2 takes effort, but it’s what we rely on for solving complex problems.

In engineering, System 1 often dominates the room — the quick answer, the gut reaction, the loudest voice. Practices like the seven-second rule are ways of nudging teams into System 2, giving time for deliberate thought and better questions to surface.

Learning to Embrace Slow Thinking

For a long time, I saw this as a disadvantage. I thought that because I wasn’t the quickest to jump in with an answer, it meant I was less sharp. In meetings, I’d sometimes hide the fact that I needed more time, or I’d let others fill the silence and convince myself that it was normal.

But over the years, I’ve learned to embrace it. I tell people openly now: I’m a slow thinker, and that’s how I work best. If you give me a little time, the outcome will usually be stronger.

What I’ve found is that naming this openly does two things. First, it sets expectations — people don’t wonder why I’m quiet, they understand I’m processing. Additionally, it gives permission to others who share the same perspective. Once you make slow thinking visible, it stops being a weakness and becomes part of the team’s strength.

The Power of Pairing Fast and Slow

I’ve also learned that slow thinking and fast thinking aren’t opposites in conflict — they can be complementary.

When I’m paired with a fast thinker, it can be a powerful combination. The fast thinker brings energy, momentum, and quick pattern recognition. I bring reflection, depth, and the ability to connect dots over time. Together, we can move both quickly and wisely.

But it only works if both people are aware of the strengths and weaknesses of each style. Slow thinking can look like disengagement if it isn’t explained. Fast thinking can push us down the wrong path if it isn’t balanced. When both sides understand this, the pairing becomes an asset rather than a frustration.

Partnering With AI

More recently, I’ve found another kind of fast-thinking partner: AI.

I’ll often ask AI to sketch options, play devil’s advocate, or summarise trade-offs. It gives me speed and breadth — sometimes in seconds — and then I bring my slow, reflective judgement to bear. Together, we find a stronger direction.

At first, it felt like cheating. But the more I’ve used it, the more I’ve realised it’s simply another form of partnership. The AI provides System 1 energy: rapid generation, connections, and hypotheses. I provide the System 2 work: scepticism, reflection, and context. The strength is in the pairing, not in either alone.

What Slow Thinking Looks Like in Practice

Slow thinking doesn’t mean stagnation. It’s about creating intentional pauses and giving people time to engage more deeply. In my teams, that looks like:

• Silent brainstorming. Everyone writes down ideas before we discuss, so it’s not dominated by the fastest voices.
• Written input ahead of time. If I’ve put together a doc, I’ll share it before the meeting so people can digest it at their own pace.
• Sleeping on it. I’ll often say, “I don’t need a decision now. Let’s revisit tomorrow.” That explicit permission changes the tempo and usually leads to stronger outcomes.

These practices aren’t complicated, but they create space for diverse voices and foster better thinking. And the difference in decision quality is noticeable. Research shows that teams with psychological safety and clear behavioural norms (such as when to pause, or how to raise concerns) report higher performance and job satisfaction¹.

Slow Thinking, Better Flow

Why does this matter for leaders? Because the benefits compound:

• Better decisions. More perspectives, fewer blind spots.
• Stronger culture. Teams feel heard, not steamrolled.
• Fewer reworks. Slower deliberation early prevents costly course corrections later.

And crucially, slow thinking doesn’t mean slow delivery. Studies of group decision-making show that when teams rush without exploring options, outcomes suffer. But when they take time to explore first, quality improves². Similarly, when engineers feel safe to speak up, their creativity and performance rise³.

Slow thinking is not wasted time — it’s an investment in better flow.

Conclusion

As leaders, we often set the tempo. If we always move at the speed of the fastest thinker, we limit what the team can bring. If we create room for slow thinking, we give space for deeper ideas to emerge — and the whole team gets stronger.

For me, what once felt like a disadvantage has become one of my leadership strengths. And when I’m paired with a fast thinker — whether that’s a colleague or even an AI tool — the combination can be even more powerful, as long as we’re aware of the trade-offs.

Sometimes the most powerful thing I can do is nothing at all… for seven seconds.

References

1. Lenberg & Feldt (2018). Psychological Safety and Norm Clarity in Software Engineering Teams.
2. Raoufi, Hamann, Romanczuk (2022). Speed-vs-Accuracy Tradeoff in Collective Estimation.
3. Zadow et al. (2023). Psychosocial Safety Climate as a Predictor of Work Engagement, Creativity, Innovation, and Work Performance.