Regarding our (PTC’s) “file-based approach”…I’d say your commentary is partly accurate. That is, PTC’s solutions for social product development use and augment the social computing capabilities of SharePoint. In this respect, it’s fair to say that since a fundamental concept of SharePoint is file-based collaboration, then, yes, PTC’s approach takes a similar tact. However, the fact that Windchill ProductPoint can/does assist in the more fluid design stages of PD is not incompatible with the point of people-centricity. Even though the focus on **processes** may be less emphasized in these early, ideation stages, there is still often (though not always) a need to share product data. That said, it’s important that the system be able to deal with such data, which, as we all know is its own special animal — structured files with numerous interdependencies. So, even though idea management/rapid info exchange may necessarily be averse to rigid processes, often these functions still need to share and maintain the integrity of (structured) product data in order to be successful.

Phew. Long winded but I hope it made some sense.