How to set product initiatives?
Product managers understand what customers want and how to build a better product. You are committed to investing in bold ideas and enhancing existing product features. And you know that everything that you do has to support the overall product strategy. That is what product initiatives are for — creating a clear connection between the work you are planning and the goals you want to achieve.
Initiatives are the major areas of investment or focused areas of delivery needed to achieve your product goals. You would typically set goals first and then tie initiatives to goals — followed by grouping features or activities under each initiative. This approach helps you prioritize the work that will bring the most value to customers and the business. Organizing around strategic imperatives like this makes it easier to push aside distractions that do not support the product vision.
The video below provides a strategic overview — showing how every feature, release, or idea should have a clear connection to your goals and initiatives.
When setting product strategy, define each of the below in the following order:
Product vision: The core essence of where you want your product to be in the future and what you are building
Product goals: Measurable objectives that will help you reach your vision and can be achieved within a fixed time frame
Product initiatives: High-level efforts or themes of work that you will complete in order to achieve each goal
The time frame for initiatives will vary but are typically aligned with strategic planning periods — such as half-yearly or quarterly. Each initiative usually spans multiple releases or sprints and contains many epics, user stories, or features.
Let's look at an example. Imagine you are a product portfolio manager for a software company that builds applications for athletes to track their workouts — one app for cyclists and another for runners. You might have a company-level goal to increase revenue by a certain percentage this year. Product goals that roll up to the company-level goal could be related to attracting new customers or reducing customer churn.
You know that page load times within the apps impact the customer experience and whether folks continue to use the apps. So you might set an initiative at the product line level to improve application performance across both apps. Individual product initiatives would then go a level deeper, such as automating performance monitoring so you can spot areas of concern quickly or optimizing a section within the app to improve responsiveness.
The table below illustrates this example:
Product line initiatives
Increase revenue by X% this year
Increase new customers by X% in 1H 2021
Reduce customer churn rate by X% in 1H 2021
Improve application performance
Automate performance monitoring
Optimize X section in the application
Of course, the next level of detail within each initiative would include the releases, epics, or features that support the workstream. In the example below, you can see the relationship between the initiative and the detailed work that underpins it — giving you a line from strategy to implementation.
Why define product initiatives?
The product features and functionality you will build vary in type, scope, and purpose. By defining initiatives or big themes of work, you can develop a structure that keeps requirements in order and allows you to prioritize what to deliver in upcoming releases. You also gain the following:
Clear roadmap direction
Creating initiatives and bundling related features allows you to set a clear path forward. You can determine the balance of work across initiatives to deliver against your goals. A strategic roadmap that showcases initiatives is a great way to share timing and progress with stakeholders and customers.
When it comes to improving your product, you are likely inundated with ideas. Trying to pursue them all would be impractical and ineffective. Choosing top-priority initiatives helps you zero in on the work that is most strategic and deserves the most attention.
Grouping work by initiatives helps leadership and stakeholders understand what you are working on at a high level — even if they do not need to dig into the details at the feature level. Initiatives allow them to see how various groupings of related work contribute to the overall business strategy.
What are the necessary elements to include in an initiative?
Depending on your organization and product portfolio, you may establish initiatives at the company, product line, or product level. The elements you include in each initiative will vary depending on its type. For instance, initiatives that impact customers directly, such as usability improvements, may include different elements than initiatives that align to company-wide goals, such as expanding market leadership.
In general, an initiative should communicate the who, what, when, and why behind the theme of work. Details could include the following:
Summary: A description of the initiative, why you are prioritizing it, and what needs to be accomplished.
Goals: The objectives that the initiative supports. Depending on its scope, an initiative may roll up to multiple goals.
Scope: Primary focus or deliverables within the initiative. It can also include details about what is out of scope.
Roles: Team members involved — including initiative owners, collaborators, and stakeholders.
Time frame: Internal start and end dates, milestones, and launch dates.
Related work: Important work associated with the initiative, such as releases, features, requirements, and dependencies.
In the example below, initiatives are grouped by status and labeled with an associated goal and the number of features within the initiative. For instance, the on-track initiative to "Enhance the partner portal" connects to the goal of building the largest partner ecosystem and includes 13 features.
A sample of strategic initiatives in Aha! Roadmaps
Visualize product initiatives on a roadmap
Once you have defined your initiatives, you can start prioritizing and assigning features within them. Visualize it all on a roadmap to highlight cross-functional work within each initiative. In the example roadmap below, you can see the following:
Initiatives mapped to goals: Initiatives are represented by purple bars and goals are represented by the colored flags.
Initiative time frames: This roadmap is a Gantt-style chart with a timeline above. Of course, you can also build various roadmap views to serve your particular audience and situation.
Related features and dependencies: Planned features are represented by blue bars while gray lines depict dependencies.
Strategic roadmap view in Aha! Roadmaps
You will likely want to create different roadmap views for different audiences. Enter goals, initiatives, and other product data once and choose from a variety of templates to quickly build different views. Show off your plans and demonstrate how you are delivering against the initiatives you have invested in.
Set brilliant strategy, prioritize features, and share visual plans with Aha! Roadmaps — a purpose-built product development tool. Get started with a free 30-day trial.