{
  "id": 8941452,
  "title": "I Am a Single Point of Failure",
  "url": "https://urgent.news/2026/09/21/i-am-a-single-point-of-failure",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-21T14:32:47.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/keenenwilkins/i-am-a-single-point-of-failure-950"
  },
  "original_language": "en",
  "account": "Every individual holds the potential to become a single point of failure for their organization. This occurs when a person's knowledge and expertise are confined to their own head, leaving no written documentation for others to follow. A memorable lesson was learned during a session on writing standard operating procedures, where someone remarked that if no one else can understand a task without your guidance, it is merely a memory, not documentation.\n\nThe consequences of such a single point of failure can be catastrophic when the individual responsible is absent due to illness or other circumstances. The session also introduced the framework of Role, Signal, and Handoff. While roles define responsibilities and signals indicate when a task is completed, handoff poses the most significant challenge, as it requires another person's confirmation of the task's successful transfer.\n\nAt various organizational scales, the issue remains consistent - knowledge is present but not easily accessible. In smaller groups, one person may take on all responsibilities, while larger organizations grapple with insufficient problem statements, untrusted data, and inadequate governance. Regardless of the size, the root cause often lies in the inability to transfer knowledge effectively.\n\nThe solution is straightforward but often overlooked: document the processes, ensuring they can be understood and executed without relying on a single individual. By doing so, organizations can mitigate the risk of single point failures and foster a more resilient and scalable environment.",
  "summary": "If someone can't follow it without you, it's a memory, not documentation. I heard that on a Monday, in a session about writing standard operating procedures. I wrote it down thinking it was about documentation. By Friday it had described two different failures of mine, and the second one had nothing to do with writing anything down. The obvious version Last week I mapped my default work habit as…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}