Leading through uncertainty requires making critical choices without all the answers. This article presents 14 strategies that help leaders move forward confidently when information is scarce, drawing on insights from experienced practitioners and decision-making experts. These approaches offer practical frameworks for reducing risk while maintaining momentum in ambiguous situations.
- Safeguard Liquidity and Preserve Flexibility
- Bet on Paths Where Knowledge Compounds
- Favor Recoverable Bets over Certainty
- Choose the Constant When Context Shifts
- Design for Reversibility and Limit Blast Radius
- Name the Gaps and Stay Adaptive
- Protect Trust and Build Capability under Pressure
- Delegate Gradually to Gain Leverage
- Apply Reversal and Time for Decisions
- Let Purpose and Values Guide Pivotal Choices
- Use Heuristics to Learn Fast
- Judge Error Cost Before Weigh Odds
- Test Small Moves and Adjust Quickly
- Seek Experts Then Empower the Team
Safeguard Liquidity and Preserve Flexibility
For most of the past 20 years, I have worked in turnarounds where waiting for perfect information would have been a decision in itself, usually the wrong one.
One case involved an industrial company that was running out of cash. We had days, not months, to act. Collections were uncertain, suppliers were tightening their terms, and the numbers coming from different parts of the business did not fully agree. I had to decide which payments to release and which operations we could afford to keep running without putting the whole company at risk.
I started by separating facts from assumptions. We rebuilt the cash position from the bottom up, invoice by invoice, and updated it every morning. The 13-week cash forecast gave us the frame, but the next ten business days drove our decisions. Every payment had to answer a simple question: does this keep the company operating or protect near-term cash generation?
We also kept the decision group small. Finance and operations sat together with sales and procurement. No long presentations. People brought the latest facts, said clearly what they did not know, and made a recommendation. When the information was still incomplete, I chose the option that preserved the most flexibility and could be corrected quickly.
We prioritized payroll, essential suppliers, and customer orders that would turn into cash soon. We held or renegotiated everything else. That gave the company enough runway to stabilize operations, regain credibility with lenders and suppliers, and move from emergency cash control to a proper recovery plan.
The lesson has stayed with me. Being fact-based does not mean waiting until every number is perfect. It means knowing which facts matter today, making the best decision available, and correcting quickly when new information arrives.
The operating logic reflects established turnaround practice: bottom-up 13-week cash forecasting, daily liquidity monitoring, frequent reassessment, and short decision cycles with clear accountability.
Luciano De Castro Carvalho, Chief Transformation Officer
Bet on Paths Where Knowledge Compounds
Early on at our ORM work, we had to pick between two client segments with almost no data to guide the call. We were getting inbound from crypto founders who needed reputation repair after exit scams or project collapses, and simultaneously from traditional B2B executives dealing with Glassdoor and Google Reviews fallout. Both paid similar retainers. Both had urgent timelines. We could only serve one well with the team we had.
The safe move was B2B executives. Established playbook. Predictable scope. Lower legal risk.
I went crypto instead.
The decision came down to three observations, not certainty. First, crypto founders talked to each other constantly. One clean reputation turnaround would get referenced in five Telegram groups within two weeks. Second, the work was harder, which meant fewer competitors willing to take it on. Third, our media network already covered blockchain, so we had distribution other ORM shops did not.
None of that guaranteed it would work. We just knew the upside was asymmetric if it did.
The first three months were rough. Clients expected faster results than the work allowed. Scope kept expanding because reputation issues in crypto are never isolated to one platform. We nearly lost two accounts in month two because suppression timelines ran longer than promised.
What saved it was treating the early clients as a learning cohort, not a revenue target. We documented every tactic that moved the needle. We tracked which content types Google actually demoted and which it ignored. We built a suppression scorecard so we could show incremental progress instead of waiting for the final result. By month four, we had a system that worked predictably enough to sell with confidence.
That crypto bet became 60% of revenue within eighteen months.
The advice I would give is this: when you are deciding with incomplete information, pick the option where learning compounds. Do not optimize for certainty. Optimize for whether each result, win or loss, teaches you something you can use in the next decision. We could have chosen the safer segment and made predictable money. Instead we chose the segment where every engagement built knowledge no one else had. That gap became the moat.
Ankush Gupta, Fractional CMO, Fameninja ORM Management Company
Favor Recoverable Bets over Certainty
The decision I keep coming back to was a product launch where the market signal was genuinely split. Our customer research said one thing, the competitive landscape was moving in a different direction, and our internal teams had strong conflicting reads on which signal to trust. We had about two weeks to land on a positioning approach that would anchor the whole launch.
What I did: I stopped trying to find the definitive answer and started asking a different question. Not, “What does the data say?” but, “Which bet is more recoverable if we’re wrong?” If we positioned around customer language and the competition turned out to be right, we could course-correct within a quarter. If we followed the competitive signal and customers didn’t recognize themselves in the message, we’d be rebuilding from scratch. That asymmetry made the call clearer than the data did.
We went with the customer language. It held. But the more important thing I took from it was the framework, not the outcome.
The advice I’d give: separate the decision from the information search. There’s a point in every ambiguous call where more research is procrastination dressed as diligence. The question isn’t whether you have enough information. It’s whether you know what you’d do with more of it. If the answer is “the same thing I’m going to do anyway,” you already have your answer.
Kuber Sharma, Enterprise AI Strategist and Go-to-Market Leader
Choose the Constant When Context Shifts
The hardest decision I made with incomplete information was leaving an international management role — where I led structured organizations and teams — for a full-time life on the road, with no guarantee of the outcome. I didn’t have a validated backup plan; only the certainty that staying would mean enduring change instead of choosing it.
My approach grew out of that choice and became the core of the framework I later developed: before any major decision, I isolate the one variable that truly matters, instead of trying to control them all. When information is incomplete, the biggest risk isn’t making the wrong call — it’s staying stuck in analysis.
The advice I’d give other leaders: when information is incomplete, don’t look for the decision that’s safest on paper. Look for the one that stays consistent even if the context shifts — because the context will shift, sooner or later.
Cristina Furlan, Author | Founder, The 4S Method of Adaptive Intelligence™, The 4S Method of Adaptive Intelligence™
Design for Reversibility and Limit Blast Radius
As a CTO building AI software over the last decade, and now leading our team, the hardest decisions usually involve balancing architectural risk with incomplete data. When we first decided to let our AI agents execute real actions — like automatically processing a traveler’s refund in a live billing system rather than just drafting an email — we had very little precedent for how the models would handle complex, multi-step edge cases in production. Giving an AI write access to a client’s backend is a massive leap, and the historical data on potential failure rates just wasn’t there yet.
Instead of trying to map out every possible scenario in a vacuum, we moved forward by tightly controlling the blast radius. We built a shadow mode where the AI would queue up the exact API calls to process the refund, but a human agent had to approve the final step. We ran it that way until the success rate hit a threshold we were comfortable with, then slowly removed the training wheels.
If I could share one lesson with other technical leaders facing a similar lack of data, it would be to optimize your early decisions for reversibility. When you cannot predict the outcome, build the architecture or the operational process in a way that lets you easily undo a mistake or roll back a feature in minutes. Once you know you can safely revert a decision, you can afford to make it without having all the answers upfront.
Damien Mourot, CTO – Co-founder, AGO
Name the Gaps and Stay Adaptive
Just one? Every day I make decisions with — what feels like, at least — suboptimal information. I’m never satisfied. I want to know everything about a client or candidate before moving forward. And maybe this thirst has actually helped me, because I know I am always operating with less information than I want. I expect blank spots and hidden factors.
Take, for example, a recent executive hire I worked on. This was a big company and an extremely coveted role. I knew a lot about it — except for one key thing: where the role would be headquartered.
Just one little thing. Nothing that would impact the candidate pool, right?
And yet, there was no choice. I needed a short list, and I needed it yesterday. So I treated the big glaring void like any other missing piece of information: separating what I knew from what I was assuming, identifying what could genuinely change the decision, and moving forward while keeping that particular variable open. I also made sure the candidates understood that there was still an unresolved piece rather than pretending I had an answer I didn’t have.
That’s the bigger lesson for me. When you don’t have all the information, don’t fill in the blanks with confidence. Identify the blanks.
You can make a very good decision with incomplete information if you know which information you’re missing, how important it is, and what you’ll do when you eventually get it. The danger isn’t uncertainty itself. The danger is forgetting that you’re uncertain.
I still want to know everything before I make a decision. That’s probably never going to change. But I’ve gotten much better at recognizing when I know enough to move forward — and building enough flexibility into the decision that I can adjust when the missing information finally arrives.
Phil Moran, Managing Director, Oryx Executive Search
Protect Trust and Build Capability under Pressure
Early on with my company, a client needed us in a city where we had no office and no crew. I had two choices. Turn the work down, or figure out how to deliver in a market I didn’t know, with people I hadn’t met yet.
I didn’t have a playbook for it. Distributed production crews weren’t common back then, so there was no model to copy and no data telling me it would work. What I had was a client who trusted us and a deadline that wasn’t moving.
I decided to build the crew from scratch in that city. I leaned on the relationships I did have, vetted local people the same way I’d vet anyone I put on my own set, and stayed close to the project so nothing slipped. It worked. Then it worked again in the next city, and the next. What started as one hard call under pressure turned into the distributed network that my business runs on today.
My approach came down to a few things. I protected the client relationship first, because that trust was the whole reason the opportunity existed. I made the decision I could stand behind rather than waiting for certainty that was never going to arrive. And I treated the unknown as a problem to solve, not a reason to stop.
One piece of advice for other leaders in the same spot:
Don’t wait for full information, because you rarely get it. Get clear on what you actually know, protect the relationships and commitments that matter most, and make the call that you are comfortable being held accountable for. Some of the best infrastructure I ever built came from a decision I had to make before I felt ready. Setbacks and unknowns often turn out to be course corrections pointing you toward something bigger.
Tavares Beverly, Founder and CEO, Beverly Boy Productions
Delegate Gradually to Gain Leverage
One difficult decision I faced while growing my web design agency was deciding when to start hiring and offloading work. I had limited information because I did not know how quickly the business would continue growing, whether someone else would meet my standards, or whether delegating would actually save me enough time to justify the cost.
I started by offloading the most repetitive and least profitable tasks, particularly work that took up a large amount of time but did not require me to be directly involved. This allowed me to spend more time on sales, client relationships, strategy, and higher-value project work. Rather than handing over everything at once, I delegated gradually, documented the process, and reviewed the work until I felt confident that it could be handled consistently.
My advice to other business owners is not to wait until they feel completely comfortable giving up control, because that point may never come. It is common to believe that nobody will complete a task as well as you can. However, even if someone initially performs one task at 75% of your level, that can still be a worthwhile trade-off when it gives you back hours to focus on work that produces more revenue and moves the company forward.
Sam Mendelsohn, Owner, Mendel Sites
Apply Reversal and Time for Decisions
The decision I keep returning to as an example: in early 2026 we had 48 hours to decide whether to reassign our senior writer from our English content strategy to a suddenly-critical German market push. We had partial data — some competitive signals, no reliable read on German-market unit economics, no baseline for German content performance. Classic high-stakes / low-information situation.
The framework I used to decide: two questions.
1. Is this decision reversible? If the decision can be unwound in 30-60 days at modest cost, decide fast on the best available signal. If it’s structurally irreversible (six-month contracts, org-wide reorganization, key hire), buy more time even if it costs opportunity value.
2. What does the timing cost of waiting look like? If waiting a week collapses the opportunity entirely, decide now. If waiting a week gives me one more concrete data point without changing the opportunity, wait.
In this specific case, the writer reassignment was reversible (we could pull her back to English strategy within 4 weeks if the German push disappointed), and the timing pressure was real — a partner deal window was closing in 3 weeks. Both variables argued for deciding fast.
We reassigned her Monday morning. By day 21, German content signals were mixed but positive; by day 45, they justified the initial commitment. If I had waited for full-quality data, we would have missed the partner window and killed the entire German push before it started.
The specific advice I’d give: never confuse “I don’t have enough information” with “I shouldn’t decide.” Those are different states. In most partial-information decisions, the actual constraint is that people are uncomfortable owning a decision — not that better data exists to unlock it. The data isn’t coming. The comfort isn’t coming. You still have to decide.
The bigger point: leadership under uncertainty is about developing a robust protocol for making decisions with partial information, not about waiting until you have complete information. Complete information is a luxury; robust protocols scale.
The rule I’ve settled on: reversible decisions get made fast with available signal. Irreversible decisions get slowed until either the signal improves or reversibility can be engineered in.
Richard Meadows, Head of Content, Streamrise
Let Purpose and Values Guide Pivotal Choices
During COVID, my highly successful seven-figure business came to a halt. I found myself at a fork in the road, having to make a difficult decision: try to revive a failing business or go in a completely different direction and launch a new business in an entirely new vertical. My original business was in the industry that I had known for fifteen years, and so I knew that I had a shot at making it successful again. I knew very little about the new vertical I was considering launching my second business in, and it was a very difficult, highly risky decision. I took a lot of time reconnecting with my personal WHY, i.e. my personal mission, as well as my core values. I compared my existing business with the one I was aspiring to launch to see which one best supported my mission and would be most aligned with my core values. The second business, despite all of the limited information, was the most aligned. Five years later, it is a globally thriving company. My main piece of advice to other leaders is to use their WHY as a compass and their core values to test alignment before making any difficult decision.
Marina Byezhanova, Co-Founder, Brand of a Leader
Use Heuristics to Learn Fast
I think that’s one of the biggest lessons in leadership: you are never going to have every piece of information before making a decision. The goal isn’t to eliminate uncertainty completely. The goal is to know what you don’t know and build systems that help you learn quickly.
Take, for example, team-building. As a recruiter, I can never know enough about a department before I step in to help expand. It’s very common to have a strong candidate who checks many of the boxes — experience, communication skills, industry knowledge — and yet doesn’t quite match with the existing team.
I am never going to be able to sit in with a team every day and really get to know them on the level I’d like, but I’ve built heuristics that help. I pay close attention to how a hiring manager describes their team. What words do they use? Are they looking for someone who challenges ideas, or someone who brings stability? Are they describing a collaborative environment, a highly independent one, or something in between? Sometimes the smallest details reveal the most.
I also spend a lot of time asking questions that go beyond the job description. What does success look like after six months? Who has excelled on this team before, and why? What type of personality thrives here? What type struggles? Those answers often tell me far more than a list of qualifications.
That approach has served me well. I don’t have a crystal ball, but I can read between the lines.
Ben Lamarche, General Manager, Lock Search Group
Judge Error Cost Before Weigh Odds
Every meaningful decision I have made came with less information than I wanted. Waiting for certainty is usually just a comfortable way to avoid deciding, and the leaders who insist on it tend to decide late and pay for the delay.
One case stays with me. A client situation was developing faster than the facts could settle, and I had to choose a direction before I could be sure which version of events was true. My approach was to separate what I actually knew from what I merely feared, because fear fills an information gap faster than facts do. I wrote down the few things I could stand behind, named the assumptions I was making, and asked one honest question. If this decision turned out wrong, could we recover from it? That question mattered more than any forecast, because a reversible mistake and a permanent one deserve entirely different amounts of caution.
Once I saw the decision was reversible, I made the call and moved, while keeping a close watch for the signal that would tell me to correct course. The facts arrived over the following days, and where I had guessed wrong I adjusted early rather than defending a position to save face. Deciding fast and adjusting honestly beat waiting for a certainty that was never going to come in time.
The advice I would give is to judge the cost of being wrong before you judge the odds of being right. Most decisions are more reversible than they feel in the moment. Move on the ones you can undo, and save your hesitation for the ones you cannot.
Sameer Somal, CEO, Blue Ocean Global Technology
Test Small Moves and Adjust Quickly
I once believed that more information meant easier decisions. Over the past 20 years in search marketing, I have realized that many decisions need to be made before finding the answers. There has never been a reason behind the search change, and AI-powered search only complicates understanding users’ actions.
A difficult decision involved how search behavior changed rapidly, and rankings and traffic trends were changing before we had enough data to understand the long-term impact. Looking at our financial and health care clients, we risked serious business challenges by being too late, but also by being too early.
Instead of doing everything at once, we decided to try a few tricks at a time. We tried new content formats and search techniques in specific areas, saw how our users responded, and made changes as necessary. We never knew what would happen, but we wanted to make decisions that we could modify with any new information.
It taught me that a leader doesn’t always have all the answers. Leadership is about using the available information to make a good decision and being willing to accept when things change. Some assumptions prove wrong; the wrong thing is to hold on to those notions out of pride.
My advice to other leaders is not to wait for clear information before making decisions. You need to make minimal decisions that will take you forward and focus on your customers’ behavior. Clarity always comes after taking decisions.
Derek Iwasiuk, Co-owner, Director of Marketing, Searchtides
Seek Experts Then Empower the Team
It can feel counterintuitive to make a decision with limited information, but trust me, I’ve been in that situation before. This was the time when I led my team to develop an eSIM API to allow businesses to build global mobile data within their apps. Though I knew little about software development, it was something I felt my company could benefit from because it would mean scalability for our tech solution.
My plan was to share this idea with our tech team to assess its feasibility and to refine it before rolling it out. After I brought it to them, they overwhelmingly supported it, mentioning that it would even help us attract more B2B customers since they wouldn’t need to develop their own system from scratch.
As leaders, we may not know everything that requires our input, but we shouldn’t be discouraged. Instead, we should give it our best shot by seeking feedback from experts in the field where we have limited information.
It’s a basic requirement for leaders to face tough situations and make the right call, even when they don’t know everything. This is what led me to task my team with developing an API to find more customers for our product and make it easy for them to use. With this approach, they chose how best to integrate it into their systems.
Mark Collie, CEO, KnowRoaming