Skip to main content
New: 9 PM Courses with hands-on exercises and certificates
← Back to Glossary
StrategyI

Initiative

Definition

An initiative is a strategic body of work that typically spans multiple sprints and consists of several epics. It represents a significant investment of team capacity toward a defined business outcome. In the product work hierarchy, initiatives sit between themes and epics: a theme is a strategic focus area, an initiative is a concrete effort that advances that theme, and epics are the deliverable components of the initiative.

For example, a theme of "Reduce churn for mid-market accounts" might contain the initiative "Build proactive health scoring system." That initiative would then be broken into epics like "Implement usage data pipeline," "Build health score algorithm," "Create PM-facing dashboard," and "Add automated alert emails." Each epic contains user stories that can be planned and delivered within individual sprints.

Initiatives are the primary unit of roadmap communication with executives and stakeholders. While executives rarely need to know about individual epics, they do need to understand what initiatives the team is pursuing and why. A well-defined initiative bridges the gap between "what is the team doing?" and "how does this connect to our strategy?"

Why It Matters for Product Managers

Initiatives are where PMs spend most of their strategic energy. Defining the right initiatives for a quarter is one of the highest-impact decisions a PM makes. It determines what the team will focus on for 8-12 weeks and, by extension, what they will not focus on. The RICE framework or weighted scoring can help prioritize competing initiative ideas.

Initiatives also serve as the accountability unit for delivery. At the end of a quarter, the question is not "did we complete 47 user stories?" but "did we deliver the initiatives we planned, and did they produce the expected outcomes?" Framing delivery around initiatives keeps the conversation at the right altitude: strategic enough to matter, specific enough to track.

How to Apply It

  • ☐ Define 1-2 initiatives per team per quarter during planning
  • ☐ Write a one-page initiative brief: outcome, success metrics, scope, timeline, dependencies
  • ☐ Break each initiative into 3-6 epics before the quarter starts
  • ☐ Map each initiative to a strategic theme or OKR
  • ☐ Track initiative progress weekly using a burn-up chart or milestone checklist
  • ☐ Review initiative outcomes at the end of the quarter, not just completion status
  • ☐ Share initiative status with stakeholders in a monthly roadmap update

For roadmap templates that organize work by initiative, see the initiative roadmap templates and the quarterly roadmap template. The roadmap-building guide covers how to scope and sequence initiatives across quarters.

Related Terms

EpicRoadmapProduct StrategyOKR (Objectives and Key Results)Backlog

Frequently Asked Questions

What is the difference between an initiative and an epic?+
An initiative is larger in scope and more strategically oriented. An epic is a chunk of development work that can be completed in 1-3 sprints and broken into user stories. An initiative spans multiple sprints (often a full quarter) and contains several related epics. For example, the initiative 'Launch self-serve enterprise onboarding' might contain epics like 'Build SSO configuration wizard,' 'Create admin role management,' and 'Implement usage-based billing setup.' The initiative defines the business outcome. The epics define the shippable pieces that get you there.
How do you write a good initiative definition?+
A good initiative has five elements: a clear outcome statement (what changes when this is done), success metrics (how you measure the outcome), scope boundaries (what is included and what is explicitly excluded), a rough timeline (which quarter or half), and dependencies (what other teams or systems are involved). Do not try to list every feature upfront. The initiative should be precise about the outcome but flexible about the solution. The team will discover the right approach through epics and sprints. A one-page brief works better than a 20-page spec for most initiatives.
How many active initiatives should a team have at once?+
One to two active initiatives per team is ideal. Three is the maximum before context-switching overhead starts degrading quality and throughput. If your team has more than three active initiatives, you are effectively working on nothing with full focus. The exception is maintenance work, which can run as a lightweight parallel stream (e.g., allocating 20% of capacity to bug fixes and tech debt). But strategic initiatives need concentrated effort. A team that finishes one initiative every 6-8 weeks will ship more than a team that half-finishes five initiatives in the same period.
← PreviousInformation Architecture (IA)Next →Initiative Roadmap

Explore More PM Terms

Browse our complete glossary of 100+ product management terms.

Full GlossaryExplore Frameworks