If you can develop a group that is even incrementally better at communicating/collaborating, then that group will be GEOMETRICALLY better at developing products. It's not simply about just getting on the same page so that skills are additive, it is about getting inside each other's heads so that the product of skills goes beyond being additive or even multiplicative and becomes exponential. Many product development efforts suck because no one in management understands the importance of building engineering communication -- one of the ways to do that is to ensure that the team is not only CAD-enabled, but CAD-literate ... your job as a CSWE is rapidly develop and extend proficiency in others to the point of where their CAD literacy reaches the "power-user" level. Product development is about ideas ... stories, jokes, metaphors, plays, novels, films. Managing product development is about managing culture -- it is not about managing humans, per se, but managing things like the group's development of language proficiency because language proficiency determines whether you develop from an advanced culture of renaissance thinkers that come up with the plays, sculptures and flying machines OR you develop from from trailer park full of beer-swilling coach-potatoes that just watch and or maybe try to find their stash and old bong.
If I have an idea with any degree of complication, I will certainly need to tell a story, i.e. use an animation to describe how components of the assembly fit together and possible function mechanical [if the parts move]. The old way is just take a sketch of an idea out to the shop ... use bandsaw, grinder, drill, machining center, lathe, welder, glue gun, duct tape, modeling clay and assemble it to see if it might work ... great in the old days, but that just takes way too much time now ... I will still want to build a real prototype, of course ... but time in the shop is extremely valuable and progress is slow; CAD software and workstations are more affordable than ever ... so it's time to THINK DIFFERENTLY because you have different feasible possibilities now. Using SolidWorks [or other similar CAD systems] I will likely want to analyze different variation on the theme of similar ideas with different simulations ... so before I even share my idea with others before we narrow our selection of what to build, I need to express a relatively RICHLY DEVELOPED idea in CAD.
Expressing richly developed ideas for the first time is not that easy ... it can be very frustrating, so people learning the language need to keep their expectations in check. Shakespeare's first words were probably something like "mama!" or "poopoo!" but those first words were a start. Taking it further one step at a time is what determines the ultimate value of your work. Shakespeare's deeper philosophical stuff like "To be or not to be, that is the question" didn't find their way onto the page until a few years later ... and maybe, those lines really belong to one of his collaborators ... the lesson is that if you do you stuff well, people will be riffing on your better ideas for a thousand years [and you might get more credit than you deserve].
After you accumulate the skills in the language and develop [or steal] a library of good ideas as templates, prototyping in CAD is LOT, LOT, LOT faster than building something in the shop ... it get's even faster if you can collaborate with others who have a strong command of the language ALSO. THAT is why I am thinking about the even better ways to rapidly make others proficient in the language. SolidWorks is not a simple language, because the ideas that are expressed are reasonably complex.
Consider even a simple exercise [from the first chapter of the text] like making a flat bar with a pattern of holes from an aluminum alloy ... the hole pattern might be part of a mating assembly, so you need to assume that it is going to be important -- you need to develop good habits from the start to get the "obviously unimportant" details right because some day those details will matter and the associativity property of models will penalize you severely if you learn to take the easy way out and skip double-checking the details. Also, the material properties could affect a simulation, so they need to be doublechecked. If you are going to do useful things with this flat bar, you have to be very careful ... it's not just a simple CAD exercise, CAD is about ideas and ideas matter more than ever!