How did you develop engineering intuition and grow into a strong problem solver?

[EdwardNigma]

Hi all,

I’m currently a stress engineer working on aircraft interiors. I’m fairly new to this kind of work but I worked on MRB stress of primary metallic structures before this primarily driven by hand analysis by extracting loads from a FEM. A lot of the FEA I do is coarse loads modeling to correlate with a test article as allowables are unknown. I also determine interface loads calculations on the surrounding structures, calculate margins of safety on inserts common to attachment areas and determine failure indices of panels. So, while I’m involved with simulation work, I’m not always deep in detailed stress calculations. That’s something I want to move toward in the future—running meaningful models, doing hand calcs, and being the person others rely on for engineering judgment.



Over time, I’ve seen both good and not-so-great engineers among the pool of senior engineers. The good ones seem to have this ability to cut through the noise, simplify complex problems, and get to a “good enough” answer efficiently. They know how to set up boundary conditions that reflect reality, approximate without losing accuracy where it matters, and understand what the FEA is actually telling them—especially when it doesn’t match the test or real-world behavior. They are also able to automate FEA processes with coding as well. Basically, they are able to predict an FEA simulation before they actually run the model with a gut feeling or good engineering judgement.



What I want to ask is: how did you develop that kind of thinking? That mix of technical judgment, modeling intuition, and practical simplification? Was it repetition, mentorship, or just digging into more real-world data?



I’d really appreciate any advice or experience you’re willing to share. I’m trying to grow—not just in tools—but in mindset.



Thanks in advance!

 

[SWComposites]

Was it repetition, mentorship, or just digging into more real-world data?

Yes, all of the above.
And with a willingness to understand structural behavior, including failure mechanisms, understand part production processes, understand the background behind analysis methods and where they should and should not be applied.
Experience also comes from conducting and analyzing structural test articles.
And working a new aircraft development program from start to finish is the best learning activity; the process of development just can't be taught in the abstract.

 

[IRstuff]

Dibert talked about the "knack," and there are two levels to that; there are those that have the basic "knack" which comes from just having the experience and guidance, and there are those that are just in another league altogether. I met one of the latter once; he showed up late to a design meeting, and came in on the MEs' CAD model in a Powerpoint and said, as he came into the room, "Isn't there a problem with the 30-Hz resonance in the fixture?" The ME giving the presentation spluttered and the chief ME directed them to check it out, and the interloper was 100% correct, simply "knowing" that the fixture depicted. I've only met two MEs my entire career that could do the voodoo that only they could do, sans FEA, or even hand calcs; the rest of the MEs still had to at least do a hand calc or two.

 

[EdwardNigma]

Yes, all of the above.
And with a willingness to understand structural behavior, including failure mechanisms, understand part production processes, understand the background behind analysis methods and where they should and should not be applied.
Experience also comes from conducting and analyzing structural test articles.
And working a new aircraft development program from start to finish is the best learning activity; the process of development just can't be taught in the abstract.

Thanks SWComposites. I'm thinking that I'd need to work on a development program from start to finish to see my actions unfold and learn from my decisions and consequently mistakes. If there's any testing that would help as well.

 

[EdwardNigma]

Dibert talked about the "knack," and there are two levels to that; there are those that have the basic "knack" which comes from just having the experience and guidance, and there are those that are just in another league altogether. I met one of the latter once; he showed up late to a design meeting, and came in on the MEs' CAD model in a Powerpoint and said, as he came into the room, "Isn't there a problem with the 30-Hz resonance in the fixture?" The ME giving the presentation spluttered and the chief ME directed them to check it out, and the interloper was 100% correct, simply "knowing" that the fixture depicted. I've only met two MEs my entire career that could do the voodoo that only they could do, sans FEA, or even hand calcs; the rest of the MEs still had to at least do a hand calc or two.

Thanks for the example IRstuff! I think I'm talking about the latter as a goal, while the basic knack is more what this post is about. I've met a few people who fit that second level you mentioned, and it's really impressive and admirable. Their ability to trust their gut and make suggestions is pretty cool!

 

[hvillasenor]

@EdwardNigma,
I'm going to give you some direct and clear advice.

If you want to develop this kind of engineering intuition and move into modeling, interpreting, and validating complex FEA analysis you first need to be passionate and have a drive for your work. I believe this you already have.

Second, be very observant and pay close attention to what both the good and not so good engineers do - you'll gain insight as to what to do and not to do.

Third, you will need to invest time and dive into more in-depth and specialized subjects; these include materials and their behavior, structural mechanics, numerical methods and approximation methods, and the finite element method in detail such as meshing, element types, and when to use and combine certain element types. You will also need to learn how to run detailed calculations by hand and you'll need to collect a good library of books, articles, and other literature related to the topics your interested in.

Fourth, you will need to be humble enough to recognize when you may have done something incorrectly, and NEVER be embarrassed to ask questions or ask for feedback from other leaders in the field. ONE SIGN OF A GREAT AND SENIOR ENGINEER IS THAT THEY ADMIT WHAT THEY DON'T KNOW.

Lastly, whenever you go out for a walk or a drive, observe how structures behave, whether its a vehicle in motion, a lightpole, a building, a carport, and highway, a scissor lift...anything. Learn to break down complex mechanical structures in your mind and understand how the load path transfers between each component to the point that you can see any structure and it becomes second nature where you can identify the critical areas without running a single calculation.

You will see what others cannot.

Mastering the computation structural mechanics and material behavior will take time but it is well worth it.

Never stop learning.

Hope this helps.

Best regards,
Humberto Villasenor, P.E.
VEMAC Consulting, LLC.
www.vemac-consulting.com

 

[GregLocock]

I think that breaking a lot of things helped me. At the very least it was fun. My second job in particular I had a surprising amount of freedom, and resources. Also in my 4th job I had 3 cars to play with, one was the program I was working on, the other two were $1 cars that could be (and often were) used for anything we felt like, they were off to the crusher once we broke them.