Although the topic mentions SOLIDWORKS, this discussion is not limited to any particular software. These principles apply to learning and mastering any engineering or design software.
Quite often, people ask me, "How do I become better at SOLIDWORKS?" or "How do I become an expert?" Yet, when I try to assess their understanding, many are still far from the intermediate level.
I won't summarize every conversation I've had, but based on years of learning and experience, I'd like to emphasize a few points that can help you break out of the loop.
1. Understand Design Intent Thoroughly
Design intent is the logical way of creating sketches, parts, and assemblies so they respond to changes with minimal rework.
Key aspects include:
- Constraints
- Feature order
- References (at all levels)
- Equations
- Assembly mates
A great modeler is not necessarily the fastest modeler, but the one who creates robust and resilient models.
Unfortunately, many YouTube channels unintentionally promote poor modeling habits by focusing on speed and shortcuts. Choose your mentors and courses wisely, not simply the ones that are easiest to find.
2. Develop a Holistic Understanding of the Software
Don't limit yourself to just the features required to complete today's task.
Learn every module and understand what it is capable of. Even if you don't use a particular function regularly, knowing that it exists broadens your problem-solving ability.
3. Experiment Relentlessly
Once you're familiar with the features, start experimenting.
This is the boring part—and precisely where growth happens.
Through experimentation, you'll:
- Understand how the software actually works.
- Encounter and solve numerous problems.
- Discover the strengths and limitations of various tools.
- Build intuition that cannot be gained from tutorials alone.
If you can embrace this process, you're already ahead of many users.
4. Use Tutorials as Exploration, Not as Truth
Once you understand the software reasonably well, start watching tutorials.
At that stage, tutorials become a source of alternative approaches rather than the approach.
When people watch tutorials without understanding the underlying functionality, they often assume:
"This is the only way to create this model."
In reality, there are usually many valid methods. Each comes with its own trade-offs.
5. Seek Feedback and Accept Criticism
Join forums and communities. Ask questions. Seek guidance.
You don't need constant mentoring. Sometimes a few good pieces of advice are enough to change your trajectory completely.
Specific to SOLIDWORKS
Spend time learning and experimenting with:
- Equations
- Configurations
- Design Tables
- External References
- Top-Down Assembly Approaches
- Structure System
- Large Assembly Handling
- Surfacing
These areas separate casual users from advanced users.
An Example from Furniture Design
Recently, I've been working in the furniture industry.
The inputs are often similar, but the required outputs vary:
- Some clients only need 3D models.
- Some need CNC-ready parts.
- Some require only assembly drawings.
- Others need complete part-level documentation.
Because the deliverables differ, the modeling strategy changes accordingly.
Take a simple drawer construction, where the bottom panel fits into grooves on the surrounding panels.
Now ask yourself:
How many ways can you model this?
The answer depends entirely on the purpose of the end results.
Few questions to consider:
- Will this design be reused?
- Do separate parts need revision control?
- Are drawings generated from it?
- Is only a 3D representation required?
- How easily should variations be created?
Possible approaches include:
- Multibody part
- Assembly with or without equations
- Configurations for size variations
- Indent and Split features
- Top-down in-context modeling
- Intersect feature
- Virtual components
- Full-size panels with cavities cut afterward
Every approach has advantages and disadvantages.
Compare them based on:
- Ease of creating variations
- Ease of implementing changes
- Drawing generation
- Reusability
- Data management
- Performance (this is very simple model hence it might open and rebuild quickly irrespective of modeling method)
This is where deep software knowledge becomes valuable.
Mastery Is Built Through Boredom
I know all of this sounds boring.
But mastery lies on the other side of boredom.
Over time, your brain begins operating like Sherlock Holmes—mapping through the available commands and strategies to achieve the desired outcome.
Yes, AI can help. But nothing replaces the hours spent thinking, experimenting, failing, and understanding.
That grind is worthwhile.
A Final Thought
One mindset I strongly recommend avoiding is:
"There must be something wrong with the software."
or
"This is just a limitation of the software."
If a feature is intended to perform a certain task and the result is incorrect, don't immediately assume the software is broken.
These systems run on mathematical engines created by humans—not on assumptions or probabilities.
Be curious.
Be restless.
When errors appear, investigate them.
Keep asking why.
If you maintain that mindset long enough, one day many things will become so obvious to you that they appear like magic to others—but routine to you.
Good luck with the journey.
Keep learning. Keep experimenting. Explore the wealth of resources available online, and follow the great people in this community. 🙂
I feel I am already on the verge of retirement while posting this. 😢
I would welcome suggestions and add in the post with credits 🙂
