I love this! One general piece of advice is to create a CTA to capture the product update task (potentially assigned to the product team) and report against those CTAs.
As a more complete suggestion, here is one possible approach.
1. Create a Survey 2.0 survey that includes the questions you want to ask your customers and an additional question marked Internal with info about the need for a product change
2. Using a Survey Model in Journey Orchestrator you distribute the survey, do followups etc. to get the customer to resond
3. Once the customer responds (so past the "Responded" step) you will notice that the Conditional Wait step will have the option to put conditions on the responses in the survey. First, you have a step where you create a CTA if there is a detractor response on the NPS question (or whatever condition you want)
4. The person handling that CTA reviews the survey response, potentially calls the customer to discuss or whatever. Then that person dispositions things by filling out the Internal survey question
5. Back in the Journey Orchestrator Program your next Conditional Wait checks on the status of the Internal Question (after waiting a period of time or until the first CTA is closed) and based on the response to that question creates a CTA for the Product team, or whichever group is responsible for the followup based on how the survey response was disposed.
Lots of variations, of course. But it is fun to think about all the power you have with Journey Orchestrator and Survey 2.0.