Free course
Communicating and leading, a lesson every weekday
A short daily lesson on saying the hard thing, asking for what you need, writing that works without you, and leading people. One framework, one story, one thing to try today.
Name two times: get a meeting on the calendar with one message.
Newest lesson · Lesson 68 · 5:51
You learn to schedule a meeting in one message by naming two specific times, stating your preference, and leaving an easy way out.
Listen to the lesson- 1.The gap between what happened and what you are about to say.5:39You learn the A-B-C model so you can separate what happened from the belief your mind added before you respond.
- 2.Blame is the wrong question, even when you know the answer.5:33You learn to replace blame with the contribution system from Difficult Conversations, so you can see how each person helped create a problem and decide what to change.
- 3.When fear outruns the facts.7:12You learn a four-pass way to keep fear from outrunning the facts: measure the danger, find trustworthy evidence, choose protective behavior, and handle the fear that remains.
- 4.Make the work visible and the room will follow.5:10You learn to make a shared problem visible so the room can work on the same thing instead of competing for airtime.
- 5.Making it cheap to tell the truth.5:01You learn how psychological safety lowers the social cost of naming a mistake, question, or concern while there is still time to act.
- 6.The tired brain turns pebbles into boulders.5:52You learn why sleep loss can magnify ordinary problems and how situation selection gives your tired judgment practical guardrails.
- 7.Make the clear ask. The DEAR MAN script.5:34You learn the DEAR MAN script for making a clear request, holding your position, and protecting the relationship.
- 8.Write it so it works without you: bottom line up front.4:49You learn bottom line up front, or BLUF, so your reader gets the decision or action first and the supporting reasons underneath it.
- 9.Ask for feedback you can act on.4:45You learn to ask for a specific kind of feedback so the answer gives you something you can actually change.
- 10.Getting things from people who do not work for you.5:18You learn influence without authority by noticing what other people value and making real deposits before you need their help.
- 11.Put the finding where the eye lands first.3:22You learn to put the most important finding where the reader looks first, then add the context needed to understand and act on it.
- 12.Name the feeling before you solve the problem.5:01You learn affect labeling: name the feeling in the room before trying to solve the problem, then leave space for the other person to correct you.
- 13.Stop rehearsing the argument that is not happening.5:58You learn to spot rumination and use cognitive defusion to stop treating an imagined argument as a problem you must solve right now.
- 14.Rest can have a learning curve.6:01You learn that recovery can come from chosen, absorbing effort, and how to tell restorative learning from another disguised performance demand.
- 15.Managing up is part of the work.5:54You learn managing up as the practical work of understanding what your manager needs, bringing decisions in a usable form, and making mutual dependence work.
- 16.Useful before perfect: how to give fast feedback someone can act on.4:25You learn to give fast feedback that identifies the decision, names what matters most, and recommends an action while the work can still change.
- 17.When the plan changes: how to set aside your work without losing it.2:54You learn how to pause changed work without wasting it by leaving a clear record of what exists, what remains, and how to restart.
- 18.Negotiate for the deal and the relationship.5:47You learn to negotiate both the deal and the relationship by separating warm intent from clear terms, risks, and review points.
- 19.Make the smaller role visible so it stays smaller.4:36You learn to make a reduced role visible by naming its limits, moving ownership, and accounting for the overhead attached to every commitment.
- 20.Do not invent a voice for a text message.4:46You learn not to invent tone for a text message, and to check the story created by egocentric anchoring before you respond.
- 21.The after-action review: twenty minutes that turn one success into a repeatable method.5:50You learn the after-action review: compare the plan with what happened, explain the difference, and capture what to repeat or change.
- 22.Leave the meeting, keep the connection.6:01You learn to treat being taken off a recurring meeting as a change in attendance, not in standing, and to stay informed by naming what should bring you back and asking for the decisions afterward.
- 23.Money already earned is not a negotiation.6:05You learn to separate money already earned from any negotiation about future work, keeping the person respected while staying firm on the settled obligation.
- 24.Shutdown complete: how to end a week when nothing is finished.5:06You learn a shutdown ritual that records open loops, names the next action, and lets your mind stop carrying unfinished work through the weekend.
- 25.Name the boundary before you join the rescue.3:42You learn to state your boundary before joining an urgent rescue, so your help has a clear scope, owner, and stopping point.
- 26.Meet people in the channel they actually use.4:02You learn to choose the channel people actually use, matching the message's complexity and urgency to the habits and experience of the receiver.
- 27.Rewrite the ask before you take it.4:27You learn to rewrite a vague request into a clear outcome, owner, timing, and dependency before accepting the work.
- 28.Give waiting an end date.6:47You learn to give waiting an end date by naming when you will check again and what you will do if no answer arrives.
- 29.Make praise specific, visible, and useful.5:31You learn to make praise specific, visible, and useful by naming the action, its effect, and what should be repeated.
- 30.Warm the bridge before you carry weight across it.5:46You learn to warm a relationship before bringing a heavy request, and to use a contrast statement so care and intent are clear.
- 31.A recurring caveat is an unfinished task.3:54You learn to treat a caveat that appears again and again as unfinished work, then assign the decision or fix instead of repeating the warning.
- 32.The question underneath the question: what to do when someone asks again.5:38You learn to hear a repeated question as evidence that the first answer did not settle the underlying concern, then answer that concern directly.
- 33.The demonstration is not the point.3:51You learn to design a demonstration around the audience's decision, showing the result first, the relevant path, and the places where the tool breaks.
- 34.Put change notices where the change happens.5:18You learn to place a change notice where people already perform the changed work, so the new instruction appears at the moment it matters.
- 35.The receipt, not the promise: how to tell whether a commitment is alive.5:58You learn to judge a commitment by its receipt: a visible record that the promised action happened, not the confidence of the promise itself.
- 36.Ask for help without making yourself smaller.6:22You learn to ask an expert for help with clear evidence and a precise question, without apologizing for your role or making yourself smaller.
- 37.Done is a message, not a feeling.5:00You learn that work becomes done when completion is communicated to the right person with the result, location, and any needed next step.
- 38.Look before you raise the alarm.5:06You learn the thirty-second rule: check the shared facts and common ground before raising an alarm when a quick look will not increase harm.
- 39.Hand over the answer without taking over the work.5:31You learn to hand over a strong lead without taking over the task, protecting the other person's competence, autonomy, and chance to finish.
- 40.Small decisions need a place to land.6:13You learn to gather small decisions into a clear place with enough context and a deadline, so they stop hiding inside larger work.
- 41.Answer the person, then the problem.4:44You learn to answer the person before the problem by acknowledging the repeated concern, giving the known answer, and naming what will happen next.
- 42.Imagine the plan has already failed.6:50You learn the premortem: imagine the plan has already failed, use prospective hindsight to name likely causes, and protect the plan before work begins.
- 43.Disagree and commit: how to lose the argument and still do the work fully.6:53You learn disagree and commit: argue clearly before a decision, then execute the chosen plan fully without hiding your earlier disagreement inside the work.
- 44.Repair the moment without surrendering the standard.8:03You learn to repair a sharp moment quickly by naming what you did, acknowledging its effect, restating the standard, and changing your next move.
- 45.The angry message is not a verdict.6:59You learn to hear the loss beneath an angry message, label it before explaining, and hold a firm boundary without treating anger as a verdict.
- 46.Answer the question that was asked: working with a mind that runs ahead.6:44You learn why a fast mind cuts in and hops topics, and five moves that get the right answer heard: answer first in one sentence, ask which question matters most, keep a visible list of open questions, check in, and send the detail in writing.
- 47.Take a public correction without defending or collapsing.6:15You learn to take a public correction by naming the fact, thanking the person, fixing the work, and refusing both defensiveness and collapse.
- 48.Schedule the check before the checking starts.6:16You learn stimulus control for worry: decide in advance when to check, what signal you expect, and what result would require action.
- 49.Ask before you agree: give your time a clear shape.6:03You learn to shape a request before saying yes by asking about the work, timing, ownership, and limits, then offering a commitment you can keep.
- 50.Tell on the mistake before the mistake tells on you.6:13You learn stealing thunder: disclose your own mistake early, state its effect, and bring the correction before someone else discovers it for you.
- 51.Stop reading minds: ask instead of guessing.6:09You learn why guessing what someone thinks rarely works, and how perspective getting, asking directly, replaces two guesses with one shared fact.
- 52.Decide it on Tuesday: make the hard choice before the moment that needs it.6:49You learn implementation intentions: choose the exact moment and the first small action in advance, so the situation starts the work instead of your willpower.
- 53.Earn the right to disagree: push back so the other person actually hears it.6:45You learn how to disagree so people actually hear you: restate their view, agree where you can, credit what you learned, then hedge your criticism.Play lesson6:45
Imagine you run a small landscaping business with a crew of four. Today's lesson is about the moment you know someone is wrong. Most people have been there a lot. You see the better answer, you say it, and it goes nowhere. Then you say it again, harder, with more evidence, and it goes nowhere faster. The landscaper meets this every week. A homeowner wants a stone patio laid flat against the back wall, and she can see the rain will pool there and creep into the basement. Her accountant gives advice that sounds too cautious about buying a second truck. The loan officer at the bank wants a repayment term she does not like. With all three, going silent is expensive and going hard is expensive. This lesson is not about being right more often. It is about what decides whether being right counts for anything, which is whether the other person can hear you at the moment you say it.
The idea comes from a game theorist named Anatol Rapoport. It was written down as a set of rules by the philosopher Daniel Dennett in his two thousand thirteen book Intuition Pumps and Other Tools for Thinking. Dennett calls them Rapoport's rules, and there are four. First, restate the other person's position so clearly, vividly and fairly that they say, thanks, I wish I had put it that way myself. Second, list every point where you agree with them, especially the ones that are not obvious. Third, name anything you have learned from them. And fourth, only after all of that, are you allowed to say one word of criticism.
Notice what the rules do to the order of the conversation. Most of us open with the disagreement, because the disagreement is what we are excited about. Rapoport puts it last. The three steps before it are not politeness. They are proof. The restatement proves you understood them. The agreement proves you are not just against them. The thing you learned proves you were listening rather than waiting for your turn. By the time you reach the criticism, you have shown them a person worth arguing with, and that changes what they do with your argument.
This could be a nice idea with no evidence behind it, so here is the research. Julia Minson at Harvard's Kennedy School has spent about a decade studying what she calls receptiveness to opposing views. In a two thousand twenty paper in Management Science with Frances Chen and Catherine Tinsley, she built a way to measure how willing a person is to take in views they oppose. What matters most here is the second paper. In two thousand twenty, Michael Yeomans, Minson, Hanne Collins, Frances Chen and Francesca Gino published a study in Organizational Behavior and Human Decision Processes called Conversational Receptiveness. They took thousands of written disagreements and worked out which words made the reader feel heard. Four things kept showing up. Openly acknowledging the other view. Hedging your own claims, saying I might be wrong about this rather than stating it flat. Framing things in positive terms, saying what you want rather than what you refuse. And finding a point of agreement. That is Rapoport, measured.
Then they tested it. When people wrote their disagreement using that recipe, readers saw the message as more persuasive and the writer as more worth working with in the future, even though the position itself had not softened. In a separate study they looked at Wikipedia editors arguing on talk pages, which is about as hostile a written setting as exists. Editors who wrote receptively were less likely to be hit with a personal attack in reply. The way they opened mattered more than they expected.
Here is why this matters for the landscaper. She has twenty years of digging behind her and a lot of certainty, and when she is right she tends to lead with the answer. That patio will flood. The people across from her are not stupid, and when they do not take her answer, it is usually not because the answer is bad. They are doing what the research says everyone does with a flat disagreement from someone who has not shown they understood the original position. They defend. The homeowner hears that her idea is foolish, and starts explaining why she wants the patio flush with the wall. And once someone is defending, the quality of your argument stops being the thing they respond to. Being ignored is what that feels like from your side.
Two notes for anyone who works for customers. First, a customer can simply stop calling you. On a crew, an ignored idea comes back around at the next morning briefing. A homeowner who feels argued with just hires someone else for the next job, and you find out in the spring when the phone stays quiet. So the opening matters more with customers, not less. Second, an accountant or an advisor is someone you are paying to disagree with you. With them the restatement does a different job. If you cannot say back their concern in a way they would sign, you do not understand the risk yet, and you are about to overrule something you have not heard.
There is a useful test buried in the first rule. If you cannot restate their position in a way they would agree with, you do not disagree with them yet. You disagree with your guess about them. When that happens the right move is not to argue. It is to ask. Let me make sure I have this. You want the patio flush with the wall because you want one step out of the kitchen door, with no lip to trip on. Is that right. Half the time you will find the position was not what you thought. Maybe she only cares about the step, and a slight slope away from the house gives her exactly that. The other half, you will have bought the thing that makes the disagreement land.
One thing to try today. There is a message somewhere, an email, a note on a quote, a reply after a phone call, where you think someone is wrong and you have either pushed once or are about to. Before you write the pushback, write three short lines above it. One sentence stating their position the way they would state it. One thing you agree with, a real one. One thing you learned from what they said. Then the disagreement, and hedge it. I might be missing something, but. Then read the whole thing back and cut anything that sounds like a verdict. Send that instead. Watch what comes back. If you get a real reply instead of silence, you have the tool. It works on people who pay you as well as it works on people you pay.
That is the lesson. You do not have to be less right. You have to earn the right to be heard, and the research says it costs you four sentences.
Key terms
- Rapoport's rules
- Four steps for criticism: restate the other view fairly, list agreements, name what you learned, and only then disagree.
- Conversational receptiveness
- Using words that show you have heard an opposing view, such as acknowledging it, hedging your claims, framing positively and finding agreement.
- Restatement test
- If you cannot state someone's position in a way they would agree with, you are disagreeing with your guess about them, so ask first.
Say it back
- What problem is this lesson helping you avoid?
- What is the first move you would make?
- Where could you use this in your next conversation?
- 54.They are not doing it to you: stop reading character into a quiet week.6:54You learn why people blame character instead of circumstances when someone lets them down, and how to check the situation before settling on a verdict.
- 55.You cannot un-know it: why your clearest explanation is the one that lands worst.7:17You learn why experts underestimate how unclear they are, and how outside checks like the pointing test fix it.
- 56.Say the number you would bet on: give an estimate you will not have to apologize for.7:27You learn why the time estimate that feels right is usually too short, and three research backed ways to give one you can keep.
- 57.Ask the second question: the person who asks the follow-up is the one who gets heard.7:24You learn why asking follow-up questions and paraphrasing before giving your answer makes people like you, feel understood, and reveal the real problem.
- 58.The instruction is not an insult: why being told what to do makes you angry, and what to do with the anger.7:25You learn why instructions trigger anger and counter-arguments, and how to turn an order into your own decision before you respond.
- 59.Change the room before you change your mind: the regulation step that comes before reappraisal.7:56You learn why changing your situation before a feeling arrives works better than reframing the feeling after it has already taken hold.
- 60.What do I actually want here: the question that turns an angry reply into one that works.5:38You learn to catch an angry reply as a draft and ask what you actually want, for yourself, the other person and the relationship, before you send it.
- 61.Say what happened, not whose fault it was: setting an expectation after someone else's miss.6:52You learn how to reply after someone else's miss by stating plain facts, your side, your need and their gain, without apology or blame.
- 62.Spend five minutes on nothing: the messages that are not about work decide who calls you next.7:16You learn why small, no-ask messages build the familiarity and loose ties that make people listen when you finally do ask.
- 63.Give the note, not the fix: tell someone what is wrong with their work so it comes back better.6:11You learn to give feedback as a specific symptom and purpose rather than a fix, so the person who made the work can find the real cause.
- 64.Ask before you prescribe: why the expert in the room should be the last one to offer a fix.6:39You learn why experts should ask what someone needs, and say it back, before offering any fix, even when they already think they know the answer.
- 65.Yes, and here is the order: how to take a longer list without promising it all tonight.6:26You learn how to answer a customer's growing list of requests with yes and an agreed order, instead of rushed promises or a flat no.
- 66.Run the replay once, on paper: what to do when a blunt call still stings the next day.5:56You learn why replaying a blunt conversation feeds anger, and how a ten minute three column sheet turns the replay into calm and one useful task.
- 67.Three short lines: how to answer a correction for something you did not do.5:24You learn how to answer a false correction in three short lines: the fact, the rule going forward, and when they will hear from you.
- 68.Name two times: get a meeting on the calendar with one message.5:51You learn to schedule a meeting in one message by naming two specific times, stating your preference, and leaving an easy way out.