The phrase “move fast and fix things” has become a rallying cry in startup culture, a more forgiving cousin of the original “move fast and break things” mantra. On the surface, it promises the best of both worlds: rapid iteration paired with accountability for the mess left behind. But inside early-stage teams operating under tight runway pressure, this hybrid philosophy often creates an invisible tax on team dynamics, one that founders rarely notice until their best engineers quietly start updating their résumés. Understanding how urgency and psychological safety interact is no longer optional for founders who want to scale without sacrificing the people who make scaling possible.
Why the Mantra Sounds Safer Than It Actually Is
“Move fast and break things” was at least honest about its collateral damage. The newer variant, “move fast and fix things,” implies that speed and repair coexist comfortably. In practice, early-stage teams interpret this as permission to ship first and apologize later, with the assumption that cleanup will happen naturally. What actually happens is different: the same three engineers who caused the production incident are also expected to architect the fix, write the postmortem, and absorb the blame during the next all-hands.
Research from Harvard Business School consistently shows that teams under chronic urgency report lower psychological safety scores even when leadership claims to value candor. The problem is not the messaging; it is the lived experience. When postmortems become performance reviews and “fixing things” means a weekend of heroic effort, the implicit message to the team is that speed will be rewarded and reflection will be tolerated.
The Three Hidden Costs Most Founders Miss
1. Decision Fatigue Becomes Quiet Defiance
When every decision carries an implicit deadline, employees stop deliberating altogether. They make the fastest possible call, ship it, and hope no one notices the corner they cut. Over time this produces what organizational psychologists call “quiet defiance” — technically compliant work that lacks judgment, ownership, or craft. The output looks fast. The actual velocity, measured by rework, customer churn, and missed opportunities, plummets.
2. Senior Talent Self-Selects Out
Experienced engineers, designers, and product leaders have options. They have already worked at companies that worshipped speed and paid the price in burnout or reputational damage. When they join a startup, they read the room within their first six weeks. If they observe that postmortems punish instead of illuminate, that “fix” is a synonym for “absorb blame,” they begin their passive job search. The people who remain are either too junior to recognize the pattern or too burned out to leave yet. Either way, the team’s collective intelligence erodes.
3. Innovation Shrinks to a Narrow Band
Psychological safety is not a soft metric. Amy Edmondson’s decades of research at Harvard demonstrate that teams with high psychological safety generate more novel ideas, surface failures earlier, and adapt faster to changing conditions. When urgency crowds out safety, experimentation narrows. People stop proposing ambitious features because the perceived cost of failure outweighs the upside. The team becomes excellent at incremental delivery and incapable of the breakthrough work that early-stage companies desperately need.
Five Practices That Preserve Both Speed and Safety
The goal is not to slow down. It is to build systems that make speed sustainable. The following practices have worked across early-stage teams from seed through Series B.
Decouple Speed From Blame
Run blameless postmortems by default. When an incident occurs, the question is not “whose fault is this?” but “what in our system made this the obvious outcome?” This shift does not eliminate accountability. It relocates accountability from individuals to processes, which is where most failures actually originate. Engineers will take bigger swings when they trust that a missed bet will be treated as a learning event rather than a career event.
Build a Two-Track Urgency Model
Not all work deserves the same urgency. Distinguish between “fire” work (production is down, customers are blocked) and “growth” work (new features, experiments, refactors). Fire work justifies all-hands mobilization and postmortems. Growth work justifies fast iteration and a tolerance for imperfection, but never at the cost of quality standards. Mixing these categories is how “fix things” starts to feel punitive.
Make Repair Visible and Resourced
If your team is shipping at speed, technical debt and customer-facing rough edges are accumulating in proportion. Reserve explicit capacity, ideally 15 to 20 percent of each sprint, for cleanup work. Make this visible on the roadmap alongside new features. When founders treat repair as a strategic priority rather than an afterthought, the team learns that quality is not negotiable even under pressure.
Instrument Psychological Safety Directly
Do not assume you know how your team feels. Quarterly anonymous surveys with three or four targeted questions — “Can you raise concerns without fear?” “Are mistakes treated as learning opportunities?” “Do you feel comfortable taking calculated risks?” — produce data you can actually act on. Share the results transparently, including the uncomfortable ones. The act of measurement signals that the answers matter.
Model the Behavior You Want
Founder behavior sets the cultural ceiling. When a leader admits their own mistake publicly, walks through their reasoning, and commits to a specific change, they give the rest of the team permission to do the same. When a leader hides errors, blames vendors, or reframes failures as successes, no amount of policy will produce psychological safety. Culture is a mirror of leadership behavior, not a function of the handbook.
The Velocity Paradox
Here is the uncomfortable truth that early-stage founders eventually confront: the teams that feel safest often move the fastest, because they surface problems early, share information freely, and recover from setbacks without political fallout. Urgency without safety produces the illusion of velocity. Teams appear busy, deploy constantly, and generate impressive-looking dashboards. But rework accumulates, talent churns, and the company eventually slows in ways no metric predicted.
The phrase “move fast and fix things” is not wrong. It is incomplete. The missing ingredient is the recognition that fixing things well requires the psychological conditions under which people can admit something is broken in the first place. Founders who invest in those conditions early will discover that safety and speed are not opposing forces. They are complementary disciplines, each one amplifying the other.
Early-stage startups do not have the luxury of choosing between velocity and humanity. They have to build companies where both can coexist, because the cost of choosing poorly is measured in the talented people who leave, the innovations that never happen, and the eventual slowdown that no amount of urgency can reverse.
