Multi-Workspace Executive Brief and Deck Builder

The Prompt

You are an executive communications strategist. Build a decision-ready brief and slide deck outline from connected workspace sources.

REVIEW PERIOD:
{{review_period}}

BUSINESS OBJECTIVES:
{{business_objectives}}

DATA SOURCES (connectors):
{{data_sources}}

AUDIENCE:
{{audience}}

DECISION SCOPE:
{{decision_scope}}

FORMAT PREFERENCES:
{{format_preferences}}

GOVERNANCE CONSTRAINTS:
{{governance_constraints}}

Return exactly these sections:

1) Executive Brief (2-4 pages equivalent)
- Top outcomes vs objectives.
- Risks, blockers, and opportunities.
- Recommended decisions for this review cycle.

2) Evidence Map
- Table columns: statement_id, statement, source, freshness, confidence, owner.

3) Deck Blueprint (10-15 slides)
- For each slide: title, key message, supporting evidence, visual suggestion, speaker note.

4) Decision Log Draft
- Table columns: decision_id, recommendation, rationale, owner_role, due_date, status (proposed).

5) Action Register Draft (PROPOSED_ONLY)
- Table columns: action_id, task, destination_system, priority, owner_role, due_date, dependency.

6) Output Packaging Plan
- Google Workspace output steps (Docs/Slides).
- Microsoft 365 output steps (Word/PowerPoint).

Rules:
- Distinguish verified facts from assumptions.
- Cite source references for every high-impact claim.
- Mark any stale data sections as LOW_CONFIDENCE.
- Keep all system writes in draft/proposed state pending human approval.

When to Use

Use this for weekly or monthly executive updates where you need a consistent narrative and slide structure from multiple knowledge systems (for example, Drive/OneDrive docs, Jira/Confluence status, and Notion planning notes).

This is especially useful for cross-functional leadership reviews where preparation time is tight and evidence quality must remain high.

Variables

Variable	What to provide	Example
review_period	Time period covered by the report	”February 2026 monthly business review”
business_objectives	Goals to evaluate against	”Ship release X, improve retention by 2pp, reduce support backlog 20%“
data_sources	Connected systems and key source paths	”Jira board CORE, Confluence product updates, Drive strategy deck, OneDrive finance model”
audience	Specific stakeholder group	”CEO, CFO, VP Product, VP Engineering”
decision_scope	Decisions expected in this review	”Resourcing tradeoffs, launch sequencing, budget reallocations”
format_preferences	Voice, length, and output style	”Crisp, evidence-first, no jargon, 12-slide max”
governance_constraints	Policy constraints to respect	”No customer-level data in slides, legal review for claims on contracts”

Tips & Variations

• Ask for a “board-ready version” and “team-operational version” in one run.
• Add explicit chart preferences (line, waterfall, stacked bar) for each metric type.
• For recurring reporting, lock the same section order each cycle to improve comparability.
• Ask for a “red-team critique” section to stress-test weak recommendations.

Example Output

A strong response includes a concise evidence-backed brief, slide-by-slide deck blueprint with speaker notes, and a draft decision/action register ready for stakeholder review and approval.