Initiative

Origin & evolution

The initiative as a portfolio🧸PortfolioPortfolioA grouping of products by strategic axisView reference →-level construct was codified by Dean Leffingwell in the Scaled Agile Framework (SAFe), released in 2011 and built on ideas he set out earlier in Scaling Software Agility (2007) and Agile Software Requirements (2010). SAFe gave the large enterprise a vocabulary for work that was too big for a single team: the portfolio epic📜EpicProduct SpecificationA large body of work that can be broken into storiesView reference →, a significant initiative that warrants portfolio oversight because of its scale and cost.

SAFe attached two demands to every such initiative. Each needs a Lean business case and a minimum viable product, and each must trace back to one or more strategic themes. The traceability rule was the real contribution. If an initiative cannot connect upward to a stated priority, the framework treats that as a signal the work may not serve the organisation's actual goals.

Outside SAFe, the word travels widely and loosely. Strategy consultancies use "initiative" for any funded programme of change; OKR practitioners use it for the bets that sit under an objective🏁ObjectiveStrategyA strategic goal (OKR)View reference →. The common thread across these usages is that an initiative is the level at which an organisation commits resources to a hypothesis🧪HypothesisValidationA testable belief about a solutionView reference → about how to move a number. The lighter-weight communities (lean startup, continuous discovery) push back on the heavyweight business case, but they keep the core idea: an initiative is a deliberate, bounded investment, and it owes its existence to an outcome🏆OutcomeStrategyA desired business or user outcomeView reference →.

Mik Kersten's *Project to Product* (2018) takes a third position: the project model itself — temporary funding, discrete scope, one-time business case — is what breaks enterprise flow. Kersten's Flow Framework measures work by four flow item types (features⭐FeatureProduct SpecificationA product capability or featureView reference →, defects, risks🎲RiskComplianceA risk to the product or businessView reference →, debts) moving through persistent value streams🌊Value StreamStrategyAn end-to-end flow delivering value to the customerView reference →, and his argument implies that an initiative worth running should be modelled as a flow item inside a funded product stream rather than as a stand-alone funded project. By that reading, the business case is not the unit of commitment; the value stream is, and the initiative is a signal of demand on it.

How it works in practice

A B2B analytics company sets a strategic theme🧵Strategic ThemeStrategyA high-level strategic focus area for a planning period. Its own time_horizon is now deprecated: promote the period to a planning_cycle and link the two with strategic_theme_scoped_to_planning_cycle, so themes share one dated, nestable interval instead of a drifting per-theme label.View reference → for the year: become the default tool for finance teams, not just data teams. Under it sits one initiative, "Finance-grade reporting," with a budget of 1.2m, a six-month window, and a single accountable owner in the VP of Product.

The initiative is not a feature list. It names the outcome it drives (finance users who complete a month-end close inside the product) and the assumptions🤔AssumptionStrategyA belief taken as true that underpins a strategyView reference → it rests on (that finance teams will trust an export they did not build in a spreadsheet). Three months in, an assumption fails research. The team can kill or reshape the initiative cleanly because its boundary, budget, and owner were explicit from the start. A loose "reporting improvements" workstream would have leaked spend for another two quarters before anyone could say it had stopped serving the theme.

Initiative vs. its neighbours

• Strategic theme: a theme is a durable direction the organisation will invest behind for a year or more. An initiative is one funded bet placed under that theme. A theme can spawn several initiatives; an initiative serves exactly one theme at a time.
• Epic: in delivery terms an epic is a large unit of buildable scope that decomposes into features and stories. An initiative is the funded strategic envelope around such work, carrying budget and a business case. SAFe collapses the two at portfolio level; most product orgs keep the initiative above delivery and the epic inside it.
• Objective: an objective states the qualitative direction for a quarter. An initiative is the resourced effort that pursues it. The objective says where; the initiative says what you are spending to get there.
• Outcome: an outcome is the measurable change the initiative exists to produce. The initiative is the cause; the outcome is the effect you can verify.

In the graph

In the Unified Product Graph, initiative🚀InitiativeStrategyA large coordinated effort to achieve a strategic goal sits in the Strategy & Outcomes region as a container, downstream of strategic themes and upstream of measurable change. A strategic theme reaches it through strategic_theme_pursues_initiativeStrategic ThemepursuesInitiativehierarchy, and the product funds it through product_invests_in_initiativeProductinvests inInitiativesemantic. Its load-bearing edges point outward: initiative_drives_outcomeInitiativedrivesOutcomecross-domain ties the spend to a result, and initiative_assumes_assumptionInitiativeassumesAssumptionhierarchy records the bets the work depends on. That last edge is what lets a graph answer the SAFe traceability question by construction: an initiative🚀InitiativeStrategyA large coordinated effort to achieve a strategic goal with no initiative_drives_outcomeInitiativedrivesOutcomecross-domain edge is queryably an investment with no stated return.