How to Make Better Project Decisions When the Evidence Is Incomplete
Perfect information is rarely available
Project decisions are often presented as if they happen at a neat moment: all the facts are known, the options are clear and everyone agrees. Real delivery is rarely like that. A sponsor may need to decide whether to begin a pilot, protect a deadline, change scope or release a team while some evidence is still emerging. Waiting for certainty can be a decision in itself, and it can carry a cost.
The aim is not to pretend uncertainty has disappeared. It is to make a decision that is proportionate to the risk, clear about what is known and honest about what still needs testing. That gives a project a useful direction without pretending it has a crystal ball.
Start with the decision, not the meeting
A surprising amount of time is lost because a meeting is booked before anyone has stated the decision that needs to be made. Start with one plain sentence: “We need to decide whether to…” Then identify who has the authority to decide, what they need to understand and when the answer is needed.
This keeps the conversation focused. It also stops an update meeting turning into an informal decision with no owner, no record of the reasoning and no shared understanding of what happens next. A good decision paper can be short, provided the question is genuinely clear.
Separate facts, assumptions and preferences
When evidence is incomplete, these three things often become tangled. A fact is something the team can show. An assumption is a reasonable belief that needs checking. A preference is a view about the route the organisation would rather take. They can all be relevant, but they should not be presented as the same thing.
For example, the available data may show that a process takes six days. The team may assume that a small pilot will reduce that time. A sponsor may prefer to protect the customer-facing team from disruption. Naming each part makes the discussion more constructive and highlights where a small test would give the most useful evidence.
Give people real options
A decision is not improved by presenting one recommendation and calling it a choice. Set out at least two credible routes where possible: proceed now, run a limited pilot, delay until a condition is met, or stop and reallocate effort. For each route, describe the likely benefit, impact on normal work, key risk and consequence of delay.
This is not about creating paperwork for its own sake. It is about helping a sponsor see the trade-off they are being asked to make. A clear option that is not chosen can still be useful later, because it shows why the project took the path it did.
Use tolerances before the pressure rises
PRINCE2’s idea of tolerances is helpful here. Agree in advance what level of cost, time, scope, risk, benefit or operational impact the project can manage without returning for a higher-level decision. That gives the team room to deliver while protecting the sponsor from surprises.
The point is not to make every small variation an exception. It is to be clear about what must trigger a conversation. If a pilot begins to draw too heavily on a service team, for instance, the agreed tolerance can prompt a timely decision about support, sequencing or scope.
Make review part of the decision
A decision made with incomplete evidence should include its review point. What will tell you whether it was the right call? Who will collect that information? When will the sponsor look at it again? A review might follow early user feedback, a benefits check, a risk assessment or the end of a defined pilot.
This is not indecision. It is disciplined learning. It lets a team move forward without treating the first answer as permanent, and it provides a route to adjust before a small concern becomes a costly one.
Keep normal delivery in view
Projects do not operate in an empty space. The people asked to test, train, communicate or adopt a change are usually also doing their ordinary jobs. Include that impact in the decision, particularly when the same managers or specialists are being asked to support several initiatives.
A technically sensible option can fail if it ignores the timing of customer commitments, reporting cycles, seasonal demand or existing workload. Better decisions recognise these realities early and make a conscious choice about what the organisation can genuinely absorb.
Ask the question at the right level
Not every uncertainty deserves the same level of governance. A low-risk, easily reversible choice can often sit with the delivery team, provided its boundaries are clear. A decision that changes customer experience, compliance exposure, expected benefits or a major operational commitment needs sponsor attention. Matching the route to the consequence avoids two unhelpful extremes: escalating everything, or allowing important decisions to happen by accident.
Before escalating, ask what additional information would genuinely change the answer. If the answer is “none”, make the decision. If the answer is “a small test, a cost estimate or feedback from the people doing the work”, define that next step and the date on which the decision will return.
A calm, practical next step
Before your next steering discussion, try writing the decision question, the two or three realistic options, the known facts, the assumptions, the operational impact and the review trigger on one page. If the choice is still unclear, that is useful information: the team may need a smaller experiment or a better question.
If you are balancing project delivery, governance and the practical realities of change, I would be happy to discuss a proportionate approach that helps decisions move work forward.
About Mark M Barton
I am a Change Management, Change/Internal Communications, and Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
