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.
- 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.Play lesson7:26
Imagine a city changes a bus route after rebuilding a bridge. The new route reaches a medical district that had little service, but it no longer stops on one residential block. Most riders adjust quietly. Then a rider writes an angry message saying the change ruined the trip she has taken to work for years.
You helped approve the route. You studied the ridership numbers, held public meetings, and announced the change. Your instinct is to explain all of that. You want the rider to know the decision was not careless.
Do not begin there.
Daniel Kahneman and Amos Tversky's prospect theory gives you a better starting point. One of its best-known ideas is loss aversion: people tend to feel a loss more strongly than an equivalent gain. The transit system may now serve more riders overall. That gain is broad and abstract. This rider lost a familiar stop, and the loss is concrete. She has to leave earlier, walk farther, or change buses. She is not balancing a public spreadsheet in her mind. She is reporting the piece of her life that disappeared.
Seeing the message as a loss report changes your posture. It does not mean the route decision was wrong. It means the first job is not defending the decision. The first job is showing that the loss was seen.
Chris Voss describes a negotiation technique called labeling. You name the emotion or experience you hear with a phrase such as it sounds like or it seems like. It sounds like losing that stop disrupted a routine you had made dependable. That sentence does not promise to restore the stop. It does not admit that the whole route was a mistake. It proves that a person, not just a complaint number, arrived at the other end.
Matthew Lieberman's research on affect labeling provides evidence for the underlying effect. Putting feelings into words can reduce the intensity of the emotional response. In practice, an accurately named feeling often no longer needs to shout for recognition.
Then give the path. Tell the rider which nearby stop serves the route, whether a transfer is needed, and where to find current arrival information. Put the steps in the order she will use them. If mobility, weather, or safety makes the alternative unrealistic, give a direct place to report that. The order matters. A path offered before acknowledgment can feel like a brush-off. The same path after acknowledgment can feel like help.
Keep the decision and the person's experience separate. You can hold the route change while taking the inconvenience seriously. Kindness does not require reopening every settled choice. Finality does not require pretending nobody lost anything.
This work also has a cost for the person answering. Arlie Hochschild used the term emotional labor for jobs that require people to manage feeling as part of the work. She distinguished surface acting, where you display calm while feeling something different, from a deeper change in how you see the person. Later research by Alicia Grandey linked surface acting with exhaustion.
That is why the loss-aversion reframe matters to you, not just to the rider. If you read each angry message as an attack on your competence, you must swallow ten attacks while sounding pleasant. That is exhausting. If you read each one as information about a disrupted routine, your calm can be real. You are not pretending the writer is reasonable. You are locating the reasonable human experience inside a message that may be badly expressed.
There is a limit. Understanding anger does not require accepting threats, abuse, or discrimination. Set a boundary when a message crosses one. You can say that you want to help with the route but cannot continue a conversation containing threats. Empathy is not surrender.
Service-recovery research adds a useful reason to take the exchange seriously. A problem handled well can strengthen trust because the person learns what the organization is like under pressure. Treat that as an opportunity, not a trick. The point is not to manufacture failures so you can look heroic. It is to respond to a real failure or loss with attention, a workable path, and follow-through.
A strong reply has three moves.
First, the label. One sentence naming the loss without adding a but. It sounds like this change turned a simple trip into an uncertain one.
Second, the path. Give the closest useful option in two or three concrete sentences. If you need information to find the right option, ask one focused question rather than sending the person to a general page.
Third, the door. Offer a clear way to continue if the path fails. If the added walk is not accessible for you, reply with the intersection you start from and our trip planner will check another route. You are offering attention and problem-solving, not promising the old stop will return.
Avoid several common mistakes. Do not lead with how many notices were posted. Do not explain how many other riders benefit. Those facts may matter in a policy report, but they answer an argument the rider did not make. Do not use I understand your frustration as a substitute for naming what actually happened. And do not apologize for a sound public decision when what you mean is that you regret a person's burden. Say the precise thing.
Precision also keeps you from making promises the organization cannot keep. There is a difference between I am sorry this added twenty minutes to your trip and I am sorry we changed the route. The first recognizes an effect. The second sounds like a commitment to reconsider the policy. If review is possible, say how and when it happens. If it is not, do not create hope just to soften the moment.
After several similar messages, look for a pattern. One angry rider may need individual help. Six riders describing the same dark crossing may have found a safety issue the route study missed. Empathy and data belong together: respond to each person as a person, then collect repeated facts for the people who can change the system. Holding the current decision does not mean refusing new evidence.
One thing to try today: when an angry message arrives, read it once as a report of loss rather than a verdict on you. Write the label sentence first. Then add the shortest usable path and one open door. After sending, notice whether you are still replaying the attack an hour later. If you are, return to the concrete loss the message described and separate it from your identity.
That is the lesson. Anger often tells you that something mattered before it disappeared. Name the loss, hold the decision, offer a path, and protect your ability to answer the next person with the same steady attention.
Sources for today: Daniel Kahneman and Amos Tversky, Prospect Theory. Chris Voss with Tahl Raz, Never Split the Difference, on labeling. Matthew Lieberman and colleagues, Putting Feelings Into Words. Arlie Hochschild, The Managed Heart. Alicia Grandey on emotional labor. Michael McCollough, Leonard Berry, and Manjit Yadav, and later work on service recovery.
Key terms
- prospect theory
- Prospect theory helps explain why a loss can feel stronger than an equal gain.
- labeling
- Labeling names the loss or feeling you hear without claiming certainty.
- emotional labor
- Emotional labor is managing feeling as part of the work while still responding professionally.
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?
- 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.