even if a PM sets an idea to not-planned it should be possible to vote on it.
if a idea is not planned but still gets contant votes from customers it will show the clear need to the feature, and might change priority on the product timeline.
Absolutely, I tell that to everybody who wants to listen. Once the PM marks the idea not planned - it just kills the thread and the idea. Furthermore the PM never pays attention again to this thread nor updates it with feedbacks or progress reports ..... potentially a wasted good idea Another problem is that someone seeing this 'not planned' might get discouraged and moves on to another topic .... instead of contributing their thoughts. This is very very very sad and one of the main reason I do not like the current community "enhancement request" process.
The other challenge is how to word an idea so that people understand it and vote for it before they desperately need the solution
I'd do away with the status 'Not Planned' completely
Perhaps the only valid status should be "Delivered, Duplicate, Under Review, and New"
well, if for example things get asked like to build in a online-shop system in to a monitoring solution or something like this you have to be able to close the idea.
This idea is Not Planned.
The reason we have the "Not Planned" stage for ideas is because we need to have an end of life stage for ideas that will not be implemented. This removes the ideas from the Product Managers' queues once a final decision has been made, and allows them to focus on newer ideas. For ideas that are not currently possible but may be in the future, we have the "Wish-Listed" stage, which allows voting and implies that the Product Managers will review the idea at a later date for feasibility. Check out this document for more information:Summary of CA Ideation Process.
its important that every PM etc. is knowing this. because not planned might be just now, but might change in the future.
Yes well spotted AaronRitter, it seems like the PMs have not been keeping up with all the enhancements in Communities (it's hard) but it sounds like that the Not-Planned should only be used rarely - when a suggestion or proposal is completely out-of-scope (e.g. Enhance CA-1-Tape management to include CD and DVD Movie collections). The feedback I've heard from customers when they see an idea moved to not-planned (especially where there is no rationale/discussion of the decision is heart-breaking. Many of them just give-up and are not tempted to return - it might have been a silly idea, but more likely it was just badly expressed. Turning an idea into a crafted deliverable User Story is a bit of an Art - but as it turns out, one that the PMs are supposed to be good at - instead of rejecting ideas, the PM should be working to refine the story to an acceptable wording that sells the value. Now as an idea on Ideation, when that crafted piece is finished, could there be a way to promote/replace it as the ideation description so it becomes the headline for anybody searching (a bit like the way Document postings can have a version history?
You are absolutely right. We need the PMs to actively manage the ideation process. Many ideas might not have enough context or are similar and could be worked on at the same time or even replaced at once. At CA World I called this a "roll up" of ideas to gather more focused voting and in larger numbers (instead of many with few votes). However, I like what you said better. The PM needs to be inquisitive and restate the use case in light of the plans or prioritization. A more focused discussion could be pursued in the less public Beta channel. Some requirements might evolve over a couple releases as we customers see the sprints or understand the strategy better.
I agree, Mel. The best option to preserve an idea and allow continued discussion is to wish-list it. For ideas that are out-of-scope and are likely to never, ever be considered, it's better to get that info out there and to indicate that it is not planned. It's critical that we are transparent and open with our customers and that we empathize with them, too. I would suggest a DIRECT conversation with any customer who is so passionate about an out-of-scope idea that they might disengage per the thread here so that the product manager can understand the root of their problem. Maybe that discussion will lead to an alternative enhancement request that is TRULY feasible or perhaps it will be the seed of a new product idea! Communicate with your customers - have a conversation. It really can lead to amazing new ideas!
Retrieving data ...