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).
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_status
Type: Text
Domain: Product
Definition
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.
Formula
Narrative — list of named strategic initiatives, each with (1) status (on-track / at-risk / blocked / shipped / cut), (2) one-line explanation, (3) for at-risk and blocked: a mitigation plan or escalation request.Why it matters
Connects the strategic narrative to delivery reality at the level the board can act on. Surfaces where engineering needs unblocking, where commitments are slipping, and where the strategy needs revision. The board's most efficient leverage point on the product organization.
How to interpret
Watch for two patterns: (1) chronic "at-risk" without escalation — usually a sign that the team has accepted the slippage and the board is being notified, not asked for help. (2) all-green status alongside declining delivery_predictability — usually a sign that the status field is being optimistically managed. The right cadence: at-risk should appear early and resolve via mitigation, not by re-labeling at the deadline.
Related KPIs
product.delivery_predictabilityproduct.portfolio_strategyproduct.offensive_roadmap_pctproduct.defensive_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_status.json - All Product KPIs:
/api/ontology/product.json - Full catalog:
/api/ontology/index.json
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).
Growth & Differentiation %
Percentage of the planned roadmap (typically next 1–2 quarters) allocated to offensive bets — net-new capabilities, market expansion, differentiation moats, new monetization. The "what proportion of the plan is about winning" view. Common pitfall: counting "improvements to existing features" as offensive when the change is really table-stakes parity work. Boards should expect a McKinsey-style horizon framing (Horizon 1 = core, Horizon 2 = adjacent, Horizon 3 = transformational) or an equivalent classification, and apply it consistently. Per the original McKinsey "Three Horizons" framing (Baghai/Coley/White, "The Alchemy of Growth", 1999), a healthy portfolio funds all three — over-indexing on any one is a strategic risk. — Product KPI, I'mBoard-authored (editorial tier).