Every engineering team deals with repetitive tasks, manual steps, and processes that take more time than they should. This is normal. We want to invest in better tools and automation to reduce this kind of work, so that you can spend more of your time on the engineering problems that need your skills and experience.
To do this well, we need your help. You are the expert in your own work.
Section 1: About Your Work
Different roles often experience different challenges. These questions help us understand patterns across the team.
Your name
Which best describes your primary role?
Which tools do you use regularly? (select all that apply)
Any other tools we have missed?
Section 2: Where Your Time Goes
Think about a recent typical project. Drag the bars to show roughly how your time breaks down. They always sum to 100% — your best estimate is fine.
If you could automate ONE part of your workflow starting tomorrow, what would you choose?
Is there a task you do that is particularly well-suited to automation — something that is repetitive, rule-based, and does not need much engineering judgement?
Is there any part of your work where you think human judgement and experience is essential and should NOT be replaced by automation?
Which statement best describes your approach to new tools or technology?All of these are valid — there is no "right" answer.
Have you created any tools, templates, macros, or shortcuts that help you work more efficiently?Optional — these are seen as a positive contribution.
Which of the following do you have experience with?Select all that apply — we are asking this to understand the range of skills across the team, not to set expectations.
How would you like to be involved in this automation project?Select all that apply — all of these are valuable contributions.
Section 4: Training
We want to make sure any training we offer is useful and relevant to your work.
What kind of training would serve you best? (select all that apply)
How would you prefer to learn?
Is there a specific skill or tool you would like training on?Optional
Section 5: How Easily Are Issues Caught?
In any engineering workflow, issues can occur at different stages. Some are easy to catch early; others are harder to detect. This is about the process, not about individuals — we want to understand where our workflows need better safeguards.
Detection difficulty
1
Easy to catch — usually noticed immediately
5
Sometimes caught during checking or verification
10
Very difficult to catch — may not be found until construction
An input parameter in a calculation or model is not correct
Easy5Hard
Data from a previous revision or outdated source is used instead of the current version
Easy5Hard
Report text or tables do not match the actual calculation results
Easy5Hard
Drawing annotations or schedules do not match the current design
Easy5Hard
A design change is not carried through to all related deliverables
Easy5Hard
A formula or method in a spreadsheet contains an error
Easy5Hard
Our work is based on another discipline's inputs that have since changed
Easy5Hard
A sensitive receiver affected by flood conditions is not identified until late in the project
Easy5Hard
Section 6: Workflow Challenges
Help us understand which areas cause the most friction in your day-to-day work.
Which areas cause you the most frustration? (select all that apply)
Describe the biggest time-waster or source of rework in your workflow
Is there anything else?Optional
Your response will be recorded securely. You can resubmit to update your answers.