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.Play lesson5:17
Imagine a family-owned landscaping company with four crews. One crew replaces a damaged fence at a daycare center on Monday. The gate closes properly, the director signs the paper, and the crew moves on. But the job card on the office board still says active.
From the crew's view, the work is finished. From the scheduler's view, a crew may still need to return. From the bookkeeper's view, the invoice is not ready. From the daycare director's view, perhaps the company has not completed its final inspection. One stale label has created four different realities.
That is not a bookkeeping problem. It is a communication problem wearing work clothes.
A status field is not merely a record that you update after reality settles. It is a message other people use to decide what is true. Most of them will not drive to the daycare and test the gate. They will read the board. When it says active, the company is telling them the job is not done, even if nobody intended to send that message.
This gap is easy to create because completed work stops demanding your attention. Bluma Zeigarnik reported in nineteen twenty seven that people remember interrupted tasks better than completed ones. Later studies have mostly failed to repeat that memory result. What has held up is the pull to return to a task you were interrupted in. Open loops stay mentally active. Once the fence is repaired, the crew leader's mind releases it and turns to the next yard. The job card is still open for everyone else, but the person best able to close it no longer feels the reminder.
Research by E. J. Masicampo and Roy Baumeister adds another useful point. Unfinished goals intrude on attention, while making a specific plan can quiet that intrusion. Think about the scheduler staring at the active card. She must remember to ask whether the gate works, whether materials came back, and whether another visit needs space on Thursday. The crew finished the physical work but left the rest of the company carrying it.
David Allen's practical version is that open loops create work simply by having to be remembered. A trusted system lets people forget safely. An untrusted board forces them to check, chase, and rehearse. If workers regularly finish jobs without changing their cards, the office learns that no status can be believed. Then every status requires a conversation, and the board stops saving anyone time.
The discipline is small: make the status change part of the job itself. The fence is not complete when the last screw goes in. It is complete when the final check is recorded, the card is moved, and the next person can act without asking a question.
Use the correct state. If a supervisor must inspect the gate, move the card to inspection rather than complete. Add one plain sentence: repair finished, gate tested, ready for Rosa's check. If no review is needed, close it and record what was delivered. Do this before leaving the site, while the facts are still in hand.
Be careful with small pending decisions too. A crew may be waiting to hear whether leftover stone should return to the yard or stay for another section. To the manager, that is a one-word choice. To the crew, it is an open loop occupying truck space and attention. A reversible answer today is often cheaper than a perfect answer after three reminders.
When you finally correct an old status, resist explaining why it sat. A long apology creates another thread to read. Update the state and give the useful fact. Fence repaired Monday, signed by the director, closing the card. The point is not to defend the past. It is to make the system trustworthy now.
Leaders have a responsibility here as well. Do not punish accurate status. If a crew moves a job to blocked and gets blamed for the blockage, people will leave cards active and hide uncertainty. A useful board must make it safe to say complete, waiting, blocked, or needs inspection. Accuracy matters more than making every column look good.
The finish line should also be visible before work starts. If the crew thinks done means the gate closes while the office thinks done means a signed inspection and returned materials, the stale card is partly a design failure. Put the definition of done on the job card. Then closing the loop is not an extra administrative favor; it is one of the promised parts of the job.
One thing to try today: open the system your team uses and look at every item marked active. Ask one question: can the next person already use the result? If yes, move it to the proper next state and add one line saying what exists and where. Then look at every item waiting on a tiny decision from you and clear the reversible ones in one sitting.
That is lesson thirty six. Finished work stays open in other people's minds until you send the message. Close the physical task and the communication loop in the same sitting, so the work and the system tell the same story.
Sources for today: Bluma Zeigarnik, On Finished and Unfinished Tasks. E. J. Masicampo and Roy Baumeister, Consider It Done! Plan Making Can Eliminate the Cognitive Effects of Unfulfilled Goals. David Allen, Getting Things Done.
Key terms
- completion message
- A completion message tells the right person what was delivered and where to find it.
- done
- Done is a shared, visible state rather than a private feeling that your part is over.
- closure
- Closure records the result and makes any review or follow-up explicit.
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?
- 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.