Add Features to multiple initiatives

Many intiatives may benefit from some common functionality.   If you could add a feature to multiple initiatives it would allow you to better track the impact of the feature across the entire business.

  • Bob Carlson
  • Mar 20 2015
  • Will not implement
Release time frame
  • Dec 12, 2018

    Admin Response

    We appreciate the feedback on this idea. Despite the interest in this request, we do not plan to implement this idea.

    That said, please note that there are a couple workarounds which would allow you to link a feature to multiple initiatives and understand the impact of the features across the business.

    1. Add an initiatives record relationship custom field to capture secondary initiatives for a feature

    2. Use record links to connect the feature to secondary initiatives

    While we can see value in particular cases for directly linking a feature to multiple initiatives, allowing this would cause other issues and limitations that may not be apparent on the surface. Since initiatives typically represent a large body of work, it is important as that work is broken down into features to be able to clearly delineate which features contribute to the work of the initiative. 

    For example, we have a major effort underway to provide enhanced capacity planning capabilities which will allow you to manage estimates and capacity at the initiative level for high level planning (which can be tracked in this idea.) This would not be possible if a feature could be related to more than one initiative.

    Implementing this would also limit future improvements to roadmap visualizations where you may want to see your initiatives and features in a single roadmap.

    Given the available workarounds and limitations of introducing this capability, we hope you can understand why we do not have plans to implement this idea.

  • Attach files
  • Guest commented
    March 22, 2015 20:19

    need it because many of our features belong to multiple initiatives.

  • Erick Crowell commented
    March 23, 2015 16:06

    Because we want to show how a single feature in a product release, delivers value / unlocks initiatives at different levels in our planning architecture.

    A feature can be associated with an initiative to deliver a complete solution in some space, as well as be associated with an initiative that delivers a similar solution in another space along with helping to reach a 'strategic  initiatives goal' at the highest level.

    Limiting a feature to belonging to a single initiative prevents us from planning common work such that everyone understand the complete impact of delivering a feature. 

  • Karthik Rajagopal commented
    September 08, 2015 03:52

    We have features that can belong to multiple initiatives, goals and such features add more value and can be prioritized. Showing a count of linked initiatives, goals can also help with the prioritization.

  • Scott Ling commented
    January 05, 2016 09:18

    Definitely need this, right now our product managers have to select 1 initiative for a feature, then when comes to reporting they are having to manually create a report showing the impact of a feature across multiple 2-3 initiatives and all goals...

    Wasting a lot of time that is better spent else where.

    It would be good to know if this will be implemented, as most companies have features that will span multiple strategic initiatives - even more so if they have department(local)/region/global initiatives that are heavily related to each over.


    For example initiative for a global roll out of a release, will have features in each localized area which apply to a local set of initiatives for that region as well as adding to the value of the global initiatives of the product roll-out which also adds to other company strategy, sales & support readiness initiatives.


    Once multiple initiatives are done, Aha, becomes indispensable for us and many other companies like us at a strategic operational level.

  • Karthik Rajagopal commented
    May 07, 2016 17:00

    Any movement on this? This is a really useful option. Features that can satisfy multiple initiatives can be on higher priority. 

  • Guest commented
    June 03, 2016 20:33

    I agree with all of the others who have posted on this issue. Many of our features are linked to more than one initiative. Having this information in the system will make it easy for us to determine the features that are helping to satisfy more than one initiative. It also will allow us to easily get access to the initiatives from the features and vice versa.

    Taking the example from the Fredwin Software (demo), consider the feature “Share places of interest in Italy”, this could be attributed to the initiative of "Launch Giro d’Italia site". However, it could also be linked to the initiative "Support Galileo GPS system" as that is the technology used to detect where you currently are to show the places of interest closest to you. Similarly, the initiative "Mobile Fredwin Cycling Tracker App upgrades" may also have to be adapted to support this initiative.

    I understand that the issue of restricting a feature to only one initiative was to cater for future plans for capacity planning. However, isn't capacity planning going to be driven at the feature level, irrespective of how many initiatives a feature it belongs to?

    I note that on Mar 20, 2015 it was indicated that you were 'likely to implement' this idea. Any idea when this is going to happen ?


  • Richard Parsons commented
    October 11, 2016 08:39

    I agree, it seems an obvious use case that a well-planned feature could contribute to several initiatives

  • Michel Besner commented
    November 09, 2016 20:43

    Yes this is an important one ... we need to have multiple initiatives linked to a feature !!! 

  • Mike Perla commented
    December 04, 2016 19:38

    get this done please :-)

  • Andrew Mackles commented
    December 13, 2016 02:37

    +++ for this feature

  • Guest commented
    January 12, 2017 23:43

    Our Company uses the Features board to track/manage "projects" as opposed to individual features. So the idea that features and Initiatives should only have a 1:1 relationship doesn't apply here. Looks like a lot of customers here are using aha in the same way.

     As such, we  need to be able to align "projects/features" with Product strategic Initiatives as well as Company strategic initiatives, so there is clear visibility. This becomes even more important as we utilize reports to communicate to the rest of the company and the board our progress against strategic objectives.

  • John Biltcliffe commented
    March 17, 2017 11:49

    This would be really useful for us.  We've found a way to work around for now which allows us to see what we need at a feature level, but we can't see features from the initiative.

  • Darrick Benson commented
    July 14, 2017 15:50

    This is a big need, especially for larger enterprise implementations.  Any status on when this is "likely to implement"?  

  • Markus Hraba commented
    August 02, 2017 15:12

    Dear AHA product people, please disclose where this feature request sits within your roadmap ;-) This is requested and pending since early 2015 and still customers keep bringing up their need.

  • Ian Aitchison commented
    October 05, 2017 11:27

    Really need this. Many planned features will support multiple initiatives but aha can't represent that.

  • nick bunte commented
    October 05, 2017 22:43

    We have many features which belong to multiple initiatives. This is almost a basic level requirement for us to track anything within aha!

  • Johny Wudel commented
    November 29, 2017 23:36

    For us an initiative is a specific area of focus that will help us reach a goal. For example, "create frictionless onboarding for customers" is an initiative. And then also "reduce calls to support" is another one. We could have a feature that we want to associate with both initiatives. 

    You can do this on a release. We'd like it on the feature as well.

  • Shawn Adams commented
    January 19, 2018 19:10

    This would help sell to senior leadership the desire to work on something by being able to show that working on one Idea or Feature is addressing multiple initiatives at the same time.  Senior leadership loves to know when something is killing two birds with one stone.

  • Ken Cantu commented
    March 02, 2018 15:45

    We have multiple initiatives at the corporate level and some features we're delivering span those initiatives even if they are secondary benefits. From the initiative level we have higher decision maker users who want to see a few of an initiative and all the features that help support and move that initiative forward in reporting. 

  • Chris Garner commented
    July 05, 2018 21:31

    I wish John Biltcliffe would have shared his work around.  We desperately need this

  • Guest commented
    July 25, 2018 16:38

    I very much agree with this! Has there been a decision? Seems like this has been "future consideration" for a long, long time.

  • Annette Edmonds commented
    July 25, 2018 21:10

    Prior to entering an enhancement request I noticed there are many asking for the same option which is to allow linking a feature to "multiple" initiatives.  I agree that there are many times that it would help prioritize, understand the where initiatives cross, etc.

  • Greg Koeka commented
    July 27, 2018 14:59

    This would benefit one of our primary Product tasks, stakeholder communication. When leadership wants to know how a feature helps us achieve our initiatives, and thus our goals, we can't show them the value of the team's efforts. This is fundamental for both a Product manager and the team.

  • Jerrold Emery commented
    September 05, 2018 16:44

    Are there any updates on this request? It certainly has a lot of votes and plenty of comments. It would be nice to see this item move forward.

  • Zach Robin commented
    October 02, 2018 21:06

    Lack of this feature is limiting further expansion of Aha! within our global organization. 


  • Walter Clarke commented
    October 03, 2018 12:41

    Please let us know when this will be available or not; either way we need to know. It will impact our use of the Aha! tool moving forward

  • K W commented
    October 11, 2018 03:10

    We're a Fortune 100 and love using Aha. This feature is important to us; any progress on this?

  • Johan Criel commented
    November 20, 2018 23:27


    Any feedback from Aha! side regarding this topic?

  • Harrison Lynch commented
    December 12, 2018 15:41

    In retrospect, only a madman would want this feature. 😀

    (But you were very kind in your explanation)

  • Ben Hampton commented
    December 12, 2018 16:54

    Thanks for the explanation!  Knowing this won't be implemented helps clarify how we should be best representing the initiative object.

  • Zachary Levin commented
    December 18, 2018 01:50

    This feature would really help us deal with a strategy aiming to integrate disparate product lines through multiple initiatives and consequently have major benefits to our prioritization system - identifying features tied to multiple key strategic initiatives

  • Yogev Barom commented
    February 20, 2019 14:08

    Thank you

  • Loic Bauduin Brunelle commented
    August 26, 2019 11:16

    The problem is to report a feature against multiple large initiatives.

    This idea refers one solution for this problem, which is to link a feature to multiple initiatives through the feature->initiative attribute. Understanding that this would break your solution, could you still provide a solution to the original problem "out of the box" / without requiring use of custom fields?

    What about including the "record links" concept into your reporting solution?

  • Loic Bauduin Brunelle commented
    August 26, 2019 11:20

    The problem is about reporting, this could still be solved without breaking the future development.

    What about including the "record links" concept in the reporting structure, so that we can pull related object data using the record links instead (or in addition to) the object hardcoded links?

  • Josh Tambor commented
    15 Jan 19:51

    Following on this would be helpful to get some additional beyond the above Admin response. I will say that adding a custom field is a good work around, however, it may become a large burden for an admin to manage a large amount of fields in time. With respect to the link feature, I do not think this a strong feature in its current state. It is a bit limiting in respect to how it is viewed. Given that the response was issued in Q4 2018, and that Aha has made some strategic choices around its position as an end-to-end management tool for strategy and requirements (i.e. inclusion of new workspace types), any additional guidance from the team is greatly appreciated

  • Scott Shultz commented
    04 Feb 13:48

    It is very limiting for a feature or master feature to link to only one initiative. In the real world it is very normal for features to be linked to multiple initiatives, as evidenced by the number of comments in this thread. Adding an additional custom field doesn't solve the problem. Please fix this limitation.