Initiatives are projects/milestones organized around specific business goal or objective. For example:

  • Deliver product MVP
  • Release new onboarding flow
  • Increase new user adoption

Whether an initiative is defined around launching a major piece of new functionality or increasing customer retention, when it's over, you should be able to evaluate whether you succeeded. So regardless of how an initiative is named, it will likely be associated with certain objectives and key results (success criteria, KPIs), which may also be added to the initiative's description.

How to add an initiative to your Features board

Like all column types, you can show/hide initiatives on your Features board using the column configurations bar at right. 

Toggle on the entire column group, then individual initiatives.

Add new initiatives by selecting [+] Add new initiative.

Adding features to initiatives

To add a feature to an initiative on your Features board, simply indicate how important the feature is to the initiative's success. Any value besides not set will add the feature to the initiative.

A feature can belong to multiple initiatives.

You can select an initiative to see additional summary details:

  • Visualize progress toward completion based on effort estimates of incomplete vs. complete features
  • Review breakdown of total effort required/expended for each feature status subgroup
  • Set initiative status: Upcoming, In Progress, Complete, or Archived

How are drivers different from initiatives?

If some of your drivers and initiatives seem related, that should come as no surprise. They all likely relate to your current areas of strategic focus!

Just remember:

  • Drivers tend to be more open-ended (e.g. New user adoption) and are never complete.
  • Initiatives are like projects/milestones (e.g. New onboarding flow) that have a start and an end. They typically represent a coordinated effort to advance one or more business objectives (e.g. increase the number of monthly active users by 4%).
  • Drivers can be rolled up into a custom-weighted Prioritization score, which can be used to sort/filter your Features board. That makes them especially useful for surfacing promising ideas in the early stages of prioritization.
  • Initiatives are for planning projects/milestones you intend to work on. They're most useful for grouping together complementary features that support a common objective. Unlike drivers, they can be used to organize features on the Matrix/Roadmap so are often more helpful during the later phases of prioritization and for fine-tuning your plans.

See also

Did this answer your question?