Case Studies: Deep-Dive Mission Reports on Projects

{
  id: "cs1",
  title: "PROJECT ORION: E-Commerce Replatforming",
  duration: "6 MONTHS",
  crew: "4 ENGINEERS, 1 DESIGNER",
  techDeployed: ["Next.js", "Shopify Storefront API", "Tailwind CSS", "Framer Motion"],
  objective: "One paragraph describing the mission goal.",
  preFlight: "One paragraph describing the situation before work began.",
  timeline: [
    { phase: "T-MINUS 6M", description: "Architecture design and technology selection." },
    { phase: "T-ZERO",     description: "Staged rollout to 10% of traffic." }
  ],
  anomalies: "One paragraph describing problems encountered and how they were resolved.",
  outcome: "One paragraph describing measurable results.",
  future: "One paragraph describing planned next steps."
}

{
  id: "cs3",
  title: "MISSION ATLAS: Design System Migration",
  duration: "4 MONTHS",
  crew: "3 ENGINEERS, 2 DESIGNERS",
  techDeployed: ["React", "Storybook", "Radix UI", "Tailwind CSS"],
  objective: "Consolidate three internal component libraries into a single, versioned design system.",
  preFlight: "Inconsistent UI patterns across products were causing a 40% increase in QA cycles.",
  timeline: [
    { phase: "PHASE 1", description: "Audit all existing components and identify duplicates." },
    { phase: "PHASE 2", description: "Build the core token layer and base primitives." },
    { phase: "PHASE 3", description: "Migrate product teams onto the new system incrementally." }
  ],
  anomalies: "Legacy IE11 support requirements forced polyfill additions that increased bundle size by 12 kB. Dropped IE11 support after stakeholder alignment.",
  outcome: "QA cycles reduced by 35%. All three products now deploy from a single component source.",
  future: "Publishing the design system as an open-source package."
}