WorkflowFor DevelopersTech Communication & Leadership

Engineering All-Hands Presentation.

Before any significant all-hands or large-audience engineering communication.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
engineering-all-hands-presentation-4.md Β· 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Tech Communication & Leadership
- Use case: Engineering All-Hands Presentation
- Source task:
  - Help me prepare an engineering all-hands presentation for {{describe_audience_whole_engineering_org_specific_team_cross_func}}. Duration: {{time}}. Key messages: {{list_2_3_things_to_communicate_roadmap_update_culture_change_new}}.
  - Step 1: presentation narrative arc (how the messages connect into a story).
  - Step 2: slide structure with speaker notes for each slide.
  - Step 3: how to make announcements that might cause anxiety (layoffs, reorg, difficult priorities) with honesty and care.
  - Step 4: Q&A preparation : the 5 hardest questions to prepare for.

# Goal
Narrative arc, slide guide with speaker notes, difficult announcement framing, and top-5 Q&A preparation.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Narrative arc, slide guide with speaker notes, difficult announcement framing, and top-5 Q&A preparation.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleengineering communications advisor
{{use_case}}Your specific valueengineering all-hands presentation
{{describe_audience_whole_engineering_org_specific_team_cross_func}}Describe audience whole engineering org specific team cross funcwhole engineering org
{{time}}Time10:00 AM IST
{{list_2_3_things_to_communicate_roadmap_update_culture_change_new}}List 2 3 things to communicate roadmap update culture change newculture change

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

Before any significant all-hands or large-audience engineering communication.

PRO TIP

People remember how an all-hands made them feel, not the specific words β€” make sure the emotional experience matches the intended message.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’