Hey everyone,
really excited to hear how others are tackling this concept or what your opinion is:
Our product team is currently revisiting how we gather insights, form ideas and shape features - the whole shebang. We started out discussing and mapping the most common and straightforward chain of events in product discovery and JIRA is a great tool to visualize that road:
Collect insights from users, form ideas, discover ideas and shape them into features. Simple enough.
But we are now at a point where we see the needs to combine this process, that is very product management centric and somewhat isolated internally, with our other internal processes for software engineering.
One thing we are really struggling with in this early stage is our understanding of system improvements, so updates to our architecture or infrastructure, and how they connect to ideas and features.
Contrary to e.g. feature requests from users, these come up in different discussions and almost exclusively internally. The impact that system improvements have on our users is, lets say, less direct than validating and implementing a feature request.
Anyway, my post is already long winded and most likely bizzare. On the off chance that this was somehow understandable, I'd love to know how some of you were able to use JIRA to bridge the gap between Product Discovery and Dev Environment, especially when it comes to system improvements.
Best, Benedict
