top of page

Navigating Uncertainty in Research: Treat VUCA as the Terrain, Not a Detour

If you lead research right now, you can feel it in the air: the ground is shifting.

Funding feels harder to predict. Review cycles feel more opaque. Institutional priorities are in motion. Meanwhile, biotech and health tech are accelerating full of opportunity, but increasingly crowded, noisy, and fast. Even when budgets stabilize, the next cycle can reopen the conversation, which means uncertainty isn’t a temporary glitch.


So here’s the reframe:

Uncertainty isn’t a detour. It’s the operating environment.


That’s not pessimism. It’s clarity. And clarity is calming because it lets you stop waiting for “normal” to return and start leading the reality you’re actually in.


VUCA: A Useful Name for What You’re Already Living


VUCA stands for:

·       Volatility: conditions shift quickly; yesterday’s assumptions expire fast.

·       Uncertainty: you can’t see far ahead, and you won’t get complete information.

·       Complexity: everything is interconnected—funding, regulation, systems, people, politics.

·       Ambiguity: even when you have data, the meaning isn’t always clear.


The point of VUCA isn’t to sound clever. It’s to name what we’re experiencing so we can manage it. When your team feels unsettled, it usually means they’re accurately perceiving the environment. Naming that out loud builds trust.


Try this framing with your team: “We’re making decisions with imperfect information and that’s the job right now.”



Step 1: Build Trust by Telling the Truth (Without Spreading Panic)


In uncertain systems, rumors thrive. Silence gets filled. And people assume the worst.


Your best tool is transparent communication that holds three things at once:

  1. Here’s what we know.

  2. Here’s what we don’t know yet.

  3. Here’s what we’re doing next.


This is what steadiness looks like: not certainty, but cadence.


A simple practice that works:

  • Short, regular updates (even if the update is “no new info yet”)

  • Clear decision points (“We will decide X by March 15 based on Y”)

  • Visible principles (“We will protect trainees,” “We won’t overpromise,” “We will prioritize projects that learn fast”)


One nuance: different audiences need different levels of detail. Your trainees, staff, chairs, funders, collaborators, and board-level stakeholders don’t all need the same message but they do need the same underlying truth. Credibility is fragile in VUCA. Protect it.

 

Step 2: Cross the Threshold Into Agency


Here’s the quiet trap in uncertainty: waiting.


Waiting for the next funding cycle. Waiting for leadership to clarify. Waiting for the market to settle. Waiting for the perfect collaborator. Waiting for the signal that it’s “safe.”

But uncertainty doesn’t reward waiting. It rewards learning velocity.


The leadership move is this: Accept that no outside rescuer is coming and act anyway.

That doesn’t mean reckless action. It means purposeful motion, with an explicit learning plan.


In academia, “agency” often needs a translation: it means being deliberate about decision rights and cycle time. Who decides? What input is required? What can be tested without permission? What requires chair approval, IRB, contracting, informatics, or a core? Uncertainty punishes slow internal loops as much as it punishes bad external luck.

 

Step 3: Make Smaller, Reversible Bets (and Run a Portfolio)


When the environment is unpredictable, you don’t want brittle, all-or-nothing commitments. You want options.


Think like this:

  • What can we do that is meaningful but reversible?

  • What decision can we delay without harm, and what must we decide now?

  • Where can we spend time-to-learning instead of time-to-debating?


This is where biotech thinking is useful for all research leaders: run a portfolio, not a single bet. Most successful groups have a stable core (the platform, the dataset, the method, the clinical program) plus a few “shots on goal” with asymmetric upside.


Practical examples:

  • Pilot a new workflow with one clinic before scaling to ten

  • Prototype an analysis pipeline before the full cohort is assembled

  • Scope a partnership with a tight deliverable and a 60-day review

  • Submit a grant that funds reusable infrastructure (registries, assays, compute, pipelines)

  • Test feasibility assumptions (recruitment, phenotype validity, data completeness) before building the full study around them

 

Step 4: Add Decision Gates (So Persistence Doesn’t Masquerade as Progress)


This is the missing piece in many research environments: we start things, but we don’t always stage them.


In VUCA, every bet should have a simple gating plan:

Scale / Pivot / Stop


Before you begin, define:

  • The 2–3 assumptions that must be true

  • What evidence would confirm or disconfirm them

  • The timeline for that evidence

  • And what you will do if the evidence isn’t there


This isn’t harsh. It’s protective. It prevents teams from burning months (and morale) on projects that were never structurally viable.


Step 5: Shorten Learning Cycles


In stable times, we optimize for efficiency. In uncertain times, we optimize for feedback.


Build learning loops into your work:

  • Weekly/biweekly project reviews with one question:“What did we learn that changes what we do next?”

  • Pre-mortems: “If this fails, why will it fail?”

  • Decision logs: write down assumptions, then revisit them in 30–60 days


This isn’t bureaucracy. It’s how you prevent slow drift into the wrong strategy.


Step 6: Protect People While You Protect the Mission


In VUCA conditions, leaders and teams carry extra emotional load:

  • Fear about jobs and grants

  • Fatigue from constant change

  • Grief for “how it used to be”

  • Cognitive overload from too many possibilities


If you want sustained performance, treat wellbeing as a system constraint, not a perk.


Two operating rules help:

Efficiency without care becomes extraction.

Care without efficiency becomes collapse.


So you hold both:

  • Reduce redundant meetings

  • Clarify decision rights

  • Share resources across groups

  • Protect deep work time

  • Normalize recovery as part of high performance


In academic settings, add concrete protection for trainees and staff:

  • Commit to no-surprises communication 

  • Have a bridge plan (even if modest) and name it

  • Create redeployment pathways for staff skills across projects

  • Tighten authorship and scope agreements so junior people aren’t stranded when priorities shift


What We Stop Doing in VUCA


Uncertainty management isn’t only about doing more. It’s also about pruning.


In VUCA, consider stopping:

  • Launching initiatives without a clear owner and decision rights

  • Meetings that don’t produce decisions or learning

  • Big bets without fast tests

  • “Just one more committee” as a substitute for execution

  • Pretending morale is separate from productivity

  • Waiting for perfect information before acting on what you already know


A Simple Call to Action: Run an “Uncertainty Sprint”


Some things you can consider trying with your team in the next 30 days. One sprint turns ambient anxiety into a plan.

1.     Pick one priority bet (project, partnership, hire, pivot)

2.     Name the three biggest unknowns

3.     Design two fast tests to reduce uncertainty

4.     Set a decision date

5.     Define a scale/pivot/stop trigger—and commit to acting on what you learn


Don’t wait for clarity. Build your way toward it.The future may be uncertain, but your approach doesn’t have to be.

 
 
 

Comments


bottom of page