Leading Through Ambiguity: How Do You Make Decisions When the Data Isn’t There?

Thank you for your perspective, Sergio Luis Conte ! , I completely agree that converting raw data into actionable information is key — even in ambiguous situations. I also like your reference to Shannon’s Mathematical Theory of Information; it reminds us that decision-making often involves filtering signal from noise and making sense of limited inputs.
In my experience, when formal data is missing, I often combine this with small experiments, iterative checkpoints, and stakeholder feedback to validate assumptions before making bigger commitments.

I’m curious — how have you applied the principles from Shannon or business analysis frameworks to guide decisions when the “right” data isn’t fully available?

In ambiguity, I use a “test-and-learn” approach, breaking big decisions into small, low-risk experiments. For example, during a tight ERP rollout with unclear user requirements, we piloted one module with 10% of users, gathered feedback in a week, and scaled only what worked.

PMI data shows projects with iterative decision-making are 28% more likely to meet goals in uncertain environments. Implementation is straightforward: set short checkpoints, utilize rapid prototypes, and keep stakeholders informed to adapt quickly without extensive rework.