“You’re Going Too Fast” Is Usually Code for “I’m Afraid of Change”

Here’s the pushback that stops improvement dead in its tracks. Your team is implementing Lean practices, fixing what bugs you, adding value to employees and customers. Progress is accelerating. Culture is improving. And then someone says: “We’re going too fast. We need to slow down and think about this.” That comment sounds reasonable. It sounds prudent. But most of the time, it’s actually fear disguised as caution. It’s people protecting their kingdoms, defending their silos, resisting change because they don’t want to lose their comfortable positions.

The question isn’t whether you’re going too fast. The question is whether you’re going fast together toward the right things or going slow toward entropy and decay. Because here’s the brutal truth: slow companies die. Projects that can’t adapt quickly fail. Teams that take months to make decisions get outpaced by competitors who think fast, decide quickly, get to market faster, and sustain velocity. Speed isn’t reckless if you’re going fast together fixing what needs fixing and adding real value.

But we’ve been programmed to think slow is safe. To believe consensus requires endless discussion. To assume speed means sacrificing quality or skipping collaboration. And that programming creates organizations where entropy wins because you can’t outpace decay when every decision takes three months and every change requires approval from people who can’t see where work happens. Meanwhile, your competitors are adapting in days, implementing in weeks, and leaving you behind wondering why your careful approach isn’t working.

The Pain of Speed Bumps That Slow Everyone Down

You’ve experienced this frustration. Your project team identifies a problem that needs fixing. The solution is obvious. Everyone agrees on what to do. And then the process begins. Submit the proposal. Wait for approval. Present to leadership. Answer questions. Wait for more approvals. Schedule implementation. And six weeks later when you finally fix the problem, three more problems have emerged because you were too slow to address the first one.

That’s what happens when organizations optimize for slow consensus instead of fast collaboration. They confuse thoughtful decision-making with endless deliberation. They think careful means taking months when it should mean thinking clearly for days then implementing immediately. And they create speed bumps—bureaucratic processes, approval layers, committee structures—that slow everyone down while thinking they’re preventing mistakes.

Jim Collins addresses this directly when talking about who should be on your bus. He says rigorous not ruthless is important—giving people opportunity to adapt and grow. But there’s one exception that requires ruthless speed: cultural fit. If someone doesn’t share your core values, you must act quickly. Not because they’re bad people, but because keeping them destroys the culture you’re building.

Here’s his full quote: “Let me be clear, rigorous not ruthless is important with one exception: those who do not share the organization’s core values. If you have core values and someone working for you or with you just isn’t aligned with those core values, I would act more quickly. I would not allow that cultural virus to infect the organization.” Every day you wait hoping they’ll change is another day that cultural virus spreads. Act quickly. Remove the infection. Protect the culture.

The System Rewards Slow Consensus That Creates Decay

Here’s what I want you to understand. Most construction organizations systematically reward slow consensus over fast collaboration. We promote people who carefully consider all options endlessly instead of people who think fast, decide with the team, and implement immediately. We celebrate caution that prevents action instead of speed that outpaces entropy. And we create cultures where “let’s think about this more” becomes the default response to every improvement opportunity.

But that slow approach guarantees failure over time. Because organizations, projects, and systems naturally decay. Entropy is always working against you. Problems compound if you don’t fix them quickly. Cultural viruses spread if you don’t remove them immediately. Competitors adapt while you’re still discussing whether to adapt. And the speed bumps you created to prevent mistakes actually guarantee failure by making you too slow to respond to reality.

Think about the four principles of fast companies that actually win. First, think fast—anticipate problems, spot industry trends, put every idea through the grinder with the team quickly. Companies that didn’t spot COVID-19 trends and adapt immediately to webinars, online learning, and remote technology went obsolete. Not because they made wrong decisions, but because they made them too slowly.

Second, make decisions quickly with the group. Create rules, parameters, guidelines that enable rapid decisions. Eliminate bureaucracy. Make information visible, accessible, quick, and relevant. Shape the path so the team can decide together in days instead of months. The key is deciding WITH the team quickly, not deciding alone fast or taking forever to get consensus.

Third, get to market faster than others. Launch your crusade. Build momentum. Use speed as competitive advantage. Set standards before competitors do. Don’t perfect things for eight months while others capture the market. Get out fast, iterate quickly, stay ahead. I’m releasing the Takt planning book in two weeks because being first to market with a definitive book creates advantage that waiting for perfection would destroy.

Fourth, sustain and maintain velocity. Calculate odds, prove direction, then apply resources ruthlessly. Measure with key metrics. Stay close to customers. Don’t believe your own PR. Adapt, improvise, overcome. Keep the speed going not just at launch but continuously so entropy never catches you.

The companies complaining “we’re going too fast” usually aren’t fixing what bugs them or adding value quickly enough. They’re creating Lean cultures, empowering teams, removing waste. And people with little kingdoms feel threatened because speed exposes inefficiency, reveals roadblocks, and eliminates the comfortable positions they’ve protected. So they push back with “slow down” when what they mean is “stop changing things that require me to adapt.”

Going Fast Together Beats Going Slow Alone

Let me walk you through how to go fast without the recklessness that “too fast” critics fear. First, understand that speed with the team is completely different from speed imposed on the team. Going fast together means thinking fast with everyone, deciding quickly as a group, implementing immediately with full buy-in. Going fast alone means deciding without input and forcing implementation. The first creates alignment and velocity. The second creates resistance and chaos.

Second, distinguish between going fast toward the right things versus chasing shiny objects. Fast toward fixing what bugs you? Good. Fast toward taking care of people and customers? Good. Fast toward competitive advantage and adding value? Good. Fast toward the next trendy tool without vetting it with the team? Bad. Fast toward changes that overburden people beyond capacity? Bad. The question isn’t speed alone—it’s speed toward what?

Third, remove speed bumps instead of just pushing harder. The key management question isn’t “how do we go faster?” It’s “what speed bumps can we eliminate that slow everyone else down?” Bureaucracy. Approval layers. Unclear guidelines. Hidden information. Complex processes. When you remove those obstacles, teams naturally accelerate because you’ve eliminated the friction that made them slow.

Fourth, make speed a cultural routine reinforced through human systems. Don’t make fast decision-making a special effort that requires heroics. Make it how you normally operate. Create guidelines that enable rapid decisions. Reinforce quick adaptation through hiring, firing, incentives, recognition. Make it easy, fast, practical, and relevant. Then speed becomes sustainable instead of exhausting.

Here’s what going fast together looks like in practice:

Think fast by anticipating problems and spotting trends with the team, then putting ideas through the grinder quickly to find best solutions. Make decisions quickly by creating clear parameters that enable the team to decide together in days, not months. Get to market faster by launching before perfection, iterating quickly, using speed as competitive advantage. Sustain velocity by measuring what matters, staying close to customers, adapting continuously without believing your own PR.

On my projects, when problems emerged, we ran them through the grinder with the team and implemented immediately. That speed created some of the most remarkable projects because we outpaced entropy, fixed issues before they compounded, and adapted faster than problems could grow.

Why Entropy Wins When You Go Too Slow

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that going fast together toward the right things beats going slow toward entropy and decay.

The current condition is we’re going too slow. We’re not fixing what bugs us. We’re not fixing things hurting our people. We’re not outpacing natural entropy. And we’re not going together—we’re letting individuals slow everyone down with “we’re going too fast” fear disguised as prudence. That guarantees failure because decay compounds faster than slow consensus can address it.

Think about boats heading toward destinations. Even if you’re steering correctly, you’ll sink before arriving if you have too many holes. Sometimes consulting is just showing people the holes so they can patch them and actually reach their destination. The holes are people protecting kingdoms. Bureaucratic speed bumps. Slow decision processes. All the friction disguised as careful consideration that actually just prevents progress.

Patrick Lencioni, Verne Harnish in Entrepreneurship 2.0, books about cascading clarity and alignment all emphasize getting clear then moving fast. But here’s the critical distinction: some organizations use alignment to control everything centrally. Don’t do that. Use alignment and clarity to enable autonomy at company, team, and project levels. Clear boundaries with fast decision-making authority creates speed. Central control creates slow bureaucracy.

The Challenge: Remove One Speed Bump This Week

So here’s my challenge to you. This week, identify one speed bump slowing your team down. One approval that takes too long. One process that creates unnecessary friction. One person pushing back with “too fast” who’s really protecting their kingdom. Remove that obstacle. Create the guideline that enables faster decisions. Address the cultural virus that’s infecting progress.

Ask yourself: are you going fast toward what? If it’s the next shiny thing, stop. But if it’s fixing what needs fixing, taking care of people, serving customers, creating competitive advantage, adding value aligned with your principles and vision—go faster. Don’t let “slow down” disguised as prudence stop you from outpacing entropy.

Get the right people on the bus. Get the wrong people off. Get the right people in the right seats. Then think fast, make decisions quickly with the team, get to market faster than others, and sustain and maintain velocity. That’s not reckless. That’s survival. Slow companies die. Fast companies together win.

As Jim Collins teaches about cultural fit: act quickly when someone doesn’t share core values. Don’t let that cultural virus infect the organization. The same principle applies to speed bumps and resistance disguised as caution. Remove obstacles quickly. Go fast together. Outpace entropy before it destroys what you’re building.

On we go.

Frequently Asked Questions

How do I know if someone’s “slow down” concern is legitimate or just fear of change?

Ask what specific risk they’re trying to prevent and what evidence supports that risk. Legitimate concerns identify concrete problems with proposed changes. Fear-based concerns are vague warnings about moving too fast without specific risks. The difference is evidence versus emotion.

Won’t removing approval layers create mistakes from hasty decisions?

Approval layers don’t prevent mistakes—they just slow them down and make them more expensive to fix. Fast decision-making with clear guidelines and team involvement catches mistakes earlier when they’re cheaper to correct. Slow bureaucracy creates bigger mistakes that take longer to discover.

What if going fast exhausts the team instead of energizing them?

Going fast toward shiny objects that overburden capacity exhausts people. Going fast together fixing what bugs you and removing friction energizes people because they see progress instead of drowning in problems. The key is speed toward things that help people, not speed that burdens them.

How do I balance thinking quickly with thinking deeply about complex decisions?

Deep thinking doesn’t require slow timelines. You can think deeply in days if you have clear frameworks, involve the right people, and eliminate bureaucratic delays. Most “slow and careful” processes are actually shallow thinking spread across months by unnecessary speed bumps.

What if I fire someone for cultural fit and they were actually just struggling with a bad system?

Jim Collins specifically says rigorous not ruthless—give people opportunity to adapt and grow. But cultural fit is different from struggling with systems. If someone doesn’t share core values after you’ve given them clear expectations and support, that’s a virus to remove quickly. Don’t confuse system failures with cultural misalignment.