He knew before he walked in.
This was going to get ugly.
u/rjboogey, a PMO director sharing this breakdown on r/PromptEngineering, had one job: walk into a room full of senior leadership and explain why the engineering team couldn’t deliver everything they were asking for. That’s not a presentation. That’s a fight where being right isn’t enough. And it’s the kind of fight where even the most prepared person can get steamrolled by the loudest voice in the room.
Here’s what he did before he stepped into that room, and why the outcome wasn’t just survival. It was complete alignment.
📊 The Data Side Was Already Handled
The author had done serious analytical prep. He took Microsoft Project exports, had Claude build a live dashboard showing every active initiative, the business value tied to each, and a toggle system where 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 that for a second. Instead of showing a static slide with a capacity bar and hoping people read it charitably, he built something interactive. Leadership could see 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 decided. He needed something else.
🧠 Why Meeting Prep Usually Fails
Most people show up with facts and forget that the people across the table aren’t primarily driven by facts. They’re driven by positions they’ve already committed to publicly. No one walks out of a meeting saying “you were right, I was wrong” in front of their peers if they can avoid it. The goal isn’t to win the argument. It’s to give people a path to change direction without losing face.
That requires a different kind of preparation. You need to anticipate the specific objections that will come up, know exactly how you’ll respond to each one, and do it without going defensive or off-message mid-conversation. Most people practice none of that. They rehearse their opening and then improvise everything else, which is where things fall apart.
What you actually need before a high-stakes meeting is a script. Not a rigid one. A flexible scaffold that keeps you composed through objection after objection without going defensive or off-message.
That’s exactly what a well-structured prompt can build for you.
🔧 How the RACE Prompt Framework Works
The author used his app RACEprompt to structure the prompt. RACE stands for Role, Action, Context, Expectation. It forces clarity on what you’re actually asking AI to produce before you start typing.
Here’s how he applied each piece:
- Role: Not just “you’re a PM.” He described the specific flavor of the challenge: composure under sustained pushback. That specificity changes the entire output. Generic role, generic advice. If you tell the model it’s playing “a strategic communicator who needs to maintain authority while delivering constrained options to an impatient executive team,” you get something completely different than “act as a project manager.”
- Action: Build a full meeting script with objection-by-objection response options tailored to real scenarios. Not a summary of talking points. An actual back-and-forth with multiple response paths per objection.
- Context: Leadership that defaults to “execute everything with the resources we have.” Every response in the output was shaped around that specific pattern, not generic negotiation dynamics. The model knew exactly who it was helping him talk to.
- Expectation: Explicit tone instruction. “Avoid apologizing for constraints, frame them as strategic levers.” That one line completely shifted the output from defensive to authoritative.
The actual prompt text wasn’t preserved in the original post, but the structure above is the skeleton worth adapting regardless of what tool you use to build it.
💡 Tips Worth Stealing From This Breakdown
A few things stood out that apply well beyond this specific meeting:
- Context carries more weight than role. Telling the model the behavioral pattern of the people in the room, not just their job titles, is what produces relevant responses instead of textbook ones. “VP who’s publicly committed to Q2 launch” is more useful than “executive stakeholder.”
- Tone instructions belong inside the prompt. “Don’t apologize, reframe as levers” isn’t a style preference. It’s a functional instruction that changes the output class entirely. Build it into the prompt, not into your post-generation editing.
- Build for variation, not a single script. The author got three different response options for the same repeated objection, each calibrated to a different source of resistance. One for the person who’s genuinely worried about timeline. One for the person protecting their pet project. One for the person who just doesn’t believe the capacity numbers. 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 It Before Your Next Tough Meeting
You don’t need any specific app to use this approach. Before your next high-stakes conversation, write out your RACE components manually. Who is the model playing (specific situation, not just job title)? What’s the behavioral pattern of the room? What tone should the output use and what should it avoid?
Spend 20 minutes on that before you spend any time on your slides. The script you generate won’t be perfect. But it will give you something to react to, refine, and internalize. That’s miles ahead of walking in with bullet points and hope.
The result for this PMO director: complete alignment. Projects got deprioritized with leadership owning that decision, not resisting it. He walked out with a signed-off tier structure.
The data set the stage. The prep won the room.
The full breakdown, including details on the dashboard build, is in the original discussion on r/PromptEngineering.
The prompt I used to prep for the most contentious executive meeting I’ve had this year — full breakdown
by u/rjboogey in PromptEngineering