{
  "id": "10",
  "content": [
    {
      "type": "heading",
      "text": "Post-Launch Review and Continuous Improvement"
    },
    {
      "type": "text",
      "html": "A post-launch review turns the launch into learning. It should capture what worked, what broke, what was delayed, what surprised the team, and what should change next time."
    },
    {
      "type": "text",
      "html": "The review should be blameless and practical. The goal is better systems, clearer ownership, stronger checklists, and fewer surprises."
    },
    {
      "type": "text",
      "html": "A mature launch process improves every time. Each launch teaches the next launch how to be calmer."
    },
    {
      "type": "callout",
      "style": "info",
      "html": "<strong>Practice:</strong> Schedule a review within one week. Document wins, issues, decisions, metrics, and checklist changes."
    }
  ],
  "quiz": {
    "questions": [
      {
        "id": "q1",
        "type": "single",
        "text": "What is the purpose of a post-launch review?",
        "options": [
          {
            "id": "a",
            "text": "Turn launch experience into better future process"
          },
          {
            "id": "b",
            "text": "Assign blame randomly"
          },
          {
            "id": "c",
            "text": "Delete all notes"
          }
        ],
        "correct": [
          "a"
        ]
      },
      {
        "id": "q2",
        "type": "single",
        "text": "When should review happen?",
        "options": [
          {
            "id": "a",
            "text": "Soon enough that details are still fresh"
          },
          {
            "id": "b",
            "text": "Years later only"
          },
          {
            "id": "c",
            "text": "Never"
          }
        ],
        "correct": [
          "a"
        ]
      }
    ]
  }
}