There is a moment almost every FEA analyst remembers. You are staring at a results plot, the stress contour looks plausible, the deflection looks plausible, and somewhere in the back of your mind a small voice asks: is this actually right, or does it just look right?
If you have felt that moment, you are not behind. You are paying attention.
The myth that keeps analysts stuck
Early in a career, it is easy to believe that expertise means knowing everything. Every solver option. Every element formulation. Every edge case in contact convergence. So when something unfamiliar comes up, the instinct is to feel like a fraud rather than like someone doing exactly what the job requires.
This belief is not just wrong, it is quietly harmful. It pushes analysts toward two bad habits: either they freeze up on anything unfamiliar, or they push forward without pausing to question a result that deserves more scrutiny.
The truth is simpler and more useful. No one holds the entire field of FEA in their head. Not the senior fellows, not the people writing the textbooks, not the people teaching the courses. What separates a competent analyst from a dangerous one is not the size of their knowledge base. It is their instinct for what needs checking, and when.
What “knowing what to check” actually looks like
This is judgment, not memorization. A few examples of what it looks like in practice:
Boundary conditions before mesh refinement. When a model gives an unexpected result, the instinct to refine the mesh is often premature. Before touching element size, an analyst who knows what to check asks whether the boundary conditions actually represent the physical constraint, and whether a rigid connection is hiding a load path that should be flexible.
Energy balance over visual plausibility. A stress plot can look completely reasonable and still be wrong. Checking internal versus kinetic energy ratios in a nonlinear or dynamic run, or reviewing residual force balance in a static solve, catches problems that a color contour will never reveal.
Units and scale, every single time. This sounds too basic to mention, and that is exactly why it causes so many quiet failures. A displacement that is off by a factor of 25.4 does not always look wrong at first glance. The habit of checking units is not a beginner’s habit, it is a lifelong one.
Where the model diverges from the real structure. Every model is a simplification. Knowing what to check means being honest about which simplifications matter for the question being asked, and which ones do not.
None of this requires knowing every corner of the software. It requires a disciplined habit of asking the right questions in the right order.
A story worth remembering
Early in my career, I once trusted a result because everything about it looked clean. Smooth contours, no error messages, a load path that seemed to match the drawing. It was only when a colleague asked me to walk through the boundary conditions out loud that I realized a constraint meant to represent a bolted joint was fully fixed instead of allowing rotation. The model was not wrong because I lacked knowledge. It was wrong because I had not yet built the habit of pausing before trusting a clean-looking answer.
That habit did not come from a course. It came from being asked the right question at the right moment, and from repeating that question to myself on every project since.
Where this leaves you
If you are early in your FEA career and feel like you are constantly catching up, you are not missing some hidden body of knowledge that everyone else has. You are building a habit of scrutiny, and that habit takes time and repetition, not memorization.
If you are further along and still second-guess yourself in front of a results plot, that instinct is not a weakness. It is the same instinct that keeps good analysts good.
The goal was never to know everything. The goal is to know what deserves a second look, and to have the discipline to look.
What is the check that saved you on a project, or the one you wish you had made earlier?
Love that you are reflecting on this behavior in the field of structural mechanics and FEA.
“The habit of scrutiny” really resonates with me and the V&V culture in my circles.
Not only is not knowing everything okay, but the ability to identify uncertainty and recognize what one does not know are key steps to unlocking personal growth. These can be opportunities for further investigation and “checking” to improve chances for success on important projects.
Keep writing Dominique!
Focusing on the mechanics of verification over the accumulation of data changes how a security team operates during a crisis. When you prioritize the process of checking, you stop chasing every signal and start isolating the ones that actually matter to your specific environment. This discipline becomes critical when external pressures or regional regulations shift the ground beneath your feet. You cannot control where the next threat originates or which borders it crosses, but you can control the rigor of your internal validation. By decoupling your detection logic from the physical location of your assets, you maintain operational continuity regardless of the geopolitical noise.
https://cyrilsimonnet.substack.com/p/the-slowdown-has-a-jurisdiction-the?utm_source=substor&utm_medium=substack&utm_campaign=comment