The executive is already talking about launch dates.
You are still wondering whether customers have the problem.
Someone presents an impressive demonstration. You know how much manual work happened behind it.
You ask what the team should learn before committing. The answer is that everyone needs to get behind the vision.
Nothing has failed yet. But something already feels wrong.
Eighteen months later, the project may finally uncover the limitations people sensed at the beginning. By then, money has been spent, other opportunities have passed, and employees have invested a meaningful part of their working lives.
The painful question is: Why did we spend so long discovering something we could have investigated much earlier?
When questions become tests of loyalty
An executive “falling in love with an idea” means something specific here: becoming so attached to a solution that questions about its assumptions are treated as questions about commitment.
Conviction can help a team attempt difficult things. Every ambitious project carries uncertainty, and waiting for complete certainty can become its own mistake.
But accepting uncertainty requires being willing to examine it.
When leadership expects full commitment while refusing reasonable opportunities to uncover risk, employees face an uncomfortable bargain. They are asked to invest their effort, reputation, and time in assumptions they have little authority to challenge.
The executive owns the decision. The team still lives with its consequences.
Give your gut feeling something concrete to say
Your unease may contain useful experience: customers repeatedly avoiding a workflow, integrations proving harder than expected, or previous demonstrations concealing operational weaknesses.
It may also contain fear of change, frustration with the executive, or attachment to your own preferred solution.
Daniel Kahneman and Gary Klein’s research offers a useful distinction: intuition is more trustworthy when someone has learned recurring patterns in an environment that provides meaningful feedback. The strength of a feeling does not establish its accuracy. Conditions for Intuitive Expertise
Treat discomfort as a reason to investigate. Give it a precise form:
“I am concerned that customers will appreciate the demonstration but will not change their existing workflow to use this.”
Or:
“I am concerned that the prototype depends on manual intervention that makes the proposed operating cost unrealistic.”
Now there is something the team can test.
Apply the same discipline to your preferred alternative. Feeling that another opportunity was better does not prove it would have succeeded.
Understand what is at stake for you
Before discussing the project, separate the observable event from your interpretation.
The event might be: “The executive declined customer testing and asked for a delivery estimate.”
Your interpretation might be: “They do not care whether this works.”
Your emotion might be anxiety about blame, anger about wasted effort, or disappointment about the work you will have to postpone.
Underneath that emotion may be a need for professional integrity, meaningful contribution, or a reasonable say in how your time is used.
Consider what you might be missing. The executive may be responding to a competitive threat, a deadline, or information the team has not seen.
That possibility gives you a useful opening:
“What makes committing now more valuable than spending a short period testing the most consequential assumption?”
Understanding their reasoning can improve the conversation. An unanswered concern still remains unanswered.
Separate the risks
“Will this work?” is too broad. A product can work technically and still fail commercially.
| Risk | Question to investigate | Useful early evidence |
|---|---|---|
| Market | Will customers change their behavior and pay? | A realistic pilot, observed use, or a buying process involving meaningful commitment |
| Technology | Can we achieve the required performance, reliability, and cost? | Testing the hardest dependency under representative conditions |
| Opportunity | What valuable work will this displace? | Comparing credible alternatives using the same people, time, and budget |
A positive customer interview does not establish willingness to buy. A successful demonstration does not establish production readiness.
NASA’s technology readiness framework distinguishes early demonstrations from validation in relevant and operational environments. The underlying lesson travels well: evidence should match the conditions under which the technology must actually work. NASA: Technology Readiness Levels
Opportunity cost needs an explicit question, too:
“If this takes two engineers for six months, which customer problem are we choosing to leave unresolved?”
The proposed project and its alternatives should face comparable scrutiny.
Propose a commitment with a review point
A debate about whether the executive is right can quickly become personal. A specific proposal gives the conversation something practical to resolve:
“I understand the outcome we want. My concern is that the plan assumes customers will replace their existing process. Before we allocate the full team, I propose a discovery phase with a fixed budget and a review date. Can we agree what evidence would justify expanding, changing, or stopping?”
The proposal should identify:
- The assumption most likely to undermine the project.
- The smallest credible test of that assumption.
- The time and resources required.
- The evidence that would change the decision.
- The person responsible for that decision.
Some risks need more than a few interviews or a quick prototype. Choose a test that can produce useful information, and acknowledge what will remain uncertain.
Agree on how results will be interpreted before they arrive. Otherwise, disappointing evidence can always become a reason to try harder.
Ask:
“What result would lead us to reduce or stop this investment?”
If no possible result qualifies, the team needs to understand that the direction is effectively fixed.
Make honest reporting possible
Testing achieves little when people expect punishment for reporting what they find.
Amy Edmondson’s study of 51 work teams found an association between psychological safety and learning behavior. The practical implication is relevant here: people need room to raise questions, discuss mistakes, and share unwelcome information. Psychological Safety and Learning Behavior in Work Teams
Where possible, raise your concern privately first. Connect it to the outcome the executive cares about. Ask what information you may be missing.
You can also clarify what you are committing to:
“I can commit to doing the work carefully and reporting what we learn. My confidence in the commercial outcome still depends on these assumptions.”
Professional effort and confidence in a forecast are different commitments.
Careful phrasing can help. It cannot make every leader receptive, and employees should not be blamed for failing to make an unreceptive environment safe.
When leadership refuses to investigate
There is a limit to what better communication can achieve.
If leadership repeatedly declines relevant evidence, changes the success criteria, or holds employees responsible for assumptions they cannot examine, you face a decision about your participation.
Record decisions neutrally through normal work channels:
“We are proceeding with the build before validating willingness to pay. That remains an open assumption. The next investment review is scheduled for [date], with [owner] responsible for the decision.”
This can preserve shared understanding. It cannot guarantee protection from blame.
Seek a trusted manager or an appropriate review forum where one exists. If disagreement has already led to retaliation, consider the likely consequences before escalating.
Set a personal review point:
What would I need to see over the next few months to keep choosing this work?
Perhaps you need permission to test assumptions, honest reporting, useful learning, or a credible opportunity to move to another team. Your options will depend on your circumstances.
You do not need to wait for a definitive public failure before considering them.
Your working life belongs in the calculation
It is possible to be right about a project and still feel that you lost something by staying.
Eventual vindication will not return the time, restore every missed opportunity, or make the experience worthwhile.
Your earlier opportunity is to make concerns specific, seek proportionate evidence, clarify who owns the decision, and decide how much of your working life you are willing to invest under those conditions.
Before your next conversation, ask yourself:
What have I observed? What am I assuming? What evidence would change my mind? What decision or boundary do I need now?
A DeepMirror check-in can help you explore the emotions, values, and communication choices underneath those questions. Use that reflection to prepare your next conversation, and let customer and technical evidence inform the investment decision.
Sources and further reading
To prepare for the conversation: Explore influence conversations with DeepMirror.