They'll Never Say Yes — Book 4

They'll never
say yes.

Book 4 · The buy-in playbook

You already know the workshop will work. You've designed the agenda. The problem isn't the workshop — it's getting someone with calendar authority to say yes. Word-for-word scripts for the five objections you'll hear most, with follow-up lines for when they push back.

Every objection to a workshop is really an objection about time. Your job is to flip that equation.

"We're at a decision point with multiple valid perspectives. Right now we're making that decision through Slack threads and it's been six weeks without resolution. I'm proposing we spend 2–3 hours getting everyone in one room to surface the disagreements, work through them with a structured process, and walk out with a decision that everyone helped shape. That's 2–3 hours versus the weeks we've already spent going in circles."

WHY IT LANDS · 01

It quantifies the cost of inaction. "It's been six weeks" is harder to dismiss than "we should do a workshop."

WHY IT LANDS · 02

It names the dysfunction without blaming anyone. You're describing a pattern, not pointing fingers.

WHY IT LANDS · 03

It makes the workshop sound like the efficient option. Because it is.

The five objections — word for word

You've heard these before. Now watch them lose.

A few rules first: don't memorize these word for word — internalize the logic so you can adapt in a hallway, on Slack, or when someone pushes back unexpectedly. Lead with listening. And take one objection at a time: answering everything at once sounds defensive, addressing one thing sounds confident.

Objection one

Why it worksYou're not asking for more time. You're offering to compress the time they've already been wasting.

The stakeholder"We don't have time for a workshop."

Say this"I hear you, everyone's stretched. But let's look at what we've already spent on this. There have been [number] meetings about [topic] over the past [timeframe], plus the Slack threads and the async back-and-forth. If we add that up, we've already spent more time than a focused two-hour session would take. The difference is that those hours didn't produce a decision. This one will."

If they push back"I can design a 90-minute version. Tight, structured, no filler. We walk in with a clear objective, work through it, and walk out with a decision. Ninety minutes to close something that's been open for [timeframe]. That's a net time savings."

Objection two

Why it worksYou've acknowledged the value of the survey while making clear what it can't do — and turned their objection into part of your plan.

The stakeholder"Just send a survey."

Say this"A survey will tell us what people prefer individually. But the decision we need to make here depends on trade-offs that require conversation. [Person A] needs X, [Person B] needs Y, and those might conflict. A survey won't surface that tension — it'll just give us two contradictory data points. The workshop is designed to get those two perspectives in the same room so we can find the path that works for both."

If they push back"Tell you what — I'll send a short pre-read survey to collect individual perspectives before the workshop. That way we walk in with the data, and the workshop is focused on the conversation the survey can't have."

Objection three

Why it worksYou've repositioned the workshop from "everyone does design" to "the design team gets the input they need to do their job well."

The stakeholder"The design team can figure this out."

Say this"The design team absolutely can figure out the design. What we can't figure out alone is the business constraints, the technical trade-offs, and the stakeholder priorities that should shape the design. If we design in isolation and then present it, we'll get feedback that sends us back to the drawing board. I've seen that cycle take three rounds. The workshop collapses those three rounds into one session by getting the constraints on the table before we design, not after."

If they push back"I'm not asking everyone to design. I'm asking the people with context — engineering, product, the business stakeholder — to spend two hours helping us frame the problem correctly. The design team will take it from there. But we'll be building on shared understanding instead of assumptions."

Objection four

Why it worksThe pulse check is your secret weapon. It almost always reveals that "we all agree" actually means "nobody has disagreed yet." Once you can show the divergence, the workshop sells itself.

The stakeholder"We know what we need to do."

Say this"That might be the case, and if it is, the workshop will be short. But in my experience, when I hear 'we already know,' it often means one or two people have a clear direction and the rest haven't been asked. If everyone truly agrees, we'll confirm it in thirty minutes and use the rest of the time to plan execution. If there are hidden disagreements, we'll surface them now instead of discovering them three weeks into implementation."

If they push back"Let me do a quick pulse check, three questions to five people. If everyone's genuinely aligned, I'll cancel the workshop. If there's any divergence, we run it. Fair?"

Objection five

Why it worksThe "straw man" approach gives the leader their recommendation while still creating the space for the group to shape the decision — and framing it as something to be improved, not defended, reduces the ego dynamics.

The senior leader"Can't you just make a recommendation?"

Say this"I can absolutely present a recommendation. But here's what happens next: you'll want input from [engineering / product / legal / whoever], they'll have questions I can't answer on their behalf, and we'll end up in a series of follow-up meetings. The recommendation becomes a starting point for debate rather than a decision. The workshop compresses that entire cycle into one session. Instead of me recommending and everyone reacting over two weeks, we co-create the answer in two hours."

If they push back"How about a hybrid approach? I'll prepare my recommendation and present it at the start of the session as a straw man. Then we use the structured workshop process to stress-test it, improve it, or replace it. Either way, we walk out with something stronger than what any one person could produce alone."

Only got a hallway? Here's the 60-second version.

If you only have a quick Slack message or a walk to the elevator, here's the compressed pitch:

Say this: "We've been going back and forth on [topic] for [timeframe]. I can design a [90-minute / 2-hour] session that gets [the key people] in a room with a structured process and walks out with a decision. It'll save us weeks of async back-and-forth. Can I send you the details?"

Short. Specific. Positions the workshop as the faster path, not the slower one.

The stakeholder email that lands the yes.

This email has landed a yes in startups, agencies, and Fortune 500 companies. Fill in the brackets. Adjust the tone for your organization. Send it.

check_circle

It names the cost of the status quo. Not in vague terms — in specific weeks, specific consequences.

check_circle

It asks for almost nothing. They don't need to prepare, design, or organize. They just need to show up.

check_circle

It's a proposal, not a permission slip. You're not asking "can I run a workshop?" You're saying "here's what I'm planning. Does Tuesday work?"

check_circle

It specifies the output. The recipient knows exactly what they'll get for their time investment.

When they still say no

Document it. "Understood. I've noted that we're proceeding with [current approach] for [topic]. I'll document my workshop proposal in case we want to revisit it."
Make your recommendation anyway. Through the channels they prefer. Don't sulk. Do the work.
Wait for the opening. When the async approach fails or the decision gets revisited for the third time, don't say "I told you so." Say "I think we're at a good moment to try that working session I proposed. Want me to set it up?"

→ The second ask almost always gets a yes.

They'll never
say yes.

Every objection to a workshop is really an objection about time. Your job is to flip that equation.

You've heard these before. Now watch them lose.

Only got a hallway? Here's the 60-second version.

The stakeholder email that lands the yes.

When they still say no

Get the playbook — free.

The hardest part of facilitation isn't the room. It's getting to the room.