Jan 29, 2019 - 01:07 PM
I like your mode of thinking.... by reducing the options from many to few, like your example of Project 2010 to Project suggests (though you may end up with two options, Project Standard and Project Professional) you have the ability to offer the end user a simple 'Amazonesq' catalog of choices that you can fulfill from your available stock as applicable. One thing to note, you should take care to not get to high level, as I reference above allowing the user to simply select 'Project' leaves room for ambiguity as it relates to the version. The same can be said were you to offer 'Laptop', what happens when they need a specific category of 'Laptop', Mac vs. Windows? By thoughtfully planning out your request catalog you can make both the user's and IT's lives a little easier while maximizing asset allocation and ROI. Good luck.