{
  "version": "1.3.0",
  "releasedAt": "2026-05-20",
  "kpi": {
    "rogueId": "hr.talent_highlights",
    "slug": "talent_highlights",
    "domain": "hr",
    "defaultLabel": "Talent Highlights",
    "description": "Free-form narrative on notable hires, promotions, internal moves, and other positive organizational developments the board should be aware of. The \"good news\" companion to `hr.talent_challenges`. Common pitfall: listing every internal move and burying the genuinely important signals (key executive hires, strategic team-build milestones). Best practice is 3–5 bulleted items per period, each tied to a board-relevant outcome or risk-it-mitigates rather than a generic celebration.",
    "fieldType": "text",
    "unit": null,
    "maturity": "general",
    "suggestedForStages": [
      "seriesA",
      "seriesB",
      "seriesC",
      "public"
    ],
    "defaultOwningFunctions": [
      "HR"
    ],
    "stageRelevance": {
      "seriesA": "recommended",
      "seriesB": "recommended",
      "seriesC": "recommended",
      "public": "recommended"
    },
    "definitionSource": {
      "tier": "editorial",
      "sourceName": "imboard Editorial",
      "sourceUrl": null,
      "sectionRef": null,
      "publicationDate": "2026-04-01",
      "attributionNotice": null
    },
    "whyItMatters": "Gives the board context for the headline numbers — a flat headcount with a major engineering leader hired tells a different story than a flat headcount with no narrative. Also primes board members for warm-intro asks and reference checks.",
    "interpretationGuidance": "Quality > quantity. Items should answer \"why does the board care?\" — a senior IC promotion to manager matters because it filled a key vacancy; a generic \"we promoted 4 people\" doesn't. Pair each highlight with the role/team it impacts.",
    "relatedKpiIds": [
      "hr.key_hires",
      "hr.executive_commentary",
      "hr.talent_challenges",
      "hr.new_hires"
    ]
  }
}