Why Pushing Harder Is Sometimes the Problem: The Engineering Manager's Pacing Framework

Quick Bridge: If you manage a team that feels slow and your first instinct is to add more meetings, more deadlines, or more urgency, this post will challenge that reflex. You will get a concrete decision framework for when to push and when to let it run, plus a practical signal checklist to read your team before you act. If the answer turns out to be yes, there is also a guide to what effective urgency actually looks like.

There is a move that looks exactly like leadership from the outside. You see a gap, you respond. You see slowness, you apply pressure.

You fill dead air with new asks. You follow up before anyone falls behind.

And it is exhausting everyone, including you.

The managers I work with who burn their teams out the fastest are not the ones who are disengaged. They are the most driven people in the room. They believe that constant forward motion is what the role requires. Nobody ever told them there is a question they should be asking before they add any urgency at all.

The Engineering Burnout Pattern Leaders Create Without Knowing It

There is a named leadership style for this behavior. Goleman identified it in his foundational research on leadership effectiveness and called it pacesetting.

Constant urgency. High standards. Always-push. It looks like excellence.

His research found it consistently produced the worst long-term team performance of any leadership style he studied. Not because the work was hard. Because the relentless pressure produced burnout, resentment, and disengagement without evaluation.

The pattern is easy to fall into because it gets short-term results. You push, the team moves. You add urgency, something happens. The problem surfaces later, when the team is too depleted to sustain the pace you need.

Teams operating beyond their capacity see quality and productivity drop, not rise. The agile community has a phrase for this: sustainable pace. Teams that preserve energy accelerate cumulatively. Teams that run at full sprint repeatedly do not.

According to data from high5test.com's leadership burnout research, managers are 36% more likely to report burnout than individual contributors. The leaders applying the most pressure are often the first ones to break.

The One Question That Changes How You Lead

When a manager I was mentoring told me his team wasn't moving fast enough, I asked him one question before offering any advice: what is the actual business need if things stay at the current pace?

He could not answer it. He had been adding pressure for weeks without asking whether more speed was actually required.

That question is the reset point. Before you add anything to your team's plate, before you schedule another check-in, before you send the follow-up message about why the deadline matters:

What is the actual business need right now?

If there is a real need, something specific is at risk. A deadline matters, a gap needs to close, or the business cannot deliver something it has committed to. The next question is: what would we say to the team, or change about their work, to actually address that?

Not more urgency for its own sake. A specific conversation about a specific need.

If there is no urgent need, the right move is to verify direction and let it run. Make sure the team is pointed where it needs to go. Then stop rowing.

This is not the same as coasting. You are making a deliberate evaluation. The momentum is real, the direction is right, and adding pressure right now creates noise rather than speed.

The Sourced Fact

According to Gallup's 2026 State of the Global Workplace report, manager engagement dropped from 27% to 22% in a single year. That is the largest year-over-year manager decline Gallup has ever recorded. Managers account for 70% of variance in team engagement.

Disengaged managers produce disengaged teams. And one of the fastest paths to manager disengagement is years of self-imposed constant pressure that never evaluated whether it was needed.

How to Read Your Team's Signals Before Adding Pressure

Stepping back requires knowing what to look for. These are the signals I check before I decide whether to push or let it run:

Signals that the team does NOT need more from you:
People are finishing what they started before picking up new work
1-on-1 conversations are about the actual work, not about managing your expectations
The team is asking questions about direction and priority, not asking you to slow down the volume of asks
People are energized after team syncs, not visibly relieved when they end

Signals that something is actually wrong:
Work is cycling without finishing
Your best people are quiet in ways they weren't before
The team stops raising problems, because they expect you to add a new task in response
You are getting more status reports and fewer conversations about the work itself

Pace is a symptom. These are the causes.

A team moving slowly but finishing things and talking openly about the work does not need more pressure from you. A team that has gone quiet and is cycling through half-done tasks needs something different. More urgency will not fix what is actually broken.

When the Answer IS Yes: How to Push Effectively When You Really Need To

This framework is not about never applying pressure. There are real moments when the business needs the team to move faster and the leader's job is to communicate that clearly and create the conditions for it.

Here is what effective urgency looks like when the business need question has a real answer.

Name the consequence specifically. Not "we need to move faster." Instead: "If we do not close this gap by [specific date], [specific business consequence] happens." The team needs to understand what is actually at stake, not just that you are unhappy with the pace.

Have a conversation about the work, not the urgency. Ask the team directly: "What would need to be different for us to move this faster?" You often discover that one or two things are creating the friction. Naming the obstacle is more useful than adding pressure to the outcome.

Remove something to create capacity. If the business need is real and the team is genuinely at capacity, adding a new priority without removing an old one is just adding noise. Explicitly retire or defer something. Say it out loud. The team needs to know what they are allowed to stop doing.

Set an end point. "We need to accelerate through [milestone or date], then we re-evaluate." Sustained urgency with no end point is exhausting. Defined urgency with a clear horizon is manageable. Teams can run hard when they know how long the sprint is.

The goal is not to never ask for more. The goal is to ask for more only when the business actually needs it, and to make that ask specific, scoped, and clear.

Monday Action

Before your next team meeting, write down three specific business commitments your team is currently working against. Not general goals. Specific commitments with dates or consequences attached.

If you cannot name three, that is the work to do before you add any urgency to anyone's plate. You cannot effectively push toward something you cannot describe.

What business need is your team actually working against right now, and could you describe it in one sentence?

You're great at the work. Let's make you impossible to ignore.

If you are looking for help building a team that runs at a sustainable pace without losing momentum, consider reaching out. https://www.jessestaffordcoaching.com

Search This Blog