Skip to content

Instantly share code, notes, and snippets.

@PaulDuvall
Last active February 3, 2025 23:06
Show Gist options
  • Save PaulDuvall/6e02d52650c36aeb136a624ca6efb3cf to your computer and use it in GitHub Desktop.
Save PaulDuvall/6e02d52650c36aeb136a624ca6efb3cf to your computer and use it in GitHub Desktop.
aws-case-study-prompt-3

Objective:

Develop a structured list of targeted questions for recorded interviews with key project stakeholders—including engagement managers, consultants, and engineers—who directly contributed to delivering AWS-based solutions. The goal is to extract precise, actionable insights to facilitate the automated generation of compelling customer case studies.

Context & Analysis:

A review of AWS and Stelligent case studies reveals distinct archetypes, structural formats, and storytelling approaches. Understanding these patterns will ensure that the questions elicit the right level of detail and depth for compelling narratives.

Case Study Archetypes:

  1. Transformation Stories – Focus on major shifts in efficiency, scalability, or innovation.

    • Example: 3M Health Information Systems automated pipeline provisioning using AWS Service Catalog, reducing setup time from days to minutes.
  2. Technical Deep Dives – Provide in-depth technical insights into implementation and architecture.

    • Example: Stelligent enabled self-service AWS deployments for Advent engineers using AWS CloudFormation and Amazon EC2.
  3. Business Impact Narratives – Highlight measurable business benefits, such as cost savings or compliance improvements.

    • Example: Verizon’s Development-Security-Operations Pipeline (DSOP) enhanced security validation, preventing insecure deployments.

Standard Case Study Structure:

Each case study typically includes:

  • Introduction – Overview of the company and industry.
  • Challenge – Clearly defined problem or opportunity.
  • Solution – Detailed explanation, including AWS services and methodologies.
  • Results – Measurable business and technical outcomes.
  • Customer Quotes – Authentic testimonials reinforcing impact.
  • Architecture Diagrams – Visual representation of the solution.

Comparative Insights:

  • AWS Case Studies – High-level, business outcome-focused, concise, with customer quotes.
  • Stelligent Case Studies – In-depth, technical, detailed architectures, and AWS service breakdowns.

Deliverable:

Develop a structured set of interview questions designed to extract key insights aligned with the above archetypes and structures. The questions should:

  1. Elicit detailed problem statements that resonate with the target audience.
  2. Capture granular technical details of AWS services and methodologies used.
  3. Surface measurable results (e.g., time savings, cost reduction, security improvements).
  4. Encourage storytelling with real-world examples and stakeholder testimonials.
  5. Support automation by structuring responses in a way that enables AI-driven case study generation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment