# Presentation Pack: Q1 All-Hands Update --- ## 1) Presentation Brief **Title:** Q1 All-Hands: What We Shipped, What's Next, and Where We Need Help **Date / deadline:** [INSERT date of all-hands] **Type + setting:** All-hands company meeting; Zoom (or hybrid, confirm logistics) **Time limit:** 7 minutes (talk) + optional 3-minute live Q&A at end **Audience:** Entire company -- engineering, product, design, sales, marketing, support, operations, leadership. No single decision-maker; the audience is cross-functional peers and leaders. **Outcome:** Inform + align. The company should leave understanding what the team delivered, why it matters, and what specific cross-team help is needed next quarter. **Ask (one sentence):** "We need three things from other teams this quarter: [prioritized engineering support / design capacity / GTM partnership] -- I'll share the specific asks and owners at the end." **Why now:** End of quarter is the natural moment to show progress, celebrate wins, recalibrate priorities, and unblock dependencies before Q2 starts. **Constraints:** - 7 minutes strict (all-hands slots are tight; assume a hard stop). - Company-wide audience means no deep jargon -- keep metrics simple and outcomes concrete. - Sensitive details: avoid naming unreleased customer deals or unannounced pricing changes unless cleared. - Level of polish: medium-high. This is a visible slot; slides should be clean but don't need agency-level design. **Source materials:** User's bullets and metrics (to be pasted/provided). Assumed to include: shipped features, adoption/usage numbers, revenue or pipeline impact, and a short list of cross-team dependencies. **Assumptions (labeled):** - [ASSUMPTION] The talk will be over Zoom (or hybrid). Adjust logistics if purely in-person. - [ASSUMPTION] Q&A will be 3 minutes at the end, not inline. - [ASSUMPTION] The user has 3-5 bullet points of shipped items, 2-3 key metrics, and a short list of asks from other teams. - [ASSUMPTION] No single executive approval is needed; the "ask" is cross-team support/commitment, not a formal decision. --- ## 2) Narrative Outline (Contrast Spine) **Core message (one sentence):** We shipped meaningful work in Q1 that is already moving key metrics -- and if we get targeted help from [2-3 teams], Q2 will be significantly stronger. ### Contrast Table | What Is (Current Reality -- Q1) | What Could Be (Better Future -- Q2) | |---|---| | We shipped [X features / initiatives] and moved [metric] from A to B. The team executed well under tight constraints. | With the right cross-team support, we can accelerate [outcome] and hit [target] by end of Q2 -- a step-change from where we are today. | | We ran into [specific dependency blocker] that slowed us by ~[N weeks]. We found workarounds but they aren't sustainable. | If [Team X] can allocate [specific resource/capacity], we remove the bottleneck and unlock [quantified benefit] for the company. | | Adoption of [feature] is at [current %]; early signal is strong but we're under-investing in [distribution / enablement / integration]. | With [GTM / support / eng partnership], we project [target adoption %] and [downstream revenue / retention impact]. | **Key supporting points (3):** 1. **What we shipped** -- Concrete list of deliverables with one headline metric each. 2. **What's working and what's not** -- Honest signal on adoption, feedback, or blockers. 3. **What we need** -- Specific, named asks from specific teams with clear "what success looks like." **Proof/evidence per point:** - Point 1: Shipped features list + headline metric (e.g., "Feature X launched; DAU up 18%"). - Point 2: Adoption curve or user feedback signal; one concrete blocker story. - Point 3: Named dependency + estimated impact if resolved vs. not resolved. **Call to action (the ask):** "Here are three specific things we need from other teams. I'll share owners and next steps at the end -- please flag me in Slack if you can help or have questions." --- ## 3) Slide-by-Slide Outline + Talk Track **Total time: 7 minutes (420 seconds). Buffer target: ~380 seconds of content + 40 seconds of transitions.** --- ### Slide 1: Title + Framing (20 sec) - **Takeaway:** This is a quick update on Q1 progress and a specific request for Q2 help. - **Key points:** - Team name + "Q1 Update" - One-line framing: "What we shipped, what's next, what we need." - **Evidence / example:** None needed; this is the opener. - **Visual idea:** Clean title slide with team name, quarter, and three words: Shipped / Next / Help. - **Speaker notes:** - "Hey everyone -- [Name], [Team]. Quick 7-minute update: what we shipped in Q1, what's coming in Q2, and three specific asks where we need your help." - **Time budget: 20 sec** --- ### Slide 2: What We Set Out to Do (30 sec) - **Takeaway:** Remind the audience of the Q1 goals so they can judge progress. - **Key points:** - 2-3 bullet recap of the Q1 goals/bets the team committed to. - Frame as: "At the start of Q1, we said we'd do X, Y, Z." - **Evidence / example:** Reference the Q1 planning doc or OKRs. - **Visual idea:** Simple checklist or 3-column layout showing the goals. - **Speaker notes:** - "Quick context: at the start of Q1, we committed to three things: [Goal 1], [Goal 2], [Goal 3]. Here's how we did." - **Time budget: 30 sec** --- ### Slide 3: What We Shipped (Wins) (70 sec) - **Takeaway:** We delivered real outcomes, not just outputs -- here are the highlights with metrics. - **Key points:** - Feature/initiative 1 + headline metric - Feature/initiative 2 + headline metric - Feature/initiative 3 + headline metric (if applicable) - **Evidence / example:** DAU lift, conversion improvement, customer feedback quote, time saved, etc. One metric per item. - **Visual idea:** 3 cards or rows, each with a short title + one bold metric. Keep text minimal. - **Speaker notes:** - "First: [Feature 1]. We launched it [date] and it's already [metric]. Second: [Feature 2] -- [metric]. Third: [Feature 3] -- [metric]. The team moved fast and I want to call out [name/subteam] for [specific contribution]." - Pause after the metrics to let them land. - **Time budget: 70 sec** --- ### Slide 4: What We Learned (Honest Signal) (60 sec) - **Takeaway:** We have strong early signal, but also honest gaps -- here's what's working and what isn't. - **Key points:** - What's working: adoption trend, user feedback, or retention signal. - What's not working or slower than expected: specific gap (adoption plateau, integration friction, support load). - One concrete example or story that illustrates the gap. - **Evidence / example:** Adoption chart (trend line), a short customer/user quote, or a support ticket pattern. - **Visual idea:** Simple before/after or trend chart. Or a two-column "Working / Not Yet" layout. - **Speaker notes:** - "[Feature X] adoption is at [current %], which is [above/below] target. The main friction is [specific issue]. For example, [one concrete story]. This leads to what we need next." - This is the "what is" tension moment -- be honest, not defensive. - **Time budget: 60 sec** --- ### Slide 5: What's Next in Q2 (60 sec) - **Takeaway:** Our Q2 plan builds on Q1 momentum and addresses the gaps we just showed. - **Key points:** - 2-3 Q2 priorities (tied back to the gaps from Slide 4). - Target outcomes (specific numbers or milestones, not vague goals). - What we are NOT doing (one line -- shows focus). - **Evidence / example:** Projected metrics or milestones (e.g., "Target: [metric] from X to Y by end of Q2"). - **Visual idea:** Short priority list with target metrics next to each. Bold the targets. - **Speaker notes:** - "For Q2, we're focused on three things. First: [Priority 1] -- target is [metric]. Second: [Priority 2] -- we're aiming for [outcome]. Third: [Priority 3]. We're explicitly NOT doing [thing] this quarter so we can stay focused." - This is the "what could be" moment -- paint the upside clearly. - **Time budget: 60 sec** --- ### Slide 6: Where We Need Help (The Asks) (80 sec) - **Takeaway:** We have three specific, named asks from other teams -- here they are, with why they matter. - **Key points:** - Ask 1: [Team] + what we need + why it matters + impact if we get it vs. don't. - Ask 2: [Team] + what we need + why it matters. - Ask 3: [Team] + what we need + why it matters. - **Evidence / example:** Quantify impact where possible ("If [Team X] can give us [resource], we project [outcome] vs. [risk if not]"). - **Visual idea:** Three rows: Team | Ask | Impact. Clean table or card layout. Highlight the team names. - **Speaker notes:** - "Here's where we need your help -- and I want to be specific. Ask 1: [Team], we need [specific thing]. If we get this, [impact]. If we don't, [consequence]. Ask 2: [Team], [thing], [impact]. Ask 3: [Team], [thing], [impact]. I'll follow up with each team lead directly this week." - Slow down here. Look at the camera. This is the core ask -- make eye contact (or camera contact on Zoom). - **Time budget: 80 sec** --- ### Slide 7: Recap + Next Steps (40 sec) - **Takeaway:** Reinforce the three asks and make it easy to follow up. - **Key points:** - One-line summary: "Shipped [X], targeting [Y], need help on [Z]." - Repeat the three asks as a simple list. - Next step: "I'll follow up with [team leads] this week. Drop me a note in [Slack channel] if you have questions." - **Evidence / example:** None -- this is the close. - **Visual idea:** Three-line recap list. Contact info / Slack channel at the bottom. - **Speaker notes:** - "To recap: Q1 was strong -- [headline metric]. Q2 is about [one-line focus]. The three things we need: [Ask 1], [Ask 2], [Ask 3]. I'll reach out to each team directly. If you have ideas or questions, hit me up in [#channel]. Thanks." - End cleanly. Don't trail off. Pause, then say "Thanks" and stop. - **Time budget: 40 sec** --- ### Slide 8 (Optional): Appendix / Backup Detail - **Takeaway:** Supporting data for anyone who wants to dig deeper (not presented live). - **Key points:** - Detailed metrics table. - Full Q2 roadmap or timeline. - Links to relevant docs. - **Evidence / example:** Metrics dashboard screenshot, roadmap Gantt, or doc links. - **Visual idea:** Dense is OK here -- this is reference material, not a live slide. - **Speaker notes:** - Not presented. Reference in Q&A if someone asks for detail: "Great question -- there's an appendix slide with the full breakdown; I'll share the deck after." - **Time budget: 0 sec (backup only)** --- **Time Check:** | Slide | Seconds | Cumulative | |---|---|---| | 1 - Title | 20 | 20 | | 2 - Q1 Goals | 30 | 50 | | 3 - What We Shipped | 70 | 120 | | 4 - What We Learned | 60 | 180 | | 5 - What's Next | 60 | 240 | | 6 - Where We Need Help | 80 | 320 | | 7 - Recap + Next Steps | 40 | 360 | | **Total** | **360 sec (6:00)** | Buffer: 60 sec (14%) | Buffer of ~60 seconds (14%) for transitions, natural pauses, and slight overruns. Well within the 7-minute slot. --- ## 4) Q&A / Objection Bank **Top 10 Questions (Prioritized by Likelihood and Risk)** **1) "Why should my team prioritize your ask over our own roadmap?"** - **Short answer:** We're not asking for a major roadmap change -- the asks are scoped and time-boxed. We've estimated [N days/weeks] of effort, and the company-level impact is [quantified benefit]. - **Proof:** Impact estimate + executive alignment on the priority (if available). - **If pressed:** "Happy to walk through the scoping with your team lead this week to make sure it fits." - **Fallback:** "Let me send you the scoped request doc by [DATE] so you can assess fit." **2) "These metrics look good, but are they sustainable or just a launch bump?"** - **Short answer:** Fair question. We're seeing [X-week] retention signal, not just a launch spike. [Specific retention or trend data point]. - **Proof:** Cohort data or week-over-week trend. - **If pressed:** "We're tracking [leading indicator] weekly; happy to share the dashboard." - **Fallback:** "I'll share the retention cohort data by [DATE]." **3) "What happens if we don't get the cross-team help you're asking for?"** - **Short answer:** We'll still make progress, but at a slower pace. Specifically, [Ask 1] would mean [consequence -- e.g., 'we'd miss the Q2 target by ~X%']. We'd need to find workarounds that cost more time. - **Proof:** Estimated impact delta (with vs. without support). - **If pressed:** "I can share the risk scenario in detail -- the short version is it's the difference between [outcome A] and [outcome B]." - **Fallback:** "Let me document the trade-off for leadership review." **4) "How does this connect to the company's top priorities / OKRs?"** - **Short answer:** [Priority 1] maps directly to [Company OKR X]. [Priority 2] supports [Company Goal Y]. We've aligned with [exec sponsor] on this. - **Proof:** Reference the company OKR doc or exec sponsor's stated priorities. - **If pressed:** Offer to share the alignment mapping. - **Fallback:** "I'll confirm the OKR mapping with [exec] and share it in the follow-up." **5) "You mentioned [feature] adoption is below target -- what's the plan to fix that?"** - **Short answer:** That's our top Q2 priority. The plan is [specific action -- e.g., 'improve onboarding flow + partner with Support on enablement']. Target: [metric] by [date]. - **Proof:** The Q2 plan from Slide 5. - **If pressed:** Walk through the specific levers and who owns each. - **Fallback:** "Happy to share the detailed adoption playbook after the meeting." **6) "Can you break down the metric by segment / region / team?"** - **Short answer:** Yes -- the headline number is [X], and the breakdown by [segment] is [summary]. The appendix slide has the full table. - **Proof:** Appendix slide (Slide 8). - **If pressed:** "I'll pull the segmented view and share it in [Slack channel]." - **Fallback:** "Give me until [DATE] to pull the segmented data." **7) "What didn't you ship that was planned? What got cut?"** - **Short answer:** We deprioritized [item] because [reason -- e.g., 'scope was larger than estimated' or 'dependency shifted']. It's on the Q2 backlog as [priority level]. - **Proof:** Reference the Q1 plan (Slide 2) for the original list. - **If pressed:** Be honest about what was cut and why; don't spin. - **Fallback:** "I can share the full prioritization rationale in the follow-up doc." **8) "Is the team properly staffed for Q2, or do you need headcount?"** - **Short answer:** Current team can deliver the plan if we get the cross-team support on Slide 6. We're not requesting new headcount right now -- the asks are about collaboration, not hiring. - **Proof:** Scoped asks on Slide 6. - **If pressed:** "If circumstances change, I'll flag it early. For now, the plan is achievable with current team + the asks I outlined." - **Fallback:** "I'll flag any staffing risks to [manager/exec] proactively." **9) "How are you measuring success for Q2?"** - **Short answer:** [2-3 specific metrics with targets]. We'll share progress at the mid-quarter check-in and the Q2 all-hands. - **Proof:** Slide 5 targets. - **If pressed:** Offer to share the metrics dashboard or weekly update cadence. - **Fallback:** "I'll share the full scorecard by [DATE]." **10) "Can we get a copy of the deck / data?"** - **Short answer:** Absolutely. I'll share the deck in [Slack channel / email] after the all-hands. The appendix has the detailed data. - **Proof:** N/A. - **If pressed:** N/A. - **Fallback:** Share within 24 hours. --- ## 5) Stakeholder Pre-Brief Plan **Goal:** Surface concerns before the all-hands, ensure no team lead is surprised by a public ask, and refine the asks based on feedback. | Stakeholder | Role / Influence | Likely Concern | Pre-Brief Goal | What You'll Ask Them For | Notes | |---|---|---|---|---|---| | Your direct manager / exec sponsor | Approver of the narrative and asks | Messaging alignment; whether asks are politically viable | Confirm the framing, metrics, and asks are endorsed | Green light on the three asks + feedback on tone | Brief early (2-3 days before). Adjust framing based on feedback. | | Team Lead -- Ask 1 target team | Owner of the team you're asking for help | Capacity constraints; whether the ask is reasonable | Give them a heads-up so they aren't surprised; get a sense of feasibility | Honest reaction: "Is this doable? What would you need from us to make it work?" | If they push back, revise the ask scope before the all-hands. | | Team Lead -- Ask 2 target team | Owner of the team you're asking for help | Competing priorities; timeline conflict | Same as above | Same as above | If you have 3 asks, pre-brief all 3 team leads. | | Team Lead -- Ask 3 target team | Owner of the team you're asking for help | Scope clarity; who owns what | Same as above | Same as above | Brief in person or over a quick 10-min call, not just Slack. | | [Optional] CEO / Head of Product | Sets company priorities | Whether your Q2 plan aligns with top-level strategy | Confirm strategic alignment; get a signal on priority level | "Does this align with your priorities? Anything I should reframe?" | Only if the all-hands is high-visibility or the asks are large. | **Change Log (after pre-briefs)** - Changed: [To be filled after pre-brief conversations -- e.g., "Revised Ask 2 scope from 'full integration' to 'API endpoint only' based on Team B lead feedback."] - Kept: [Items that were validated -- e.g., "Metrics framing confirmed by exec sponsor."] - Open questions: [Items still unresolved -- e.g., "Team C capacity not confirmed yet; will follow up by [DATE]."] --- ## 6) Rehearsal + Delivery Plan **Timeline:** - **Day -3:** Finalize slide content and speaker notes. Pre-briefs complete. - **Day -2:** Visualization + Timed Run #1. Record and review. - **Day -1:** Timed Run #2 + Hard-Mode Q&A role-play. Final adjustments. - **Day 0:** Logistics check 30 min before. Deliver. **Rehearsal Plan (minimum)** 1. **Visualization (Day -2, 10 min):** - Close your eyes. Walk through the entire talk from "Hey everyone" to "Thanks." - Visualize the Zoom grid (or room). Imagine clicking through each slide. Notice where you feel uncertain -- those are the spots to rehearse more. 2. **Timed Run #1 (Day -2, 10 min):** - Speak the full talk out loud (not in your head). Use the speaker notes as a guide but don't read them verbatim. - Time it. Target: 6:00-6:30 (leaving buffer). - Note: if you run over 6:30, cut content -- don't speed up. 3. **Record + Review (Day -2, 10 min):** - Record Timed Run #1 on your phone or Zoom. - Watch it once. Look for: filler words ("um", "so"), reading slides, rushing through the asks, flat energy on the wins. - Pick 1-2 specific things to fix. Don't try to fix everything. 4. **Timed Run #2 (Day -1, 10 min):** - Incorporate the fixes. Time it again. Target: 5:45-6:15. - If it's clean and within time, you're ready. 5. **Hard-Mode Q&A Role-Play (Day -1, 10 min):** - Ask a colleague (or do it solo) to throw the hardest 5 questions from the Q&A bank. - Practice answering each in under 40 seconds. If you ramble, tighten the answer. **Delivery Cues** - **Pauses:** - After the headline metric on Slide 3 (let the number land). - Before the asks on Slide 6 ("Here's where we need your help" -- pause 2 beats). - After the final "Thanks" (don't rush off; hold for a beat). - **"Think Up" Reminder:** - On Zoom: when thinking or transitioning, look up (not down at notes). This projects confidence and avoids the "reading" look. - Tape a small note above your camera: "LOOK UP." - **Speed:** - Target pace: slightly slower than feels natural. All-hands energy tends to make people rush. - If you feel yourself speeding up on the asks (Slide 6), consciously slow down -- the asks are the most important part. - **Energy:** - Wins (Slide 3): bring genuine enthusiasm. Smile. Call out specific people. - Honest gaps (Slide 4): be matter-of-fact, not defensive. Lean into candor. - Asks (Slide 6): be direct and specific. Don't hedge. **Logistics** - **Zoom:** - Camera on, good lighting (face the window or use a ring light). - Wired internet if possible; have phone hotspot as backup. - Screen share: test before the meeting. Have slides open and ready. - Mute notifications. Close Slack/email. - Gallery view on a second monitor so you can see faces. - **In-person (if applicable):** - Visit the room beforehand. Test the projector/screen. - Bring your own adapter (USB-C to HDMI) and clicker. - Have a backup: slides on your laptop screen + PDF on a USB drive. --- ## 7) Risks / Open Questions / Next Steps ### Risks 1. **Metrics not finalized.** If the user's bullet metrics aren't locked by slide-creation time, the talk will feel vague. Mitigate: lock all numbers 48 hours before. 2. **Cross-team asks may land poorly if not pre-briefed.** A public ask that surprises a team lead can create friction. Mitigate: complete all pre-briefs by Day -2. 3. **7 minutes is tight.** Any tangent or slow start eats into the asks. Mitigate: rehearse to 6:00 target, not 7:00. The buffer absorbs natural overrun. 4. **Zoom fatigue / attention drift.** All-hands audiences tune out fast. Mitigate: open with a concrete win/number, not a preamble. Keep slides visual, not text-heavy. ### Open Questions 1. What specific metrics does the user want to highlight? (Need the actual bullets and numbers to finalize Slides 3-5.) 2. Which three teams are the cross-team asks directed to? (Need names + scoped requests for Slide 6.) 3. Is there a sensitive topic to avoid (e.g., layoffs, unreleased pricing, specific customers)? 4. Will there be live Q&A at the end, or should questions go to Slack/async? 5. Who is the exec sponsor / direct manager who should pre-approve the narrative? ### Next Steps 1. **User provides:** final bullets, metrics, and the three specific cross-team asks. 2. **Finalize slides:** Populate Slides 3-6 with real content. Cut anything that doesn't fit the 6:00 target. 3. **Pre-brief target team leads:** Schedule 10-minute conversations by Day -3. 4. **Rehearse:** Follow the rehearsal plan (Day -2 and Day -1). 5. **Logistics check:** Confirm Zoom/room setup, screen share, and backup plan 30 minutes before. 6. **Deliver.** Then share the deck + appendix in [Slack channel] within 24 hours. --- ## Quality Gate: Checklist + Rubric Scores ### Checklist Pass/Fail | Checklist | Status | |---|---| | 1) Brief + ask | PASS -- Ask is explicit ("three specific things from other teams"); audience and outcome defined. | | 2) Narrative (contrast) | PASS -- "What is" (Q1 results + honest gaps) vs "what could be" (Q2 outcomes with support). Concrete, not vague. | | 3) Slides + talk track | PASS -- 7 slides, 1 takeaway each, talk track in bullets, 6:00 content with 60-sec buffer. | | 4) Q&A + objection | PASS -- 10 questions with short answers, proof, and fallbacks. | | 5) De-risking (pre-brief) | PASS -- Pre-brief plan targets all ask-receiving team leads + exec sponsor. Change log template ready. | | 6) Rehearsal + delivery | PASS -- 4-day plan with visualization, 2 timed runs, record/review, Q&A role-play, and delivery cues. | ### Rubric Scores (0-2 each) | Dimension | Score | Rationale | |---|---|---| | 1) Objective + ask clarity | 2 | Ask is stated early (Slide 1), developed (Slide 6), and reinforced at close (Slide 7). Audience can repeat it. | | 2) Audience fit | 2 | Tailored for whole-company: no deep jargon, metrics are simple, asks are cross-functional. Acknowledges different team perspectives in Q&A bank. | | 3) Narrative + contrast strength | 2 | Concrete contrast: Q1 results + honest gaps vs Q2 outcomes with support. Evidenced with metrics. Emotionally grounded in candor + ambition. | | 4) Slide clarity + structure | 2 | 7 slides, single takeaway each, clean flow (Context > Wins > Signal > Plan > Ask > Recap). 14% time buffer. | | 5) Proof and credibility | 1 | Structure calls for metrics and evidence at every point, but actual numbers are placeholder until user provides them. Labeled as assumptions. | | 6) De-risking (pre-brief + alignment) | 2 | Pre-brief plan covers all ask-receiving team leads and exec sponsor. Change log template included. | | 7) Delivery readiness | 2 | Full rehearsal plan: visualization, 2 timed runs, record/review, Q&A role-play, delivery cues (pauses, "think up", pacing). | **Total: 13/14** -- Passes the >= 10/14 bar. The one area to strengthen (Proof, scored 1) depends on the user providing final metrics and data. Once real numbers are plugged in, this dimension should reach 2/2. --- *End of Presentation Pack.*