Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:07
In order for any change to stick, you need to manage it.
00:11
That starts with a great plan and that plan is the new workflow model you created.
00:18
Now is the time to run it through a pilot project and test it out. For that, you need the right team.
00:25
The power users involved in designing the new workflows are likely the best people to lead that effort.
00:33
The goal is to test the new work flows on the new technology and make sure that they work before you implement them company-wide.
00:42
A few things to consider before you start your new project. First, make sure everything is installed.
00:48
The new software needs to be integrity tested meaning that you need to make sure,
00:54
that the technology will run on your chosen operating system and devices.
00:59
Also make sure that the customizations for your old software installations,
01:03
transition properly to the new software if those customizations are still needed.
01:10
Next, you'll implement it on the project. Many companies prefer to use a current project to test new technology.
01:17
This allows them to put billable hours against the testing. However, I'm going to challenge you to do just the opposite.
01:27
You may find it's better to run it against a completed project.
01:31
Reason being, a current project could cause delays in the testing as you hurry up and wait for project approvals.
01:39
Using a completed project, however, allows you to work all the way through the project without approval delays slowing you down.
01:48
An additional benefit of a completed project is that it's easier to measure the return on your investment of the new technology.
01:57
Using time cards, you can calculate how long the project took the first time around.
02:05
So, as long as you track how long it takes using the new technology and workflows,
02:10
you can do an apple to apple comparison and get a good return on your investment measurement.
02:18
Of course, the first time you try anything, you're almost always going to suck. It's okay.
02:26
It takes time to improve your aim and create muscle memory around new ways of working.
02:33
So, try the new workflows on a couple of projects and continue to improve them each time.
02:40
Then, when you roll the new technology and workflows out to the company,
02:45
you will be more confident that it will cause minimal amount of disruption.
Video transcript
00:07
In order for any change to stick, you need to manage it.
00:11
That starts with a great plan and that plan is the new workflow model you created.
00:18
Now is the time to run it through a pilot project and test it out. For that, you need the right team.
00:25
The power users involved in designing the new workflows are likely the best people to lead that effort.
00:33
The goal is to test the new work flows on the new technology and make sure that they work before you implement them company-wide.
00:42
A few things to consider before you start your new project. First, make sure everything is installed.
00:48
The new software needs to be integrity tested meaning that you need to make sure,
00:54
that the technology will run on your chosen operating system and devices.
00:59
Also make sure that the customizations for your old software installations,
01:03
transition properly to the new software if those customizations are still needed.
01:10
Next, you'll implement it on the project. Many companies prefer to use a current project to test new technology.
01:17
This allows them to put billable hours against the testing. However, I'm going to challenge you to do just the opposite.
01:27
You may find it's better to run it against a completed project.
01:31
Reason being, a current project could cause delays in the testing as you hurry up and wait for project approvals.
01:39
Using a completed project, however, allows you to work all the way through the project without approval delays slowing you down.
01:48
An additional benefit of a completed project is that it's easier to measure the return on your investment of the new technology.
01:57
Using time cards, you can calculate how long the project took the first time around.
02:05
So, as long as you track how long it takes using the new technology and workflows,
02:10
you can do an apple to apple comparison and get a good return on your investment measurement.
02:18
Of course, the first time you try anything, you're almost always going to suck. It's okay.
02:26
It takes time to improve your aim and create muscle memory around new ways of working.
02:33
So, try the new workflows on a couple of projects and continue to improve them each time.
02:40
Then, when you roll the new technology and workflows out to the company,
02:45
you will be more confident that it will cause minimal amount of disruption.
Components that will increase the success of a pilot project:
Plan – This is the new workflow diagram you created.
Team – Using your power users will increase your likelihood of success since they know your company and project standards better than other end users.
Installation – Check all the software installations on the hardware your pilot team will be using. Make sure that old customizations transition successfully if they are still needed.
Execution – Select the right project for the execution stage. While it is tempting to use a new project that you can bill against, project delays will inevitably delay your implementation as well. Avoid this be using one or more historical projects. The benefits of using historical projects are:
Measurement – Calculating the return on your investment makes it easier to secure your software budget year over year.
Improvement – Test the new workflows on a couple different project and improve them each time to minimize disruption when you roll the new workflows out company wide.
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.