The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart from initiatives for a couple reasons:
Thank you for your idea. In addition to the option mentioned of using initiatives, another option would be to create a custom field or custom table (for Enterprise+ customers) to capture the related user journeys. The benefit of this option would be that you could associate a feature with multiple journeys (using a predefined tag custom field.) This would also allow you to keep your initiative rollup available to show strategic alignment of features.
One option for visualization would be to create a diagram using mockups. We have done this and it is quite effective.
Given the options above and other priorities, we are unlikely to implement this idea at this time. We hope you can understand.
The problem with tags is that there isn’t a “landing page” for the tag itself. For example, I can tag Epics with “Data Onboarding” user journey (implemented as a custom tag field).
Okay, the custom tag field is not a bad idea. That might work. I don't know that we need to use predetermined ones. Probably better to keep it open so people can easily create new journeys and just police them.
Thanks for your thoughts.