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.
- 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.Play lesson6:47
Good morning. Imagine you lead a small architecture team designing a community arts center. During a public review, a junior designer points out that the seating layout in your presentation leaves too little clearance along one exit route. She is correct. The drawing is on the screen, the client is at the table and everybody is waiting for your response.
The next ninety seconds will shape their trust more than the error itself.
Start with what happens in your head. Leon Festinger’s theory of cognitive dissonance describes the discomfort that appears when a fact conflicts with your picture of yourself. You see yourself as a careful professional. Now a visible fact says you missed something important. The discomfort is fast, and the mind reaches for the cheapest way to reduce it.
Often the cheapest move is not updating your picture of yourself. It is weakening the fact. Maybe the guidance was unclear. Maybe the drawing was only a draft. Maybe somebody changed the room dimensions. Carol Tavris and Elliot Aronson explain this pattern in Mistakes Were Made, But Not by Me. Self-justification is not reserved for arrogant people. It is a human default, and confidence that you are above it does not protect you.
When you feel the urge to explain why the mistake was reasonable, that is dissonance doing its job. Naming it gives you a small pause. That pause is enough to choose a better response.
Carol Dweck’s work on mindset adds another useful piece. In research led by Jennifer Mangels, people answered difficult questions and received feedback while researchers measured their brain activity. People who treated ability as fixed showed strong attention to the fact that they were wrong, then less attention to the correct answer. People who believed ability could grow paid more attention to the corrective information and later learned more from it.
That is the difference between registering the hit and receiving the correction. In the design review, the useful information is not that you were caught. It is where the clearance fails and what must change. Put your attention there.
This matters for standing as well as learning. Adam Grant argues in Think Again that people who update their beliefs openly can become more trustworthy, not less. Philip Tetlock’s forecasting research points in the same direction. Strong forecasters were willing to revise their views in small steps as evidence changed. Their credibility came from tracking reality, not protecting every earlier statement.
In a working group, the person who says “I was wrong” quickly makes their future certainty more valuable. Colleagues learn that this person’s yes is not glued in place by ego.
There is another bad response besides defense: collapse. You can apologize repeatedly, criticize yourself and make the room manage your embarrassment. That may look like humility, but it pulls attention away from the correction. Research by Juliana Breines and Serena Chen on self-compassion found that treating yourself as you would treat a friend after a failure can increase motivation to improve. Harsh self-attack consumes energy that could go into the repair.
So neither extreme helps. Do not defend the mistake, and do not turn it into a public trial of your character.
Use three sentences, in this order, and then stop.
First: “You are right,” or “That is correct.” Not “I see your point,” “fair enough” or “that may be an issue.” Those phrases keep a small escape hatch open. Close it.
Second: state what was wrong in your own words, specifically enough to show that you understood. “The aisle narrows below the required clearance where the last row meets the side wall.” This takes the correction seriously and tells the other person they do not need to keep proving it.
Third: say what changes. “We will remove two seats, rerun the path check and send the revised plan this afternoon.” If you do not yet know the fix, say when the next answer will come: “I will verify the options with the code consultant and return by noon.”
Then stop. No history of the drawing. No explanation of the pressure you were under. No speech about your standards. Context can matter later, especially if the group needs it to prevent another error. In the first reply, unrequested context sounds like a defense because it delays the clean update everybody is waiting for.
Do not attack the other person’s tone in that moment, even if the correction was delivered badly. Tone may deserve a separate conversation. Mixing it into the factual correction turns one solvable issue into a fight over status.
Do not disappear and fix the plan silently either. The error was public. A silent repair leaves everybody who saw it to invent a story about whether you understood, agreed or cared. The reply closes that loop.
The three sentences are a practice, not a magic script. A serious mistake may later require an apology, an investigation or a fuller explanation. The script handles the first moment: agree with reality, demonstrate understanding and name the next move. It keeps your ego from making the first decision.
Try this today. Think of a recent correction that made you feel heat. Write the response again in exactly three sentences: agreement, the specific error and the change. If you add a fourth, examine it. Most fourth sentences defend, punish or ask for reassurance. Delete it unless it adds something the other person truly needs to act.
At the next live correction, notice the first physical flash. Name it silently as dissonance. Listen for the useful fact. Then use the three sentences before your mind builds a case. Watch what happens to the room when there is nothing left to fight.
That is lesson forty six. The mistake is already visible. Trust grows from a clean update: agree, show you understand, state the change and return to the work.
Sources for today: Leon Festinger, A Theory of Cognitive Dissonance. Carol Tavris and Elliot Aronson, Mistakes Were Made, But Not by Me. Jennifer Mangels, Catherine Good, Ronald Whiteman and Carol Dweck, Why Do Beliefs About Intelligence Influence Learning Success. Adam Grant, Think Again. Philip Tetlock and Dan Gardner, Superforecasting. Juliana Breines and Serena Chen, Self-Compassion Increases Self-Improvement Motivation.
Key terms
- cognitive dissonance
- Cognitive dissonance is the discomfort created when a fact conflicts with your picture of yourself.
- public correction
- A public correction is visible evidence that something in your work needs to change.
- accountability
- Accountability means accepting the fact and taking the next corrective action without making the moment about your worth.
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?
- 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.