The ‘Insights’ series is a broader look at engineering. We will explore some ideas, philosophies and lessons learned.

Today, we dig into some key skills for professional engineers. While these might not be the definitive top skills, they are important.

I have included the article below if you prefer to read rather than listen. I execute some side missions during the podcast, so some additional topics are covered exclusively in the audio version.

In this episode, I share what I believe are pivotal skills for engineers. It's important to note that these views are my own and may not align with the broader industry consensus. Every engineer has unique experiences and perspectives, contributing to a diverse range of valid opinions. I offer one viewpoint among many.

We'll be exploring:

* Cross-disciplinary understanding

* System-level thinking

* Adaptability in problem-solving

* Ethical engineering

* Storytelling and visualization

* Plus, a bonus skill: Managing personalities and conflicts

These skills are more than just theoretical concepts; they're practical tools that can significantly advance your efficacy as an engineer.

Books Mentioned

* "The Obstacle Is the Way" by Ryan Holiday - Goodreads

* "The Feynman Lectures on Physics" by Richard Feynman - Goodreads

* "Six Easy Pieces" by Richard Feynman - Goodreads

* "Sapiens: A Brief History of Humankind" by Yuval Noah Harari - Goodreads

Your thoughts and perspectives are valuable; please add your comments.

James 🌊

Interdisciplinary Understanding

The crux of my message revolves around the interdisciplinary nature of engineering projects. Professionals in civil, structural, mechanical, geotechnical, and electrical engineering are often highly specialized in their domains. However, a broader understanding of how these areas intersect becomes pivotal, especially when coordinating complex designs.

Think of it as a Venn diagram, where each circle represents a different engineering discipline. The overlap, though seemingly small, is where the magic happens.

Being fluent, or even moderately conversant, in these overlapping areas offers a significant edge in managing and orchestrating intricate projects. It's a universal truth in engineering or any organization, for that matter.

A few examples that come to mind.

* Mechanical and structural discussing operating loads for pumps/valves/support systems.

* Prefab components or modular engineered solutions being installed into a larger global structure.

* Equipment suppliers and issues surrounding weight, access, constructability, sequencing, lead times, etc.

* Environmental review or community engagement

* Lab testing or more specialist work like specific concrete mix design, interpreting instrumentation data, or other sub-disciplines often engaged on larger projects.

The gaps between these specializations and the often loosely defined scope limits are where the challenges instantiate themselves {🐍👀}.

So, why is this cross-disciplinary fluency so crucial? Simply put, it's about aligning diverse objectives that, while distinct, often intertwine with the work of other teams. By understanding these connections, we can navigate the complexities of collaboration more effectively.

Every project I've been part of has reaffirmed this. A broad grasp of various fields doesn't just add value—it's often the linchpin in transforming a complex project from a jumble of individual efforts into a well-oiled machine.

Systems Level Thinking

In a past episode, we discussed the parallels between programming and engineering and some viable problem-solving strategies in both. Systems-level thinking is another great example.

Systems-level thinking is an analytical approach to understanding complex systems by examining the linkages and interactions between the components that comprise the entirety of that system. It’s about seeing the 'big picture' rather than focusing on individual elements in isolation.

Key aspects of system-level thinking include:

* Interconnectedness: Recognizing that changes in one part of a system can have ripple effects throughout the entire system.

* Holistic Perspective: Focusing on the whole system rather than just its individual parts.

* Contextual Awareness: Understanding how external factors, such as environmental, social, or economic elements, impact the system.

* Feedback Loops: Identifying how actions within the system produce reactions which may influence future actions.

* Dynamic Nature: Appreciating that systems are constantly evolving and that solutions may need to adapt over time.

Imagine it as adjusting a lens. One moment, you're zoomed in, immersed in the intricate details of your design – the specifications, the technical requirements. You're focused on the minutiae, ensuring every aspect of your work is heading in the right direction. But, at a moment's notice, you need to zoom out. You shift from a micro to a macro perspective, taking in the entire landscape of the project.

Why is this shift significant? Because the decisions you make in those detailed designs don't always exist in isolation. They can ripple through the project. For instance, a small change in your design could lead to significant alterations in geometry, impacting other team members' work. It might necessitate logistical shifts or even affect procurement timelines. This is where system-level thinking intersects with interdisciplinary understanding. It's about recognizing that your piece of the puzzle is part of a larger one. Fractal puzzle pieces, if you will.

This constant reframing – moving between the granular details and the overarching project goals – requires cognitive flexibility and a broad understanding of engineering principles. Who's affected by your decisions? How do your actions impact the timeline, the budget, and the overall project flow?

It's about wearing different hats, understanding different perspectives, and always being ready to adjust your approach based on the project’s evolving needs.

It is important to appreciate that this skill develops over time as you gain experience. However, asking the right questions and keeping this concept in mind will accelerate this process considerably.

Adaptability in Problem-Solving

Consider the early stages of a project: brainstorming sessions ensue, conceptual designs are outlined, plans take shape, and expectations are formed. Brainstorming and concept design are the best parts of a project; I love it—engineering freedom. Then, the sh*t hits the fan.

The transition from theory to practice often reveals the fluid nature of real-world conditions. When on-site work commences—boots are on the ground. Drilling, digging, constructing, implementing—and unforeseen challenges arise. It's in these moments that the ability to pivot becomes invaluable.

Adaptable problem-solving is more than a skill; it's a mindset. It's about maintaining composure and responsiveness in the face of new challenges. The key lies in how we interpret and react to changing conditions. Can we remain calm and solution-oriented? Can we extract critical information from evolving scenarios to make informed decisions? These are the hallmarks of an effective engineer.

Being adaptable also means being resourceful. It involves evaluating the available information and considering various options. By asking intelligent questions, we can draw additional insights out of situations, guiding us toward more informed, nuanced solutions. The value is immense if you can work towards becoming this type of hypothetical question master. I have always loved people that ask good questions. They elevate the room, and they promote better thinking.

In essence, adaptability in engineering is about thriving within constraints, whatever they may be. It's about seeing change not as an obstacle but as an opportunity, as annoying and cliched as that sounds.

This mindset, which requires rigorous cultivation and willpower, can transform challenges into triumphs, ensuring that you are always part of the solution.

Ethical Engineering

This is a broad topic, and I’ll try to do a dedicated episode on ethical engineering topics because so much falls into this very interesting bucket. Many issues are grey areas, philosophical discussions that can be quite polarizing for people.

In my experience working in several countries and jurisdictions, while ethical considerations are universally acknowledged as crucial, they often need to receive extra emphasis during execution. This is easy to say, but the world is a complicated place. In reality, there’s often a layer of financial or legal abstraction between the words in a contract and the real-world application. Ultimately, everything hinges on the context of local culture, project budgets and regulatory requirements.

It’s easy to whine about it as a backseat driver, but I don’t have a clean solution other than to try