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.Play lesson6:53
Imagine you have just become treasurer of a neighborhood housing cooperative. The building's longtime accountant is guiding you through an insurance audit, and the paperwork is unfamiliar. You send four focused questions about replacement-cost estimates, reserve records, signatures, and the deadline. Then you add, “Sorry for all the basic questions. I promise I will stop bothering you soon.”
You meant the line as courtesy. It sounds harmless. But it quietly frames useful questions as a burden and you as the person creating it. Today's lesson is about asking for the help you need without apologizing for needing it.
The reflex has a logic. You are entering another person's area of expertise. You imagine every question drawing down a limited balance of goodwill. By apologizing first, you try to pay for the interruption before the bill arrives. The research suggests that we misread both how likely people are to say yes and what the request does to our standing.
Francis Flynn and Vanessa Lake studied how people predict responses to requests for help. Participants had to approach strangers and ask for things such as directions, the use of a phone, or help with a survey. Before they began, they estimated how many people they would need to ask. They expected far more refusal than they actually encountered. Across the studies, people underestimated others' willingness to help by a wide margin.
Vanessa Lake, who now publishes as Vanessa Bohns, has continued studying this gap. Her explanation is that we think about what a yes would cost the other person and miss how awkward it is for them to say no. That cuts both ways. Some of those yeses come from social pressure, so a yes is not proof that the request cost nothing. And the gap showed up when people asked out loud, face to face. When they asked by flyer or by email, they expected more yeses than they got. What the studies do show is that your private estimate of how likely a refusal is should not be treated as a measurement.
The second finding is even more useful. Alison Wood Brooks, Francesca Gino, and Maurice Schweitzer studied how asking for advice changes the way people see us. Participants expected advice seekers to look less capable. In many conditions, the opposite happened. People who asked for advice were judged as more competent, especially when the problem was difficult and the person being asked had real expertise.
Why? Asking for someone's advice communicates that you respect that person's judgment. Experts generally do not hear a focused question as proof that you are foolish. They hear that you know where the knowledge lives. Knowing what you do not know is part of competence.
Put these findings together and the pre-apology becomes unnecessary. You apologize in advance for a refusal you cannot predict as well as you think, in order to protect a reputation that a good question may improve. If you repeat the apology often enough, however, it can teach the group to see your participation as costly. You are supplying a negative description nobody requested.
There is a quieter version of the same mistake: the question you never ask. You worry that a fifth question will be too much, so you search through old folders, guess at the accountant's meaning, and submit the wrong form. Avoiding ten minutes of help can create hours of correction. Silence is not cheaper merely because nobody watches you buy it.
The solution is not to ask carelessly. It is to separate the question from your anxiety about the question. Make the request easy to answer. Give only the context needed. Group related items. Say what you have already checked. Distinguish the part where you need a fact from the part where you want judgment.
For example: “I found the latest reserve study and the insurer's worksheet. I need your judgment on four entries before I submit it Thursday. Can you confirm whether the roof estimate should use the study's current value or its projected value?” That message respects the accountant's time without turning you into a nuisance in the first sentence.
If the volume is real, acknowledge it with a plan, not a confession. Say, “I will collect audit questions and send one batch each afternoon this week.” Or, “Would you rather answer these in writing or spend fifteen minutes together on Wednesday?” Those sentences manage load. “I am such a pain” merely announces shame.
Notice that a clear question and a clear boundary work together. The other person can say, “Use the current value,” or, “This needs a call,” without sorting through your feelings first. A pre-apology can accidentally create extra labor because the helper now has to reassure you as well as answer.
There are times an apology is appropriate. Apologize if you ignored an answer, failed to prepare, interrupted protected time after agreeing not to, or created avoidable rework. Those are actions. Do not apologize merely because learning requires access to someone else's knowledge.
Here is the practice. Find a recent request for help. Circle every phrase that describes you instead of the question: sorry to bother you, this is probably obvious, I know you are busy, I hate to be annoying. Remove those phrases. What remains should contain three things: the context, the exact question, and when you need the answer.
If the message is still hard to answer, improve the question. If the message becomes clear, save that shape for next time. Then write one load-management sentence you can use when several questions are coming: “I will batch these,” “I have three related questions,” or, “Tell me which channel works best.”
Try it during the next week. Keep count of the questions you ask plainly and the ones you hide. For each plain question, notice three things: how long the answer took, whether the person seemed burdened, and whether asking prevented a wrong move. Let the record correct your prediction.
Sources today: Francis Flynn and Vanessa Lake, “If You Need Help, Just Ask,” Journal of Personality and Social Psychology, two thousand eight. Vanessa Bohns, the same researcher under her later name, “Misunderstanding Our Influence Over Others,” Current Directions in Psychological Science, two thousand sixteen. Alison Wood Brooks, Francesca Gino, and Maurice Schweitzer, “Smart People Ask for My Advice,” Management Science, two thousand fifteen.
That is lesson thirty five. Respect another person's time by asking clearly, not by apologizing for having something to learn.
Key terms
- expert help
- Expert help adds knowledge you do not yet have without taking away your responsibility for the work.
- precise question
- A precise question shows what you checked and identifies the exact uncertainty you need help resolving.
- self-respect
- Self-respect means asking plainly without turning a knowledge gap into a judgment 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?
- 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.