Free course
Communicating and leading, one lesson a day
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.
Ask before you agree: give your time a clear shape.
Newest lesson · Lesson 49 · 6:18
You learn to shape a request before saying yes by asking about the work, timing, ownership, and limits, then offering a commitment you can keep.
Listen to the lesson- 1.The gap between what happened and what you are about to say.6:02You 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:48You 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.Play lesson5:48
Good morning. Yesterday we worked on the half-second between an event and the feeling. Today we go one layer down, into the conversation itself. Imagine you help run a neighborhood garden. A new bed of seedlings has dried out just before the garden’s open day. The volunteer lead thought the facilities crew would turn on the irrigation. The facilities crew thought volunteers were watering by hand. Everybody cares, everybody is embarrassed, and the first meeting after the loss is full of sentences that sound like accusations. This lesson is about what to do with that.
The source is a book from the Harvard Negotiation Project called Difficult Conversations, by Douglas Stone, Bruce Patton and Sheila Heen. The authors studied hard conversations in workplaces, families and public life. They found that every difficult conversation is actually three conversations happening at once, and people get stuck because they are often having different ones.
The first is the what-happened conversation. Who said what, who did what and whose version is right. The second is the feelings conversation, which often runs silently underneath. The third is the identity conversation: what does this say about me? Am I responsible? Am I competent? Am I the kind of person people can count on? Arguments that look like fights about facts often become painful because someone’s identity has been touched.
In the garden meeting, the visible question is who was supposed to water the seedlings. Underneath it, the volunteer lead may be hearing, you are careless with other people’s work. The facilities coordinator may be hearing, you do not belong in a community-led project. Once either person starts defending that identity, more evidence about hoses and schedules will not settle the conversation. When you feel the heat rise, ask yourself which of the three conversations just got touched. If it is identity, piling on facts usually makes the defense stronger.
Now the main idea. Stone, Patton and Heen say that who is to blame is the wrong question. They do not mean nobody is accountable. They mean blame is a poor tool for learning. Blame asks who caused the damage and what they deserve. It looks backward, invites a defense and makes people manage their exposure. The minute somebody feels they are on trial, they stop offering the very information the group needs.
The replacement is contribution. The question becomes: what did each part of the system add to this result, and what can we change before the next planting? Contribution is wider than blame because it includes reasonable choices, missing agreements and quiet assumptions. The volunteers never confirmed the watering plan. Facilities changed the timer during nearby repairs. The planting group moved the trays without updating the map. None of those facts needs a villain. Together they explain the loss and point to repairs.
Contribution also includes yours. That is not a confession and it is not false balance. It is an accuracy move. Suppose you chaired the planning session and ended it without asking one person to read back the watering plan. You did not dry out the seedlings, but the missing readback contributed. Say that first: “I closed the meeting without confirming an owner. The tray move was not recorded, and the timer change was not shared. Let’s put one person on the check and make the map the record.”
Notice what that language does. It does not erase anyone’s part. It names all of the parts, including yours, and then turns toward the next action. When you own your contribution first, other people stop bracing for a trial. Your credibility usually rises because you have shown that you can examine the whole system without protecting your image.
There is a second tool in the book that helps. The authors call it the third story. Each person has a story in which they are the reasonable one. The third story is the version a neutral observer could tell without deciding who is good or bad. In this case: “We had one watering task and two groups with different understandings of who owned it.” Both sides can usually nod at that sentence. If you open with your story, the other person has to defend theirs. If you open with the third story, both of you can look at the same problem.
This matters for anger because blame manufactures it. Each time you build a case against a person, you get another burst of certainty. That can feel useful while it costs you the room. Contribution is drier. It asks what inputs produced the result, what information failed to move and what safeguard belongs next. When you catch yourself rehearsing the prosecution, stop and ask the contribution question.
One thing to try today. Think of a problem involving at least two people. Write three lines before you discuss it. First, the third story: the neutral description both people could accept. Second, your contribution, stated without drama. Third, the change that would prevent a repeat. Then open the conversation in that order. You are not letting anyone off the hook. You are replacing a hook with a handle everybody can use.
That is lesson two. Blame finds a person to punish. Contribution finds the gap you can close.
Sources for today: Douglas Stone, Bruce Patton and Sheila Heen, Difficult Conversations: How to Discuss What Matters Most, especially the chapters on the three conversations, blame versus contribution and the third story.
Key terms
- three conversations
- A difficult conversation contains what happened, feelings, and identity at the same time.
- contribution system
- A contribution system looks at how each person helped produce the result instead of deciding who deserves blame.
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?
- 3.When fear outruns the facts.7:09You 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:21You 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.6:40You 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:59You 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:42You 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:16You 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:22You 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.6:03You 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:55You 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:20You learn to end a meeting while preserving connection by giving the conversation a clear close, owners, next actions, and a path back to one another.
- 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:58You 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.7:25You 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:27You 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.6:13You 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:53You 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:17You 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.7:04You 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.5:01You 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.7:07You 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:55You 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:21You 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.7:26You 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.7:17You 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:47You 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:33You 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:18You learn to shape a request before saying yes by asking about the work, timing, ownership, and limits, then offering a commitment you can keep.