Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

Pulled, Not Pushed

A field guide for a leader whose team is not performing to its potential: why a busy team can stop reaching for more, and how to bring back its drive.

Pulled, Not Pushed
100
pulled-not-pushed

Why a busy, competent team can stop reaching for more, and how to bring back the drive that comes from the work itself rather than from the pressure around it.

Why the work matters

The challenge: The team is falling short of its potential

A busy, competent team can stop reaching beyond what it is asked. Deadlines, stretch targets and closer review raise effort for a while, but push produces compliance rather than commitment, and the lift fades within weeks. What is often missing is pull: the why behind the work reaching the people doing it, and connections that make the work feel shared. The guide helps you bring the why into ordinary decisions, make the people the work serves real to the team, and look at the team before adding more pressure.

Who it’s for: Leaders of a competent team that has stopped reaching: a manager, a function head, anyone who has tried a tighter deadline and watched the lift fade. Read it on your own first, then take the conversation in part three to your team.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

The calendar is full. The status updates arrive on time, the meetings run to the hour, and the team hits most of what it was asked to hit. Looking back over the quarter, though, the leader struggles to name one thing the team did that it wasn’t asked to do. The work is competent. It isn’t distinctive. The hard problems wait to be assigned, and the people who once argued about how to do the work better now mostly agree. The leader has tried a tighter deadline and a stretch target, and both worked for a few weeks. Then the team settled back to where it was, and the distance between what it is doing and what it could do is still there.

Where it lands

  • In you: you often sense a lack of urgency, and you reach for the levers that are fastest to pull: deadlines, targets, closer review. They work for a while, and then you are reaching again.
  • In your team: effort tends to be busy while the large things don’t move. Disagreement fades, and it gets mistaken for alignment when people are simply not invested enough to argue.
  • In your organization: results are typically competent rather than distinctive, the gap rarely shows on a dashboard because dashboards measure what was asked for, and the strongest people drift toward work that draws them in.

Questions to ponder

Think of the last month of the team’s work, and ask:

  • When we want more from the team, what do we tend to reach for first?
  • Could each person say, in their own words, why their work matters?
  • When did someone on the team last see, hear from or picture the people the work serves?
  • Do people tend to ask each other for help, push back and argue about the work, or mostly work alone?
  • Who on the team still does more than they are asked, and what draws them to it?

Questions to discuss

With the decision from Try this week in mind, the why that was said before the what:

  • Where do we feel pulled forward, and where do we feel pushed? Both get results, and only one of them builds on itself.
  • Can each of us say why our work matters, in our own words? The gaps show where the why hasn’t landed.
  • How could we change the way we work together so that each of us helps the others see who the work is for, and the connections between us carry the work when the pressure is off? Name one person on the team whose work connected to someone the work serves, and say so in front of the others.

Try this week

The next time a real decision lands in front of the team, take twenty seconds before the what and say the why: who this decision serves, why it matters to them, and why now. Name the person on the other end of the work if you can. Then, before the week ends, find one person on the team whose work connected to that person, and say so, by name, in front of the others.

Keep reading with a free account

  • How to tell whether the team is being pushed rather than pulled, missing the why, or working with connections that have thinned
  • The two halves of the practice, saying why and building connection, and the four connections that matter
  • When adding pressure is the right move, and the warning that comes with it
  • The signs it’s working, from someone volunteering for the hard problem before it is assigned to the slower sign of who stays
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.

His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.

Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.

More about Mark can be found at markdbenson.com.