January Update - Intent Driven Design
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi all,
With the latest update released today, you’ll have seen that the new Intent Driven Design workflows are now fully available to all users.
This has been in development for around six months, with heavy involvement from our Insider Program to help guide direction and gather feedback as we moved toward public release.
I wanted to share a few top tips to help everyone get up to speed as quickly as possible.
Choosing a document type
When you create a new document, you’ll now see a dialog allowing you to choose the type of design you want to work in:
-
Part – A single component design. Parts can still be multi-body.
-
Assembly – Used to bring multiple components together to build an assembly.
-
Hybrid – The flexible Fusion workflow you’re already familiar with, allowing a combination of internal and external components.
All of this was technically possible before, but working in a fully external, component-based workflow was difficult for many users. That’s why this has now been elevated to a first-class workflow, allowing you to explicitly choose how you want to work from the start.
For those who prefer it, Hybrid remains fully supported, and you should see no change in Fusion’s behavior when using it.
Preferences and shortcuts
There is a new preference to pre-select the default design type. By default, this is set to Part, but you can change it to Assembly or Hybrid.
Once set, you can click Create New with minimal disruption. You can also use Ctrl + N to create a new document without showing the dialog at all.
For example, you could set Hybrid as your default, create a new document once, and then use Ctrl + N going forward to quickly create new designs without seeing the prompt.
Add-ins and scripts
You may notice some changes in how certain add-ins and scripts behave:
-
In Hybrid, all add-ins and scripts should behave exactly as they did previously. Please let us know if you see any differences.
-
In a Part experience, add-ins or scripts that attempt to create components are not allowed and will fail to execute.
-
In an Assembly experience, some add-ins may not appear. This is typically due to panel IDs needing to be updated.
If you encounter issues, please contact the relevant third-party developer. They can refer to the updated documentation to ensure compatibility.
Changing experience type
If you choose the wrong experience type, don’t worry. You can change it at any time via Document Settings in the browser.
The only limitation is that you cannot switch back to Part once components exist—you can only do so while the design contains bodies only.
That’s a quick overview of some key tips for working with the new experience types. As always, please let us know how you’re finding it and continue to share your feedback.
Here is a more detailed write up on Intent Driven Design.

Richard Stubley
Product Manager - Fusion Mechanical Design