Why Your Best Engineers Can’t Ship Fast Enough

By: Alon Cohen & Ai freinds

Introduction

I recently saw a video about the need for speed that made me think about delivery speed, but outside the Tech Talent box. Every company claims its biggest risk is talent shortages. “If we just hire better engineers…”, "If we just had more development resources...". But is it really the only reason for slow deliveries?

Here is what I think I learned over the years.

The single point of failure in almost every development organization isn’t code, architecture, or even headcount. It’s the decision-making culture.

When smart, capable people at every level are afraid to decide, or feel they must escalate every meaningful choice to someone higher up, the entire machine grinds to a halt. The best engineers in the world cannot ship fast enough if their work has to survive endless review cycles from people who haven’t touched the product every day.

I bet you heard the phrase “a camel is a horse designed by committee.” It means that when too many people have a say or try to shape a design, the result often becomes awkward or compromised instead of elegant.

However, this isn’t a “process” problem. It’s a cultural one. And it quietly kills more companies than bad technology ever will.

How Decision Fear Creates Bottlenecks

It starts innocently enough:

• A mid-level engineering manager sees a feature that needs a small scope change.
• Instead of deciding, they schedule a sync with the director.
• The director, wanting to be “aligned,” loops in the VP.
• The VP, now three layers removed from the actual users and code, asks for more data, more options, market research, different vendors, a presentation, animated graphics design, etc., adding more and more stakeholders.

Each escalation adds days or weeks. Requirements drift. Context is lost. By the time the decision finally comes back down, the original problem has changed, and the team is already working on the next sprint, or even worse, the next shiny project.

In many cases, the "hierarchy" (if they understand what was asked) decides that the feature might be needed, but the developers are so busy that, as gatekeepers, they must say no (or he/she cannot ask for more people). By that time, that feature could have been done, tested, deployed, and made a few customers happy.

The people closest to the product, the ones who actually ship it, are no longer empowered to own it. The result? More iterations, more meetings, more “let me check with leadership” Slack threads.

Even elite development teams become order-takers and ticket hoarders instead of owners.

Why Upper Management Is the Worst Place for Most Decisions

The higher you go in most organizations, the further you are from the customer, the code, and the day-to-day reality of building the product. Yet many cultures treat senior sign-off as the gold standard for “good governance,” or a CYA methodology. 

This creates two toxic outcomes:

1. Decision latency explodes. A two-way-door decision (reversible, low-cost) gets treated like a one-way door (high-stakes, irreversible).
   
   
2. Accountability evaporates. When everyone is “aligned,” no one is truly responsible. Mistakes get blamed on “the process” instead of being owned and fixed fast.
   
   
3. Legal eliminates. When it comes to the point where legal get involved, an innovative product is as good as dead. No one wants to take a risk because no one in legal can provide a straight answer, certainly not a corporate lawyer, and certainly not on any innovative technology. (examples are AI, AI Voice Agents, Transcription Agents, and so on).

Real Competitive Advantage Is Talent AND Speed of Decision

You can have the most talented developers on the planet. If your culture punishes mistakes more than it punishes stagnation, you will lose.

Companies that win treat fast, decentralized decision-making as a feature, not a bug.

Real-World Proof: When Decision Culture Wins (or Loses)

NASA vs. SpaceX

For decades, NASA operated with a classic bureaucratic, risk-averse model: heavy documentation, multi-layer approvals, and waterfall-style development. Decisions that should have taken days dragged on for years.

“[At SpaceX] we would make a decision in a single meeting that would take years to reach the same decision point at NASA.”
— Garrett Reisman, former NASA astronaut and SpaceX Dragon program lead

An Oxford University study of 203 space missions found that SpaceX projects took an average of about 4 years from decision to build, while comparable NASA projects took nearly twice as long.

SpaceX vs. Blue Origin

SpaceX sprints with transparent, rapid iteration and a bias toward action. Blue Origin has historically emphasized methodical, consensus-driven progress.

In February 2025, Blue Origin CEO Dave Limp openly cited the problem in an all-hands meeting while announcing a 10% workforce reduction:

“We grew and hired incredibly fast in the last few years, and with that growth came more bureaucracy and less focus than we needed.”

The Boeing Cautionary Tale

Once legendary for engineering excellence, Boeing moved decision-making power toward finance and short-term profit metrics. Engineers, the people closest to the product, were increasingly sidelined. The result: the 737 MAX tragedies and ongoing safety issues, widely linked to this exact cultural failure. Read the Harvard Business School analysis

What a Healthy Decision Culture Actually Looks Like

A culture that prefers some mistakes over stagnation has these traits:

• Empowerment at the edge: The people writing the code (or bolting on the heat shield) make the majority of product decisions, exactly what lets SpaceX outpace NASA and Blue Origin.
  
  
• Clear decision rights: Everyone knows who owns what and when escalation is truly necessary.
  
  
• Psychological safety around reversibility: “We can fix this in the next release” (or next flight) is treated as a feature, not a failure.
  
  
• Leadership that stays out of the weeds: Senior leaders set strategy, context, and guardrails, then get out of the way.
  
  
• Metrics that reward speed and learning, not just zero defects.
  
  
• Small teams, with minimal overhead that value cross-collaboration, meaning they can introduce small projects to other teams with specialized knowledge as quick interruptions, and receive fast unblocking without reprioritization red tape. In other words, operating with a true “we’re on the same team” mindset.

If You Are in a Position to Fix It in Your Own Company

Start small and be brutally honest:

1. Audit your last five major features. How many decisions were escalated unnecessarily?
   
   
2. Introduce the Type 1 vs. Type 2 framework in your next leadership offsite.
   
   
3. Give teams explicit decision-making authority and protect them when they exercise it (even if the decision proves imperfect).
   
   
4. Kill the phrase “Let me run this up the flagpole.” Replace it with “You own this, ship it.” As a lead back your team decisions as if they are yours. 
   
   
5. Measure decision speed the same way you measure velocity or quality.

Conclusion

Talent is the bare minimum.

The companies that dominate the next decade won’t necessarily have the smartest engineers; they’ll have the ones who are allowed (and expected) to make decisions without waiting for permission from someone three layers removed from the product.

NASA, Blue Origin, and Boeing all had (or still have) extraordinary talent. What separated the winners from the laggards was the decision-making culture.

Fix the culture.
Empower the team.
Prefer motion over perfection.

Because in the end, the market doesn’t reward the most careful companies.
It rewards the ones who ship.

###

Drop it in the comments below. The more specific, the better. I read most comments and will try to respond.

Thanks
Alon