Key takeaways
The room agrees. The vendor has presented. The internal champion is nodding. The executive sponsor asks if there are any concerns, and nobody speaks.
On this page
The room agrees. The vendor has presented. The internal champion is nodding. The executive sponsor asks if there are any concerns, and nobody speaks.
Six months later, the pilot stalls.
In the post-mortem, three different people say some version of:
“I had a bad feeling about that from the start.”
The information that could have changed the decision was in the room. It just wasn’t spoken.
This is not a soft-skills problem. It’s a structural one.
When organisations are deciding whether to invest in a digital twin, deploy VR training, or commit to an AI programme, different people around the table have different incentives. Sometimes the most important information is precisely the information nobody wants to introduce into the conversation.
What the Vendor Isn’t Saying
Vendors know their products better than anyone. Good vendors are honest about their strengths, but naturally focus their attention on where their technology can deliver value.
That means the buyer has to actively explore what isn’t in the presentation.
Ask how many reference customers are still using the product two years after go-live, at the same scope.
Ask what the average implementation actually cost. Not just the licence fee, but integration, data preparation, change management and the internal resources required to make it work.
Ask which capabilities demonstrated in the sales process required additional professional services.
You will get answers.
The important thing is that you asked the questions.
What the Consultant Isn’t Saying
Consultants face a different incentive.
If a consultancy concludes that the technology is too immature, the organisation isn’t ready, or the business case doesn’t stack up, it may be talking itself out of an engagement.
So the conversation can easily shift towards what is possible rather than whether it is the right thing to do.
Every risk becomes a workstream.
Every capability gap becomes a programme.
Every problem appears solvable with the right implementation.
A useful test is simple:
Ask a consultant what they have recently told a client not to do, and why.
A willingness to recommend “not yet” can tell you a great deal about how independently they are assessing the opportunity.
What Your Own Team Isn’t Saying
The hardest omissions are often internal.
The engineer who thinks the data infrastructure won’t support what is being promised, but doesn’t want to be the person who kills the innovation project.
The operations manager who knows the frontline workforce won’t adopt the tool, but has learned that raising the concern can be interpreted as resistance to change.
The finance partner who has watched the last three transformation programmes miss their numbers and has stopped pointing it out.
These concerns don’t necessarily remain hidden because people are dishonest.
They remain hidden because raising them can have a cost.
And when meetings reward enthusiasm and make friction uncomfortable, people learn to keep the friction to themselves.
Eventually, it appears somewhere else — as scope creep, poor adoption, cost overruns or a stalled implementation.
How Do You Surface What Isn’t Being Said?
There are a few approaches we’ve found useful.
Ask the negative version of the question
Instead of asking:
“Will this improve safety outcomes?”
ask:
“Under what conditions could this make safety outcomes worse?”
The second question creates permission to discuss failure rather than simply justify the investment.
Separate advocacy from evaluation
The people who benefit from a project going ahead should not necessarily be the only people assessing whether it should.
This isn’t about mistrust. It’s about recognising that incentives influence how decisions are presented.
Give sceptics a formal voice
On one engagement, we explicitly asked team members to argue the case against the investment.
It changed the scope of the decision.
Arguments that would probably never have surfaced in a conventional review became part of the conversation.
Ask what happened last time
Every organisation has adopted technology before.
What did the vendor promise that didn’t materialise?
What did the internal team underestimate?
What created unexpected costs?
What prevented adoption?
The answers are often more useful than another presentation about the future.
Patterns have a habit of repeating.
Why We Care About This
This is one of the reasons we developed the GreenSpot Framework.
GreenSpot looks at three things:
Technology maturity. Is the technology capable of delivering what is being proposed?
Organisational readiness. Is the organisation actually prepared to adopt and operate it?
Commercial opportunity. Does the business case make sense?
The value isn’t in the framework itself.
It’s in bringing the right questions into the room.
The vendor’s timeline meets the organisation’s actual capacity for change.
The consultant’s roadmap meets the finance team’s experience of previous programmes.
The innovation champion’s enthusiasm meets the engineer’s assessment of the data.
Sometimes the answer is green and we build.
Sometimes it’s yellow and we scope a smaller, more controlled pilot.
Sometimes it’s red and we recommend waiting.
All three answers can be valuable.
Only the first one leads directly to a larger engagement, but we’ve learned that saying “not yet” earns more trust over time than saying “yes” to something that is unlikely to succeed.
The Question Worth Asking
The most valuable contribution someone can make to a technology decision is often the thing nobody else in the room is prepared to say.
If you’re the executive sponsor, you don’t need to have every answer.
But you do need to create an environment where someone can challenge the answer you have.
Before committing significant capital to AI, digital twins, AR, VR or any other emerging technology, ask:
What is it that we’re not saying?
And then give someone permission to answer.