top of page
Search

Why wont Your Board Still Won’t Make that Decision

Writer: Chris Gracie
Chris Gracie
19 hours ago
6 min read
You’ve done the work and explored the options. You may have even gone to market and selected a preferred supplier. Yet every time the decision gets close, another question sends it around the loop again.

Why can’t we keep what we’ve got?

Did we look at other options?

Why does it cost this much?

Could we wait another year?


So you do more work. More analysis. Another conversation. Another presentation. You’re putting more and more work into the decision without actually getting any closer to making it.


Then something happens outside the business. A similar organisation makes the news because its technology programme has blown its budget, run late or had a difficult go-live.

Suddenly, there’s a fresh round of questions.


Could that happen to us?

Have we underestimated the risk?

Are we really ready to commit to this?


And around you go again.


This can go on for six months. Sometimes SO MUCH longer.


At this point, another 20 pages of analysis probably isn’t going to solve the problem. What might be missing is an anchor for the decision. Something that brings together what has already been agreed, why the recommendation has been made, the concerns that have been addressed, and the basis for moving forward. Something you can come back to when the next question arises, rather than reopening the whole conversation.


Your anchor might be a technology strategy, Board decision paper, investment roadmap, options paper, procurement recommendation, or independent assurance report. Different products anchor different decisions. But when you’re asking a Board to commit significant money to a technology investment, the strongest anchor is usually a good business case.


A business case connects the case for change; strategic options, investment, value, timing and risk into one coherent decision. Once agreed, it draws an important line in the sand. This is what we know. This is what we’ve considered. This is why we believe we should proceed.


Having the business case changes the nature of questions that are raised by the Board. Instead of every new concern sending management off for another lap, you can test it against the case, decide whether it materially changes anything, and move the decision forward. If it doesn’t, you have an agreed position to come back to and review.


That’s the real value of a good business case. It's just the document, but the process of getting there, the alignment it creates, and the milestone it marks once the case is agreed.



The questions that keep sending decisions around the loop

The questions coming from Board members are usually reasonable. In fact, they’re exactly the questions you want a Board to ask before committing the organisation to a major investment.


The problem is when there’s no common framework for answering them. Instead of testing one part of the decision, each new question can reopen the whole thing.


A good business case It gives each question somewhere to be addressed, without sending the entire decision back to the beginning.


Here’s what that looks like in practice.



1. “Why can’t we just keep what we’ve got?”

This is one of the most important questions to answer early.


Management may have lived with the limitations of the current system for years, but the Board hasn’t... From their level, keeping what you already have can look like the cheapest and safest option.


A good business case makes the case for change explicit. It describes the current position, its limitations and risks, and what happens if the organisation does nothing. Doing nothing should be an option that has been properly assessed, rather than something that can reappear every few months as a path of least resistance.

The conversation can then shift from:

“Why can’t we just keep what we’ve got?”

to:

“We could keep it, but we’d still need to spend money supporting it, carry the risks we already have, and accept that it won’t give the business what it needs next. That doesn’t sound like the safer option anymore.”

The business case anchors why something needs to change.


2. “Did we look at other options?”

This question can send management straight back to the drawing board.

But often this question isn’t really about whether another vendor was considered. It’s the Board testing whether management has chosen the right strategic direction before committing to a solution.


Could we upgrade what we have?

Could we outsource it?

Do we build something ourselves?

Do we buy an off-the-shelf platform?


These are fundamentally different ways of solving the same business problem and a good business case will demonstrate that all credible alternatives were considered before the preferred solution was selected. It establishes how they were assessed, the trade-offs involved and why one direction came out ahead.


The question can then become:

“So we could upgrade, build or buy, but once we compare cost, time and risk, buying is the strongest option. I can see why we’ve chosen this direction.”

The business case anchors why this direction was chosen.


3. “Why does it cost this much?”

When a supplier gives you a price It doesn’t necessarily tell the Board what the organisation is really investing, or what it expects to get in return.


The true cost may include implementation, integration, data migration, internal effort, change management, contingency and ongoing operating costs. But even the total cost doesn’t mean much on its own. It needs to be weighed against the expected benefits, the timeframe for realising them, and the cost and risk of doing nothing.

A good business case changes the conversation from price to value.

The conversation can then move from:


“Why does it cost this much?”

to:

“This is the total investment required to achieve the outcome, not just the supplier price. We understand what makes up that investment, what we expect to get back, and over what period. The question is whether that value justifies the investment.”

The business case anchors the economics of the decision.


4. “Could we wait another year?”


Of course you could.


But waiting isn’t a neutral position. It’s another option, with its own costs, risks and consequences.


Another year might mean another year of manual work, support costs and operational risk. It might mean delaying benefits, missing opportunities, or continuing to invest in something the organisation already knows it needs to replace. A good business case puts the cost of waiting alongside the cost of acting now. So the conversation moves from:


“Could we wait another year?”

to:

“We could wait. But we know what another year will cost us, which risks we’ll continue to carry, and which benefits we’ll delay. What do we gain by waiting?”

Sometimes waiting will be the right decision. But it should be a deliberate choice supported by the evidence, not simply what happens because a decision wasn’t made.


5. “Could what happened to them happen to us?”

You’ve definitely seen this one before. Another organisation has a major technology programme run over budget and it hits the news. An implementation fails publicly. A troubled go-live becomes the story everyone is talking about. Suddenly, your project is in the spotlight and a decision that felt well understood starts to feel a lot less certain around the Board table.


External triggered concern shouldn’t be dismissed. But it also shouldn’t automatically send the whole decision back to the beginning. A good business case gives you something to test the new information against.


What actually went wrong?

Do we face the same risks?

Have we accounted for them?

Are our controls strong enough?

Does anything we’ve learned materially change the case?


If it does, update the case. If it doesn’t, address the concern without reopening everything that has already been settled. The conversation can move from:

“Could the same thing happen to us?”

to:

“It could. But we now understand what went wrong there, where we have similar exposure, and what we’re doing differently. If our controls aren’t strong enough, that’s what we need to address before proceeding.”

The business case anchors the risk conversation when new information emerges.


Build the confidence your Board needs to make the decision

In my experience, A Board doesn’t need every possible question eliminated before it can make a decision. It needs enough confidence that the recommendation is sound, the investment makes sense, the risks are understood, and management knows what it is taking on.

A good business case is a key tool you can use to build that confidence. It gives the Board something to challenge, something to come back to when new questions emerge, and something that holds the decision together.


Need to get an important technology decision moving?

If your technology decision keeps coming back around the table, more analysis may not be what’s missing. Pro Partner helps leadership teams establish the case for change, assess the options, test the investment, work through commercial and delivery risk, and build the evidence executives and Boards need to make the call.




 
 
bottom of page