Every conductor I know carries a version of the same nightmare. You’re on the podium at Carnegie Hall. Weeks of preparation, every cue rehearsed. The hall is packed, the lights go down, the musicians lift their instruments.

You give the downbeat, and the orchestra is playing a different piece.

Not a variation. A different piece. No warning, no new sheet music, and no stopping, because the audience is already leaning in. You’re expected to conduct it anyway.

That’s what leading feels like right now in tech and government contracting. The plan changed mid-performance and the stakes didn’t. AI is accelerating everything it touches, policy shifts land without notice, federal and contract budgets are being cut while the missions stay the same size. Roles that used to be clear aren’t. Timelines that used to be linear aren’t. And in the middle of it, leaders are expected to stay calm, make sound decisions, and keep the whole thing from unraveling. No rehearsal, no score, no break between movements.

A few years ago I came across a name for this. The relief lasted about a second.

“That’s exactly what’s going on,” I thought.

“Oh shit,” came next.

The world according to BANI.

The futurist Jamais Cascio coined BANI because he thought VUCA (volatility, uncertainty, complexity, ambiguity) no longer captured what we’re up against. His claim: the world isn’t just volatile anymore. It’s brittle, anxious, nonlinear, and often flat-out incomprehensible.

Trendy acronym, real experience. I’ve worked with senior leaders in federal agencies and tech organizations who are doing everything “right” on paper and still feel like they’re being asked to perform a piece nobody handed them. The old rulebook fails on contact: control-based thinking cracks brittle systems further, confidence erodes in anxious cultures, linear plans miss nonlinear problems, and in incomprehensible moments clarity feels out of reach.

If deliberate practice is how leaders close the knowing-doing gap (I’ve written about that separately), BANI names the conditions you’re practicing for. It means practicing the two or three moves you’ll need when the plan dies: reading the room, resetting the tempo, saying plainly what you know and don’t.

Each letter of the acronym asks for one of those moves. Take them one at a time.

Brittle: resilience beats control.

Brittle systems crack under pressure, and I’ve watched well-intentioned leaders across federal and commercial work respond to that by gripping harder. The tighter the grip, the more fragile the system. One change request, one outage, one policy shift, and the whole thing snaps.

In a brittle environment, control is a liability. What holds up instead is flexibility: the ability to change strategy mid-passage without losing your grounding.

I coached a leader scaling a tech modernization program who struggled with exactly this. Brilliant, precise, used to building clean structured systems, and visibly frustrated when those systems didn’t respond as designed. The work of the coaching was a shift from builder mode to conductor mode: stepping back, scanning the room, adjusting tempo, responding to what’s actually being played. The shift didn’t just help her. It calmed her team, and they started experimenting and speaking up again.

Resilience here isn’t gritting your teeth. It’s changing your plan while staying in the room.

Anxious: space beats speed.

Anxiety grows where clarity is missing, and tech and GovCon teams live there: ambiguous requirements, thin resources, ground that moves weekly.

The reflex response to an anxious team is speed. More check-ins, more metrics, more dashboards. But anxious teams don’t need speed. They need space.

A leader I worked with on a mission-critical federal program watched his team spiral from constant context switching and unclear priorities. Instead of pushing harder, he introduced short weekly reality checks. Not status meetings. Quiet, intentional space where people could name what was in their way: confusion, burnout, fear of failure. People hesitated at first. Over time it became the one place everyone could exhale, and the team’s focus came back with it.

Anxious teams don’t need another dashboard. They need to hear what’s actually decided, what isn’t, and when they’ll know. That’s care, and it’s also management.

Nonlinear: sensemaking beats project plans.

In nonlinear work, A stops leading to B. Projects evolve, stakeholders shift, timelines change mid-flight, and you can be halfway through something when the goalpost moves again. Traditional project management wasn’t built for this, and neither were most leaders’ habits.

The skill that holds up is sensemaking: helping people name the complexity, spot the patterns, and decide what matters most right now. Not having the answers. Making meaning fast enough to act.

The most useful sensemaking tool I’ve seen is a shared metaphor. A small tech startup I coached adopted the image of a red sports car for their business. What happens when they hit the gas. What braking hard feels like. The thrill of nimble steering and the risk of it at speed. The noise the car makes when something’s wrong, and what breaks when it skips regular service. A clever analogy at first, and then something better: a shared mental model they could point at when things got messy, a language for tension and misalignment that didn’t require blame.

Incomprehensible: presence anchors.

Some problems defy logic. Requirements contradict each other. Decisions arrive from five layers up with no context. You stare at the complexity and feel the creeping sense that nothing here is meant to be understood.

That’s the I in BANI, and in those moments what a team needs most is a leader with a calm, grounded presence. Which doesn’t mean pretending to have answers. It means staying in the room, listening, and naming what you do know while everything around you feels absurd.

Musicians know this moment. It’s the silence between movements, the breath before the next note. It lasts a second or two, and everything hangs in it: the audience waiting, leaning into what comes next. That pause is my favorite part of any performance, and it’s the moment leaders are standing in right now. How you show up in the pause shapes what the next movement sounds like.

The part the audience never sees.

Here’s what makes the Carnegie nightmare survivable, and it’s the part that never makes it into the program notes: sight-reading is not a talent. It’s a drilled skill. Musicians get good at playing unfamiliar music by playing unfamiliar music, a little every day, until being surprised is itself the practiced thing. The player who reads a new piece cold and makes it sound intentional has done that thousands of times where no one was listening.

The leaders in these stories are drawn from real engagements, with details changed to protect them.

The four skills above work the same way. Flexibility, space-making, sensemaking, presence: none of them is a trait, and none of them shows up on demand just because the moment is important. They’re built in low-stakes reps before the lights come up, or they’re not there when the orchestra starts playing the wrong piece.

We don’t need perfect performances. We need practiced presence.

⁂   End of essay

One essay, a few times a year. No promotional sequence, and we don’t add you to anything else.