Implementing feature innovation in the Community is a fantastic idea, but for those of us whov’e done it, ‘Ideation’ is an advanced play that requires internal readiness, commitment and overall org-maturity to sustain. It's advisable to wait until you have enough buy-ins, especially for SAAS companies embracing Community for the first time.

On the other hand, 'Product Updates' is a straightforward play right from the start, since you are already documenting your Releases, Marketing your features, etc, it is a straight out of the gate play.

However, the current configuration of Product Areas filters doesn't allow for a phased launch, hindering the ability to prioritize 'Product Updates' before 'Ideas'.

There is no way to control

“I will start publishing Product Updates for product modules X, Y, Z, but not open up Ideation for them”.

That basically means, as soon as you enable Product Updates for certain product areas, you are automatically committed to accepting Ideas, as per the UI, regardless of your readiness to begin Ideation.

So we should be able to make ‘Product Area’ filters selectively available as we chose between the two modules, Product Updates and Ideas. Need that additional level of choice.