Skip to content

Instantly share code, notes, and snippets.

@PaulDuvall

PaulDuvall/prompt-2.md

Last active February 3, 2025 23:06
Show Gist options
  • Save PaulDuvall/90e65d84500dbe6d9002025e409b8535 to your computer and use it in GitHub Desktop.
Save PaulDuvall/90e65d84500dbe6d9002025e409b8535 to your computer and use it in GitHub Desktop.
Download ZIP
aws-case-study-prompt-2
Raw
prompt-2.md

AWS Case Study Analysis Guide

Objective:

Analyze the case studies from the provided sources to identify common archetypes, structural formats, and storytelling techniques used in their presentation. The goal is to extract key patterns and variations that can inform the creation of compelling, structured case studies.

Analysis Criteria:

1. Archetype Identification

Categorize case studies based on recurring patterns, ensuring each is classified into one or more of the following:

  • Transformation Stories – Highlight major shifts in efficiency, scalability, or innovation.
  • Technical Deep Dives – Provide in-depth insights into AWS service implementation, architectures, and DevOps strategies.
  • Business Impact Narratives – Emphasize measurable business benefits, such as cost savings, time efficiency, or security enhancements.

2. Structural Breakdown

Identify the core sections commonly included in case studies:

  • Introduction – Company background and industry context.
  • Challenge/Problem Statement – Clearly defined business or technical problem.
  • Solution – AWS services, methodologies, and implementation details.
  • Results & Impact – Quantitative and qualitative benefits, including metrics.
  • Customer Quotes – How frequently they appear and their role in storytelling.
  • Architecture Diagrams – Usage and level of technical detail provided.

3. Comparative Analysis

Evaluate differences in presentation styles and target audience adaptations across various sources:

  • AWS Case Studies – High-level, business-oriented, often concise.
  • Stelligent Case Studies – Technical, detailed architecture discussions, in-depth AWS service breakdowns.
  • Partner Success Stories – Focused on business impact, often with customer testimonials.
  • Individual Case Studies (e.g., 3M, Verizon) – Unique elements or deviations from standard structures.

4. Storytelling Techniques

Analyze how these case studies engage readers:

  • Narrative Style – Formal, technical, or storytelling-driven approaches.
  • Depth vs. Brevity – Level of technical granularity versus executive summaries.
  • Target Audience Adaptation – How the content is tailored for executives, engineers, or decision-makers.

Case Study Sources:

  1. AWS Solutions Case Studies: https://aws.amazon.com/solutions/case-studies/
  2. Stelligent Case Studies: https://stelligent.com/resource-tag/case-study/
  3. 3M HIS Service Catalog Case Study: https://aws.amazon.com/solutions/case-studies/3m-his-service-catalog/
  4. AWS Partner Success: Verizon: https://aws.amazon.com/partners/success/verizon/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment