{
  "id": 8234638,
  "title": "People: Bus Factor, Expectations and Day One",
  "url": "https://urgent.news/2026/09/18/people-bus-factor-expectations-and-day-one",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-18T11:20:01.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/fattakhov/people-bus-factor-expectations-and-day-one-2hl4"
  },
  "original_language": "en",
  "account": "<step 1. Bus factor: find the hostages>\nIdentify which individuals hold critical knowledge or control over essential components of a project. The \"who knows what\" map can reveal if multiple people depend on the same person. This creates a bus factor of 1, meaning the project is vulnerable if that person is unavailable. Look for cases where one individual knows everything about multiple services, as this is a high-risk situation.\n\n<step 2. Ownership: assemble from facts, don't draw it>\nCreate an ownership matrix based on actual work patterns, not intended roles. Analyze who completes tasks and who makes decisions. This can reveal discrepancies between who does the work and who is officially responsible. Document the real relationships between roles, including who executes, who is accountable, who is consulted, and who is informed. Use this matrix to identify mismatches and initiate conversations to clarify responsibilities.\n\n<step 3. Delegate - and spell out expectations>\nDelegation is crucial to reduce the bus factor. When delegating tasks, clearly communicate the expected outcome, timeline, and boundaries of autonomy. Define what constitutes a successful result, set deadlines with checkpoints, and outline what decisions the delegate can make independently. Additionally, specify any resources or support needed to complete the task successfully. By clearly defining expectations upfront, you can avoid misunderstandings and ensure the task is completed as intended.\n\n<step 4. Onboarding and one-on-ones>\nEffective onboarding is essential to integrate new team members quickly. The first day should focus on getting the person set up with the project environment. Within a week, the new hire should be able to ship a real, albeit small, production task. To facilitate this, create concise onboarding documents covering the company's mission, engineering processes, and domain-specific terminology. Regular one-on-one meetings during the initial months are important for addressing questions, clarifying doubts, and ensuring the new team member feels supported. These meetings also provide an opportunity to reassess expectations and address any issues that may arise.",
  "summary": "Part of the \"How to bring order to a project\" series — the people track. It comes after infrastructure and architecture not because it matters less, but the opposite: it's the most important and the slowest track. A config can be moved into git in a day; trust, habits and the understanding of \"who owns what\" take months to rebuild. Let me repeat the track's thesis from the hub, because it's the…",
  "key_points": [
    "Identify critical individuals with high bus factor risk",
    "Create ownership matrix based on actual work patterns",
    "Clearly delegate tasks with defined expectations and outcomes"
  ],
  "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."
}