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 your best to be vocal about issues you encounter in the most productive manner possible and offer viable solutions or alternatives.
There are many topics to consider under the ‘ethical engineering umbrella’ and many deep dives.
One aspect of my industry that I find extremely interesting is First Nations’ engagement and partnerships. This is a huge focus here in BC, Canada.
For subscribers in other parts of the world, First Nations people in Canada refer to the diverse groups of Indigenous peoples who were the original inhabitants of the land that is now Canada. There are over 600 recognized First Nations governments or bands across Canada.
It’s been a fascinating journey for me, an Irish immigrant (I moved here after university in 2010), observing the complex interactions of FN communities with the federal and provincial governments. Given the topic’s history and politics, there is a lot to unpack, which I will hopefully do in a future post. It’s certainly not my area of expertise, but from a purely sociological and personal learning perspective, there are many valuable discussions to be had.
Professionals involved in large-scale projects often face compartmentalization and time constraints, making it challenging to engage fully with the multifaceted aspects of ethical engineering. Few clients are willing to pay to philosophize. It’s a difficult thing to nail down.
Navigating complex and bureaucratic regulatory environments is a constant challenge in my work. These regulations significantly impact project timelines and execution strategies. Energy projects, my neck of the woods, whether they involve wind, solar, hydro, nuclear, or thermal energy, require a careful balance between societal power needs and environmental impacts. There has been a recent push to modernize the process (The Importance of Streamlining Hydropower Licensing).
This balance is not just a technical challenge but an ethical one, highlighting the need for engineers to consider the broader implications of their work. I’m still not sure where we are supposed to find the time/budget to consider all these things!
Storytelling & Visualization
Effective communication, particularly through storytelling and visuals, shapes project outcomes and guides stakeholder decisions. Communication is about transmitting ideas and concepts.
“Our language allows us to share information about objects, events, and ideas that are not present at the moment.” - Yuval Noah Harari, Sapiens.
Throughout my career, I've encountered communicators of all stripes. Some have been exceptionally clear and concise, providing value and insight with every word spoken. Elite communication skills are both impressive and impactful, whether it's articulating a problem, offering a solution, or eliciting valuable responses through sharp, insightful questioning. Such individuals understand the power of clear, concise updates and instructions. It’s a game-changer.
One of my heroes, Richard P. Feynman, is a master of this craft. His ability to distill complex concepts in various branches of physics into simple, understandable explanations is inspiring. I highly recommend digging into his work if you are interested in physics and the nature of reality.
For me, receiving clear instructions is like a breath of fresh air. It gives me a clear direction, allowing me to dive straight into the task at hand. In contrast, vague or poorly communicated instructions can be a real headache. This is particularly true in engineering, where project requirements often have a degree of intentional ambiguity. We're frequently walking a tightrope, balancing general criteria with specific project needs, and there isn't always a clear-cut path to follow.
Sometimes, an owner or a client is still determining what they want, so it takes some creative reasoning and preparation to get everything outlined in an actionable plan that aligns with their objectives.
This ambiguity often leads to some engineering 'freestyling.’ In these situations, the ability to communicate effectively becomes even more critical. The skill of storytelling and visualization helps immensely here.
Visualization, in particular, is a tool I value. It's about painting a picture in the mind's eye, helping others to see and understand complex concepts or problems. The ability to do this effectively can significantly enhance understanding and collaboration in a project.
Your effectiveness is only as strong as your ability to communicate it.
Managing Personalities or Conflict
If you’re a human being, you will inevitably run into personality clashes and people that frustrate the living daylights out of you.
Folks that make the veins in your temple pulse so violently, it’s like they’re drumming for Metallica. Perhaps you’re a jaw clencher? Determined to powderize your molars. It’s just the nature of being human, there’s an arch nemesis out there for all of us! Everything they say elicits some sort of primal reaction convincing you it’s the stupidest thing you’ve every heard.
Maybe you’ve white-knuckled your way through this entire article despite me being that very person.
If you’re still here, I appreciate it. It’s not easy.
Navigating personality clashes and conflicts in the workplace can be a real challenge. I have my share of war stories, but I won't dive into those. Generally, my strategy is to take a step back and try to see the bigger picture. Often, I find that the person causing the friction is under significant stress themselves. It's like they're a character in their own intense Brazilian soap opera (apologies to the Brazilians but you guys have been my most dramatic friend demographic by at last 10X), and I'm just an extra.
I try to avoid taking things personally, which is easier said than done, but losing your cool professionally rarely ends well.
Of course, there are times when confrontation or a reality check is necessary. But I approach these situations with extreme caution. It's about finding that balance between standing your ground and maintaining professional decorum. The arts of negotiation, de-escalation, and defusing are all in this bucket, and they warrant some consideration so that you’re ready, if required, to step into the ring.
And in the very worst of cases, clocking up some mat time in BJJ will (a) help blow off some steam and (b) give you the tools to fold your mortal enemies into pretzels or as some people say folding peoples clothes while they’re still in them. I jest, don’t do this.
Closing
Wrapping up today's article, let's quickly revisit our skills list:
* Cross-disciplinary understanding
* System-level thinking
* Adaptability and problem-solving
* Ethical engineering
* Storytelling and visualization
* Managing personalities and conflict
Discover more about how flocode can enhance your engineering toolkit by visiting flocode.dev and stay updated with our latest insights and resources through this newsletter at flocode.substack.com.
What do you think about engineering skills? Let’s discuss below.
See you in the next one.
James 🌊
Get full access to Flocode: Engineering Insights 🌊 at flocode.substack.com/subscribe
