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.Play lesson5:54
Imagine you run school programs at a regional aquarium. Your director has asked for a plan to handle a surge of spring field trips. You have staffing numbers, bus-arrival problems, and three possible schedules. You also know that your director is juggling a facility inspection and a difficult budget review. If you walk into the meeting focused only on your own plan, you may leave angry that a good idea went nowhere. Today's lesson is about managing up: taking responsibility for how you work with the person who has authority over your role.
This is not flattery or office politics. It is a practical skill built on mutual dependence. John Gabarro and John Kotter introduced this idea in their 1980 Harvard Business Review article, “Managing Your Boss.” Their central point is still useful: you and your manager are two fallible human beings who need different things from each other. Your manager needs your knowledge and execution. You need their decisions, cover, resources, and access. The person who understands both sides can make the relationship work better.
People who have spent years working independently often find this especially strange. When you control the work, you decide, build, and deliver. Inside a larger organization, someone else's understanding of the work affects which ideas receive time and money. Shaping that understanding is not a character test. It is a skill, and it may be one you never needed before.
Gabarro and Kotter describe two sides of the task. Begin by learning the manager's world. Which outcomes matter to them now? Which demands are coming from their leaders, customers, or targets? What do they handle well, and what tends to escape their notice? Which form of communication helps them think?
A reader may want a short document before talking so there is time to think alone. A listener may understand the issue by hearing it worked through aloud. Send a listener a long document without context and it may sit untouched. Bring a reader a complicated surprise in a live meeting and they may spend the whole time trying to catch up. Communication is not complete when you send information. It is complete when the other person can use it.
Then study your own side. Identify the support you need, the way you naturally communicate, and the points where your habits clash with the manager's. The authors describe two common failures. A counterdependent person treats ordinary oversight as an insult and resists instructions on reflex. An overdependent person hides every disagreement, agrees in the room, and resents it afterward. Neither one is managing the relationship. Both are reacting to it.
So what do you do in practice?
First, learn how the person wants information and use that form. You can ask directly: would a one-page summary before the meeting help, or would you rather talk through the options together? That question is normal and useful. It tells the other person you care about making their attention easier to use.
Second, make expectations explicit in both directions. Friction often begins when the same conversation produces two different memories of the agreement. Close the meeting by saying it back in plain language: I will revise the volunteer schedule by Thursday, and you will confirm whether facilities can open the side entrance. That is not needless process. It is cheap insurance against a week of misaligned work.
Third, create no surprises. Managers usually handle bad news better than late news. If one of the aquarium's education rooms may be unavailable, raise it while the schedule can still change. A problem reported early is something you can solve together. The same problem revealed when buses are already booked becomes a trust problem, and trust is much harder to repair than a calendar.
Fourth, use the person's time selectively. Batch small approvals. Bring large problems with a recommendation attached. There is an old rule that makes this simple: bring the problem and a proposed solution together. Your director should hear, I recommend two arrival waves because it reduces crowding without adding staff, not simply, what should we do about all these buses?
Managing up also changes how you read emotion. James Gross's research on emotion regulation shows that acting early is cheaper than suppressing a feeling after it takes hold. If you know before the meeting that your director is dealing with an inspection, a brief reply is less likely to feel like a verdict on your competence. It may simply be pressure passing through the room. That does not excuse disrespect. It keeps you from turning every strained moment into a story about yourself.
There is one more trap. People often present their best idea as a finished object. Then they are confused when the person above them does not adopt it. A finished idea can leave no handle for anyone else to grab. Adam Grant has written about the value of giving people a way to shape an idea. Try: here is my recommendation, here is the part I am least sure about, and here is the choice I need from you. People are more likely to support work they helped improve.
The practice is ten minutes of preparation before your next meeting with a manager. Write three lines. What outcome does this person need from the conversation? What pressure are they carrying that is not about you? How do they best receive information? Then open with your recommendation, leave one real handle for their input, and close by saying back what each of you agreed to do.
That is the lesson. Managing up is shared work, and doing your half on purpose makes better ideas easier to hear and easier to act on.
Key terms
- managing up
- Managing up means taking responsibility for how you work with the person who has authority over your role.
- mutual dependence
- Mutual dependence means you and your manager each need knowledge, decisions, resources, or execution from the other.
- proposed solution
- A proposed solution gives your manager a concrete option to decide on alongside the problem.
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?
- 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.
- 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.