You will be able to turn the conversation into a specific request the other person can say yes or no to.
Many difficult conversations go well right up to the end, and then fizzle. Both people feel better. There has been some understanding, maybe an apology. Everyone says "okay, let's try to improve things". A month later, nothing has changed, and the person who raised it feels worse than before, because now they have tried and it did not work.
What was missing was a request. Feeling understood is not the same as agreeing what happens next. This lesson is about ending the conversation with something specific the other person can say yes or no to.
Marshall Rosenberg's Nonviolent Communication, which you met in lesson 4.3, ends with a request. Rosenberg was specific about what makes a request work. A request needs to be concrete, so both people know exactly what is being asked, and doable, meaning the other person can actually carry it out. Rosenberg also wanted it phrased as what you want, rather than what you do not want.
That last point is easy to miss. "Stop sending your section late" tells Ben what to avoid but not what to do instead. "Could you send your section by the 4th?" gives him something to act on.
Compare two versions. "Please be more responsible about deadlines" is a hope dressed up as a request. It does not say what responsible looks like, by when, or how anyone would know if it happened. "Could you tell me by Wednesday if a deadline is at risk?" is specific, doable and positive. Ben knows exactly what to do, and both of them will know whether he did it.
Most vague requests are vague because the person asking has not decided what they actually want. So before the conversation, decide. If the other person said "fine, what do you want me to do?", what would you answer?
Rosenberg drew a sharp line between requests and demands. A request means the other person can say no, and you will respond to the no with curiosity rather than punishment. If saying no is not really allowed, what you are making is a demand.
There is nothing wrong with demands when they are honest. A manager can require a deadline. A client can insist on terms. A safety rule is not up for negotiation. The trouble comes when you dress a demand up as a request. "Could you maybe get it to me by the 4th?", said in a tone that makes clear there is only one acceptable answer, confuses people and breeds resentment. They feel they were asked, then punished for not saying yes.
So be honest about which you are making. If no is acceptable, ask, and be ready to hear it. If no is not acceptable, say so plainly and kindly: "I need it by the 4th. If that's not possible, I need to know now so I can raise it with our manager."
For Jia Hui, a no was acceptable, because she and Ben were peers. If he could not commit to the 4th, the next step was to work out together what he could commit to, or to take it to their manager jointly.
A good request ends in an agreement, and a good agreement answers three questions: who will do what, by when?
Jia Hui and Ben's conversation ended with two agreements. Ben would send his section by the 4th of each month, or message her by the 2nd if it was at risk. And they would both raise the deadline with their manager at the next team meeting, to clear up the "some flexibility" message. Jia Hui would add it to the agenda.
Each agreement has a name, an action and a date. Nothing is left as "we'll try to improve communication".
If the other person counter-offers, take it seriously. Ben said the 4th was tight in a client-heavy month and asked for the 5th, with a message by the 3rd if needed. Jia Hui thought about it and agreed, because the 5th still gave her a working day to consolidate. That small adjustment made the agreement his as well as hers.
People remember conversations differently, especially emotional ones. A week later, both of you will be sure of what was agreed, and you may not be sure of the same thing.
So after the conversation, send a short written follow-up. Keep it friendly and factual: thank them, list what was agreed with names and dates, and invite correction. Think of it as a shared record that either of you can point back to, written in a tone that would look odd in a contract.
Jia Hui's message to Ben that afternoon read: "Thanks for talking it through this morning, that helped a lot. Just so we're both on the same page: you'll send your section by the 5th each month, and message me by the 3rd if it's at risk. I'll put the deadline on the agenda for Thursday's team meeting so we can both check with our manager. Shout if I've got any of that wrong."
That message took two minutes to write. It also did something less obvious: it showed Ben that she was not going to hold a grudge, because the tone was easy, and it showed that she was serious, because the dates were there in writing.
The request is the part of a difficult conversation people are most likely to leave out, because it feels pushy. Writing it in advance makes it far easier to say. You know what you are going to ask for, you have checked that it is specific and doable, and you have decided whether a no is acceptable.
In the activity below you write one specific request for your own conversation, and the follow-up message you would send afterwards to confirm what you agreed.
Write one specific request for your conversation and a follow-up message that confirms what you both agreed.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).