Teaching Engineers to Present Technical Findings to Non-Technical Boards
Engineers are trained to be precise, and precision is a virtue until the audience is a city council, a school board, or an owner's finance committee. These groups make decisions based on what they understand, not on how much data they were shown. Presentation training helps engineers close that gap without giving up accuracy.
Start With the Decision the Board Must Make
Technical presentations often begin with background, methods, and data, and reach the recommendation at the end. A non-technical board needs the reverse. State the decision on the table, give the recommendation, and then offer the reasons. If the board knows within the first minute what is being asked of it, it can follow the details with a purpose.
Translate Units Into Consequences
A number without a consequence rarely lands. Instead of saying the culvert is sized for a twenty-five year storm, say that it is designed to carry the water from a storm that is likely to occur once in a generation, and show what happens on the road during a larger one. Train engineers to ask of each figure, what would a resident notice if this number changed? The answer is the sentence the board will remember.
Cut the Method, Keep the Confidence
Engineers often feel obliged to describe how they reached a conclusion. Boards typically care more about whether the conclusion can be trusted. A short statement of what was checked, by whom, and against which standard usually satisfies that need. Move the full method to an appendix and offer to discuss it if a member asks. This keeps the presentation short and signals that the work is solid.
Use Visuals That Show Cause and Effect
A single drawing that shows the existing condition beside the proposed condition often explains more than a slide of calculations. Use color sparingly, label what matters, and remove anything the board does not need. Practice walking through a figure in order, from the problem area to the fix to the outcome. An engineer who can narrate a drawing in thirty seconds is easier to follow than one who reads a table.
Prepare for Questions From Outside the Discipline
Board members ask about cost, schedule, risk, and neighbors, which are not always engineering questions. Prepare short answers on each, and know who else can respond if the question falls outside your scope. Practice saying, I do not have that figure here, I will send it by Friday, without apology. It is better than guessing.
Rehearse With a Non-Technical Listener
The best test of an engineering presentation is a listener outside the discipline. Ask an administrator, a project coordinator, or a colleague from another department to hear the talk and say what they understood. Where they are confused, the board will be too. Revise those points and run the talk once more before the meeting. This single step often removes more jargon than any amount of self-editing.
Pace and Silence
Engineers who know the material well often speak quickly, assuming the audience is keeping up. Slow down at the key point of each section and leave a pause after the recommendation. Two seconds of silence feels long to the speaker and gives the audience time to absorb the message. Practice it deliberately, because the instinct is to fill the gap.
The Bottom Line
Engineers do not need to simplify the science to reach a non-technical board. They need to organize the message around the decision, translate numbers into consequences, shorten the method, and prepare for questions beyond the discipline. Presentation training that practices these habits produces engineers whose recommendations are understood and acted on.
