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.Play lesson7:07
Imagine a regional orchestra is taking a youth ensemble on its first overseas tour. The flights are booked, host families are assigned, instruments have travel cases, and the concert halls are confirmed. At the final planning meeting, everyone wants to feel that the plan is finished. You notice risks: one student's passport may arrive late, a cello case may not fit the airline's rules, and a host family may cancel. If you raise each concern in the usual way, you can quickly become the person who does not believe in the tour.
That is a social problem inside a planning problem. The useful tool is a pre-mortem.
Research psychologist Gary Klein described the pre-mortem after studying how people make decisions in demanding settings. The method is simple. Before a plan begins, ask the team to imagine that it is now later and the plan has failed badly. Give everyone a few quiet minutes to write every reason the failure happened. Then collect the reasons before discussing solutions.
In an ordinary planning meeting, a warning can sound like a vote against the plan. “What if the passports do not arrive?” invites someone to defend the schedule. “What if the airline refuses the cello?” can sound like criticism of the person who booked the tickets. Soon the conversation is about whether you are too negative, not whether the risk is real.
A pre-mortem changes the assignment. Failure is temporarily treated as a fact. Everyone must explain it. Finding a risk is no longer an act of disloyalty; it is the task the whole group shares for ten minutes. The person who sees several problems is contributing, not objecting.
The psychology underneath the method is called prospective hindsight. Deborah Mitchell, Jay Russo, and Nancy Pennington compared people asked why a future event might happen with people asked to imagine that it had happened and explain why. Treating the event as certain produced more reasons and more specific ones. Once the mind stops debating whether failure is likely, it gets better at explaining how it could have occurred.
Daniel Kahneman praised the pre-mortem because it creates permission to challenge a plan after momentum has formed. Once a leader is visibly excited, people often keep doubts to themselves. The pre-mortem creates a short, protected period in which doubt is required.
Here is how to run one for the tour.
Start with a specific future scene: “It is the morning after the final concert. The tour went badly enough that we would not repeat it. What happened?” Name the method, set a ten-minute limit, and make clear that everyone will participate. This framing turns your concern into a process rather than a speech about your private worries.
Next, give everyone two or three minutes to write alone. Silent writing is essential. If discussion begins immediately, the first confident speaker sets the frame. Other people respond to that idea instead of searching their own experience. The percussion teacher may think about freight delays. A parent chaperone may notice a medication issue. A student may know that the host-family rules are unclear. You want those thoughts on paper before anyone hears the tour director's answer.
Then collect one reason from each person in turn. Keep going around until the useful reasons are out. Do not solve them yet. If the group starts solving the first risk, people stop searching and begin defending. Collection and response are two different stages.
Make each reason concrete. “Travel chaos” is too broad to act on. “The connecting flight is missed, and half the instruments travel without their players” is specific. “Communication fails” is vague. “The emergency phone list is stored only in the trip leader's lost bag” is specific.
After collecting, sort the list. Which risks are plausible? Which would cause serious harm? Which are cheap to reduce now? Choose a small number that score high enough to deserve action. Do not convert every imagined failure into a task. A pre-mortem that creates thirty new assignments will not be welcomed again.
For the tour, the group might choose three protections: copy every passport into an encrypted travel file accessible to two leaders, obtain written airline approval for oversized instruments, and assign a backup host location in each city. Those steps do not guarantee success. They reduce failures the group could reasonably foresee.
Be careful with low-probability, high-harm risks. Some deserve action even when unlikely, especially where health or safety is involved. Others need only a response plan. You may not buy a second seat for every possible missed flight, but you can write down who contacts the airline and where students gather if a connection breaks.
The method also protects relationships. People often hear a warning about their part of a plan as a judgment of their competence. When everyone is asked to find failure paths, risk stops belonging to one person. A parent who identifies a medication gap is not accusing the nurse. A teacher who identifies a baggage problem is not attacking the travel coordinator. They are completing the same exercise.
This does not mean hiding criticism inside a game. If someone has ignored a known safety requirement, say so directly. A pre-mortem is for discovering and preparing for uncertain failure, not avoiding an overdue accountability conversation.
The facilitator has one more job: make it safe to name the awkward reason. A student may worry that a popular soloist ignores curfew. A chaperone may know that two adults do not cooperate. Thank people for specific risks before debating them. If the room punishes the first uncomfortable answer, the rest of the exercise becomes theater.
Here is the practice. Take one plan you are about to commit to. Alone, write a date after it is supposed to succeed. Then write, “The plan failed,” and set a three-minute timer. List every reason. Circle the failure that would embarrass you most because it was preventable. Give that one an action or response plan today.
For a shared plan, propose the ten-minute version. State the failed future, use silent writing, collect one reason per person without discussion, and select two or three protections. End by naming an owner and a deadline for each one.
That is the lesson. Do not carry the role of the lone pessimist. Give the whole group permission to imagine that the plan already failed, learn why, and prevent the few failures worth preventing.
Sources for this lesson: Gary Klein's Performing a Project Premortem; the prospective-hindsight study by Deborah Mitchell, J. Edward Russo, and Nancy Pennington; and Daniel Kahneman's work on judgment, overconfidence, and debiasing.
Key terms
- premortem
- A premortem asks a group to imagine a future failure and explain what caused it.
- prospective hindsight
- Prospective hindsight makes possible causes easier to see by treating an imagined future event as if it already happened.
- risk
- A risk is a possible cause of failure that the plan can reduce, watch, or prepare for.
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?
- 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.