Caswell Software Advisory Ltd

Rushed decisions often slow projects down

2026-05-12T08:30:00.000Z

Rushed decisions often slow projects down.

After working on complex technical projects for a long time, I’ve come to believe something that sounds counter-intuitive: pressuring decisions in order to speed progress usually has the opposite effect.

Stable, considered direction is often more valuable than moving quickly in any direction.

A pattern I’ve seen more than once is pressure to decide design direction in meetings.

A meeting starts to review a design or discuss what the system must do. Ideas get thrown around, someone suggests an alternative approach, someone else builds on it, and before long the discussion turns into design by committee. It often becomes clear that not everyone in the room has fully followed what’s been discussed - unsurprisingly, as these conversations can become chaotic.

Then comes the pressure to decide before the meeting ends.

“It’s just a small change.” “It’s only a flag.” “We should be able to agree this now.”

From the outside, that looks productive. From a management perspective, it can look like real progress.

In reality, it often creates churn. It creates ambiguity, and ambiguity punishes schedules.

Good engineering decisions rarely happen in the room. They happen afterwards, when someone has time to think through the consequences, check the assumptions, and understand the second-order effects.

When design happens live in a meeting, the cost of change is easy to underestimate. The implementation work, the testing impact, the integration risk, the knock-on effects, the rework effort — none of these are visible on the whiteboard or in an open debate.

I’ve seen projects fall behind not because the engineers weren’t working hard, but because the system never had time to converge.

Experienced engineers sometimes ask for time to think, or push back on late changes. That isn’t resistance. It’s an attempt to protect progress.

Decisions made under pressure often look right in the moment, but turn out worse than those made with time to think.

In complex systems, good decisions rarely come from pressure. They come from giving engineers enough time to think.