Why Most Technical Presentations Fail and How FINESSE Fixes Them
Technical professionals spend a significant amount of time preparing presentations for senior management and decision boards. Yet many of these presentations fall short and result in frustration on all sides. The presenter feels unheard. Leadership feels the presentation did not help them move forward. Ultimately, a presentation of complex technical issues succeeds by making complex information aligned and actionable with the decision body’s needs.
FINESSE provides a structure that helps technical professionals communicate in a way that supports decision making — not by demonstrating how much the presenter knows, but by aligning what the presenter knows with what the decision body needs to act.
From the Real World
“So, where is the regionalization process bogging down?, I asked.
“It has legs as far as the majority of the board goes,” explained the Mayor. “If its bogging down, its because of our consultants and our own staff.”
Let me guess,“ I replied. “The engineers are talking about their own engineering things, the financial consultants are talking about their own things, and your staffs are probably rehashing all of their recent problems.”
“You got it,” the Mayor said in exasperation. “And everybody wants their 30 to 45 minutes to talk about their special parts with the commission”
“And no one is asking you what the decision body needs - correct?” I added.
“I can see you have been down this road before,” the mayor said with a smile.
The Ways That Technical Presentations Fail
At the highest level, presenters of complex technical issues tend to overwhelm the audience with detail, bury (or lose) the key message, and fail to connect the technical work to the decision that needs to be made.
A few years ago, I sat down with four of my peers and we developed a Top 10 (it ended up being a baker’s dozen instead) of reasons that technical presentations to executives fail. From there, I consolidated into three categories:
Overwhelming the audience with detail
1. too much about the presenter’s expertise and experience
2. too many graphs and other visuals that make the same point
3. too many explanations about the analysis and models, rather than the business impact — the cost, risk, schedule, and regulatory consequences that matter to the decision
4. too much unnecessary technical jargon, used as if it signals rigor rather than getting in the way of clarity
Burying (or losing) the key message
5. just providing information (never had the key message)
6. never state the “thesis” up front
7. are ill-prepared for Q&A
8. pushing a preferred solution instead of acting as a neutral, trusted facilitator
Failing to connect with the decision
9. jumping to solutions before the core issue and the real concerns are identified
10. not asking the decision maker what they need
11. lack understanding of the problem frame
12. don’t understand the inner circle and group dynamics that shape the decision
13. presenting in ways that leave part of the audience out entirely (visual or hearing barriers, or generational differences in how people take in information)
By mistaking thoroughness for effectiveness, technical presenters force decision makers to work to deduce the core message. This quickly leads to overload and disengagement.
Senior leaders want to understand the situation, the implications, and the choices.
The Problem With Most Technical Presentations
Most technical presentations fail because they are built from the inside out. The presenter starts with the analysis, the data, and the technical process. They then work outward toward the conclusion. This approach makes sense to the person trained in the scientific process and through cumulative learning from grade school through college.
A sequence-based approach does not work well for the people who must make a decision.
Senior leaders need the punchline first. The sequence-based journey and the mounds of information associated with it produce fatigue. Senior leaders have more than one decision to make at any given time; give them your recommendations and trust them to follow up if they have questions.
How FINESSE Improves Technical Presentations
The FINESSE Fishbone Diagram® solution is a formal, cause-and-effect communication approach: get the seven key inputs right (the bones of FINESSE) and you get the desired output — effective communication. In summary:
Frame the problem (focusing on business needs and real stakeholder concerns).
Illustrate the key points visually.
Noise reduction (removing jargon, unnecessary data, and distracting detail).
Empathy for the audience's perspective.
Structure in the delivery.
Synergy with group dynamics and key decision-maker advisors.
Ethics to maintain trust and credibility.
FINESSE is one proven communication approach for complex problems. There are others.
Frameworks like the Pyramid Principle or BLUF (Bottom Line Up Front) solve the sequencing problem — putting the conclusion first — which is exactly what FINESSE's Structure bone covers. But sequencing is only one of the reasons (number 6 above) technical presentations fail; the other six bones — framing the problem, illustrating it, cutting the noise, reading the audience, managing group dynamics, and protecting trust — are what a structure-only framework leaves unaddressed.
One key point is that all of the thousands of communication tips don’t get the job done unless we tie them to an overarching approach. Another key point is that FINESSE is a system, which means you don’t have to be a natural or gifted presenter to be an effective communicator – just trust the system and your approach.
From the Real World
We had been selected to perform the feasibility assessment for an incinerator project that proposed gas-to-energy. A big milestone presentation with the governing commission was in two weeks. I got the call that I had been expecting from one of my bosses.
“JD, I assume we need to get Carl up there to give the presentation to the board?” he asked. Carl was one of our global experts in incineration gas-to-energy projects.
“Yes, I would like for him to be here. But there is no reason for him to do the presentation, I replied. “He would be of great support as an expert during the Q&A period.”
”What? You are going to do a highly technical presentation without a technical expert?”
“Yes, I calmly replied. Carl has done great in our technical workshops and one-on-one with the client’s engineers. And we have all of his technical memos that we will provide to the commissioners in advance,” I explained.
“But you don’t want him to present?” my boss replied, a bit frustrated. “That’s not the way we usually do it. Why not have him explain the technical aspects?”
“Because that’s not what the commissioners need. I know that because I have already asked them. “They want to understand the business case – the risks, the pitfalls, and the financial boundaries.”
Clarity Creates Confidence
Technical presentations succeed when they create confidence for the decision maker. Confidence comes from clarity related to the issue at hand- not how smart you are, how hard your team worked, how much information you have, or that you claim to have a better “mousetrap.” When executives are making big, complex decisions, they want to know that you understand their issue, its implications for them, and their choices. With that, they can make decisions more quickly and with greater conviction.
Creating Technical Presentations That Succeed
A strong technical presentation is a decision support tool, not a data dump. When you structure your communication with intention, you help executives move forward. After all, we are not judged by how much we know — we are judged by how well we turn it into a decision.
First published as: Solomon, J. D. (2026, September 16). Why most technical presentations fail. Communicating with FINESSE. https://communicatingwithfinesse.substack.com/p/why-most-technical-presentations?r=1g8fml
JD Solomon champions practical communication skills that help technical professionals convey complex ideas clearly and confidently. Learn more at www.jdsolomonsolutions.com and www.communicatingwithfinesse.com.
Comments