Resourceful pivoting is the ability to convert the friction of a blocked path into a new direction by rapidly re-marshalling existing insights and assets toward a more viable opportunity.

In the context of learning agility, resourceful pivoting is the steering mechanism of the sprinting pillar. While experimental fluidity provides the speed, and calculated risk-taking provides the courage, resourceful pivoting ensures that no effort is ever truly wasted. It requires cognitive flexibility to see hidden utility in failed experiments and emotional detachment to abandon a dead end without losing momentum. It is the transition from seeing a dead-end to seeing a new point of departure, ensuring that the organisation’s learning is cumulative rather than fragmented.

Why resourceful pivoting matters

In a volatile environment, sticking to a failing plan is not discipline; it is obsolescence. When this dimension of agility is low, leaders succumb to the sunk cost fallacy, pouring more resources into a broken strategy simply because of the time already invested. This creates organisational rigidity where the team becomes exhausted by friction and the lack of progress.

High resourceful pivoting allows a leader to maintain momentum through change. By identifying what can be salvaged from a setback, whether it is a piece of data, a customer insight, or a team dynamic, you ensure that the organisation is always failing forward. This behaviour transforms obstacles into pivots, allowing the team to navigate around barriers while retaining the speed of their initial sprint. It ensures that the strategy remains a living, breathing response to reality rather than a static document.

Resourceful pivoting spectrum

Effective leadership requires a balance between the persistence needed to see a difficult task through and the fluidity required to change course when the data demands it.

Left side: Dogged persistence Right side: Resourceful pivoting
Strengths

  • Demonstrates high levels of grit and commitment to the vision
  • Ensures that projects are not abandoned at the first sign of trouble
  • Provides a sense of stability and reliability to the team
  • Effective in environments with high noise-to-signal ratios
  • Builds deep expertise through long-term focus on a single problem

Liabilities

  • Can lead to catastrophic failure by ignoring obvious warning signs
  • Wastes significant resources on non-viable outcomes
  • Creates a culture where changing one’s mind is seen as a weakness
  • Results in missed opportunities that require a quick change in direction
  • Often leads to burnout as the team fights against the environment
 Strengths

  • Maximises the value extracted from every failed experiment
  • Keeps the organisation’s metabolic rate high during transitions
  • Reduces the psychological impact of setbacks on the team
  • Identifies non-obvious applications for existing technology or ideas
  • Allows for rapid alignment with new market realities

Liabilities

  • May be perceived as a lack of focus or strategic whiplash
  • Can lead to a shallow understanding of problems if done too early
  • Risks confusing stakeholders who value a consistent narrative
  • Requires high levels of internal communication to manage the shift
  • Can result in zombie assets if repurposing is not done cleanly

What good and bad look like for resourceful pivoting

What bad looks like What good looks like
Double down: Responding to a failed project by increasing the budget and ignoring the negative feedback. Asset harvest: Shutting down the project but immediately moving the core technology to a new department.
Starting from zero: Treating every change in direction as a total restart, losing all previous learning. The 30-degree shift: Changing the target or the method while keeping the underlying knowledge base intact.
The blame game: Focusing the post-mortem on who made the mistake rather than what can be reused. The salvage mission: Specifically asking what part of this failure is a secret weapon for our next move.
Frozen in place: Recognising a path is blocked but being unable to act until a new 12-month plan is approved. Liquid re-deployment: Moving the team’s energy to a high-potential alternative within 48 hours of a block.
Hidden dead-ends: Continuing to work on a doomed project in secret to avoid the shame of quitting. Proud abandonment: Publicly celebrating the decision to pivot based on superior data.

Barriers to resourceful pivoting

  • The sunk cost fallacy: The irrational desire to continue an endeavour because of the resources already invested, rather than the future value.
  • Identity lock-in: When a leader’s professional identity is tied to a specific project, making a pivot feel like a personal defeat.
  • Rigid budgeting: Financial systems that do not allow for the movement of funds between projects once the annual cycle is set.
  • Siloed information: Not knowing that a solution for your blocked path already exists in another part of the organisation.
  • Fear of quitting: A cultural stigma that equates pivoting with giving up, rather than with intelligent navigation.
  • Inertia of scale: The larger the project, the more physical and emotional energy it takes to change its trajectory.
  • Lack of spare capacity: Pivoting requires a burst of creative energy; if the team is at 110 per cent capacity, they will stick to the path of least resistance.

Enablers of resourceful pivoting

  • Component-based thinking: Viewing projects as a collection of modules that can be unbundled and rearranged.
  • The red line criteria: Setting clear data points in advance that, if hit, trigger an automatic review of the current direction.
  • Cross-functional visibility: Regular asset sharing sessions where teams show what they are building, even if it is currently failing.
  • Outcome detachment: Training the brain to value the lesson as much as the win, making it easier to let go of the specific tactic.
  • The pivot or persevere meeting: A recurring, formal session designed specifically to challenge the viability of current paths.
  • Rapid de-briefing: Extracting the harvestable assets from a project within hours of the decision to stop.
  • Resource liquidity: Maintaining a small pivot fund or reserve team that can be deployed to support a sudden shift in direction.

Questions for reflection

  • If we had to stop this project today, what is the one gold nugget of data or code we would definitely keep?
  • Am I sticking to this plan because it’s working, or because I don’t want to admit I was wrong?
  • If a competitor started with our current assets but a completely fresh perspective, what would they do differently?
  • What is the smallest possible turn we could make to bypass this current obstacle?
  • Who in the organisation is currently facing the problem that our failed experiment actually solves?
  • Do I have the emotional slack required to lead my team through a major change in direction right now?
  • How much of our current effort is being spent on zombie work that we all know deep down will never launch?

Micro practices for resourceful pivoting

  1. The 10-minute salvage: At the end of every week, identify one thing that didn’t go as planned and list three ways that specific failure could be useful next month.
  2. The Lego audit: Look at your current major project and break it down into five components. Ask which of these could stand alone as a separate product or service.
  3. The stop-doing list: Every month, identify one initiative to stop immediately to free up resources for a more promising pivot.
  4. The outsider review: Present your biggest challenge to someone from a completely different department and ask them how they would use your scrap materials.
  5. The pivot pitch: Practice explaining a major change in direction as an upgrade based on new data rather than a change of mind.

This is one of the 20 behaviours in the learning agility library. Visit the learning agility library to explore the rest.