Key Initiatives
Container handle for the field-array of strategic product initiatives committed for the current quarter / half — each entry tracks the initiative name, status (on-track / at-risk / blocked / shipped / cut), owner, target date, and a one-line explanation or mitigation plan. The structured, per-initiative companion to the `product.key_initiatives_status` narrative: the narrative gives the execution-pulse story, this gallery makes each initiative individually trackable with its own owner and status. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: every initiative defaults to "on-track" until two weeks before its deadline — require an explicit at-risk state with a mitigation plan, not a re-label at the deadline. — Product KPI, I'mBoard-authored (editorial tier).
I'mBoard-authored (editorial tier)
No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.
Rogue ID: product.key_initiatives
Type: Text
Domain: Product
Definition
Container handle for the field-array of strategic product initiatives committed for the current quarter / half — each entry tracks the initiative name, status (on-track / at-risk / blocked / shipped / cut), owner, target date, and a one-line explanation or mitigation plan. The structured, per-initiative companion to the product.key_initiatives_status narrative: the narrative gives the execution-pulse story, this gallery makes each initiative individually trackable with its own owner and status. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: every initiative defaults to "on-track" until two weeks before its deadline — require an explicit at-risk state with a mitigation plan, not a re-label at the deadline.
Formula
Container — field-array of initiative items (name, status, owner, targetDate, explanation / mitigation). No aggregate calculation; the surface makes each strategic initiative individually trackable at the board level.Why it matters
Connects the strategic narrative to delivery reality at the level the board can act on — surfaces where engineering needs unblocking and where commitments are slipping, per named initiative with a named owner. The board's most efficient leverage point on the product organization.
How to interpret
Watch for chronic "at-risk" items without escalation (the team has accepted slippage and is notifying, not asking for help) and for all-green status alongside a declining product.delivery_predictability (status is being optimistically managed). Pair with the product.key_initiatives_status narrative — the gallery tracks the items, the narrative explains the pattern.
Related KPIs
product.key_initiatives_statusproduct.delivery_predictabilityproduct.portfolioproduct.offensive_roadmap_pctproduct.capacity_allocation_pct
Source
I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Stage relevance
| Company stage | Priority |
|---|---|
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- Product
Machine-readable
- This KPI as JSON:
/api/ontology/product/key_initiatives.json - All Product KPIs:
/api/ontology/product.json - Full catalog:
/api/ontology/index.json
Innovation Capacity %
Percentage of R&D capacity (typically measured in engineering-weeks or story points over a quarter) allocated to net-new capabilities, as opposed to maintenance, bug fixes, internal tooling, or customer-support engineering. The "available bandwidth for offense" view. Common pitfall: confusing innovation capacity (input — how much team-time is available for new work) with `offensive_roadmap_pct` (output — what proportion of the planned roadmap is growth-oriented). A team can have 60% innovation capacity allocated entirely to defensive work if the roadmap demands it. Boards should look at both together. — Product KPI, I'mBoard-authored (editorial tier).
Key Initiatives Status
Stoplight-plus-narrative status of the strategic product initiatives committed for the current quarter / half — each initiative ideally tagged on-track / at-risk / blocked / shipped, with a one-line explanation. The execution-pulse view that connects strategy intent to delivery reality. Common pitfall: every initiative defaults to "on track" until two weeks before the deadline, then turns red — a board that only sees binary green-or-red status without intermediate "at-risk" signaling is being managed reactively. Pair with `delivery_predictability` to detect this pattern; require at-risk initiatives to surface a mitigation plan, not just a label. — Product KPI, I'mBoard-authored (editorial tier).