He walked into a hostile meeting and left with full alignment

He knew before he walked in. This was going to get ugly.

A PMO director posting on r/PromptEngineering had one job: walk into a room full of senior leadership and explain why engineering couldn't deliver everything they'd already committed to publicly. That's not a presentation. That's a fight where being right isn't enough, and the loudest voice in the room usually wins.

He walked out with complete alignment. Projects got deprioritized with leadership owning the decision, not resisting it. He left the room with a signed-off project tier structure.

The data wasn't what did it. The prep was.

In partnership with

LLM traffic converts 3× better than Google search

58% of buyers now start their research in ChatGPT or Gemini, not Google. Most startups aren't showing up there yet.

The ones that are get cited by the AI tools their buyers, investors, and future hires already use. And they convert at 3×.

Download the free AEO Playbook for Startups from HubSpot and get the exact steps to start showing up. Five minutes to read.

Get the free playbook

The data side was already handled

He had done serious homework before the meeting. Microsoft Project exports pulled into a live dashboard Claude built for him. Every active initiative, every linked business value, a toggle system so leadership could flip projects on and off and watch engineering capacity shift in real time. Monte Carlo simulations for schedule risk. Delay scenarios. The full picture.

Think about what that shift does. Instead of a static slide and a prayer, leadership watched the consequences of their own choices play out live on the screen. That's a fundamentally different conversation.

But data doesn't move a room where people have already committed to a position publicly. He knew the numbers alone wouldn't carry it.

Why most meeting prep fails

Facts don't flip rooms. Positions do.

People across the table aren't primarily driven by the information you put in front of them. They're driven by what they've already said out loud to their peers. Nobody walks out of a meeting saying "you were right, I was wrong" in front of their colleagues if they can possibly avoid it.

The real goal in a high-stakes meeting isn't to win the argument. It's to give people a way to change direction without losing face.

That takes a different kind of prep. You have to anticipate every objection, know exactly how you'll respond, and do it without going defensive when someone pushes hard. Most people rehearse their opening and then improvise the rest. That's where everything falls apart.

What you actually need is a script. Not a rigid one. A flexible scaffold that holds you up through objection after objection without pulling you off-message.

That's what a well-built prompt can give you.

When Pressure Rises, Here’s Where Leaders Turn

Costs rise. Clients delay. Pressure builds.

The Survival Hub gives you practical ways to respond from cutting costs to tightening operations and staying on top of revenue.

Built to help you take control when things feel uncertain.

Visit BELAY’s Survival Hub

*Ad

How he used RACE

He structured it through his own app (RACEprompt), but the framework matters way more than the tool. RACE = Role, Action, Context, Expectation.

Here's how each block did work for him:

Role. Not "you're a PM." He described the specific flavor of the challenge: composure under sustained pushback. That one change reshapes the whole output. "A strategic communicator who has to maintain authority while delivering constrained options to an impatient executive team" is a completely different instruction than "act as a project manager." Generic role, generic advice.

Action. Not a summary of talking points. The action was "build a meeting script with objection-by-objection response options tailored to each scenario." Multiple response paths per objection. An actual conversation tree, not a monologue.

Context. This is where most people fail. They tell the model who's in the room by job title. He told the model the pattern he was walking into: leadership that defaults to "execute everything with the resources we have." Every response the model generated was calibrated to that exact resistance pattern. The model knew the specific team, not executives in general.

Expectation. He told the model: "avoid apologizing for constraints, frame them as strategic levers." That one line shifted the output from defensive to authoritative. Tone isn't a style preference you fix in editing. It's an instruction that changes the entire class of response the model produces. Build it into the prompt.

Four things worth stealing

A few patterns from this breakdown worth pulling forward:

Context carries more weight than role. The behavioral pattern of the people in the room beats their job titles every time. "VP who's publicly committed to a Q2 launch" is more useful than "executive stakeholder."

Tone instructions live inside the prompt. "Don't apologize, reframe as levers" is a functional instruction, not a style note. Build it into the prompt, not into your post-generation editing.

Build for variation, not a single script. He got three different responses for the same repeated objection. One for the person worried about timeline. One for the person protecting their pet project. One for the person who just doesn't believe the capacity numbers. Same objection, three sources of resistance, three different replies. That's a strategy, not a script.

AI compresses build time, not refinement time. He spent 90 minutes customizing a solid scaffold instead of 3 days building from scratch. That's where the real leverage sits. You still have to know your material. You just don't have to start from a blank page at midnight before a 9am showdown.

Try this before your next hard meeting

You don't need his app. Before your next high-stakes conversation, write out the four RACE blocks by hand.

Who is the model playing (the specific situation, not the job title)? What's the behavioral pattern of the room you're walking into? What tone should the output use, and what should it actively avoid?

Spend 20 minutes on that before you touch your slides. The script you get back won't be perfect. It'll give you something to react to, refine, and internalize. That's miles ahead of walking in with bullet points and hope.

Data sets the stage. The prep wins the room.

Check out the original post here.

Hiring in 8 countries shouldn't require 8 different processes

This guide from Deel breaks down how to build one global hiring system. You’ll learn about assessment frameworks that scale, how to do headcount planning across regions, and even intake processes that work everywhere. As HR pros know, hiring in one country is hard enough. So let this free global hiring guide give you the tools you need to avoid global hiring headaches.

Download the free guide today

*Ad