The story mapping capability is nice to have in Aha in order to take advantage of easily creating Aha artifacts/work items. However, until we have the refined user journey, we don't want any artifacts to be created. The purpose should be to allow for brainstorming/collaboration/discussion and don't want to have to do cleanup afterward. Also, because definitions of master features and features can vary, we want to be able to indicate the journeys and the activities and then come back and organize and select what we should identify for each of those artifacts. And not everything truly equates to one of those items as they are not engr work - they are work items for others to do and we utilize To Dos and release activities for that. Consequently, we are using flow charting tools instead and have stated to not use this feature as it creates too much clutter.