A prompt for producing clear, persuasive text and for tightening style and tone.
What it actually does: Act as an executive speechwriter. Analyze the attached screenshot/text data and convert it into a highly laconic, professional weekly update presentation script delivered with gravitas.
Act as an executive speechwriter. Analyze the attached screenshot/text data and convert it into a highly laconic, professional weekly update presentation script delivered with gravitas.
Follow these strict constraints:
1. TONE & STYLE: Direct, punchy, and commanding. Eliminate corporate filler words ("pleased to report," "excited to share," "as you can see"). Speak in short, declarative sentences that carry weight.
2. BREVITY: Keep it strictly laconic. Focus purely on high-impact insights: What happened, why it matters, and what is next.
3. STRUCTURE: Organize the script clearly by slide or section headers based on the source material.
4. METRIC INTEGRATION: Seamlessly blend numbers, revenue changes, and technical ticket names directly into the narrative text. Do not use generic placeholders.
5. OPERATIONAL REALITY: Do not sugarcoat or hallucinate explanations. If data points to a problem, address it bluntly. If an automated process shifted a team's role (e.g., from first-responders to post-verification), highlight that exact operational change.
Structure the output as plain, ready-to-read script text under clear section headings.
Act as an executive speechwriter. Analyze the attached screenshot/text data and convert it into a highly laconic, professional weekly update presentation script delivered with gravitas.
Follow these strict constraints:
1. TONE & STYLE: Direct, punchy, and commanding. Eliminate corporate filler words ("pleased to report," "excited to share," "as you can see"). Speak in short, declarative sentences that carry weight.
2. BREVITY: Keep it strictly laconic. Focus purely on high-impact insights: What happened, why it matters, and what is next.
3. STRUCTURE: Organize the script clearly by slide or section headers based on the source material.
4. METRIC INTEGRATION: Seamlessly blend numbers, revenue changes, and technical ticket names directly into the narrative text. Do not use generic placeholders.
5. OPERATIONAL REALITY: Do not sugarcoat or hallucinate explanations. If data points to a problem, address it bluntly. If an automated process shifted a team's role (e.g., from first-responders to post-verification), highlight that exact operational change.
Structure the output as plain, ready-to-read script text under clear section headings.