As a CAD manager you are responsible for implementing new software tools and motivating users, but how do you do that when you have to train, implement standards, and deal with everything else? By establishing a CAD proving ground, you can treat your super users like test pilots and build a strong software development environment that benefits your users and your company. The proving-ground concept starts identifying new tools and customization through testing, training, standardization, constant improvement, and broad user adoption. In this class we will challenge you to think about software implementation in a totally different way than you have in the past, but the change will be worth it when you build a powerful proving ground. If you have to develop and/or deploy new software tools, you can’t afford to miss this class.

1. Establishing a CAD
Proving Ground
Robert Green
Robert Green Consulting
RGreen@GreenConsulting.com

2. Robert Green quick biography
Mechanical engineer turned CAD manager
Private consultant since 1991
Focus: CAD standards and management
Cadalyst Magazine author & contributing editor
20 year AU speaker
Facebook: CAD Managers Unite!
Twitter: @RGCADMan
Web site: www.CAD-Manager.com

3. What’s the best way to prepare
software for rollout to my users?

4. Key steps for CAD success …
Research must be done
Software must be configured
Hardware must be optimized
New methods must be put in place
Training must be delivered
Low cost, low risk, on time rollout
The boss has to be happy …

5. You must find a way to get your management
pumped up, contain costs and train everyone or
you’ll never survive. But how?

6. How can your research best benefit others? _
“Research is what I’m doing when
I don’t know what I’m doing.”
Wernher von Braun
But what if you don’t have a NASA budget?

7. Key software research metrics?
Research must be done
It can’t seem disorganized
It should seem very focused
You should move towards a defined goal
The boss must be in the loop …

8. You’ve got to look like you know exactly what
you’re doing even when you don’t.

9. Enter the proving ground concept
What is a proving ground?

10. A place where high performance
research can be conducted.

11. What is a proving ground?
A place to simulate actual usage scenarios
A controlled environment where:
 Risk is limited
 Changes can be made quickly
 Mistakes are learned from
A way to create better products …

12. The CAD proving ground
Why should software be any different?

13. The CAD proving ground
Investigate new software tools
Using real hardware/network scenarios
With specially qualified users
Debugging and fixing as you go
Creating training plans for the masses
Building the better software tool …

14. Find your test pilot users
Based on their attributes

15. Who is a test pilot user?
They’re willing to test new features
They realize new features will crash
They’re calm under pressure
They can communicate what’s wrong
They are project motivated
They thrive on learning …

16. Who is NOT a test pilot user?
Those not willing to self learn
Those not willing to work extra hours
Those that freak out when things crash
Those who simply say “this doesn’t work”
Those who can’t help you debug …

17. A few test pilots working closely with you will
speed testing, reduce frustration and limit the
number of users you have to deal with.

18. The proving ground environment
How should it be setup?

19. A proving ground is …
As a subset of your total network
That emulates real usage scenarios
Walled off from other production users
With full IT support …

20. To setup the proving ground you need …
Software licenses and deployment kits
All required folders and network permissions
Standard content for software usage
Project filing standards
EDM/PDM integration
Flight manuals for test pilots …

21. The proving ground environment
When should it be setup?

22. When to setup the proving ground …
After you’ve investigated new software
Prior to test pilot involvement
Key reasons:
 To test EVERYTHING
 To gauge WAN/cloud performance
 To best support test pilots
Do sweat the details now …

23. Everything you validate in the proving ground is
one less thing that’ll blow up later. Don’t skip
steps – don’t make assumptions.

24. Assign your test pilots
Based on their skill set

25. Match pilot to test flight …
Revit users test new Revit tools
Inventor users test new Inventor tools
AutoCAD users test improved AutoCAD features
Note: You need several test pilots …

26. Support and interview your pilots
They’ll tell you what’s wrong and right

27. Test pilot debriefing …
After they do a test flight ask them:
 What worked?
 What didn’t?
 What could be better?
 What would you change?
Do this immediately after test flight …

28. Debug the debriefing …
Your tasks now are:
 Document what worked
 Fix what didn’t work
 Make pilot requested changes
 Think about teaching strategies
Setup another test flight …

29. Use a punch list mentality …
Perform a test flight
Perform a debug
Repeat
When the pilot is happy you’re done
Software can now move to production …

30. Not only will you get things right you’ll actually
know when your done by monitoring your debrief
and debug punch lists over time.

31. Iterate and improve
The never ending proving ground

32. After your software rolls out …
Think about your next research project
Plan for another round of test flights
Keep the proving ground going
How better to keep making progress …

33. Training and standards benefits
How to pay for the proving ground

34. The benefits of the proving ground …
Standards are proven in testing
Training concepts can be identified
Lesson plans can be created
Test pilots become product experts
Errors are minimized
How much time/money will this save …

35. Nothing cuts costs like error reduction and
nothing cuts software rollout errors like a proving
ground approach!

36. Pilot peer envy creeps in
Use it to motivate and inspire

37. How would things change
If everybody thought like a test pilot?

38. Make the test pilot position highly sought after
and watch your user base strive to get better.

39. Using positive peer pressure
to cement methodologies/change
https://encrypted-
tbn3.gstatic.com/images?q=tbn:ANd9GcThqgQLAzIds
S0M8fV9JirM3vXiY4ImtDOxVZ6fSPWnCJGGN2T6M
Q

40. What if it were cooler
To use proving ground tools rather than
going rogue with new software?

41. Stick with the proving ground concept until
everyone sees the value and arguments over
standards will start to go away.

42. Advertise your results!
How else will they know how much you’re doing?

43. Management wants to know how well the proving
ground concept is going. Tell them! Be sure to
outline error reduction and savings.

44. What were the steps again?
Any last thoughts?

45. The steps …
Build your proving ground ecosystem
Identify your test pilots
Perform test projects in the proving ground
Debrief test pilots
Thoroughly debug new software
Rollout will now be smooth …

46. A few closing thoughts …
A proving ground approach is a shift:
 In methodology
 In psychology
 In personnel motivation
It takes time to setup properly
It pays for itself quickly
Your company will benefit from it
As will your career …

47. Establishing a CAD
Proving Ground
Robert Green
Robert Green Consulting
RGreen@GreenConsulting.com