Windchill works great if you are a content consumer. A content consumer can freely delete workspaces as there is nothing they need in them and create new ones to load the currently desired information.
In a collaborative content creation environment, Windchill is frequently a hassle.
While I understand there needs to be a lot of redesign to do so, content creators need a system that pushes changes, not waiting for participants to pull them. That is, if I'm working on a complicated assembly and someone else on the team checks in a new version of a part that's in that assembly, then Windchill should push that update automatically to all the Workspaces that item is in and the active Workspace should flag Creo that a new version of the part should be loaded into session.
This means part files and meta-data.
Flagging is required for those working on As-Stored data, but that could also be handled with a "Don't Update" flag on the Workspace.
Instead, in a team environment, Windchill withholds new information unless specifically requested, leaving a pie-in-the-face / rug pulling situation. This is especially true for family table management where Windchill won't automatically gather (at least through 9.x) all the members of a table for Update that are in the Workspace. Instead it's like HAL 9000, "I'm sorry Dave, I can't do that," followed by a lengthy separate search for all the individual family table members because Windchill isn't programmed to update the instances when the generic alone is chosen.
Another place for confusion is where an unwanted change is made.
The choices are Update and Add. In Intralink, where a lot of people started, Update would overwrite the Workspace version with the Commonspace version, discarding unwanted changes. This is not the same behaviour in Windchill, causing no end of problems for people during their learning transition period.
There should be a clearly defined operation, like "Restore" that would take modified items and restore them with the Commonspace configuration. Software developers may love overloading operators, but humans don't do so well and benefit from clear differences in descriptors and vocabulary that doesn't change meaning.