Product Initiative
A coordinated, strategic body of product work that groups multiple efforts toward a shared objective or outcome.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-initiative/
01What it means
A product initiative is a planning construct that connects strategy to a substantial, coordinated area of action, often grouping several epics or team efforts under one objective. The term is not standardized: some organizations use it for an outcome-oriented investment, while tools may define it mainly as a hierarchy level.[1][2]
02Why it matters
Initiatives help leaders allocate attention and funding above individual features while letting teams coordinate dependencies and explain how separate efforts contribute to one strategic intent.
03When to use it
Use an initiative when an objective requires multiple meaningful workstreams or teams and needs portfolio-level visibility. Avoid creating one for ordinary features or using initiatives as fixed annual projects disconnected from evidence.
04How it works
- Connect the initiative to a strategic choice and measurable objective.
- Define its boundaries, accountable decision makers, constraints, and major assumptions.
- Identify contributing epics, teams, dependencies, and enabling work.
- Sequence learning and delivery without prescribing every feature in advance.
- Review outcomes and evidence at decision points, then continue, adapt, or stop investment.
05A practical example
A commerce company creates an initiative to improve international checkout completion. Payments, localization, fraud, and support teams contribute separate epics, while leaders review conversion, loss, and service outcomes together rather than reporting only epic completion.
06Where it breaks
Because the term varies, initiatives can confuse teams unless hierarchy and decision rights are explicit. They may become oversized projects, absorb unrelated work, or persist because of sunk cost after the strategic case weakens.
Common mistakes
- Defining an initiative as a bundle of preselected features with no objective.
- Creating initiatives too small to need coordination.
- Assuming every tool’s initiative level means the same thing.
- Tracking child-item completion instead of the intended outcome.
07Sources
- Epics, Stories, and InitiativesAtlassian · Professional practice guideEpics, Stories, and Initiatives
- Product RoadmapsAtlassian · Professional practice guideProduct Roadmaps