How to Reject a Project at Work Using DESC (Without Torching the Relationship)

The Scene

You are a senior product manager on the Platform team. You currently own the checkout-redesign migration (shipping end of Q2), the merchant API v3 deprecation (six-month runway), and a part-time mentorship of a new APM. Your calendar this month has 62% meeting load and two late evenings you have not told anyone about.

Monday morning, your skip-level manager messages: "Hey, got a minute? We want you to lead the compliance portal project. Starts next week. Timeline is tight — wanted to offer it to you first because I trust your judgment on this one. Think about it and let's chat at 3?"

Three observations:

1. It is an explicit offer, not an order.
2. It is being framed as an honor.
3. You know, within ten seconds of reading it, that you cannot take it without dropping one of the existing commitments or blowing up your health.

You need to say no at 3 pm. You need to say no in a way that:

• Does not burn the relationship with your skip-level
• Does not sound whiny or over-explained
• Offers an actual alternative
• Leaves them with a concrete next step that does not boomerang

This is exactly what DESC was built for.

DESC Recap in 30 Seconds

DESC (Bower & Bower, Asserting Yourself, 1991) is the assertiveness framework for structured no's. Four steps, each one job:

| Step | One-Liner | |---|---| | Describe | Name the situation factually, no judgment. | | Express | State your view or feeling, in first person. | | Specify | State what you want. One specific alternative. | | Consequences | Name what is true in each branch — the yes and the no. |

DESC is different from NVC here: NVC is for emotionally charged relationships (spouse, parent, close friend). DESC is for structured professional asks where the relationship is transactional-but-important. A skip-level you respect is textbook DESC.

The 5-Round Script

Round 1: Describe (The Facts)

You: "Thanks for offering me this — I take it seriously that you thought of me first. I want to give you a real answer, which means walking through where I actually am right now.

Current scope: checkout redesign shipping June 28, API v3 deprecation with six-month runway, and part-time mentorship of Dev. Calendar is at 62% meeting load this month. Realistically, I have about 6-8 hours of deep work a week right now, and I have been running two late evenings to close the gap."

Notice what is NOT here: no "I am so swamped," no "you have no idea how busy I am," no "I literally cannot handle one more thing." Just the numbers. The facts do the work.

Round 2: Express (Your Honest View)

You: "My honest read is: taking the compliance portal on this timeline means one of three things breaks. Either checkout misses June 28, the API deprecation slips past its hand-off, or Dev's mentorship becomes transactional. I am not willing to let the first two slip quietly, and the third one I would not even notice until he stopped asking for 1:1s — which is the worst outcome.

I also want to say the straight version: I am reaching the capacity line. Another month at 62% meeting load and I am going to make a mistake on something that is currently going fine. I would rather flag that now than after the first missed deadline."

This is the assertive part. "Reaching the capacity line" is a complete sentence in DESC — you do not apologize for it, and you do not dress it up.

Round 3: Specify (The Alternative, Not Just the No)

You: "Here is what I want to propose. Three options, in the order I'd pick them:

Option A: Give the compliance portal to Rahul. He has just wrapped the integration project, has the compliance background from his last role, and has been asking for a lead rotation. I will advise on week-1 kickoff and check in weekly. That is probably 2-3 hours a week for me, which I have.

Option B: Defer the kickoff 8 weeks. After checkout ships on June 28, I have about 30% capacity back. I can lead the portal starting July 7. That is a longer timeline, but the kickoff is mine and the quality is what you want.

Option C: If it has to be me and it has to be now — I can take it, but something has to slip. I want you to tell me which of the three existing commitments you want me to renegotiate. I am not making that call unilaterally.

I think A is the best answer. B is the acceptable one. C I want you to pick with eyes open."

The move here is counterintuitive: by offering an acceptable-to-you option A, a fallback option B, and a "you pick the trade" option C, you make it easy for the skip-level to say yes to A — and you have shown that your no is not a dodge.

Round 4: Consequences (Honest, Both Ways)

You: "Consequences of option A: Rahul gets a visible project, the portal ships with someone who is fresh and focused, and I keep the things already committed to on track. The risk is Rahul has not led a project solo before — I am partly proposing him because I think he is ready, and I am partly proposing him because growing that next layer of leads is how our team scales. I am willing to own that risk with you.

Consequences of option C: we get me on the portal, and something else gets renegotiated. I want to be careful here — the thing I am most protective of is the mentorship, because that one is invisible in a status report and shows up six months late when Dev leaves. But if you want to pick checkout or API, we can have that conversation."

DESC consequences are not threats. They are the honest accounting of each path. Giving the skip-level a real picture of both lets them make a real decision.

Round 5: Propose a Clear Next Step

You: "I would like to leave this call with a decision or a decision-by date. If you need to think about Rahul, let's give it until Wednesday EOD — that gives you time to check with Maya, and it gives me time to talk to Rahul about whether he wants it before Thursday's staff meeting.

Does that work?"

Always leave with a concrete next step. "Let me think about it" without a date is how the ask comes back to you in a week with the timeline already tighter.

Common Reactions and How to Respond

| Skip-Level Says | You Say | |---|---| | "I really want you on this one." | "I hear that, and I take it as real praise. My options A and B are both ways to get you what you need without burning down the other commitments. Which concern is driving the 'it has to be you' — the content expertise, the stakeholder relationships, or the timeline risk?" | | "Can't you just deprioritize the mentorship?" | "I can, and I want to flag what that actually means. Dev came in 4 months ago and the structure is weekly 1:1s. If those go to every-other-week, he is fine. If they go to ad-hoc, he drifts. I want to make the trade explicitly, not quietly." | | "Rahul isn't ready." | "I disagree, but that is a real question. Want to do a 20-minute check-in with him Wednesday, the three of us? If you come out of it still unconvinced, I will take option B instead." | | "Then we're stuck." | "We are not stuck. The options A and B are both paths. We are stuck only if the constraint is 'me, now' — and I am telling you honestly that constraint is the one that breaks the other work. Which of the three do you want to pick?" | | "I need to think about it." | "That is fine. Let's put a decision on the calendar for Wednesday 5 pm. If we miss Wednesday, I will default to starting option A conversation with Rahul on Thursday — not to force your hand, but because the kickoff clock is running." |

Why DESC Beats "I Am Too Busy Right Now"

| Saying No Approach | How Skip-Level Hears It | Professional Cost | |---|---|---| | "I am too busy right now" | Vague, whiny, suggests poor prioritization | "They can't handle scope" — invisible mark | | "Sure, I can take it" (then you drown) | Wins the meeting, loses the quarter | Credibility loss when something drops | | "I would need to drop something" (without alternative) | Pushes the problem back up without a solution | Frames you as a blocker | | DESC with options A/B/C | Structured no + alternatives | "They manage load well and think like a manager" |

DESC for saying no is not about being polite. It is about demonstrating that your no is informed, that you have thought about the system not just yourself, and that you are offering actual paths — not just an excuse.

Try It With Your Specific Situation

The script above is for a senior PM declining a compliance portal. Your version might be an engineer being asked to lead a migration on top of current oncall, a designer being handed a rebrand while finishing a redesign, or a sales rep being asked to cover another territory without backfill.

Each version has different numbers, different alternatives, and different stakeholder politics. The DESC skeleton is the same — but Option A (the replacement you propose) is where most people freeze, because finding the actual right alternative is the hard intellectual work of the conversation.

ConvoPrep takes your specific workload, the new project, and your organizational context — and generates a DESC script with three specific alternatives customized to your situation. Then it lets you practice Round 4's pushback with an AI that plays your specific manager, including the "I really want you on this" push.

Try ConvoPrep free — convoprep.co. Walk into the 3 pm meeting with the script, the alternatives, and the reps.

FAQ

Is DESC appropriate for turning down a CEO or founder, not just a manager?

Yes, with one tweak: shrink the Describe section. A CEO does not need your full scope summary — they will skim. Compress Describe to 2-3 sentences and let Specify do the heavy lifting. "Here is the current stack, here are the three options, I recommend A — do you want me to proceed?" fits in one Slack thread.

What if I genuinely can't think of an Option A?

Then the DESC has to be option C — "if you need this, pick what slips." Do not invent a fake alternative to make the no easier. A fake alternative that falls apart in week 2 is worse than a clean "then something has to go, and I need you to tell me which."

How do I do DESC over Slack instead of in a meeting?

It still works, with slightly different rhythm. Describe and Express in one paragraph. Specify as a bulleted list of options (A/B/C). Consequences as a short paragraph. Close with "happy to discuss live — open for a 10-min slot at X time?" A Slack DESC is 200-300 words, no more.

What if my manager gets visibly upset that I said no?

Do not retreat. "I can see this landed hard. I want to be useful to you, and I want to be straight that the options I just laid out are the real ones. If none of them work, I am open to hearing what else is on the table — but I am not willing to pretend I can add this on top." DESC + holding the line under pressure is what makes the framework actually work.