Thamires Lima, a research professor in chemical engineering at Drexel University, has been studying what it takes for thick, viscous liquids to flow under stress. In her lab, extensional rheology is the microscope: she stretches materials between metal plates and measures the force needed to make them move. The goal sounds simple. But the surprising part is what happens when the “simple” behavior stops being simple.

Lima focuses on properties of thick, viscous liquids such as honey or molasses, though in experiments you are more likely to see industrial stand-ins like polypropylene or crude oil. Researchers had been leaning on a particular explanation for why complex fluids break apart: elasticity. The working assumption was that it is the stretchy, spring-like behavior that enables a material to unravel into cracks. Lima’s experiments are forcing a rethink, because a crack can form in a nonelastic simple fluid.

That reversal matters because it attacks the clean mental model many scientists and engineers have used to predict fracture and failure. If elasticity were the whole story, you would expect nonelastic materials to resist cracking under the kind of deformation extensional rheology creates. Instead, the evidence points to fracture behavior that does not require elasticity at all. In other words, some liquids that should behave like straightforward, viscous media can still fracture when pulled apart.

From an industry point of view, this is more than academic hair-splitting. Thick, viscous fluids show up everywhere where flow, mixing, pumping, and processing intersect with real-world constraints. When a material cracks instead of smoothly flowing, the downstream effects can include changes in transport efficiency, altered mixing performance, and unexpected variations in how a product spreads or sets. If a failure mechanism was modeled too narrowly around elasticity, the “safe operating window” that process teams trust could be narrower than they think, or mischaracterized entirely.

There is also a governance layer here, even if the story is happening in a physics and chemistry lab. When research changes the mechanism behind failure, it often ripples outward to how companies document risk and validate designs. Boards and executive teams are not typically testing extensional rheology on a bench, but they do oversee the systems that rely on correct failure assumptions. If the scientific basis for “why fracture happens” shifts, teams responsible for product qualification, reliability testing, and manufacturing robustness may need to revisit protocols, particularly when those protocols were built on older mechanism assumptions.

This is where the “second-order” implications get interesting. A fracture mechanism that was previously attributed to elasticity may have acted like a shortcut in engineering decision-making: choose materials that are elastic enough to avoid cracking, or treat nonelastic formulations as intrinsically safer. Lima’s results undermine that shortcut. That means the industry may need to pay more attention to other structural or interfacial factors that influence how stress localizes and turns into cracks, even when the fluid does not behave like a spring.

For executives operating in adjacent areas of materials science and industrial processing, the message is straightforward: mechanism matters, and so does the specific type of stress you apply. Extensional deformation is not the same as simple shear, and the way a fluid is forced to separate can reveal fracture pathways that other tests might miss. As more work like Lima’s challenges the elasticity-first narrative, decision-makers will likely see a growing need to treat fluid behavior as test-dependent, not theory-assumed.

The strategic stakes are real for anyone whose products or processes involve thick fluids under tension. If a nonelastic simple fluid can crack, then the risk of unexpected failure is not confined to the most “complex” materials. That broadens the scope of what needs to be engineered, tested, and monitored. For leaders, the takeaway is to respect the nuance of physical mechanisms, because the cost of assuming the wrong one can show up later, in the form of variability, downtime, or quality problems that do not map cleanly onto the old playbook.