Free course
Communicating and leading, a lesson every weekday
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.
Name two times: get a meeting on the calendar with one message.
Newest lesson · Lesson 68 · 5:51
You learn to schedule a meeting in one message by naming two specific times, stating your preference, and leaving an easy way out.
Listen to the lesson- 1.The gap between what happened and what you are about to say.5:39You 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:33You 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:12You 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:10You 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.5:52You 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:45You 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:18You 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:01You 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:01You 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.5:47You 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:46You 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:01You learn to treat being taken off a recurring meeting as a change in attendance, not in standing, and to stay informed by naming what should bring you back and asking for the decisions afterward.
- 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:42You 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.6:47You 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:31You 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.5:46You 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:22You 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:00You 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.6:13You 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.4:44You 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.6:50You 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:53You 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:03You 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.6:59You 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.6:44You 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:15You 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:16You 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:03You learn to shape a request before saying yes by asking about the work, timing, ownership, and limits, then offering a commitment you can keep.
- 50.Tell on the mistake before the mistake tells on you.6:13You learn stealing thunder: disclose your own mistake early, state its effect, and bring the correction before someone else discovers it for you.
- 51.Stop reading minds: ask instead of guessing.6:09You learn why guessing what someone thinks rarely works, and how perspective getting, asking directly, replaces two guesses with one shared fact.
- 52.Decide it on Tuesday: make the hard choice before the moment that needs it.6:49You learn implementation intentions: choose the exact moment and the first small action in advance, so the situation starts the work instead of your willpower.
- 53.Earn the right to disagree: push back so the other person actually hears it.6:45You learn how to disagree so people actually hear you: restate their view, agree where you can, credit what you learned, then hedge your criticism.
- 54.They are not doing it to you: stop reading character into a quiet week.6:54You learn why people blame character instead of circumstances when someone lets them down, and how to check the situation before settling on a verdict.Play lesson6:54
Imagine you run a small catering kitchen with one part time helper, and most of your new work comes from quotes you send out. Today's lesson is about the story you tell yourself when someone lets you down. Not the big ones. The small ones. The reply that never came. The tasting that got moved twice. The person who said they would look at the menu and did not. Working for yourself means a lot more of these, because most of what a small business sends out is met with silence. By Friday the caterer has a list. And if she is honest, each item has quietly become a fact about the person. They are not serious. They do not respect the work. They are stringing her along. This lesson is about why that move is usually wrong, and it rests on one of the most studied findings in social psychology.
The name for it is the fundamental attribution error, coined by Lee Ross at Stanford in nineteen seventy seven. The idea is simple. When we explain other people's behavior, we reach for character and give too little weight to the situation they were in. A few years earlier, Edward Jones and Richard Nisbett had proposed the other half: that for our own behavior, we reach for circumstances. Someone misses your message and they are careless. You miss theirs and you were slammed. Same behavior, two explanations, and the only thing that changed is which side of it you were standing on.
The study that started it is worth knowing because it is so clean. In nineteen sixty seven Edward Jones and Victor Harris had people read essays arguing for or against Fidel Castro. Some readers were told the writer had chosen the position freely. Others were told the writer had been assigned the position and had no choice. Then everyone was asked what the writer really believed. The people who knew the side was assigned should have said, I have no idea, the essay tells me nothing. They did not. They still rated the pro Castro writers as more pro Castro. The situation fully explained the behavior, and they reached for character anyway. In nineteen ninety five Daniel Gilbert and Patrick Malone reviewed the whole literature in Psychological Bulletin under a second name, the correspondence bias. Their explanation is the useful part. Reading character off behavior is fast and automatic. Correcting for the situation is slow and takes attention. When you are tired, busy or annoyed, you do the first step and skip the second. Which is to say, you skip it exactly when it matters.
Now the part that is about everyday life, and it is worth being precise, because the honest version of this research is more useful than the folk version. The folk version says everybody does this to everybody all the time. The research says something sharper. Bertram Malle pooled every actor observer study he could find in two thousand six, a hundred and seventy three of them. He found the general effect is small and sometimes absent. But it shows up clearly for negative events. We explain other people's bad behavior by who they are, and our own by what was going on. That is not a footnote. That is the Friday list. The bias is not a fog over all your judgments. It is a spotlight that comes on when someone has let you down, and it points straight at their character.
Think about what this does to someone who sells her own work. The caterer sends a quote for a company holiday lunch and hears nothing. The character story says, they were never serious. The situation story says, this office manager is also handling the move to a new floor and the year end parking passes, the quote landed between two other fires, and an email with no date in it does not survive an afternoon. Both stories fit the evidence. Only one of them lets her do something useful next, which is to send it again with a date on it. The character story just leaves her angry, and the anger is the expensive part. A good share of that anger is not about what happened. It is about the character she assigned to explain it, and she made that assignment in under a second without noticing.
There is a second reason this matters. For a small business, the character story has a price tag. If she decides a slow customer is a bad customer, she starts writing to them like one. If she decides a quiet wedding couple has lost interest, she stops following up, and then they have. The verdict makes itself true. And the other side runs the same quick judgment on her. When she pushes hard and gets nothing back, they are thinking: she is intense, she will be hard to work with. Nobody has learned anything about anybody. Two people swapped a situation for a personality.
So what do you do. The correction is not to stop judging. It is to slow the second step down until it runs. Ross later wrote a book with Richard Nisbett, The Person and the Situation, whose whole argument is that situations drive behavior far more than we assume. The habit worth building on that is small. Before you settle on what someone is like, write down what they were up against. One sentence. Not to excuse them. Just to make the situation visible before the verdict lands. If you cannot think of a situation that would explain it, you probably do not know enough about their week to have a verdict yet. The right move then is a question, not a conclusion.
One limit, so this does not turn into making excuses for people. The situation story is where you start, not where you must end. If the same venue manager misses three dates in a row after the caterer has asked plainly, that is a pattern, and she is allowed to plan around it. Planning around it is still not a verdict on his character. It is a decision about what she will rely on.
One thing to try today. Make the list. Every person who let you down in a small way this week, one line each. Next to each, write the character story you have been carrying, honestly, the unflattering version. Then write one situation that would fully explain the same behavior. You do not have to believe it. You only have to be able to write it. Look at the two columns and notice which one you would want someone using on you. Then pick the one item that actually needs a follow up and send it, with a date in it, and no trace of the character story in the wording.
That is the lesson. When someone lets you down, your brain hands you a verdict about who they are in less than a second. It is fast, it feels like insight, and it skips the step that would have checked it. The situation is almost always there. You just have to make yourself look for it before you decide.
Key terms
- fundamental attribution error
- The habit of explaining other people's behavior by their character while underweighting the situation they were in.
- correspondence bias
- Another name for inferring a person's traits from their behavior even when circumstances fully explain it.
- actor observer asymmetry
- The tendency, strongest for bad events, to explain our own lapses by circumstances and other people's by who they are.
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?
- 55.You cannot un-know it: why your clearest explanation is the one that lands worst.7:17You learn why experts underestimate how unclear they are, and how outside checks like the pointing test fix it.
- 56.Say the number you would bet on: give an estimate you will not have to apologize for.7:27You learn why the time estimate that feels right is usually too short, and three research backed ways to give one you can keep.
- 57.Ask the second question: the person who asks the follow-up is the one who gets heard.7:24You learn why asking follow-up questions and paraphrasing before giving your answer makes people like you, feel understood, and reveal the real problem.
- 58.The instruction is not an insult: why being told what to do makes you angry, and what to do with the anger.7:25You learn why instructions trigger anger and counter-arguments, and how to turn an order into your own decision before you respond.
- 59.Change the room before you change your mind: the regulation step that comes before reappraisal.7:56You learn why changing your situation before a feeling arrives works better than reframing the feeling after it has already taken hold.
- 60.What do I actually want here: the question that turns an angry reply into one that works.5:38You learn to catch an angry reply as a draft and ask what you actually want, for yourself, the other person and the relationship, before you send it.
- 61.Say what happened, not whose fault it was: setting an expectation after someone else's miss.6:52You learn how to reply after someone else's miss by stating plain facts, your side, your need and their gain, without apology or blame.
- 62.Spend five minutes on nothing: the messages that are not about work decide who calls you next.7:16You learn why small, no-ask messages build the familiarity and loose ties that make people listen when you finally do ask.
- 63.Give the note, not the fix: tell someone what is wrong with their work so it comes back better.6:11You learn to give feedback as a specific symptom and purpose rather than a fix, so the person who made the work can find the real cause.
- 64.Ask before you prescribe: why the expert in the room should be the last one to offer a fix.6:39You learn why experts should ask what someone needs, and say it back, before offering any fix, even when they already think they know the answer.
- 65.Yes, and here is the order: how to take a longer list without promising it all tonight.6:26You learn how to answer a customer's growing list of requests with yes and an agreed order, instead of rushed promises or a flat no.
- 66.Run the replay once, on paper: what to do when a blunt call still stings the next day.5:56You learn why replaying a blunt conversation feeds anger, and how a ten minute three column sheet turns the replay into calm and one useful task.
- 67.Three short lines: how to answer a correction for something you did not do.5:24You learn how to answer a false correction in three short lines: the fact, the rule going forward, and when they will hear from you.
- 68.Name two times: get a meeting on the calendar with one message.5:51You learn to schedule a meeting in one message by naming two specific times, stating your preference, and leaving an easy way out.