{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/review-a-risky-success-not-only-a-visible-failure",
  "id": "MHC-D-RESEARCH-1269",
  "version": "0.1.0",
  "title": "Review a risky success, not only a visible failure",
  "summary": "Success can be a bad process wearing a good outcome.",
  "kind": "principle",
  "body": "Debrief the process when the outcome was better than the path deserved. Ask what had to go right, which adaptations rescued the work, what nearly failed and whether the same process would be acceptable if repeated. Preserve useful resilience as well as weaknesses. This prevents a lucky result from silently certifying a fragile method.",
  "limits": [
    "Do not manufacture problems from every successful task. Use this when the path contains credible risk, surprise or recovery worth understanding."
  ],
  "topics": [
    "union-error-prevention-weak-signals"
  ],
  "intents": [],
  "source_ids": [
    "RS-00E7F25184BF4AAC"
  ],
  "evidence": [
    {
      "claim": "AHRQ recommends using briefings and debriefings as learning opportunities after routine work and after exceptionally poor or good outcomes.",
      "source_id": "RS-00E7F25184BF4AAC",
      "role": "supports",
      "note": "A debrief can surface hypotheses and adaptations but does not establish causality by itself.",
      "locator": "Strategy 5: Incorporate Learning Opportunities into Routine Processes"
    }
  ],
  "use_when": [
    "The result was good, but the path included an unsafe shortcut, surprising recovery, fragile assumption or unusual rescue."
  ],
  "avoid_when": [
    "Do not manufacture problems from every successful task. Use this when the path contains credible risk, surprise or recovery worth understanding."
  ],
  "example": "A deployment succeeds only because one engineer manually spots an undocumented configuration mismatch. The release is successful, but the mismatch and rescue still deserve review.",
  "check": "At least one process lesson is recorded independently of whether the final outcome was good or bad.",
  "sources": [
    {
      "id": "RS-00E7F25184BF4AAC",
      "title": "Engineering Safe Practices Affinity Group",
      "url": "https://www.ahrq.gov/action-alliance/engineering-safety-practice/index.html"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-1269",
      "to": "MHC-D-RESEARCH-1267",
      "type": "useful_with",
      "url": "/knowledge/capture-the-near-miss-while-the-evidence-still-exists"
    }
  ],
  "collections": [
    {
      "id": "RC-4BAD27B85771C63B",
      "title": "Catch weak signals before they become expensive errors",
      "url": "/collections/catch-weak-signals-before-they-become-expensive-errors"
    }
  ]
}