Principles of Product Management: Epics, Themes, Initiatives – Hierarchy of Work

Epics, Themes, Initiatives – Hierarchy of Work

Epics, Themes, Initiatives – Hierarchy of Work

What This Is

Epics, themes, and initiatives are the organizational scaffolding that helps PMs break down large, ambiguous goals into actionable, trackable work. They bridge the gap between high-level strategy (e.g., "Become the #1 neobank for freelancers") and day-to-day execution (e.g., "Build a tax-withholding feature for 1099 workers"). Without this hierarchy, teams risk misalignment, scope creep, or building features that don’t ladder up to business outcomes.

Real-world example: At Square, the theme "Improve cash flow for small businesses" might include the initiative "Launch Instant Deposits for Payments." This initiative could be broken into epics like: - "Enable instant transfers to debit cards" (backend + compliance work) - "Design a 1-tap instant deposit UX" (frontend + user testing) - "Educate merchants on instant deposits" (marketing + support)

Key Terms & Frameworks

• Theme: A strategic focus area (e.g., "Increase retention for power users") that aligns with company goals. Themes are not time-bound and often span multiple quarters. Think of them as "North Star" categories.

• Initiative: A time-bound, cross-functional effort (e.g., "Redesign the onboarding flow to reduce drop-off by 20%") that delivers a measurable outcome. Initiatives roll up into themes and typically involve multiple teams (engineering, design, marketing).

• Epic: A large body of work that can be broken into smaller user stories or tasks (e.g., "Build a progress tracker for onboarding"). Epics are not features—they’re containers for related work. Example: "Implement OAuth 2.0 login" might include epics for "Backend auth service," "Frontend login UI," and "Security testing."

• User Story: A small, actionable unit of work written from the user’s perspective (e.g., "As a freelancer, I want to see my tax withholdings so I can file quarterly estimates"). Follows the template: "As a [user], I want [action] so that [benefit]."

• OKRs (Objectives and Key Results): A goal-setting framework where:

• Objective = Qualitative goal (e.g., "Become the most trusted neobank for freelancers").

• Key Results = 3–5 quantitative metrics (e.g., "Increase freelancer NPS from 45 to 60," "Reduce support tickets about tax features by 30%"). Themes and initiatives should map to OKRs.

• ICE Score (Impact, Confidence, Ease): A prioritization formula: ICE = Impact × Confidence × Ease

• Impact: How much this moves the needle (1–10).
• Confidence: How sure you are about the impact (1–10).

• Ease: How quickly/easily it can be built (1–10). Use this to rank epics or initiatives.

• Now-Next-Later Roadmap: A visual framework to communicate priorities without committing to dates:

• Now: High-priority, in-progress work (e.g., "Launch instant deposits").
• Next: Planned but not started (e.g., "Add multi-currency support").

• Later: Exploratory or low-priority (e.g., "AI-powered expense categorization").

• Double Diamond (Design Council): A problem-solving framework for scoping epics:

• Discover: Research user pain points (e.g., "Why do freelancers churn?").
• Define: Narrow to a specific problem (e.g., "They struggle with quarterly tax estimates").
• Develop: Brainstorm solutions (e.g., "Tax withholding calculator").

• Deliver: Build and test the solution.

• MoSCoW Prioritization: A categorization method for epics/features:

• Must have: Critical for launch (e.g., "OAuth login").
• Should have: Important but not urgent (e.g., "Dark mode").
• Could have: Nice-to-have (e.g., "Custom avatars").

• Won’t have: Out of scope (e.g., "Desktop app").

• Dependency Mapping: A visual tool to identify blockers between epics/initiatives (e.g., "Can’t build the tax calculator until the backend tax API is ready"). Use a dependency matrix or Gantt chart to track cross-team work.

• RACI Matrix: A role-clarification framework for initiatives:

• Responsible: Who does the work (e.g., engineers).
• Accountable: Who owns the outcome (e.g., PM).
• Consulted: Who provides input (e.g., legal, design).
• Informed: Who needs updates (e.g., marketing).

Step-by-Step / Process Flow

1. Start with Strategy (Themes-OKRs)

• Action: Align with leadership on company/team themes (e.g., "Improve retention for power users").
• How:
• Review company OKRs (e.g., "Increase DAU by 15%").
• Conduct a SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) to identify gaps.
• Example: If retention is a theme, OKRs might include "Reduce churn by 20%" or "Increase session frequency by 30%."

2. Break Themes into Initiatives

• Action: Translate themes into time-bound initiatives with clear outcomes.
• How:
• Use ICE or RICE to prioritize potential initiatives.
• Validate with data (e.g., "Our churn spikes after 30 days—let’s focus on onboarding").
• Example: For the theme "Improve retention," initiatives might include:
  • "Redesign the first-time user experience (FTUE)."
  • "Launch a loyalty program for power users."
  • "Add in-app tutorials for advanced features."

3. Decompose Initiatives into Epics

• Action: Split initiatives into epics (large chunks of work).
• How:
• Use the Double Diamond to explore solutions.
• Map epics to user journeys (e.g., "Onboarding"-"Sign-up flow," "Profile setup," "First transaction").
• Example: For the initiative "Redesign FTUE," epics might include:
  • "Simplify sign-up to 2 steps."
  • "Add a progress tracker."
  • "Personalize the first screen based on user type."

4. Break Epics into User Stories

• Action: Turn epics into actionable user stories for engineers.
• How:
• Write stories using the template: "As a [user], I want [action] so that [benefit]."
• Add acceptance criteria (e.g., "User can complete sign-up in <60 seconds").
• Example: For the epic "Simplify sign-up," stories might include:
  • "As a new user, I want to sign up with Google so I don’t have to remember a password."
  • "As a new user, I want to skip non-critical fields so I can start using the app faster."

5. Prioritize and Sequence Work

• Action: Decide what to build now, next, or later.
• How:
• Use MoSCoW or ICE to rank epics/stories.
• Map dependencies (e.g., "Can’t build the loyalty program until the rewards API is ready").
• Example: For the initiative "Launch a loyalty program," sequence epics as:
  • Now: "Build rewards API" (dependency for all other work).
  • Next: "Design loyalty dashboard."
  • Later: "Add social sharing for rewards."

6. Communicate the Plan

• Action: Share the hierarchy with stakeholders.
• How:
• Use a Now-Next-Later roadmap (avoid dates to reduce pressure).
• Create a RACI matrix to clarify ownership.
• Example: Present to leadership with a slide showing:
  • Theme: "Improve retention."
  • Initiative: "Redesign FTUE."
  • Epics: "Simplify sign-up," "Add progress tracker," etc.

Common Mistakes

PM Interview / Practical Insights

1. "How do you decide what to build next?"

• What they’re testing: Can you balance strategy, data, and execution?
• How to answer:
• Start with themes (e.g., "Our theme is ‘Increase engagement for new users’").
• Break into initiatives (e.g., "Improve onboarding").
• Use ICE/RICE to prioritize epics (e.g., "Simplify sign-up has ICE=42 vs. add dark mode at ICE=18").
• Validate with user research (e.g., "Interviews showed 60% of users drop off at step 3").
• Trap: Don’t just say "I’d build what users ask for." Show you use data + strategy.

2. "How do you handle a stakeholder who wants to add a feature that doesn’t fit your theme?"

• What they’re testing: Can you push back diplomatically?
• How to answer:
• Ask: "How does this align with our current themes/OKRs?"
• Use ICE to compare the feature’s score vs. existing work.
• Propose a trade-off: "If we add this, we’d need to delay [higher-priority epic]. Is that worth it?"
• Example: "Our theme is ‘Improve retention,’ but this feature targets acquisition. Let’s revisit it in Q3 when we focus on growth."
• Trap: Don’t say "No" outright. Show you’re data-driven and collaborative.

3. "What’s the difference between an epic and a feature?"

• What they’re testing: Do you understand work decomposition?
• How to answer:
• Epic: A container for related work (e.g., "Build a tax calculator" includes backend, UI, and testing).
• Feature: A shippable unit (e.g., "The ‘Calculate’ button in the tax calculator").
• Example: "The epic ‘Improve search’ might include features like ‘Add filters,’ ‘Autocomplete,’ and ‘Recent searches.’"
• Trap: Don’t say "An epic is just a bigger feature." Epics are organizational, not just "bigger."

4. "How do you measure the success of an initiative?"

• What they’re testing: Can you tie work to outcomes?
• How to answer:
• Start with the initiative’s goal (e.g., "Reduce onboarding drop-off by 20%").
• Define leading indicators (e.g., "Time to complete onboarding") and lagging indicators (e.g., "7-day retention").
• Use A/B tests to isolate impact (e.g., "Test the new onboarding flow vs. control").
• Example: "For the loyalty program initiative, we’d track:
  • Leading: % of users who enroll.
  • Lagging: 30-day retention for enrolled vs. non-enrolled users."
• Trap: Don’t just list metrics. Show you design experiments to measure them.

Quick Check Questions

1. Your team wants to add a "social sharing" feature to increase virality, but user research shows it would hurt NPS. How do you decide?

Answer: Use ICE to compare the feature’s score (e.g., high Impact for virality but low Confidence due to NPS risk) vs. other initiatives. Propose a small experiment (e.g., A/B test with a subset of users) to validate the trade-off. Why: Never prioritize based on one metric (e.g., virality) without considering others (e.g., NPS).

2. A stakeholder says, "We need to launch this epic in 2 weeks," but it has 3 dependencies. What do you do?

Answer: Map the dependencies (e.g., "Epic A needs API X, which is blocked by Team Y"). Propose a phased launch (e.g., "Ship the MVP without API X, then add it in v2") or escalate to leadership to unblock Team Y. Why: Unrealistic timelines without dependency planning lead to missed deadlines.

3. Your CEO says, "Our theme is ‘Become the #1 app for X,’" but the team is working on unrelated epics. How do you align them?

Answer: Facilitate a workshop to break the theme into initiatives (e.g., "Improve feature Y for user segment Z"). Use MoSCoW to reprioritize epics, and create a Now-Next-Later roadmap to show the path to the theme. Why: Themes are useless if they don’t translate into actionable work.

Last-Minute Cram Sheet

1. Theme = Strategic focus area (e.g., "Improve retention"). Initiative = Time-bound project (e.g., "Launch loyalty program"). Epic = Large body of work (e.g., "Build rewards API").
2. OKRs = Objectives (qualitative) + Key Results (quantitative). Themes/initiatives should map to OKRs.
3. ICE Score = Impact × Confidence × Ease. Use to prioritize epics/initiatives.
4. Now-Next-Later = Roadmap framework to avoid committing to dates.
5. Double Diamond = Discover-Define-Develop-Deliver. Use to scope epics.
6. MoSCoW = Must have, Should have, Could have, Won’t have. Use to prioritize features.
7. RACI = Responsible, Accountable, Consulted, Informed. Clarify roles for initiatives.
8. Dependency Mapping = Identify blockers between epics (e.g., "Can’t build UI until API is ready").
9. Epic-Feature: Epics are containers; features are shippable units.
10. Don’t prioritize based on opinions: Use data (ICE, A/B tests, user research).