End of Internship; My takeaways

Hi all, I apologize for the dry spell of posts these past few weeks; with my internship in full swing, the start of football season, and the onset of my junior year, I've had a lot on my plate. However, now I am coming back to you with tons of new things to discuss. Over the next few weeks, I will aim to discuss a new club I've founded, how operational research pertains to decision-making in football teams and the sport in general, the use of industrial engineering in theme parks, what I hope to accomplish in my junior year of high school, Value Stream Mapping, and much more. However, today, I will discuss my internship and my takeaways from it.
I was very fortunate to be under the mentorship of Jabra Batshoun on the Capacity team, who truly took me under his wing and helped me learn everything I needed to know to be able to complete my project. First of all, beyond Value Stream Mapping (VSM), what even was my project all about and why? As we know, industrial engineering is the engineering of systems, uniting many different teams, processes, and organizations into one cohesive unit, especially identifying waste and removing it. At a company like CoreWeave, the effective collaboration between teams and the efficient completion of tasks is paramount to the company's success in the rapid scaling of AI datacenter infrastructure. Process and VSMing was how I decided to go about that job. Through the estimations of completion times as well as understanding the complex relations between one process and another, my chart proved successful at identifying waste. However, what I did not expect were other improvements I never would have thought to make. Through mapping, I realized there were discrepancies in understanding between different industry-standard terms that could cause confusion. Therefore, not only did this map assist the process of identifying inefficiencies, but it also acted as a directory for those seeking more information and understanding, providing a clear, simple, and intuitive way to visualize the intricacies of an augmentation. Due to my age, I faced a few constraints in the construction of my map that shaped my construction of the chart. I was not able to gain access to company resources, which made it so I had to rely entirely on interviews. Below is my week-by-week process of constructing the map.
Weeks 1 and 2:
My mentor started me off with relatively simple instructions: learn about VSMing, learn how to use Lucidchart and Tableau, and read "The Goal" by Eliyahu Goldratt.
Week 3:
I began constructing a simple outline of the full process map through conducting interviews with a few members of the Capacity team.
Week 4:
I then branched out to other teams, collecting the majority of the data required for the map and began to compile all the new information into a comprehensive map to the L1, L2, and some of the L3 detail.
Week 5:
The map was expanded even further through more interviews, as well as polished, checked for accuracy, and made presentable.
Week 6:
I prepared for the presentation of my map to the executives and members of the Capacity team and presented, making recommendations on what to improve about the augmentation process.
First, I have to say what a surreal experience it was to come in as a high school student and complete a project worthy of presentation to executives and getting to actually present in a corporate setting. Before this I never had the opportunity to present for anything more impactful than a grade. Besides that, my biggest takeaway was learning how to construct process maps and VSMs.

The significance of process mapping and diagrams in understanding complex processes cannot be overstated. It is crucial for every member of a system to comprehend their role within it. When individuals lack a full understanding of the augmentation process and have no resources for guidance, problems are bound to occur. Enhancing comprehension is vital. Improved understanding not only boosts the ability of various teams to collaborate by increasing awareness of each other's roles and potential contributions but also ensures that if an issue arises during a process, whether early or late, a team member can identify what to do, where the problem might have occurred, and whom to consult. Furthermore, broader comprehension can help identify problems and inefficiencies in the system without the need for a complete internal audit, and employees might even spot issues that such an audit could miss.
Learning through school and research is amazing, but the chance to see industrial engineering in action has been an invaluable experience to me and I am very excited to use all of the things I've learned in the future!

Comments