The hardest part of organizational change is rarely the change itself. It's the stretch beforehand — when everyone can feel something is coming, but no one knows what. Whether you're leading a nonprofit navigating a funding review or a life science startup watching runway shrink, the team dynamics are the same: anxiety goes underground, collaboration slows, and people start protecting themselves instead of each other. (Details have been adapted to protect confidentiality.)

The organization wasn't in crisis yet — but everyone could feel one coming. A major funding source was under review, and leadership didn't yet know whether the next year would mean business as usual, a significant restructure, or something in between.

Staff picked up on the ambiguity even when it wasn't named. Conversations got quieter. People started guarding information instead of sharing it. Some pushed for answers leadership didn't have. Others disengaged and waited. A few started quietly exploring other positions.

Core issues:

• Significant funding uncertainty with no clear resolution timeline
• Visible anxiety and bracing behavior across the team
• Inconsistent reactions to ambiguity creating friction between colleagues
• Leadership unable to offer certainty, but needing to keep the team functional
• Risk of disengagement, attrition, and eroding trust if left unaddressed

This is one of the most common — and least prepared for — challenges in nonprofit leadership: not the moment of impact, but the unresolved stretch before it.

We facilitated a half-day Motion Sprint built specifically for this kind of in-between moment — not after a change has landed, but before anyone knows which way things will go.

We opened by naming what was already in the room: the uncertainty was real, and the team's unease wasn't a personal failing — it was a predictable, human response to genuine ambiguity.

From there, we drew a clear line between the external situation (which the team didn't control) and the internal process of adjusting to it (which they did). That reframe mattered. People stopped reading their own anxiety as weakness and started understanding it as a normal response to an abnormal amount of not-knowing.

The core of the session explored how different working styles shape reactions under pressure. Some people default to seeking more information and structure. Others push for decisive action. Some quietly protect team relationships. Others look for the upside and try to keep morale up. None of these responses are wrong — but unrecognized, they collide. The person seeking facts reads the person seeking action as reckless. The person protecting morale reads the quiet colleague as checked out, when they're actually just processing differently.

Through structured exercises, the team mapped their own reactions, recognized those patterns in each other, and talked openly about what they each needed from colleagues during this stretch of not-knowing. The session closed with lightweight, concrete commitments for how the team would support each other — regardless of how the funding situation resolved.

• Half-day Motion Sprint (in-person or online)
• Interactive exercises on external change vs. internal adjustment
• Individual mapping of reactions to uncertainty and ambiguity
• Structured peer discussion on mutual support during uncertain periods
• Lightweight team agreements for the weeks ahead
• Tools to build organizational resilience and adaptability.

The funding situation didn't resolve in the workshop. What changed was how the team held the uncertainty together.

Conversations that had been happening in side channels came into the open. People stopped reading each other's coping styles as character flaws and started recognizing them as different, valid ways of handling the same hard moment.

Leadership reported a steadier team in the weeks that followed: fewer anxiety-driven side conversations, more direct questions asked openly, and a noticeably calmer baseline — even though the underlying uncertainty hadn't gone away.

No promises were made that couldn't be kept. No false reassurance was offered. What the team gained was a shared language for what they were going through, and the confidence that they could handle whatever came next — together, rather than each person bracing alone.

Most change management for nonprofits happens too late — after the announcement, after the restructure, after people have already started protecting themselves instead of each other.

This case shows the value of building resilience before it's needed, not after. By the time change arrives — in whatever form it takes — this team won't be starting from a place of fracture and self-protection. They'll be starting from a place of having already practiced staying grounded together.