{"id":63173,"date":"2021-07-22T15:30:27","date_gmt":"2021-07-22T14:30:27","guid":{"rendered":"https:\/\/www.prodpad.com\/?post_type=pp_resource&p=63173"},"modified":"2022-10-31T13:52:23","modified_gmt":"2022-10-31T13:52:23","slug":"initiative","status":"publish","type":"pp_glossary","link":"https:\/\/www.prodpad.com\/glossary\/initiative\/","title":{"rendered":"Initiative"},"content":{"rendered":"\n
\n
\n
<\/div>\n\n\n\n
\n

What is an Initiative in product management?<\/h2>\n\n\n\n

Product management initiatives represent a key part of your theme based product roadmap. An initiative represents a broad piece of work that you wish to undertake, and can be expressed as a problem to solve.<\/p>\n\n\n\n

Initiatives are sometimes referred to as projects or themes. They encompass a collection of ideas<\/a> or experiments<\/a> to explore as you attempt to solve a customer problem and work towards your product and company objectives. <\/p>\n\n\n\n

It’s sometimes helpful to think of initiatives as a level above features or epics. They’re less granular than the specific changes which you’re considering, and are a useful way of talking to your stakeholders and customers about what you’re working on.<\/p>\n\n\n\n

Thinking about your roadmap at this level is also a useful way to do prioritization. It’s much easier to consider which is the most important problem to solve next than it is to determine the next feature to build. Determining the highest priority problem to focus on drastically reduces the number of ideas to consider and gives you a small set of ideas to experiment around.<\/p>\n\n\n\n

For example, imagine you were aware of a problem in your product where users are struggling to understand how to use it – that’s a classic onboarding problem! You can express this as an initiative on your roadmap, linked to your product objectives around user growth and onboarding to highlight what’s being done, and why.<\/p>\n\n\n\n

\"An
An initiative should show the problem to be solved and why it should be solved<\/figcaption><\/figure>\n\n\n\n

Expressing your plans in this way gives you the freedom to be lean, and to experiment with the different ways you might solve this problem. <\/p>\n\n\n\n

It’s important to go back and measure the success of your roadmap initiatives after they are completed. Doing so allows you to learn more about how your customers are using your product, and open up opportunities for further improvements. This is an important part of continuous discovery<\/a>.<\/p>\n\n\n\n

If you want to learn more about how to add initiatives to your product roadmap, check out how to build a product roadmap everyone understands<\/a>.<\/p>\n\n\n\n

\nBack to The Product Management Glossary<\/a>\n<\/div>\n\n\n