Not all agreement is the same. There are three distinct types of yes, and conflating them is one of the most common and costly mistakes founders and product teams make — in customer conversations, in leadership reviews, in hiring, and in building internal alignment.
The committed yes
This is the only yes that actually drives results. A committed yes is backed by intention, resources, and urgency. The person saying it is genuinely agreeing to take action. They know what that action is, they have what they need to do it, and they're motivated to follow through.
The tell: they do something. The deal closes. The feature gets prioritized. The decision gets made and held. If you're not sure whether you got a committed yes, watch what happens next.
The confirmation yes
This is an acknowledgment, not a decision. "Yes, I understand what you're proposing." "Yes, that makes sense." "Yes, I can see how that would solve the problem." All of these are confirmation yeses — they're saying they've heard you and tracked with you, not that they're going to act.
Confirmation yeses build alignment but don't close deals or move roadmaps. A customer who understands your product isn't a customer. A leader who agrees with your strategy isn't a sponsor. You need to get from confirmation to commitment, and the path there usually involves making the cost of inaction real.
The counterfeit yes
This one is the most expensive. It sounds like agreement but hides uncertainty, conflict avoidance, or a competing priority that never gets surfaced. People give counterfeit yeses to end conversations, to avoid conflict, to buy time, or because they genuinely don't know how to say no in that context.
"So many people said they love my idea." Great — did any of them give you money?
In customer discovery, the counterfeit yes is endemic. "That's a great idea." "I can totally see how someone would use that." "We'd definitely be interested in something like this." None of these are commitments. They're politeness. The customer is giving you the answer they think you want because rejecting your pitch feels unkind.
On internal teams, the counterfeit yes shows up in roadmap reviews, design critiques, and quarterly planning. Someone in the room has a real objection but doesn't raise it. The plan moves forward with an apparent consensus that doesn't actually exist. Six weeks later, the thing falls apart — and the person with the objection says "I knew that wasn't going to work."
How to get real signal
The discipline is giving people a genuine chance to say no — and making it safe enough that they will. In customer conversations, that means asking them to do something before the conversation is over: pre-order, commit budget, intro you to their team, something with friction. A customer willing to take a real action is a committed yes. A customer who says they love it but won't take an action is a confirmation at best, a counterfeit at worst.
In internal alignment conversations, it means directly asking "what would make you not support this?" Give the room permission to surface the objection in the meeting rather than after it. The conversation is harder. The outcome is better.
Your roadmap should be built from committed yeses — from customers who demonstrated need with real behavior, from stakeholders who put their name behind it. Anything else is a wish list with dates.
