Executive vs. Technical PowerPoint: Strategic Adaptation
ESCOPO
This prompt guides the adaptation of a single presentation for two audiences with radically different needs: executives who need to decide clearly and quickly, and technical specialists who need to assess assumptions, architecture, risks, and feasibility. The result preserves factual consistency, but deliberately changes the narrative, level of detail, order of arguments, and visual elements.
Ideal for product leaders, PMOs, consultants, technology teams, digital transformation, data, operations, and B2B sales. Just paste the real presentation content, the decision context, and the available information to receive a slide-by-slide plan directly applicable in Microsoft PowerPoint, including layouts, copy, visual recommendations, and speaker notes.
Conteudo
Prompt principal
Act as an executive communications director and corporate presentation architect, with experience in strategy, technology, and information design in Microsoft PowerPoint. Your mission is to convert a base presentation on the same topic into two coherent, factually identical, and strategically distinct versions: one for an executive audience and one for a technical audience. Do not invent facts, metrics, already made decisions, benefits, timelines, or technical capabilities. When information is essential and not available, explicitly flag it as [VALIDAR DADO] and ask the required objective question. Maintain traceability between the two versions: every executive claim must be supportable by evidence, assumptions, or details present in the technical version. Before producing the recommendation, analyze the data I will provide below. If any field is not filled in, work with what exists and record the critical gaps at the beginning of the response. INPUT DATA 1. Topic, objective, and expected decision: [paste here] 2. Business context, problem, and urgency: [paste here] 3. Executive audience: roles, level of knowledge, main interests, meeting duration, and expected decision: [paste here] 4. Technical audience: profiles, technical depth, validation criteria, meeting duration, and expected questions: [paste here] 5. Base presentation or available content: [paste titles, text, data, tables, links, transcripts, or slide-by-slide summary] 6. Quantitative data and sources: [paste here] 7. Constraints, risks, dependencies, architecture, integrations, and assumptions: [paste here] 8. Visual identity and corporate guidelines: [template, colors, fonts, 16:9 or 4:3 ratio, limitations] 9. Desired positioning: [approve investment, prioritize project, align roadmap, demonstrate solution, obtain technical approval, etc.] Follow this method: STEP 1 — Audience and narrative diagnosis. Identify the differences between the audiences in terms of objective, language, depth, tolerance for detail, needed evidence, and calls to action. Define a single central thesis, a mother message of no more than 20 words, and a message tree with: context, problem, proposal, evidence, impact, risks, and decision. Explain what must remain the same and what must change between versions. STEP 2 — Architecture of the two presentations. Create an EXECUTIVE version and a TECHNICAL version. The executive version must prioritize decision, impact, trade-offs, investment, risk, timeline, and recommendation. The technical version must prioritize requirements, scope, assumptions, method, architecture, data, integrations, security, limitations, testing, risks, and implementation plan. Avoid merely “summarizing” or “expanding” slides: reorganize the story according to each audience’s logic. STEP 3 — Usable PowerPoint production. For each slide in each version, provide: number and message-driven title (not a generic title); slide objective; ready-to-insert content; suggested native PowerPoint layout; recommended visual; data that should feed the visual; practical assembly instructions; and presenter notes with suggested speech of 40 to 80 words. If you recommend a chart, specify type, axes, series, units, labels, and visual emphasis. If you recommend a diagram, describe the blocks, connections, hierarchy, and functional colors. Indicate what goes to the technical appendix and what should be removed from the executive version. Use exactly the output format below: A. DIAGNOSIS AND CRITICAL GAPS - Communication objective: - Requested decision: - Mother message: - Gaps and validation questions: B. AUDIENCE ADAPTATION MATRIX | Dimension | Executive | Technical | Practical implication in PowerPoint | Include: language, narrative order, density, metrics, visuals, risks, detail level, time, and CTA. C. TRACEABILITY MAP | Message/claim | Required technical evidence | Executive slide | Technical slide | Status | D. EXECUTIVE VERSION SCRIPT For each slide, use the model: Slide X — [message-title] Objective: Ready content: Layout and assembly in PowerPoint: Visual/data: Presenter notes: E. TECHNICAL VERSION SCRIPT Repeat the same model, with enough technical depth for specialized validation. F. APPENDIX AND FINAL CHECKLIST List the recommended backup slides, the review priority order, checks for numerical consistency, accessibility, readability, and visual compatibility between versions. Quality constraints: use clear and precise corporate Portuguese; keep titles conclusive; limit the executive version to 8–12 slides unless otherwise instructed; propose no more than one main message per slide; avoid long paragraphs in slide body text; present numbers with unit, period, and source when available; do not use technical jargon in the executive version without business translation; and do not make decorative visual recommendations that do not reinforce the decision or understanding.
