What is the challenge? |
Remembering that, typically, end-Customers giving f/b or suggestions -- and product owners/managers -- are unknown to one another. End-Customers value transparency in the treatment of them and the suggestions they make. Currently, end-Customers' only way of second-guessing the product owner/manager (PO/PM) to gain an insight into their priorities, is to filter ideas on the ideas board by In development status and, less-concretely, Planned status. Supposing In development gives the end-Customer insight into the current sprint and Planned status insight into the backlog. Then, if most of what's there is all about (for example) the current flavour of the month (currently AI, previously big data), end-Customers can set their own expectations when putting-forward ideas on say, unrelated bread-and-butter matters like privacy, etc. So, the challenge is knowing whether an idea (before it's even submitted) is likely to fall on unreceptive ears, or, after it's been submitted has fallen on unreceptive ears. |
What is the impact? |
|
Describe your idea |
(Relates to public-facing end-Customer) view -- not internal MI to Aha's Customers) In short: Provide two additional idea 'statuses' auto-set in the absence of assigned status, to show that an idea was "read". |