{
  "version": "1.3.0",
  "releasedAt": "2026-05-20",
  "kpi": {
    "rogueId": "hr.departments",
    "slug": "departments",
    "domain": "hr",
    "defaultLabel": "Departments",
    "description": "Field-array of per-department rows — department name, leader status (resolved against `hr.leader_status`), and headcount metrics with stable-count auto-calc — rendered as a drag-sortable table grouped by department. Common pitfall: department boundaries drift over time (Eng+R&D merging, GTM splitting into Sales/Marketing/CS) — when boundaries change, prior-period comparisons need an explicit reconciliation note. This KPI is structural, not numeric — no formula applies.",
    "fieldType": "text",
    "unit": null,
    "maturity": "general",
    "suggestedForStages": [
      "seriesA",
      "seriesB",
      "seriesC",
      "public"
    ],
    "defaultOwningFunctions": [
      "HR"
    ],
    "stageRelevance": {
      "seriesA": "core",
      "seriesB": "core",
      "seriesC": "core",
      "public": "core"
    },
    "definitionSource": {
      "tier": "editorial",
      "sourceName": "imboard Editorial",
      "sourceUrl": null,
      "sectionRef": null,
      "publicationDate": "2026-04-01",
      "attributionNotice": null
    },
    "whyItMatters": "Shows the org map at a glance — where capacity is allocated, which departments are short-staffed, where leader-vacancies are concentrated. Boards use this to validate the strategy-vs-investment alignment (\"we say we are product-led but R&D is 20% of headcount\").",
    "interpretationGuidance": "Read with `hr.leader_status` alongside — a department with strong leader and on-plan headcount tells a very different story from one with interim/vacant leader and growing headcount. Material department-shape changes should be called out in `hr.talent_highlights` or `hr.talent_challenges` narrative.",
    "relatedKpiIds": [
      "hr.leader_status",
      "hr.total_headcount",
      "hr.key_hires",
      "hr.key_openings",
      "hr.executive_commentary"
    ]
  }
}
