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.Play lesson7:25
A wedding bakery has sent a couple three sketches for a tiered cake. The tasting is complete, the venue has confirmed the delivery door, and the baker is ready to order the sugar flowers. One thing is missing: the couple has not chosen a design.
For several mornings, the baker opens the order book, sees the blank choice, and wonders whether to send another message. She cannot finish the supply order, but she also does not want to pressure people who are planning a wedding. The job is neither active nor closed. It simply takes a little attention every time she sees it.
That is the hidden cost of waiting. Silence looks like nothing is happening, but an open loop keeps making a small claim on your mind. The other person may not be thinking about the choice at all. You are carrying it for both of you.
First, a correction. An earlier version of this lesson rested on one study: a two thousand two paper by Dan Ariely and Klaus Wertenbroch about students who set their own deadlines. The journal that published it, Psychological Science, retracted that paper in September two thousand twenty six. That summer, another team had repeated one of its experiments and reported that changing the deadlines had almost no effect on how people performed. So this lesson no longer leans on that study, and it no longer claims that a date will change your behavior just because you chose it.
Two other pieces of research suggest why the method may still help. The first is about open loops. In a set of experiments published in two thousand eleven, E. J. Masicampo and Roy Baumeister asked students to write about important tasks they had not yet done. A little later, while reading a story, those students were more distracted by thoughts of the tasks, and they understood less of what they read. Another group did one extra thing first. They wrote down how, when, and where they would do each task. Their distraction disappeared. They read as well as a comparison group that had written about tasks already finished. The tasks were still undone. The plan was enough to let the mind put them down.
The second finding is about what kind of plan works. Peter Gollwitzer and Paschal Sheeran pooled ninety four tests of if-then plans: if this situation arrives, then I will take this action. Across those tests, people who made an if-then plan were more likely to reach the goal than people who only intended to. The size of the effect was medium to large.
Neither finding is about waiting on someone else. Both studied people’s own goals, so applying them to a silent customer is a step this lesson takes, not something the researchers tested. But the baker’s problem has the same shape: an unfinished item with no plan attached. And the evidence points at what to add. Not a date alone. A date with an action tied to it. An open item is a question. A dated item with a next step becomes a plan.
Apply that idea to waiting on another person. Do not invent a deadline as a threat to them. Set a date for yourself: the day when silence will count as information and you will take the next action.
The baker writes three sentences in the order book. She is waiting for the final cake design. If no choice arrives by Tuesday afternoon, she will treat the simplest sketch as the working plan. On Tuesday, she will send one message explaining that assumption and the last date on which it can be changed without affecting the price.
Now the order is not hovering over every morning. It has a place to return and a decision attached to it.
The method has three parts. First, name exactly what you are waiting for. “A response” is too vague. “Approval of the blue cover proof” is clear. Second, choose the date when the silence becomes an answer. Base that date on the work, not on your irritation. A lunch count may need an answer today. A volunteer application can wait a week. A custom material order may need a decision before the supplier’s cutoff.
Third, decide in advance what you will do. This is the part that makes the date real, and it is the part the research supports most directly: if the date arrives with no answer, then I will do this. You may send one final note stating what you will assume. You may ask a different authorized person. You may choose a safe default. You may close the request and release the time. The right action depends on the stakes, but “keep checking forever” is not an action.
Do not confuse this with punishment. The baker is not trying to teach the couple a lesson. She is protecting the production schedule and making the consequence of silence predictable. A good stop date should be calm enough that you could explain it without blame.
There are two common traps. The first is endless generosity. You tell yourself the person is busy, traveling, overwhelmed, or deciding carefully. Any of that may be true. A date does not deny it. It simply limits how long their uncertainty gets to organize your attention.
The second trap arrives when your date passes. Following the plan can feel like giving up, so you grant one more day and reopen the loop. That teaches you not to trust your own deadlines. The research has a matching caution: in one of the Masicampo and Baumeister studies, the benefit of a plan showed up in the people who later carried their plan out. If new information appears, change the plan openly. If nothing has changed, take the action you chose.
There are situations where silence cannot safely become consent. Medical choices, legal approvals, spending authority, and other high-stakes decisions may require an explicit yes. In those cases, your action is not “assume approval.” It is “pause the work,” “use the approved default,” or “close the request until consent arrives.” The method still works because the date governs your action, not another person’s rights.
Try this today. Find the item that has waited longest for someone else. Write what is missing, the date you will stop waiting, and what you will do then. Put that action on the date where you will see it. Remove the item from the list you scan every day.
When the date comes, look once. If the answer is there, continue. If it is not, follow the plan without adding a story about what the silence means. Silence may mean forgetfulness, avoidance, overload, or a lost message. You do not need to diagnose it. You only need to know what you will do next.
That is the lesson. Waiting is not neutral, and patience does not have to be endless. Give the silence a date, give yourself a next action, and let the open loop rest until then.
Sources for this lesson: E. J. Masicampo and Roy Baumeister, Consider It Done, Journal of Personality and Social Psychology, two thousand eleven. Peter Gollwitzer and Paschal Sheeran, Implementation Intentions and Goal Achievement, Advances in Experimental Social Psychology, two thousand six. The withdrawn study was Dan Ariely and Klaus Wertenbroch, Procrastination, Deadlines, and Performance, Psychological Science, two thousand two, retracted in September two thousand twenty six. The repeat of it was by Kyle Hyndman and Alberto Bisin, in the same journal, two thousand twenty six.
Talk to you tomorrow.
Key terms
- end date
- An end date turns indefinite waiting into a specific decision point.
- default action
- A default action is the step you will take at the stated time if no reply arrives.
- consent
- Consent must be received when another person's rights are involved; silence does not replace it.
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?
- 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.