The above ideas are fantastic. I'd also add that you could show common tasks and goals and associate them with the appropriate software package. Users purchase software to solve a problem - give them some examples of problems they can solve with each of your products.
This article by 37signals highlights this idea: http://www.37signals.com/svn/posts/1582-design-in-progress-choosing-the-right-product 37signals, however, is in search of a new design for this process (i.e. software feature charts are out) but you probably don't need to reinvent the wheel, just make it easy to understand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=39255 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
