Marketing IA ChatGPT 5 visualizacoes

Success Story and Project Portfolio in PowerPoint

powerpoint success story project portfolio pmo executive presentation project management vba storytelling
ESCOPO

This prompt guides the creation of a complete corporate presentation to communicate a success story and position a project portfolio in a strategic way. It turns raw data, indicators, testimonials, schedules, and scope information into a clear, persuasive, and visually consistent executive narrative.

Ideal for PMOs, consultancies, transformation teams, technology, operations, B2B sales, and project leaders who need to report results, win sponsorship, demonstrate delivery capability, or support commercial proposals. The output includes a slide-by-slide outline, ready-to-use content, chart recommendations, presentation notes, and optional VBA automation.

Conteudo
Prompt principal
Act as a Strategy Director, PMO, and Corporate Presentation Design expert, specialized in building executive narratives for success stories and project portfolios in Microsoft PowerPoint. Your mission is to transform the real data provided into a clear, persuasive, visually sophisticated presentation that is ready to be produced in PowerPoint.

Before developing the solution, analyze the briefing below. If there are critical gaps, ask up to 8 objective, prioritized questions. If I do not answer, assume explicit, plausible premises and mark them as [PREMISSA A VALIDAR], without inventing results, clients, percentages, or evidence.

DATA AND CONTEXT TO BE PASTED BY THE USER:
- Company, business unit, industry, and desired positioning:
- Presentation audience (leadership, client, committee, investor, sales team, etc.):
- Main objective and expected decision/action at the end:
- Presentation duration and maximum number of slides:
- Success story: initial problem, anonymized client/unit, context, challenge, scope, deadline, team, and constraints:
- Strategy, methodology, implemented solutions, and differentiators:
- Quantitative results (before/after, target/achieved, ROI, savings, revenue, timeline, quality, NPS, SLA, etc.) and data source:
- Qualitative results, learnings, overcome risks, and approved testimonials:
- Project portfolio: name, objective, sponsor, status, priority, budget, timeline, stage, benefits, risks, and dependencies for each project:
- Capacity data, investments, roadmap, prioritization criteria, and governance, if available:
- Visual identity (colors, fonts, logo, templates, tone of voice, and brand restrictions):
- Available materials (spreadsheets, reports, images, screenshots, links, and attachments):

Follow this framework strictly:
1. Define a central thesis in one sentence: what proof of value the audience should retain at the end of the presentation.
2. Create a narrative using the model Context -> Challenge -> Decision/Strategy -> Execution -> Evidence -> Scale/Portfolio -> Next Steps. Avoid treating the case as a mere operational chronology.
3. Select only metrics that support the thesis. For each metric, provide comparison, period, unit, source, and any necessary methodological caveats.
4. Structure the portfolio as a decision-making tool: balance between value, urgency, risk, investment, capacity, and dependencies. Differentiate completed, in-progress, planned, and at-risk projects.
5. Apply executive communication principles: one main idea per slide, conclusive titles (not generic titles), visual hierarchy, objective language, and a clear decision recommendation.

DELIVER THE RESPONSE EXACTLY IN THE FOLLOWING SECTIONS:

A. STRATEGIC SUMMARY: central thesis, audience profile, objective, recommended tone, and 3 key messages.

B. PRESENTATION ARCHITECTURE: table with slide number, conclusive title, slide objective, main message, ready-to-paste text content, recommended visual, required data, and transition to the next slide. Produce between 10 and 16 slides, adjusted to the specified limit. Include, when applicable: cover; agenda; context; challenge; approach; implementation journey; results; visual proof; testimonial; consolidated portfolio view; prioritization matrix; roadmap; risks and governance; call to decision; closing.

C. VISUAL SPECIFICATION FOR POWERPOINT: for each slide, detail layout (16:9 ratio), element distribution, type of chart or diagram, labels, legend, icons, colors, and emphasis rules. Recommend suitable charts, such as waterfall for value creation, before/after for transformation, timeline for execution, bubbles for prioritization, and simplified Gantt for roadmap. Never recommend a chart when a textual message or diagram would be clearer.

D. PORTFOLIO AND GOVERNANCE: deliver a ready-to-fill template table, with columns for project, objective, status, owner, investment, expected benefit, realized benefit, deadline, risk, dependencies, and required decision. Include criteria and a conceptual prioritization formula, for example: Score = (Impact x Strategic Alignment x Urgency) / (Effort x Risk), explaining scales from 1 to 5 and interpretation limits. If sufficient data is available, classify the projects without hiding uncertainties.

E. PRESENTER NOTES: write a 45- to 90-second speaking script for each slide, with opening, data interpretation, and transition sentence. The text should sound natural for a Brazilian executive, without excessive jargon.

F. POWERPOINT PRODUCTION: provide practical instructions for building the slides, including theme setup, slide master, typography standards, margins, alignment, subtle animations, and accessibility. Also create an optional, commented, and safe VBA code to generate the initial slide structure with titles and placeholders. The VBA must work in the desktop PowerPoint, declare variables, avoid external references, and clearly indicate where to insert the final text.

G. QUALITY CONTROL: end with a validation checklist for data, narrative, design, confidentiality, accessibility, and audience fit.

Restrictions: do not use fictitious numbers; mark missing fields as [DADO PENDENTE]; do not present unnecessary confidential information; prioritize clarity over ornamentation; avoid long text blocks, clichés, and unsupported promises. Every title must express a conclusion or actionable insight.

Conteudo completo

Cabecalho, escopo, prompt principal, modulos, agentes

Visao completa do projeto

Success Story and Project Portfolio in PowerPoint

# www.prompthubai.com.br
# Encontre prompts, agentes e workflows testados para vender, programar e automatizar com IA em português.

# Success Story and Project Portfolio in PowerPoint

## Cabecalho
- Tipo: Conteudo
- Categoria: Marketing
- Modulos: 0
- Agentes: 0

## Escopo
This prompt guides the creation of a complete corporate presentation to communicate a success story and position a project portfolio in a strategic way. It turns raw data, indicators, testimonials, schedules, and scope information into a clear, persuasive, and visually consistent executive narrative.

Ideal for PMOs, consultancies, transformation teams, technology, operations, B2B sales, and project leaders who need to report results, win sponsorship, demonstrate delivery capability, or support commercial proposals. The output includes a slide-by-slide outline, ready-to-use content, chart recommendations, presentation notes, and optional VBA automation.

## Prompt Principal
Act as a Strategy Director, PMO, and Corporate Presentation Design expert, specialized in building executive narratives for success stories and project portfolios in Microsoft PowerPoint. Your mission is to transform the real data provided into a clear, persuasive, visually sophisticated presentation that is ready to be produced in PowerPoint.

Before developing the solution, analyze the briefing below. If there are critical gaps, ask up to 8 objective, prioritized questions. If I do not answer, assume explicit, plausible premises and mark them as [PREMISSA A VALIDAR], without inventing results, clients, percentages, or evidence.

DATA AND CONTEXT TO BE PASTED BY THE USER:
- Company, business unit, industry, and desired positioning:
- Presentation audience (leadership, client, committee, investor, sales team, etc.):
- Main objective and expected decision/action at the end:
- Presentation duration and maximum number of slides:
- Success story: initial problem, anonymized client/unit, context, challenge, scope, deadline, team, and constraints:
- Strategy, methodology, implemented solutions, and differentiators:
- Quantitative results (before/after, target/achieved, ROI, savings, revenue, timeline, quality, NPS, SLA, etc.) and data source:
- Qualitative results, learnings, overcome risks, and approved testimonials:
- Project portfolio: name, objective, sponsor, status, priority, budget, timeline, stage, benefits, risks, and dependencies for each project:
- Capacity data, investments, roadmap, prioritization criteria, and governance, if available:
- Visual identity (colors, fonts, logo, templates, tone of voice, and brand restrictions):
- Available materials (spreadsheets, reports, images, screenshots, links, and attachments):

Follow this framework strictly:
1. Define a central thesis in one sentence: what proof of value the audience should retain at the end of the presentation.
2. Create a narrative using the model Context -> Challenge -> Decision/Strategy -> Execution -> Evidence -> Scale/Portfolio -> Next Steps. Avoid treating the case as a mere operational chronology.
3. Select only metrics that support the thesis. For each metric, provide comparison, period, unit, source, and any necessary methodological caveats.
4. Structure the portfolio as a decision-making tool: balance between value, urgency, risk, investment, capacity, and dependencies. Differentiate completed, in-progress, planned, and at-risk projects.
5. Apply executive communication principles: one main idea per slide, conclusive titles (not generic titles), visual hierarchy, objective language, and a clear decision recommendation.

DELIVER THE RESPONSE EXACTLY IN THE FOLLOWING SECTIONS:

A. STRATEGIC SUMMARY: central thesis, audience profile, objective, recommended tone, and 3 key messages.

B. PRESENTATION ARCHITECTURE: table with slide number, conclusive title, slide objective, main message, ready-to-paste text content, recommended visual, required data, and transition to the next slide. Produce between 10 and 16 slides, adjusted to the specified limit. Include, when applicable: cover; agenda; context; challenge; approach; implementation journey; results; visual proof; testimonial; consolidated portfolio view; prioritization matrix; roadmap; risks and governance; call to decision; closing.

C. VISUAL SPECIFICATION FOR POWERPOINT: for each slide, detail layout (16:9 ratio), element distribution, type of chart or diagram, labels, legend, icons, colors, and emphasis rules. Recommend suitable charts, such as waterfall for value creation, before/after for transformation, timeline for execution, bubbles for prioritization, and simplified Gantt for roadmap. Never recommend a chart when a textual message or diagram would be clearer.

D. PORTFOLIO AND GOVERNANCE: deliver a ready-to-fill template table, with columns for project, objective, status, owner, investment, expected benefit, realized benefit, deadline, risk, dependencies, and required decision. Include criteria and a conceptual prioritization formula, for example: Score = (Impact x Strategic Alignment x Urgency) / (Effort x Risk), explaining scales from 1 to 5 and interpretation limits. If sufficient data is available, classify the projects without hiding uncertainties.

E. PRESENTER NOTES: write a 45- to 90-second speaking script for each slide, with opening, data interpretation, and transition sentence. The text should sound natural for a Brazilian executive, without excessive jargon.

F. POWERPOINT PRODUCTION: provide practical instructions for building the slides, including theme setup, slide master, typography standards, margins, alignment, subtle animations, and accessibility. Also create an optional, commented, and safe VBA code to generate the initial slide structure with titles and placeholders. The VBA must work in the desktop PowerPoint, declare variables, avoid external references, and clearly indicate where to insert the final text.

G. QUALITY CONTROL: end with a validation checklist for data, narrative, design, confidentiality, accessibility, and audience fit.

Restrictions: do not use fictitious numbers; mark missing fields as [DADO PENDENTE]; do not present unnecessary confidential information; prioritize clarity over ornamentation; avoid long text blocks, clichés, and unsupported promises. Every title must express a conclusion or actionable insight.

Todos os modulos

0 modulos deste projeto

Todos os agentes

0 agentes deste projeto

Prompts Relacionados

test 123
Marketing ChatGPT
Operational prompt Ideal for Teams putting AI to work

test 123

Faster delivery with real context

turn a photo into a drawing

Saves: less trial and error Includes: prompt + context Ready to adapt
Framework: Content Partnership Plan
Marketing Gemini
Operational prompt Ideal for Teams putting AI to work

Framework: Content Partnership Plan

Faster delivery with real context

A partnership framework for working with a creator or complementary company. Structured prompt with steps, output format…

Saves: less trial and error Includes: prompt + context Ready to adapt
Email Funnel Auditor Workflow
Marketing ChatGPT
Operational prompt Ideal for Teams putting AI to work

Email Funnel Auditor Workflow

Faster delivery with real context

Review an email sequence and pinpoint where people drop off. A structured prompt with steps, output format, and quality …

Saves: less trial and error Includes: prompt + context Ready to adapt
Critique: Sales FAQ Generator
Marketing Claude
Operational prompt Ideal for B2B Sales

Critique: Sales FAQ Generator

Prospecting, qualification and follow-up

Anticipate a purchase objection in a question-and-answer format. Structured prompt with steps, output format, and qualit…

Saves: 2h per campaign Includes: prompt + process Ready to adapt