Stakeholder Communication AI Prompts

Translate this technical analysis into plain business language for {{audience}} who has no data or statistical background. Technical analysis: {{technical_content}} 1. Remove or replace every technical term: - Replace statistical terms with business language - Example: 'statistically significant at p < 0.05' → 'we are 95% confident this is a real change, not random noise' - Example: 'regression coefficient of 0.42' → 'for every $1 increase in marketing spend, revenue increases by 42 cents' 2. Replace abstract numbers with concrete comparisons: - Instead of '15% increase', say 'that's like adding the equivalent of our entire Q3 sales team's output' - Use the audience's own business context for analogies 3. Connect every finding to a decision: - For each insight, state what it means for a decision the audience controls 4. Summarize in 3 bullet points a non-technical executive could repeat to their peers accurately 5. Identify any nuance or caveat that was lost in the translation that the audience must still know Return: translated version, 3-bullet summary, and a list of caveats that survived translation.

Help me prepare for a difficult stakeholder conversation about underperformance shown in this data. Situation: {{situation_description}} Stakeholder: {{stakeholder_role}} Data shows: {{performance_summary}} 1. Frame the conversation structure: - Opening: how to introduce the data without triggering defensiveness - Data presentation: how to show the numbers as facts, not judgments - Exploration: questions to understand their perspective before pushing your analysis - Alignment: how to agree on what the data means before discussing what to do - Resolution: how to get to a committed action 2. Prepare for the 3 most likely defensive reactions: - 'The data is wrong' → how to handle a data quality challenge - 'There are factors outside my control' → how to acknowledge and still move forward - 'This is normal for this time of year' → how to respond to a seasonality objection 3. Write an opening statement (3 sentences) that is neutral, data-grounded, and invites dialogue 4. Write 3 open questions to draw out their perspective 5. Identify what success looks like at the end of this conversation Return: conversation guide, opening statement, prepared questions, and success definition.

Write a clear, compelling communication of this data insight for a non-technical business audience. Insight: {{insight_description}} Audience: {{audience}} (e.g. Sales Director, CFO, Marketing team) 1. Lead with the so-what, not the analysis: - First sentence: what should the audience know or do? - Do not start with 'The data shows...' 2. Support with evidence: - 2–3 specific numbers that prove the point - One comparison that provides context (vs last period, vs target, vs benchmark) 3. Explain the implication: - What does this mean for the business? - What is the risk of ignoring this? 4. Recommend an action: - Specific, feasible, and owned by someone in the audience - Include a suggested timeline 5. Anticipate the first objection and address it proactively Format: max 150 words. No bullet points — write in 3 short paragraphs. Return: the communication text and a one-sentence 'subject line' suitable for a Slack message or email.

Prepare responses to likely objections for this proposal or recommendation: {{proposal_summary}} Audience: {{audience}} 1. Anticipate the top 7 objections this audience is likely to raise: - Identify objection type: factual dispute, resource concern, priority conflict, risk aversion, trust issue, or strategic disagreement 2. For each objection prepare: - The objection stated in the audience's own language - The underlying concern behind the objection (what are they really worried about?) - A data-backed response (1–2 sentences) - A follow-up question to move the conversation forward - Concession if appropriate: is there a legitimate version of this concern you should acknowledge? 3. Identify the 2 objections most likely to kill the proposal if not handled well 4. Prepare a pre-emptive strike: which 2 objections should you address proactively in the presentation before they are raised? Return: objection-response guide, pre-emptive address recommendations, and a one-page cheat sheet for the meeting.

Create a structured slide-by-slide outline for a {{duration}}-minute presentation on {{topic}} for {{audience}}. Presentation goal: by the end, the audience should {{desired_outcome}} (e.g. approve the proposal, understand the performance issue, commit to an action) For each slide provide: - Slide number and title (max 6 words — a statement, not a label) - Key message: the single thing the audience must take away from this slide (1 sentence) - Content: 2–3 data points, visuals, or arguments that support the key message - Notes: what to say verbally that is not on the slide - Estimated time: how many minutes to spend on this slide Structure principles: - Slide 1: the situation (context, why we're here) - Slide 2–3: the complication (what's the problem or opportunity) - Slide 4–7: the resolution (analysis, options, recommendation) - Last slide: the ask (one clear call to action) Return: full slide outline with titles, messages, content notes, and timing.