Lessons Learned

The end of the calendar year presents a natural opportunity for reflection. This coming January marks my first full year with ARS. Over the course of the year, I participated in five test campaigns, spoke at two conferences, and solo authored my first professional paper since 2013. I am deeply grateful for each opportunity. Every test, study, or writing endeavor has allowed me to tackle obstacles and occasionally make mistakes, all serving as a vehicle for personal and professional growth.

Beyond my individual journey, the organization has grown considerably this year. We have added seven full-time employees with diverse backgrounds. Our Neutron™ inventory is larger than ever, and we are developing new offerings and capabilities to propel us forward. Most importantly, we continue to refine our craft. This is something I attribute to our practice of discussing and documenting our “lessons learned.”

Cultivating a culture of reflection.

“Lessons learned” refers to valuable insights gained from experiences, especially those involving challenges or mistakes. By sharing experiences within the organization, we have encouraged multidisciplinary discussions that translate into actionable steps aimed at avoiding repeated mistakes and fostering continuous improvement.

Developing a process for collecting and sharing individual lessons required inclusivity. Gathering opinions from all organizational levels has been crucial for a comprehensive understanding of successes and challenges from diverse perspectives. It is gratifying to work for a company that ensures all employees have a voice and can drive change.

It’s vital that our “lessons learned” conversations go beyond mere rhetoric. Discussions must lead to actionable steps or institutional knowledge that helps us avoid repeating mistakes. By doing this, we strive for continuous improvement of the organization and the services we provide.

After each test campaign or project, my colleagues and I compile our thoughts into a comprehensive list of individual lessons learned. Each point is reviewed and assigned an action item, ranging from acquiring new tools or gear to altering documentation like drawings and procedures, or clearly defining staff responsibilities.

Key insights for future success
As we work onsite during our last test campaign of the year, I’ve asked my colleagues to share their biggest lessons learned. I’ve compiled some of these insights below, offering commentary where needed:

• All tasks take longer to complete than you think they will. Plan accordingly.
• Constant and open communication is essential for fostering a cohesive group. Internally, we’ve added check-in meetings to share ideas. Onsite, we have implemented the use of a hardwired comms system that allows us to communicate between our control system and test configuration.
• It takes months of planning to seamlessly make five minutes of noise. This involves weekly client meetings, creating thorough procedures, and developing drawing documentation for system construction and deconstruction before we arrive onsite.
• Evaluating your space is the key to an organized and smooth testing campaign. We’ve started to draw up staging and sequencing plans for construction and deconstruction to identify and mitigate challenges before campaigns begin.
• Define discrete roles for individuals and give them an agency in that job. All our pre-test planning meetings now include job definitions that keep staff focused and on track during testing campaigns.
• As our Director of Testing & Operations likes to say, “Embrace the suck.” There will always be things that do not go as planned, that push or extend the schedule, or that ask for changes to be made on the fly. This is a part of the process and should be embraced!

We see the outcomes of our reflection each time we take the system on the road. Each test enhances our organization, streamlining, and team cohesion. By sharing our insights, I hope you feel inspired to reflect on your year and commit to being a continuous learner of your professional experiences.