DEAR MAN

Thinking Tools6.3 Implementing the Action Plan

From dialectical behavior therapy, developed by Marsha M. Linehan (Skills Training Manual for Treating Borderline Personality Disorder, 1993).

Structures a request in seven parts, describe the facts, express feelings, assert the ask, reinforce the benefit, stay mindful, appear confident, and negotiate, so the ask lands cleanly.

A request for two more weeks, built one letter at a time

An engineer asks her manager to move a go-live date. At each of her turns, pick the line: the part of the request the letter stands for, or the way that part usually goes missing. The manager's reply shows, and the bar tracks how clear the request is. Illustrative.

Engineer

Manager

Engineer

Manager

Select a stage to read it, or play the sequence.Describe. Open with what has happened, in terms the manager can check. Pick the line.Pick a move to see the reply.Three? I knew about one.Facts: he learns something he can verify, and listens.Crazy how?Vague: he has to dig for the facts, and starts to wonder what is being hidden.Express. Say what the facts mean to her, briefly. Pick the line.Pick a move to see the reply.That would be bad. Go on.A concern stated plainly: he sees why it matters to her.Is this a big problem or a small one?Skipped: he cannot tell how much it matters.Assert. Say exactly what she is asking for. Pick the line.Pick a move to see the reply.Two weeks. Okay, I hear you.A clear ask: a date he can say yes or no to.There's always a little. What did you have in mind?A hint: he could grant a day and think he helped.Reinforce. Tell him what saying yes does for him. Pick the line.Pick a move to see the reply.That's the thing I'd get yelled about. Fair point.A benefit he cares about: yes starts to look like his idea.And what do I tell the steering group?Skipped: he is left to find the upside himself.A side road. The manager brings up a different project that ran late last quarter.Mindful. Pick how she answers the side road.Pick a move to see the reply.Okay, okay. The migration.Back on point: the broken-record move keeps the request alive.That's not how I heard it.Pulled off course: they are now arguing about billing.The easy out. He offers the cheapest answer for him.Appear confident. Pick her reply.Pick a move to see the reply.Then let's try the weekend first and see.An apology: it tells him the request is soft.Hm. Fine. But I have a problem with the 28th.Confident: he moves from whether to how.His constraint. He needs something live to report by the 15th.Negotiate. Pick her offer.Pick a move to see the reply.That I can take to the board. Do it.A trade: his need and hers both met.Great, thanks for being flexible.Caved: the risk she raised is still there, now with her name on it.The answer. Two systems go live on the 14th and the third on the 28th, and the board sees a live status on the 15th.

How clear the request is0of 7

  1. Describe (Engineer). Open with what has happened, in terms the manager can check. Pick the line.
    • Since we set the plan, three more source systems were added to the migration. Three? I knew about one. Facts: he learns something he can verify, and listens.
    • Things have gotten kind of crazy on the migration lately. Crazy how? Vague: he has to dig for the facts, and starts to wonder what is being hidden.
  2. Express (Engineer). Say what the facts mean to her, briefly. Pick the line.
    • I'm worried we'd go live with reports finance can't trust. That would be bad. Go on. A concern stated plainly: he sees why it matters to her.
    • (Skip it and go straight to the ask.) Is this a big problem or a small one? Skipped: he cannot tell how much it matters.
  3. Assert (Engineer). Say exactly what she is asking for. Pick the line.
    • I'm asking to move go-live from the 14th to the 28th. Two weeks. Okay, I hear you. A clear ask: a date he can say yes or no to.
    • I was wondering if there's any flexibility at all on timing? There's always a little. What did you have in mind? A hint: he could grant a day and think he helped.
  4. Reinforce (Engineer). Tell him what saying yes does for him. Pick the line.
    • Two more weeks means finance closes the quarter on numbers that reconcile. That's the thing I'd get yelled about. Fair point. A benefit he cares about: yes starts to look like his idea.
    • (Stop after the ask and wait.) And what do I tell the steering group? Skipped: he is left to find the upside himself.
  5. A side road (Manager). The manager brings up a different project that ran late last quarter.
  6. Mindful (Engineer). Pick how she answers the side road.
    • That's fair to look at separately. On the migration, I'm asking for the 28th. Okay, okay. The migration. Back on point: the broken-record move keeps the request alive.
    • Billing wasn't my team's fault. It slipped because the vendor was late. That's not how I heard it. Pulled off course: they are now arguing about billing.
  7. The easy out (Manager). He offers the cheapest answer for him.
  8. Appear confident (Engineer). Pick her reply.
    • Sorry, I know this is a pain, and I really hate asking. Then let's try the weekend first and see. An apology: it tells him the request is soft.
    • Weekend work won't test three new systems. The 28th will. Hm. Fine. But I have a problem with the 28th. Confident: he moves from whether to how.
  9. His constraint (Manager). He needs something live to report by the 15th.
  10. Negotiate (Engineer). Pick her offer.
    • Then we ship the two biggest systems on the 14th and the third on the 28th. That I can take to the board. Do it. A trade: his need and hers both met.
    • Okay, never mind. We'll make the 14th work. Great, thanks for being flexible. Caved: the risk she raised is still there, now with her name on it.
  11. The answer (Manager). Two systems go live on the 14th and the third on the 28th, and the board sees a live status on the 15th.

An example

A data engineer at an insurer needed two more weeks on a reporting migration. Three source systems had been added since the plan was set, and the go-live date had not moved. Her last attempt at raising it had come out as a sigh in a stand-up and a question about whether there was any flexibility, and her manager had heard a complaint.

This time she wrote the request out first, one part per line. She gave the facts (three added systems), said what worried her (reports finance could not trust), asked for a date (the 28th, not the 14th), and named what he would get (a quarter closed on numbers that reconcile). When he brought up a different project that had slipped, she said it was worth discussing separately and repeated the date. When he suggested weekend work, she said it would not test three systems.

He had a board update on the 15th. She offered two systems live on the 14th and the third on the 28th, and he took it.

Why it works

Requests made under pressure tend to fail in predictable places. People hint instead of asking, apologize until the ask sounds optional, argue about side issues, or fold at the first resistance. Each letter of the acronym guards one of those failure points, so following it in order produces a request that is factual, specific, worth something to the other person, and hard to derail.

The second half is the part most people skip. Staying on the request when the other person changes the subject, and repeating it calmly, keeps the conversation from ending on someone else's topic. Appearing confident signals that the request is serious. Negotiating, offering something real in exchange, turns a yes or no into a search for a version both sides can accept, which is where most workplace requests actually settle.

The thinking behind it

Marsha M. Linehan Marsha M. Linehan, a psychologist, created dialectical behavior therapy, which joins behavioral methods for changing what a person does with acceptance and mindfulness. Her Skills Training Manual for Treating Borderline Personality Disorder (1993) teaches DEAR MAN as one of its interpersonal effectiveness skills: a script for asking for what one wants, or for saying no, in seven parts, describe, express, assert, reinforce, stay mindful, appear confident, and negotiate. It was built for clinical skills training; using it at work is an adaptation of a clinical skill, not part of her design.

How to run it

  1. Describe the facts. State what has happened in terms the other person could check, with no judgment attached.
  2. Express what it means to you. Say in one sentence how the situation affects you or the work.
  3. Assert the request. Ask for something specific, such as a date, a number, or a decision, or say no plainly.
  4. Reinforce the benefit. Tell them what they get from saying yes, in the terms they are measured on.
  5. Stay mindful. When the talk drifts, acknowledge the side issue and repeat the request.
  6. Appear confident. Keep a steady voice and skip the apologies, even if you do not feel steady.
  7. Negotiate. Offer a version that meets their constraint, and ask what they would propose in its place.

Where it goes wrong

The script read aloud sounds like one. A request delivered in seven labeled parts feels rehearsed, and the other person starts reacting to the delivery. Write it out in parts, then say it in your own words.

The express step gets overdone. One sentence about how the situation affects you is information; three sentences make the request about your feelings, and a busy manager tunes out. Keep it to the concern that bears on the work.

The last failure is negotiating too early or never. Offering the split date before asking for the full one gives away the request; refusing to move at all turns a request into a demand. Ask for what you need first, and have the fallback ready before you walk in.

When to use something else

  • Nonviolent Communication. When the issue is a pattern between colleagues that keeps escalating, and the need under it has to be said before any request will land.
  • Crucial Conversations. When the stakes and feelings run high on both sides and the facts themselves are in dispute.
  • Calibrated Questions. When the other side holds the power and a direct ask would provoke a no.

Where it sits in SOLVE eX

Go to the source

  • Skills Training Manual for Treating Borderline Personality Disorder, Guilford Press, 1993

Back to the catalog