The Assumption Slide: What Engineers Forget to State Before Making Their Case

An engineer presents a load calculation, a schedule recovery plan, or a cost estimate, and the numbers are right. The pushback still comes, not because the math is wrong but because nobody in the room knows what the math assumes. A recommendation without its assumptions stated looks like an opinion. The same recommendation with the assumptions up front looks like a conclusion.

Why Engineers Skip This Step

Engineers live inside their assumptions all day. Soil bearing capacity, design life, load factors, escalation rates: these are so embedded in the daily work that stating them out loud can feel redundant, like explaining that water is wet. But the audience in the room did not do the analysis. They are hearing the output for the first time, and without the inputs, they have no way to judge whether the conclusion is conservative, aggressive, or somewhere in between.

What an Assumption Slide Actually Does

A single slide near the front of the deck that lists the three or four assumptions the analysis depends on changes how every subsequent number is received. It tells the audience what would have to be true for the numbers to hold, and by extension, what would change if a condition shifted. This is not a hedge or a disclaimer buried in fine print. It is the frame that makes the rest of the presentation legible.

The Cost of Skipping It

Without stated assumptions, questions default to attacking the number itself: "why is this estimate so high," "why does this take that long." With assumptions stated, the same questions shift to something answerable: "what happens if we use a faster cure time," "does this assume union labor." The second kind of question moves the conversation forward. The first kind just puts the engineer on the defensive over a number they already know is correct.

Where to Put It and How Much to Include

The assumption slide belongs before the recommendation, not after, and it should hold three to five items, not fifteen. A wall of caveats reads as an engineer covering themselves rather than informing the room. The discipline is picking the assumptions that would actually change the outcome if they were wrong, not documenting every input for the sake of completeness. That editing decision is often the harder skill than building the slide itself.

Practicing the Delivery, Not Just the Slide

Building the slide is the easy part. Saying it out loud with the same confidence as the conclusion is what most engineers skip in rehearsal. It is common to watch someone build a strong assumptions slide and then rush past it in under ten seconds to get to "the real content." The assumptions need the same pacing and eye contact as the headline number, or the slide becomes decoration instead of the frame it is meant to be.

The Bottom Line

A recommendation that arrives without its assumptions invites the room to argue with the number. The same recommendation, framed by three or four clearly stated assumptions, invites the room to test the reasoning instead, which is a far more productive conversation and one that engineers are far better equipped to win.

The PRESWERX Team