Need specific support for user journeys

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:

1. Often initiatives are used to group features/master features that are functionally or structurally related.  The features contained within these typically map to only a single initiative.  However, a single feature can potentially be used within many different user journeys, for one or more different personas.  Generally you want a feature to be mapped to an initiative, and ALSO mapped to one or more journeys, simultaneously.  So a journey is a distinct way of grouping features, orthogonal to master features/epics.  I want to be able to roll up my features in multiple ways and either view them by initiative, or by journey.  I shouldn't have to be limited to one organizational structure or the other.
2. User journeys by definition represent a directional graph of steps.  This means there is a time-based relationship between steps would not normally be represented by just throwing them all into a single initiative bucket at random.  There is an order to them, and potentially loops and different endpoints.  This could be complex to represent, but I think it's a quality that is important and should be explored when defining a journey feature.  I could see this as a follow-on feature to add to journey support--it would be a huge help just to be able to group master features separately by journey and by initiative.

Thanks!

/mike