& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:08
The easiest way to assess your current workflows is to watch your team work.
00:13
While watching them, you may want to ask them questions about why they do things the way they do.
00:19
Understanding why they do things one way versus another, helps you make more informed decisions on what to change and what to leave the same.
00:29
As you watch, document what you see.
00:32
Workflow diagrams can show both the steps and the decision points that your teams go through.
00:39
A typical workflow diagram will show steps in a rectangular box with decision points indicated as diamonds.
00:48
Arrow show the connection between the steps and indicate when the process repeats.
00:54
Adding text to the decision point arrows help your team know when one answer leads one way,
01:01
while another answer leads them down another way.
01:06
If you can show swim lanes in your graphs, then it becomes clear on where teams interact with one another.
01:15
This becomes more important to illustrate when teams start using the right technology for the task they are responsible for completing.
01:26
Don't forget to document the explanations of why they do the things the way they do.
01:32
If they name files a certain way, ask them why.
01:36
They may have already made arrangements with other teams on how to name work sets that is not documented in the company standards.
01:45
The is a great time to update those standards to include best practices that are already in play.
01:52
This is also a great time to ask your team if they are open to changing their workflows,
01:57
that will make their work more efficient in their day-to-day roles.
02:02
Use the provided checklist to help capture as much information as possible.
02:08
Ask things like, "What software they're using"? There may be technology that they've implemented that you aren't aware of.
02:16
Ask them if they're working in teams or if they're still working in silos. If they are working together, what could be improved?
02:25
Are the team interactions efficient? If not, what would you do to make them better?
02:33
Which teams need training to get them working more efficiently using the technology that they already have.
02:40
And is it important to update that training?
02:44
Is everyone properly following both internal and external standards,
02:49
or what project requirements or internal organizational requirements do you need to consider?
02:56
Who are your key stakeholders and how do they feel about the efficiencies they see today?
03:03
Who are your power users? These are the people that know the ins and outs of the software and your projects.
03:10
Figure out if they're willing to champion the changes coming their way or if they will derail them.
03:17
Finally, don't forget to calculate how much time the current workflows take.
03:24
This will help you later on show the time savings to stakeholders.
03:30
I guarantee they're going to ask about the return on your investment before they give you more money to renew that software next year.
Video transcript
00:08
The easiest way to assess your current workflows is to watch your team work.
00:13
While watching them, you may want to ask them questions about why they do things the way they do.
00:19
Understanding why they do things one way versus another, helps you make more informed decisions on what to change and what to leave the same.
00:29
As you watch, document what you see.
00:32
Workflow diagrams can show both the steps and the decision points that your teams go through.
00:39
A typical workflow diagram will show steps in a rectangular box with decision points indicated as diamonds.
00:48
Arrow show the connection between the steps and indicate when the process repeats.
00:54
Adding text to the decision point arrows help your team know when one answer leads one way,
01:01
while another answer leads them down another way.
01:06
If you can show swim lanes in your graphs, then it becomes clear on where teams interact with one another.
01:15
This becomes more important to illustrate when teams start using the right technology for the task they are responsible for completing.
01:26
Don't forget to document the explanations of why they do the things the way they do.
01:32
If they name files a certain way, ask them why.
01:36
They may have already made arrangements with other teams on how to name work sets that is not documented in the company standards.
01:45
The is a great time to update those standards to include best practices that are already in play.
01:52
This is also a great time to ask your team if they are open to changing their workflows,
01:57
that will make their work more efficient in their day-to-day roles.
02:02
Use the provided checklist to help capture as much information as possible.
02:08
Ask things like, "What software they're using"? There may be technology that they've implemented that you aren't aware of.
02:16
Ask them if they're working in teams or if they're still working in silos. If they are working together, what could be improved?
02:25
Are the team interactions efficient? If not, what would you do to make them better?
02:33
Which teams need training to get them working more efficiently using the technology that they already have.
02:40
And is it important to update that training?
02:44
Is everyone properly following both internal and external standards,
02:49
or what project requirements or internal organizational requirements do you need to consider?
02:56
Who are your key stakeholders and how do they feel about the efficiencies they see today?
03:03
Who are your power users? These are the people that know the ins and outs of the software and your projects.
03:10
Figure out if they're willing to champion the changes coming their way or if they will derail them.
03:17
Finally, don't forget to calculate how much time the current workflows take.
03:24
This will help you later on show the time savings to stakeholders.
03:30
I guarantee they're going to ask about the return on your investment before they give you more money to renew that software next year.
SOFTWARE
TEAMWORK
TRAINING AND LEARNING
EXTERNAL STANDARDS
INTERNAL STANDARDS
PROJECT REQUIREMENTS
INTERNAL ORGANIZATIONAL REQUIREMENTS
STAKEHOLDERS
POWER USERS
REQUIRED OUTPUT
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.