Video summary
How to Create a Winning Deck for a High School Case Competition? | HSACC
Main summary
Key takeaways
Workshop Summary: Building a Winning Case-Competition Deck
The workshop’s central message: make the recommendation easy to understand, support it with evidence, address its risks, and show how to execute it. Judges skim quickly, so each slide should communicate one clear point.
Recommended Presentation Playbook
- Answer: State the recommendation upfront in the executive-summary slide.
- Argument: Explain why the recommendation is appropriate.
- Evidence: Use relevant data and calculations to substantiate the argument.
- Trade-offs: Acknowledge counterarguments, risks, and unintended consequences, and explain how to manage them.
- Action plan: Translate the recommendation into specific steps and a timeline.
Compare alternatives—such as closing stores, fixing them, or using a mix—rather than relying on an initial gut reaction. A blended recommendation may be stronger when the situation varies across locations.
Slide and Communication Tactics
- Use claim-based titles, not topic labels. For example, replace “Revenue Analysis” with “Half of our stores lose money because sales fell, not because costs rose.”
- Put the executive summary immediately after the title slide. State the recommendation and its main rationale; use subsequent slides as evidence.
- Assume a judge may spend only about 10 seconds on a slide. If the main takeaway is not apparent quickly, simplify it.
- Keep slides focused and avoid dense text, cluttered visuals, and unnecessary detail.
- Make charts directly support the slide’s claim:
- Label axes and units.
- Use color selectively to highlight the key point; keep other data visually subdued.
- Sort or group data to make patterns clear.
- Include a brief source or calculation line; put detailed workings and citations in the appendix.
- Anticipate likely questions: How was this number calculated? What is the source? Why does this evidence matter to the recommendation?
- If data is unavailable, use reasonable estimates and make the assumptions clear. Cite sources and disclose any AI assistance.
Illustrative Coffee-Chain Case and Metrics
The workshop used a hypothetical chain to demonstrate how to move from analysis to a recommendation:
- The case involved 200 stores, with 100 losing about $60,000 each per year.
- One illustrative proposal was to close the 30 worst-performing stores. At an average loss of approximately $67,000 per store, that would avoid roughly $2 million in annual losses.
- Another comparison cited fixing 70 stores as potentially recovering about $3 million per year.
- A sample action plan was to close the 30 worst stores promptly and fix the remaining 70 within 12 months.
- These figures are workshop examples, not validated company results. The recommendation should depend on the evidence and store-level differences.
- Possible supporting claims included competitors opening 40 shops near the weakest stores since 2024, coffee beans making up nearly 90% of cost of goods sold, and costs rising 40% alongside wage and maintenance increases. The speaker emphasized that claims need context, sources, and a clear connection to the decision.
Submission Rules and Key Dates
- Maximum of 15 slides: one title slide, up to 10 content slides, and up to four appendix slides. The executive summary counts as a content slide.
- The title slide should show only the participant ID; names, schools, and logos are excluded for blind judging.
- Use appendix slides for detailed calculations, supporting data, external research, citations, and AI-use disclosure.
- The workshop stated that registration closed October 17, submissions opened October 18, and the submission deadline was October 31. Participants were advised to submit early and check the official website for current rules.
Presenter and Sources
- Presenter: Bridget Carl, Senior Partnerships Manager at Ladder Internships.
- Sources: Bridget Carl’s HSACC workshop and its illustrative coffee-chain case; submission requirements and dates as presented in the workshop.
Rate this summary
Your feedback will help improve summaries.
Improve this summary
Reprocess with a stronger model when the summary feels incomplete or inaccurate.
Translate summary in another language
Ask questions to this video
Chat for follow-up questions, clarifications, and source-backed answers.