Kind Is Not Yes

This article contains affiliate links. Full disclosure.

The call felt good.

Too good. They nodded at every slide, praised the idea, and gave you the sentence that ruins more young products than a hard no ever could.

"Keep me posted."

You left with a little heat in your chest. Not proof exactly, but something close enough to borrow confidence from. The notes looked promising. The faces were warm. Someone even said they could "totally see teams using this."

Then the week passed. The follow-up sat there. No calendar invite. No forwarded intro. No messy spreadsheet. No budget owner pulled into the thread. No price question sharp enough to draw blood. Just silence with good manners.

This is one of the nastiest traps in building anything: positive feedback that costs the other person nothing. It feels like market signal because it arrives wearing human warmth. It is often just social smoothness. A little kindness placed gently over the awkward fact that nobody has committed to anything.

The False Diagnosis Is Confidence

The usual diagnosis is that you need to pitch better. Tighten the deck. Make the demo cleaner. Add the missing slide. Sound less nervous. Ask a sharper closing question. Practice until your voice stops doing that tiny betrayal at the end of the sentence.

Sometimes, yes. A bad pitch can bury a good thing. But that is not the deeper problem here. The deeper problem is that you are asking questions designed to produce encouragement instead of evidence.

"Do you like this?" is not a discovery question. It is a request for emotional anesthesia. The other person can answer yes, feel generous, avoid hurting you, and leave the room without changing a single inch of their life.

Rob Fitzpatrick built The Mom Test around this rude little truth: people will give you bad data when your questions make kindness too easy. They are not villains. They are humans in a mildly uncomfortable social situation, and you have handed them the softest exit in the room.

This is why your notes can look beautiful while the business stays still. You collected reactions. You did not collect stakes. You heard what people think of the idea in the clean room of a conversation, not what they do when the actual problem is making a mess on a Tuesday.

Compliments are not useless. They can reveal language. They can show you which part of the story made someone lean forward. They can tell you where the emotional surface is. But they are not proof of demand. They are not proof of urgency. They are not proof of willingness to change.

A compliment is a warm object. Signal is heavier.

The Yes Has a Body

A real yes usually leaves the meeting carrying something. A calendar hold. A forwarded email. A budget objection. A file they were embarrassed to show you. A live workflow. A sentence like, "Can this be ready before the next review?"

The yes has a body. It takes up space in someone's day. It asks for a handoff. It creates a small inconvenience. It makes the person spend a little attention, a little access, a little risk, a little reputation, or a little money.

Nielsen Norman Group puts the usability version bluntly: pay attention to what users do, not just what they say, because self-reported claims and future speculation are unreliable when you are trying to understand behavior. Founders love to pretend sales is exempt from that rule because the conversation felt honest. It is not exempt. The mouth is generous. The calendar is stricter.

This is the difference between approval and commitment. Approval lives in tone. Commitment lives in behavior. Approval says, "That makes sense." Commitment says, "Send it to me before our Monday meeting." Approval smiles at the concept. Commitment drags a real problem into the room and lets you touch it.

If you only listen to approval, you will build for a person who exists only during the call. That person is thoughtful, optimistic, generous, and full of imaginary future intent. They disappear the moment Slack reopens, the boss asks for something, a customer complains, or the day resumes its normal violence.

The buyer you need to study is less charming. They are late. They are tired. They are using a broken spreadsheet because replacing it sounds annoying. They do not care how clever your system is. They care whether it removes a pain that is already costing them something.

That buyer is harder to impress. Good. They tell the truth faster.

The Velvet No

Most polite feedback is not deception. It is maintenance. The person is maintaining the room, the relationship, their self-image as someone supportive, and your self-image as someone who brought them something worth hearing.

That is why the soft maybe is so dangerous. A hard no wounds the fantasy immediately. A soft maybe lets the fantasy walk around for weeks wearing a visitor badge.

"Interesting." "Smart." "I like where this is going." These phrases feel better than rejection because they keep every possibility alive. They also keep every decision unpaid. Nothing has to be chosen. Nothing has to be risked. Nothing has to be installed into reality.

This is the velvet no. It is rejection with upholstery. It does not slam the door. It gives you a comfortable chair in the hallway and lets you wait there like a fool.

The stuck builder secretly prefers the velvet no at first because it preserves identity. You can tell yourself the market is warming up. You can refine the offer. You can have another round of calls. You can extract another sentence from another friendly person and place it in the evidence pile where only behavior belongs.

Then months pass and you realize the pile was padded. It was full of social kindness, borrowed enthusiasm, and future-tense fog. The market was not warming up. You were warming yourself by the exit sign.

Future Tense Is Cheap

The worst questions invite people to imagine a better version of themselves. "Would you use this?" "Would your team pay for this?" "Would this save time?"

Of course they say yes. In the future, everyone is decisive, rational, well-funded, and finally ready to fix the thing they have ignored for two years. Future people are excellent customers. Unfortunately, they do not buy software. Present people do.

Present people have habits, politics, existing tools, half-owned budgets, emotional resistance, procurement weirdness, and a private tolerance for pain that may be much higher than they admit. Your job is not to ask their future self for permission. Your job is to locate their present behavior and see whether the problem already has gravity.

Product Talk describes product discovery as decision-making work that should include the customer throughout the process rather than a separate guessing ritual. That distinction matters. You are not interviewing people to feel brave. You are bringing their actual behavior into the decisions that would otherwise be made by your optimism.

Past tense is dirty in the useful way. "When did this last happen?" "What did you do?" "Who noticed?" "What broke?" "What did it cost?" Those questions do not let the ideal buyer perform. They force the real buyer to walk you through the floor where the problem lives.

Present tense is useful too. "Can you show me the current workaround?" "Can we try this on the next live case?" "Who else has to approve it?" "What would make this a no?" These questions take the oxygen away from vague encouragement. The answer either starts behaving like a signal, or it collapses into manners.

That collapse is not failure. It is mercy arriving early.

Build a Commitment Surface

A commitment surface is any place in the conversation where a nice opinion has to become behavior or disappear. It is not pressure theater. It is not bullying someone into a close. It is a clean test of whether the problem is strong enough to move anything.

The smallest commitment may be a calendar hold. It may be access to a real file. It may be an introduction to the person who owns the budget. It may be permission to watch the ugly workflow. It may be a paid pilot. It may be a pre-order. It may be a promise to use the rough version on the next real case and send back the result.

Do not worship money too early. Money is beautiful because it tells the truth loudly, but attention and access tell the truth before money is socially available. A person who will not spend five minutes showing you the current mess is unlikely to spend serious money replacing it.

Product Talk's guide to assumption testing makes the same operating point from another angle: teams need a regular cadence of tests to learn which ideas will work and which will not before too much belief hardens around the wrong thing. Your customer conversation is one of those tests. Treat it that way.

Before the call, decide what assumption is on trial. Is the pain real? Is the current workaround expensive enough? Does the buyer own the problem? Is the person with pain also the person with power? Does the promised outcome matter this month, or only in a prettier imaginary quarter?

Then design the moment where the answer has to spend something. If the assumption is urgency, ask for a live case. If the assumption is budget, ask what they already pay to manage the problem. If the assumption is access, ask for the introduction while the conversation is still warm. If the assumption is usage, place the rough thing into the next real workflow and see whether it survives.

This will make some calls less pleasant. Excellent. Pleasant was never the goal. Clear is the goal.

The No Gives You Back the Road

A real no is not the enemy. A real no gives you the road back. It tells you the pain is weak, the buyer is wrong, the timing is bad, the budget is elsewhere, the workflow is stickier than you thought, or the offer is solving a problem people would rather complain about than change.

That hurts. It also gives you material. You can change the buyer, change the promise, change the channel, change the price, change the scope, or stop spending your life polishing a door nobody is trying to open.

The velvet maybe gives you none of that. It lets you keep sanding the same handle. It feeds the part of you that wants progress without market contact, courage without exposure, sales without the possibility of being refused.

This is why kind feedback can be more dangerous than hostile feedback. Hostility is easy to discount. Kindness feels like proof because it seems emotionally expensive. It is not. Most people can be kind for free. Very few will rearrange their day for a problem they do not actually feel.

So let kindness stay where it belongs. Let it be human. Let it make the room less cold. Let it show you which words landed. But do not let it sit in the evidence column unless it came attached to behavior.

Your evidence column should be almost rude in its standards: paid, scheduled, introduced, shown, forwarded, installed, tested, repeated, complained about, renewed, referred, or used when nobody is watching.

The Next Call

On the next call, do not enter looking for belief. Enter with one decision you need the conversation to make. The smaller and sharper the decision, the harder it is for vague warmth to sneak through wearing a lab coat.

Ask about the last time the problem happened. Stay there longer than feels polite. Make them walk you through the tabs, tools, people, workarounds, delays, approvals, and little humiliations that surround the problem. Do not rescue them with your idea too early. If the pain is real, the story will have edges.

When they praise the idea, thank them and translate the praise into a test. "Can we try it on the next live case?" "Would you send me the ugly version you use now?" "Who would block this?" "If I build the rough version, what has to happen for you to keep using it?"

If they dodge, believe the dodge. Not as a moral judgment. As data. The problem may still be real, but not urgent. The person may be sincere, but not empowered. The idea may be liked, but not wanted enough to survive contact with their calendar.

If they commit, protect that signal. Move fast. Send the recap. Put the next action in writing. Get the file, the date, the intro, the payment, the test case, or the explicit no. Do not let a living signal decay into another pretty memory.

This is less flattering than being liked. It is also cleaner. A builder can survive rejection. What kills them is months of being politely encouraged by people who never had to mean it.

The call will still feel human. It may even feel warm. But now the warmth has to pass through a door before you count it.

Some people will say no. Some will say not now. Some will vanish the moment the conversation asks for a real next step. Let them. The fog is leaving the room.

And when one person opens the calendar, forwards the ugly file, asks the price, brings in the owner, or lets your rough thing touch a real wound, you will feel the difference immediately.

It will not sound as kind.

It will be much more useful.