SolidWorks Top 10 List and What’s New

I always applaud a CAD company, or any company, really, trying to really understand what their customers want. Forums are a great way to do that indirectly. You set up a nice area for them to talk to one another and listen in on their conversations, answer when relevant, damage control when needed, and mostly try to be humble and learn. SolidWorks has done this, and the Top 10 List is another way they are trying to connect with users. It’s a good thing. Programmers don’t think like CAD users. Product Managers sometimes get confused and need a check from the real world. Real hands-on-the-mouse users have a lot of information they would like to share, and SW would like to hear.

If you haven’t seen the Top 10 List, or haven’t voted, here’s a link. Go check it out.

My favorite stuff to write about is the What’s New list every year. You’d think there would be a direct correlation between the What’s New and the Top 10 List. Maybe there is and maybe there isn’t. We’ve heard from SW before about how new functionality gets into the software. Customer enhancement requests are one way, and I’m assuming that the Top 10 List functions as a weighted enhancement list. They look at the bug list, or reported problems, both internal and external. Competitive issues are another. If they see that Solid Edge has added some cool new feature, SolidWorks is likely to add it too. Items that come from the sales channel, such as a big potential customer really wants wiring, boom, it can get added like that. SolidWorks, like all companies, tries to keep their ear to the ground and be on the front end of the wave for new stuff. They added ScanTo3D 10 years ago or more, even though it was very rough.

One time, quoting Steve Jobs, the execs at SW claimed that a lot of functionality was added to the software on SW’s own initiative. We got stuff we never asked for because “customers don’t know what they want“. There’s a part of me that is extremely offended by this kind of arrogance, but then there’s part of me that recognizes that genius is not always on the customer side of the equation. Arrogance (thinking he could cure pancreatic cancer without doctors) ultimately killed Jobs, but in a way he was right. Would I have known to ask for the Boundary surface when we already had the Lofted surface? Would I have asked for Intersect when we already had trim, mutual trim, cut with surface, and boolean tools? Maybe not.

So sometimes, SolidWorks adds stuff that they come up with on their own. Users tend to focus on solutions to immediate problems, but if we open that up a little, you might be able to come up with something Now if that’s a new color scheme for icons, or another renderer, we all know how we feel about that stuff, but if it would wind up being an answer to Tsplines or Power Surfacing or something like that, well, I’d be pretty happy about that.

If you read through some of the more popular items, there are 2 items related to the problem of SolidWorks flipping things (mates, planes, tangencies, etc), 1 actual geometry creation enhancement (3D sweep), and several admin type requests (infinite undo, service packs, multicore stuff…). They even managed to come up with a couple of ideas that were so misguided that I actually voted against them. There’s no end of complaining about simple things, whining about a couple percentage points when there are such larger gains to be had. Splitting frog’s hair.

What does this say about where SolidWorks is in the lifecycle of the product itself? Is it still a young and growing company, or are they riding this wave until it crashes on the beach? All the first string players went to Onshape or somewhere else. Even most of the second string is gone. The CAD world is full of old companies/products, with a couple of exceptions. The old guard isn’t really doing anything exciting these days. Even Onshape, the one I hoped would bring some exciting stuff, pretty much gave CAD a pass when it came to making a new CAD product, and innovated mostly on the file management side of things. Interesting, but kinda lame.

I’m really surprised that the SW Top 10 List didn’t include things that make history-based modeling and parent/child relations less rigid, or things that allow you to escape those structures altogether. They have added some mesh capabilities, but not really on the creation side. There are several directions CAD can go in the future, and every direction would be away from history-based tools.

I’d argue that the users that are left (or at least the ones making noise) are also not the first string users. Judging from the Top 10 List, they just don’t have much imagination. They seem content with managing the over-the-hill-slide of their pet program.

What surprises me most about returning to SolidWorks users is that more people aren’t fed up with the limitations and frustrations of history-based modeling more than they are. This says to me that people are making simple stuff. Really simple geometry, to the point that they aren’t seeing any of the drawbacks of history-based modeling. These are actually the people who would benefit the most from direct edit or its extension Synchronous Technology.

I wrote about problems with history-based CAD long ago, and SolidWorks did add some things that help manage the history and parent/child stuff. They added the Freeze bar and the Dynamic Reference Visualization.

I don’t really expect SW at their advanced age to suddenly come up with something like Sync Tech (although the Solid Edge product is the same age, and they managed to reinvent their product without killing it), but they could act a little more energetic to come up with ideas that “customers don’t know they need”. There’s just so much maintenance, and messing with outlying areas, CAD has become boring.

10 Replies to “SolidWorks Top 10 List and What’s New”

  1. My main concern is how few votes are recorded. Everyone seems very enthusiastic by the TTL, but this year, the top idea has less than 100 votes at this time. For a software that has millions of users, this number is insignificant.

    A lot of ideas are good, but how much weight should be placed on the number of votes recorded?

    1. Alin, yeah, that’s a great point. I wrote some time ago about all of the “dark matter” in the SW universe – lots of people you never hear from online or in user groups or anywhere. Hard to imagine.

    2. @ Alin-
      Actually, I don’t think the voting numbers are terribly off from industry standpoint. To be honest I don’t know of many software OEMs that have this type of forum for users to vote up or down.

      In the case of SW, it relies 100% on the forum participants- not the users themselves. Siemens had a decent process that was worked between PLM World SIGs and the Siemens Product Managers. Once a suitable list was compiled, condensed and then weighted a ballot would go out to the licensed customers (current). The problem here is that the notice went to a single person- whomever was the contact on the license file- and rarely didn’t make it down to users. So while the listing was a sound list the voting mechanism had its issues.

      1. Thanks for the info, Ryan. What else can SW do to ensure users are aware of the TTL? It is always hard to communicate with customers, who have a hard time separating the marketing heavy emails and the technical ones.

  2. @Ryan,
    I think I meant it was a good place in that it’s a place where you can get a lot of feedback. Not necessarily that it was really well thought out feedback.

    Plus, I had this thought in the middle of writing that just insulting my readers isn’t a great tactic. I might have to rethink a few things…

    SolidWorks folks get the benefit of having a lot of smart people talk it over and give the ups and downs. Most people on the forum just blurt out ideas without it passing the committee test. That’s where devil’s advocates like you and me come in, I guess. Forum members only get one side of the story without the benefit of learning really why a particular idea like infinite undo seems obvious from a conceptual point of view, but a massively bad idea when it comes to the practical nuts and bolts. SolidWorks doesn’t see any detriment to leaving customers hanging like that, they are not obligated to remedy a lack of facts. I wish they (meaning some sort of customer liason person) were equipped to educate users on things like this. Unfortunately, customer liason types are usually isolated from the technical side of the business. So there’s this huge cloud of …not ignorance, really, but… lack of facts that surrounds enhancement requests and knowledge of how things work.

  3. Glen, yeah, I think it just didn’t make sense to me from an English point of view, not the functionality. Anyway, it depends on what kind of parent it is. If it’s a sketch plane or an end condition, you can’t really have a feature without that kind of parent. If it’s just a missing relation or dimension, then that’s ok. I think we do that now with “dangling” condition.

    Wouldn’t that drive people crazy? I mean SW users are hypersensitive to flags in the tree. I don’t think you can have it both ways with parent/child stuff. You either have it or you don’t.

    1. Matt,

      I agree that there are certainly circumstances where you can’t suppress a parent without suppressing the child, but as you mentioned, for a missing sketch relation, or dimension reference, it should certainly be do-able.

  4. @Matt
    I disagree with you. I don’t think a forum area is good place to start this process. As I mentioned before, most people don’t know what they really need. If so, they have a difficult time explaining their request. SW should provide a template for each request and then build the comments off of the template. This way everyone understands what is required to flesh-out a real enhancement.

    Ryan

  5. @Glenn
    I tried to understand the request but didn’t get it. That might be part of Matt’s concerns with this type of open forum for requests. Very few people understand how to actually word a request.
    I am assuming you meant to say, “Provide an option to allow children features to rebuild regardless of the parent status.”
    This would be interesting but how do you show holes, fillets, chamfers and other child features if the parent is suppressed? Think about this. If your parent is a secondary extrude and it is suppressed how do you keep the children active/unsupressed?
    Maybe this can be done but you would like to see the failed geometry in a translucent state until it is repaired and then it would shade like the rest of the model?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.