Related Posts
What’s it like at Camp J these days?
Additional Posts in Product Management
Preference and viewpoints on B2B vs B2C ?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.



Epics -> Features -> Stories
In collaboration with engineering. I will do story mapping for larger efforts with them to talk through what they think the work is and where the bulk of the effort will go. Then we can take the story map and distill that into tickets more easily. My years of experience mean I can often guess what is a “manageable” amount of work for a story but I’m wrong often enough I try to work with an eng counterpart when mapping the work.
I find it easier if I have a user flow in front of me. Epic is the big chunk that you have on the roadmap. Features are... big steps user has to take - login, payment etc. Stories - what user has to do step by step in the feature. As a user I want to be able to: register account, receive verification email, enter my email and password, recover password. Then for each story you might try to dive into tasks, but those would be high level strokes to kick it off with the engineering team. They are the ones responsible for the tasks, but you can help with the bigger ones.
We do the typical epics -> features -> stories + tasks, also still use releases to plan and ship functionality.
We actually published our own framework to show how we work: https://www.aha.io/roadmapping/guide/templates/create/the-aha-framework
Curious what you think about it!
Great try
I would really consider user story mapping. Take a look at Jeff Pattern's book "User Story Mapping". Alternatively you can also consider the jobs to be done framework as another way of breaking big and scary into small and manageable.