A NO can hit surprisingly hard. Especially when you made an effort for something, showed yourself or really believed that you were making a good proposal. A customer says NO. Your employer chooses someone else. A loved one does not want something. Your child refuses just about everything you have lovingly created. The word consists of three letters, but we are perfectly capable of building a complete autobiography around it in just a few seconds.
I know that mechanism. A NO is rarely just about what is said at that moment. We bring our previous experiences to the conversation. If you have often heard that something was not for you, that you could not do something or that you were not businesslike, smart, attractive or experienced enough, a new NO can connect remarkably easily to a much older story. Before you know it, you no longer hear: “I am not choosing your proposal now.” You hear: “See, you're not good enough.”
And those are two completely different messages.
When someone else's voice becomes your own
Someone once told me that her father said she would never be businesslike enough to own her own business. Her father had now passed away, but his judgment still cheerfully contributed to important business decisions. Not because he said it again. She had now taken over his voice herself.
I find that a confrontational but important distinction. We can respond for years to words that are no longer spoken at all in the here and now. Not because we are weak, but because previous experiences determine the meaning we give to new situations.
That starts early. As a child you ask for a piece of candy and you get NO. A little later you ask again, this time with more persuasiveness. Maybe crying will help. Sometimes stomping feet. Maybe a charming look at grandma. Children are excellent researchers of negotiation techniques. We slowly learn that a NO can mean different things: not now, not this, if not, I want something else, or sometimes simply NO.
However, as adults we often forget that distinction.
A NO is often about interests, not about your value
You also notice this in business. A customer who rejects your proposal does not automatically say anything about your quality. Perhaps there is a lack of budget. The customer may see the problem differently. Maybe the timing is wrong, the risk is too great or the decision-making is internally more complicated than you know. And yes, sometimes someone just doesn't think your offer is good enough. That can also happen without you as a person having to be immediately redesigned.
The same applies in other relationships. An employee who is not enthusiastic about your plan is not necessarily unmotivated. A supplier who refuses a condition is not automatically difficult. A partner who wants something different is not against you. Behind a position there is usually an interest, need, boundary or concern that you are not yet fully aware of.
That's exactly why I find the simple choice between giving in and fighting less and less interesting. There is a third option: research. What does this NO actually mean? What is he about? What is the other person trying to protect? And what does my own response to that NO mean?
That's where adult communication starts for me.

You don't have to immediately turn a NO into a YES
That's also why I wrote the original title How do you turn a NO into a YES? would change now. There is something in that formulation that no longer fits with how I view communication. As if NO is just an annoying way station on the way to the answer we actually wanted.
Sometimes a NO should just remain a NO.
The trick is not to overcome every rejection. The trick is to understand whether there really is a conflicting interest, a misunderstanding, missing information, insufficient trust or simply a boundary that must be respected.
A real YES only has value if someone was also free to say NO. This applies to customers, employees, partners and yourself. As soon as a YES arises mainly because someone is tired of your arguments, is afraid of the consequences or wants to get rid of you, you may have received an agreement but no connection yet.
The Connective Code helps me listen to NO differently
The Connective Code helps me to interpret less quickly and investigate better. When someone says NO, Vision may be missing: the other person does not see where your proposal leads or why it is relevant. With Trust, someone can understand the content of what you mean, but still have insufficient confidence in you, themselves or the relationship.
Structure may lack answers to practical questions. How is this going to work? What happens if things go wrong? Who does what? What certainty is there? And with Action, someone can be numb to all the information and need a clear decision, a small first step or a concrete moment when things will be re-examined.
The interesting thing is that the same thing also happens within yourself. A NO from outside can affect your own Vision: maybe I shouldn't want this at all. It can gnaw away at Confidence: you see, I can't do this. You can look for Structure by reanalyzing everything or take Action and immediately call ten other prospects so you don't have to feel that this one NO hurt.
None of those responses have to be wrong. It only helps when you recognize what you are doing.
Saying YES to yourself is different from always proving yourself right
I used to write that you first had to say YES to yourself. I still believe in that, but I mean something different by that now. Saying YES to yourself does not mean that you tell yourself in the mirror every morning that you are fantastic and then kindly return criticism from others to sender.
It means that you take yourself seriously enough to be able to listen to a NO without immediately attaching your own value to it.
Sometimes the other person is right. The proposal could be better. Maybe you need to learn something you can't do yet. Or is your timing wrong. To me, self-confidence does not mean that you are convinced of your own right. It means that you can receive information without doubting yourself with every disappointing answer.
That makes a NO suddenly useful. You can ask questions, learn, adapt, negotiate or decide that this is indeed not a fit. And then move on without having to pick up your entire identity off the floor first.
What do you hear when someone says NO?
Perhaps that is ultimately the more interesting question. Not: how do I still get my YES? But: what do I make of the NO I receive? Do I hear information, a boundary or some other interest? Or am I mainly hearing an old judgment that I have now started repeating myself?
With the Connective Code Quiz you will discover which language is naturally strong for you and what you need to understand and trust information, differences and decisions.
Have you encountered three concrete situations in which NO, resistance or conflicting interests keep getting stuck? Then include them in an introductory meeting. Together we look at what is actually said, what you may hear and where Vision, Trust, Structure or Action can help to move the conversation forward.