The Units Problem: When Engineering Data Overwhelms the Room
Engineers are trained to be precise, and precision generates numbers: load factors, deflection limits, tolerances, flow rates. That precision is exactly what makes a design defensible in a permit review or a construction dispute. It is also exactly what empties a room of attention when the audience is an owner, a city council, or a client's finance committee rather than another engineer. The instinct to show the work, all of it, is a habit worth examining before the next presentation rather than during it.
Why More Data Doesn't Mean More Trust
A common assumption is that showing every calculation demonstrates rigor and earns confidence. In practice, a slide dense with figures the audience can't evaluate often does the opposite: it signals that the presenter hasn't done the translation work of deciding what actually matters to this particular audience. A city council does not need the full structural analysis to trust a beam size. It needs to know the design meets code, carries margin for the load cases that matter, and was checked by someone qualified to check it. Piling on additional decimal places past that point reads less as thoroughness and more as a presenter unsure which numbers the room actually needs.
Separate the Proof from the Decision
Every technical presentation contains two different kinds of content: the proof that the engineering is sound, and the information the audience actually needs to make a decision. These belong in different places. The proof lives in the calculations, the stamped drawings, the appendix available on request. The decision-relevant summary, a handful of numbers with context, belongs on the slide. Engineers who keep these separated in their own head before building slides produce far cleaner presentations than those trying to sort it out live in front of an audience.
Translate the Number, Not Just the Unit
Converting psi to a plain-language sentence is not the same as converting it to something meaningful. "This beam carries three times its expected load" tells an owner something. "This beam has a safety factor of 3.0" technically says the same thing but requires the listener to already know what a safety factor is and why 3.0 is good. The habit worth building is asking, for every number on a slide, what decision this number is supposed to support, and then saying that decision out loud rather than trusting the audience to derive it.
When the Room Actually Wants the Detail
Not every audience wants the summary version, and treating all audiences as allergic to technical depth is its own mistake. A peer review panel, a permitting engineer, or a technically literate client representative may specifically want to see the calculation path, and simplifying too aggressively in front of that audience reads as evasive rather than clear. Reading who is actually in the room, and adjusting depth accordingly, matters as much as having a simplified version ready. The same deck rarely serves both audiences well without at least some rework between the two meetings.
Building the Habit Before the Big Presentation
The fix isn't a rule about slide density, it's a rehearsal habit: before a presentation to a non-engineering audience, walk through the deck with a colleague from outside the discipline and ask what confused them or lost their attention. That single dry run, done consistently, catches the places where technical shorthand crept back in far more reliably than any checklist.
The Bottom Line
The engineering doesn't change based on the audience, but what gets shown, and how, should. A presentation that respects the room's actual decision needs, rather than defaulting to full technical disclosure, earns more trust than one that simply proves the math was done.
The PRESWERX Team
