Here's a question I'm facing re an upcoming product release - I've picked a way to go but am hoping you guys (and girls) can validate it for me.
We have built a product that is going to be offered in 2 flavours - Standard (very limited features, but enough to satisfy simple use cases), and Advanced (lots of features satisfying very complex use cases).
PM believe that maybe 20% of the users who download the Standard product from the web site will ultimately migrate to the Advanced version (this % hasn't been based on any real user studies; its pretty much just their best guess). They believe the other 80% will be quite happy with the much cheaper Standard version.
So the question is how best to educate the users of the Standard version of the great wealth of features in the Advanced version, in case they want to upgrade.
We now have 2 firmly entrenched factions within the Development team and I'm being asked to adjudicate. One side wants the Standard version to be just that - ONLY the standard version, with no hint of the treasures in the advanced version. The other side wants to ghost the Advanced features in the Standard version (for example, list the other middleware transports supported by the tool in the menus, but dim them so they can never be selected) so that the Standard users can see what they're missing and rush out to buy the Advanced version.
I'm inclined to go with the first option, and find other ways to educate users of the Advanced product's capabilities - like information panels during installation, documentation, and other marketing materials. But being the last Usability resource standing in my company, it would be nice to be able to bounce this off some like-minded folk! Has anyone had a similar situation and been able to gauge any user response to either scenario?