How is wish list being used by JMP developersI was first going to post this to Community discussion, but I thought it might be enough to write it here to smaller audience.
I have had (and many others) items in JMP's wish list for some time now with status still being New. It seems like currently newer New Wish list items are being quickly taken some sort of notice and changed to at least Investigation status and old are just left there with New status. How is Wish List being used currently? Is it being worked from new to old ones?
Seems like the current "notice line" is currently somewhere here (page 11 when sorted by date) https://community.jmp.com/t5/JMP-Wish-List/idb-p/jmp-wish-list/tab/most-recent/page/11
Currently I don't really bother writing wish list items because old items aren't being noticed at all (or at least it feels like that) and it does take quite a bit of time to write good wish items. I just write my own workaround functions/add-ins and use those if needed.
Re: How is wish list being used by JMP developersHi @jthi and @ih, thank you for your comments, and for your active involvement in the JMP Community. Let me assure you that the JMP wish list is an integral tool for understanding user pains and challenges and for capturing potential improvement opportunities.
JMP Product Management has recently implemented a new process for reviewing and evaluating wish list requests, with the goal that all incoming requests are acknowledged and recorded in a timely manner. We then evaluate (or, investigate) the requests, often with the developer, to determine feasibility and priority relative to current projects and the overall JMP product roadmap.
Our focus has largely been on staying on top of incoming requests, but we're also reviewing, evaluating and prioritizing past requests. This can be a challenge. Some past requests are no longer valid, some are addressed via add-ins, jsl or workarounds. And, others don't align with our current product roadmap or are technically challenging given our development framework and tooling.
While we can't act on everything, weâre working on a process to make sure all new and highly kudoed requests are taken under consideration.
Note that a key challenge in evaluating requests is having enough context and background information. For example, when wish list posts include clearly defined problems, screenshots, sample jsl code, and information on how important the request is to you and/or your organization (show stopper? nice to have?...), it is much easier to evaluate and prioritize.
Please let me know if you have any questions, and thanks again for your contributions to the jMP Community.
Mia
Re: How is wish list being used by JMP developersI'm guessing here:
Every time I've inquired about this I'm told that it is used, and I've been asked by developers to add items to this list. I suspect there is not a formal review process with any sort of constrained timeframe though. I wonder if it is up to developers or product/platform managers (probably not a job title) to look through the list and find things pertain to them.
Re: How is wish list being used by JMP developersThanks for sharing your thoughts on this issue. I will acknowledge that in the past we did not do as well as we should have on responding to and reviewing the wish list requests. I have had this experience as a user, and in my current role as a Product Manager I wanted to us to improve that experience for our users.
@mia_stephens described above what we currently doing. I wonder if we should probably create a Community Blog post on what makes a good Wish List request. Because we need to prioritize what we work on, knowing the "why" (what is the problem you want to solve) is as important as the "what", and many times the wish lists items don't provide us a lot of information about the the "why". It ultimately comes down to balancing what our users say they want and the priorities and plans and resources we have within JMP.
We value the input of our users very much, and while it may seem that your wish list requests are not heard, I want to ensure you that we do look at them and we are continuing to seek to improve the process we use to manage and review the wish lists.
Re: How is wish list being used by JMP developersThanks for chiming in @SamGardner! A Community Blog post on what makes a good Wish List request is a nice idea!
Re: How is wish list being used by JMP developersHere are some of my thoughts and ramblings:
Yes, establishing some criteria for how to submit a wishlist item sounds appropriate. Don't forget to view this from the perspective of the customer, not just the developer.
I think, though, this does not address points made above by providing some sort of status to the submitted wishlist item. I have found myself not submitting wishlist items. I tried a couple of times and got no response or follow-up...so I gave up (of course maybe my idea was a bad one). Also, it is very challenging for us users to review the list to see if the wishlist item is already suggested (although perhaps worded differently...search on what?). The "kudos" idea, perhaps is useful for prioritizing, but honestly I don't go through the list and vote. So I wonder who does? What is the process? How could this process be streamlined? It appears as if the items are organized based on developer categories (New, needs info, stay tuned, implemented) vs. organized with the user in mind with topics, subtopics, etc. It could potentially be quite biased to a certain type of user. Doing an actual survey of potential wishlist items may be appropriate.
Re: How is wish list being used by JMP developersThis reminds me of a discussion some time ago: one way to promote these would be to display them on some sort of a support page for each platform. Imagine that you write a post that references Graph Builder, that post could have a link to a graph builder page, which in turn has links back to discussion posts, blog posts, wish list items, support pages, and other info related to that platform. Now users would be more likely to find the wish list items they care about.
Re: How is wish list being used by JMP developersThe promotion idea is on our roadmap for 2023 now that there is slightly more consistency between tags/labels throughout the Community.
Re: How is wish list being used by JMP developersInteresting.
Amazon has a mechanism to show me things I've purchased and ask me to rate them, and offers a tiny reward (in the form of a really bad dad-joke) after every 5 ratings.
Maybe instead of popping up the current rating screen,
you could ask to have several wish list items ranked. Maybe get one of the DOE or consumer survey developers to help.
-----------
Please take a moment to help us organize our wish list by giving a kudo to an item you might find useful:
o No thanks, or None of these
o Take me to the big list
o Show me three different choices
Thanks! you are just 3 ratings away from the participation badge. Want to do another?
