Successful Speaking for Technical Professionals

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” — Antoine de Saint-Exupéry — French Writer and Aviator

Technical presentations often run over because engineers and other technical professionals try to fit too much information into too little time. 

Effective time management means prioritizing essential information, rehearsing your delivery, and controlling your presentation’s pace.

In this week's podcast, we will explore three ways to manage your time during your technical presentations.

References

• Massachusetts Institute of Technology (MIT), Electrical Engineering and Computer Science Communication Lab. "Slide Presentation," CommKit. Explains how to organize technical presentations around a central purpose, limit each slide to one primary message, and prepare backup slides for technical questions. Read MIT guidance. mitcommlab.mit.edu
• Toastmasters International. "Manage Your Speaking Time," Toastmaster Magazine, February 2025. Discusses the importance of respecting presentation time limits, practicing aloud, and preparing presentations that fit their allotted duration. Read article. 
• MIT, Nuclear Science and Engineering Communication Lab. "Delivery and Q&A," CommKit. Recommends rehearsing early, timing transitions, controlling speaking pace, and preparing for audience questions. Read MIT guidance. mitcommlab.mit.edu
• Toastmasters International. "25 Ways to Nail Your Workplace Presentation," Toastmaster Magazine, May 2018. Advises speakers to rehearse in real time, focus on their central message, and remove content rather than accelerate delivery when running overtime. Read article. 
• Joel Schwartzberg. "10 Ways to Prepare for a Work Presentation," Toastmaster Magazine, March 2026. Provides practical guidance on defining a presentation's main point, eliminating unnecessary material, and rehearsing aloud to improve clarity and efficiency. Read article. 

___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparation time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience, and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“We are what we repeatedly do. Excellence, then, is not an act but a habit.” — Will Durant, American philosopher and historian.

As I write this, I am sitting in the dealership where I have brought my SUV in for its 60,000-mile maintenance.

Most people agree that to keep your car running as long as possible, you need regular maintenance.

However, how many of us technical types realize that, to maintain excellent technical communication skills, we also need scheduled maintenance?

Your technical communication skills deserve the same attention to ensure every presentation delivers maximum impact.

In this week's podcast, you will discover three ways to maintain peak performance in your technical speaking.

References

• Gallo, Carmine. (September 9, 2019). "How to Rehearse for an Important Presentation." Harvard Business Review. Explains the importance of systematic rehearsal and reviewing recorded presentations. Read article.
• Toastmasters International. (2023). "Expert Advice for Evaluations." Toastmaster Magazine. Describes structured feedback and continuous improvement through speech evaluations. Read article.
• MIT Electrical Engineering and Computer Science Communication Lab. "Slide Presentation." Guides technical presentation design, equipment preparation, and handling audience questions. Read guide.
• MIT Electrical Engineering and Computer Science Communication Lab. "Virtual Presentations." Recommends practicing delivery, checking technology, and evaluating presentation clarity. Read guide.
• Toastmasters International. "How to Write and Deliver a Speech." Provides practical techniques for vocal variety, recording presentations, and gathering feedback. Read guide.

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“The right word may be effective, but no word was ever as effective as a rightly timed pause.” — Mark Twain, American Author and Humorist

You have attended technical presentations where the speaker talks too slowly or too fast.  If the speaker keeps these paces throughout their presentation, they will lose you. 

Your speaking pace can determine whether your audience understands your technical message or gets overwhelmed. 

Even the most innovative engineering solution can lose its impact when presented too quickly, too slowly, or without meaningful pauses.

The key is to speak at a pace that allows your audience to understand, process, and remember your message. 

Here are three strategies you can use to improve the pace of your technical presentation delivery.

References

• Mayer, Richard E., and Roxana Moreno (2003). "Nine Ways to Reduce Cognitive Load in Multimedia Learning." Educational Psychologist, 38(1), 43–52. Explains how limited cognitive processing capacity affects learning and why reducing information overload improves comprehension
• Reynolds, M. E., and J. Givens (2001). "Presentation Rate in Comprehension of Natural and Synthesized Speech." Perceptual and Motor Skills, 92(3), 958–968. Examines comprehension at speaking rates of approximately 130, 150, 170, and 190 words per minute, finding no significant effect of rate on response latency within this range in the study's sentence-verification task. 
• Lasky, Elaine Z., William E. Weidner, and John P. Johnson (1976). "Influence of Linguistic Complexity, Rate of Presentation, and Interphrase Pause Time on Auditory-Verbal Comprehension of Adult Aphasic Patients." Brain and Language, 3(3), 386–395. Investigates how slower delivery and pauses affect comprehension in adults with aphasia, providing evidence about processing time in that specific population. 

___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparation time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience, and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“The audience is not the enemy. They are the reason we are there.” — Nancy Duarte, presentation expert and author of Resonate: Present Visual Stories That Transform Audiences (2010)

Imagine spending weeks preparing a technical presentation, only to watch your audience lose interest within minutes. Your information may be technically brilliant, but brilliance means little if nobody is listening.

Engineers frequently present complex information to colleagues, managers, executives, and customers. Unfortunately, technical accuracy alone does not guarantee audience engagement.

An effective technical presentation must capture attention, maintain interest, and encourage action. Your challenge is to make complicated information understandable, relevant, and memorable.

In this week's podcast, we will explore three ways to keep your audience engaged throughout your technical presentation.

References 

• Alley, Michael. (2013). The Craft of Scientific Presentations: Critical Steps to Succeed and Critical Errors to Avoid. 2nd Edition. Springer. Explains how scientists and engineers can structure technical presentations, design effective visuals, and communicate complex material clearly.
• Mayer, Richard E. (2021). Multimedia Learning. 3rd Edition. Cambridge University Press. Describes evidence-based principles for combining words and graphics to improve audience understanding and learning.
• Duarte, Nancy. (2010). Resonate: Present Visual Stories that Transform Audiences. John Wiley & Sons. Explores audience-centered storytelling, presentation structure, and techniques for making messages compelling.
• Heath, Chip, and Heath, Dan. (2007). Made to Stick: Why Some Ideas Survive and Others Die. Random House. Introduces six principles for making ideas memorable, including simplicity, concreteness, credibility, and stories.
• Kosslyn, Stephen M. (2007). Clear and to the Point: 8 Psychological Principles for Compelling PowerPoint Presentations. Oxford University Press. Applies cognitive psychology to designing slides that direct attention, reduce confusion, and improve comprehension.
• Freeman, Scott, et al. (2014). "Active Learning Increases Student Performance in Science, Engineering, and Mathematics." Proceedings of the National Academy of Sciences, 111(23), 8410–8415. https://doi.org/10.1073/pnas.1319030111. Provides research supporting active participation as an effective learning strategy in STEM education, with principles that can inform interactive technical presentations.

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“Cost, Schedule, and Risk are the three items foremost in a decision-maker's mind.” — Eric C. Stasiunas, How to Educate Decision Makers on the Value and Necessity of Modal Testing and Model Correlation: Tips for Young Engineers, NASA Technical Reports Server, NASA Engineering and Safety Center, 2021

Changing requirements are not necessarily evidence of poor engineering; they often result from learning more about the problem, customer, technology, or operating environment. 

The engineering challenge is to manage change deliberately rather than allowing it to become uncontrolled requirements creep. NASA    NASA Science

In this podcast, we'll consider three ways to help management understand technical concerns.

References

• NASA, NASA Systems Engineering Handbook, NASA/SP-2016-6105 Rev. 2, Section 6.2, Requirements Management. Discusses evaluating requirement changes for effects on cost, schedule, architecture, design, interfaces, technical requirements, and other system elements. NASA
  NASA Systems Engineering Handbook
• NASA, “6.2 Requirements Management.” Describes baselining requirements, managing changes throughout the product life cycle, maintaining bidirectional traceability, evaluating change requests, and maintaining consistency among requirements and system design. NASA
  NASA Requirements Management guidance
• NASA Software Engineering Handbook, SWE-053, “Manage Requirements Changes.” Provides detailed guidance on capturing proposed changes and analyzing their cost, schedule, technical, stakeholder, safety, testing, and rework implications before implementation. SWEHB
  NASA Software Engineering Handbook — Requirements Changes
• NASA Procedural Requirements NPR 7123.1B, NASA Systems Engineering Processes and Requirements. Specifies formal requirements-management activities including change procedures, traceability, review of engineering change proposals, documentation, and dissemination of approved changes. Nodis3
  NASA Systems Engineering Processes and Requirements
• NASA Systems Engineering Handbook, “Requirements Creep.” Defines requirements creep as incremental growth in requirements that can produce a system more costly and complex than originally intended, emphasizing the importance of disciplined change management. NASA Science

___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparatory time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience; and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“As an evolving program is continually changed, its complexity… increases unless work is done to maintain or reduce it.”  — Meir M. Lehman, computer scientist and pioneer of the Laws of Software Evolution

Engineers can spend large portions of their time fixing legacy systems, addressing defects, updating documentation, and dealing with technical debt instead of designing and building something new.

When engineers complain about “too much maintenance and too little real engineering,” the underlying issue is usually not maintenance itself. 

It is repetitive, reactive work that consumes capacity that should be spent producing permanent improvements, innovation, and better designs—what Google’s Site Reliability Engineering literature calls excessive “toil.” Google SRE

Consider three methods in this podcast to reduce maintenance and increase engineering.

References

• Challoner, David, et al. “Eliminating Toil.” The Site Reliability Workbook, Google/O’Reilly Media, 2018. Provides methods for identifying, measuring, prioritizing, and eliminating repetitive operational work and recommends treating toil reduction as an engineering project. Google Research Google SRE — Eliminating Toil
• Rau, Vivek. “Eliminating Toil.” Site Reliability Engineering: How Google Runs Production Systems, Google/O’Reilly Media, 2016. Defines engineering toil and explains Google's objective of limiting operational work so engineers retain substantial time for long-term engineering projects. Google SRE
  Google SRE — What Is Toil?
• Google. “Introduction.” Site Reliability Engineering: How Google Runs Production Systems, 2016. Describes Google's 50% cap on operational work and its rationale for preserving engineering capacity to make systems more stable and operable. Google SRE  Google SRE — Introduction
• DORA. “Continuous Delivery.” Summarizes research connecting continuous-delivery practices—including automated testing and deployment—with improved delivery performance, quality, reduced rework and lower deployment pain. Dora
  DORA — Continuous Delivery
• Carnegie Mellon University Software Engineering Institute. “Managing Technical Debt with Data-Driven Analysis.” Describes technical debt as a tradeoff between short-term delivery and the long-term ability to evolve, modify, repair, and sustain systems, and emphasizes actively identifying and managing that debt. SEI
  SEI — Managing Technical Debt

___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparatory time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience; and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“The extra effort that it takes to add new features is the interest paid on the debt.” — Martin Fowler, British software developer, author of Technical Debt, 2019, and international public speaker on software development

Engineers contend with technical debt daily.  But what exactly is technical debt?

Technical debt is the future cost created when an organization chooses a quick or suboptimal technical solution today instead of a more sustainable one. 

Like financial debt, the initial shortcut may provide an immediate benefit, but carrying it can create recurring “interest” through additional maintenance, rework, delays, and complexity. 

Schedule pressure, changing requirements, outdated technology, architectural decisions, inadequate testing, and deliberate shortcuts can all create debt that becomes increasingly expensive as a system evolves. 

Engineers must learn to convince executives that technical debt is a business problem. But how can engineers do this?

Explore three ways to do this in this podcast.

References

• Ozkaya, I., & Nord, R. — Carnegie Mellon University Software Engineering Institute. Managing the Consequences of Technical Debt: 5 Stories from the Field, May 13, 2019. Defines technical debt and explains how short-term design and implementation decisions can increase future costs and impede system evolution. 
• Besker, T., Martini, A., & Bosch, J. “Software Developer Productivity Loss Due to Technical Debt—A Replication and Extension Study Examining Developers’ Development Work.” Journal of Systems and Software, 2019. The study reports developers losing an average of approximately 23% of their working time because of technical debt. 
• McKinsey & Company. Breaking Technical Debt's Vicious Cycle to Modernize Your Business, 2023. Examines technical debt as a business and financial issue, including its effects on engineering capacity, modernization, operating costs, and organizational performance. 
• Carnegie Mellon University Software Engineering Institute. 5 Recommendations to Help Your Organization Manage Technical Debt, 2024. Discusses technical debt at the program level, including architecture, testing, documentation, technology refresh, sustainment, cybersecurity, and lifecycle consequences. 
• McKinsey & Company. Tech Debt: Reclaiming Tech Equity, 2020. Recommends that organizations treat technical debt as a business issue rather than merely a technology problem and link technical-debt reduction to business value, strategic priorities, and risk reduction. 

___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparatory time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience; and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“Meetings are a symptom of bad organization. The fewer meetings the better.”
— Peter F. Drucker, management consultant and author

One of the most frustrating activities for engineers is attending inefficient meetings.

Engineers are taught in engineering school to always use the most efficient design.  Why can’t this apply to the meetings they attend?

The truth is, meetings can be more efficient if you follow the three steps in this podcast.

References 

• MIT Sloan School of Management — Meredith Somers, “5 Ways to Avoid Ineffective Meetings,” June 17, 2020. Recommends cataloging issues in advance and measuring meeting effectiveness through decisions made and problems solved. 
• Atlassian — “How to Run Effective Meetings in the Era of Hybrid Work,” February 24, 2022. Addresses agendas, meeting objectives, attendee selection, decision-making, action items, and when information should be communicated asynchronously. 
• Atlassian — “How to Write an Effective Team Meeting Agenda.” Recommends prioritizing agenda items, defining meeting purposes, allocating time to topics, and giving participants advance preparation time. 
• Atlassian — “How to Turn Meeting Action Items Into Trackable Work.” Defines effective action items around an owner, specific action, scope, expected outcome, and deadline. 
• Atlassian/Confluence — “Meeting Minutes Template.” Recommends documenting agenda items, decisions, action items, owners, and deadlines while using time-boxes to maintain meeting focus. 

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

“When you get to about 70% of all possible data, it’s probably time to make a decision and not wait for the last 30. That’s judgment.” — General Colin Powell, former U.S. Secretary of State and Chairman of the Joint Chiefs of Staff

You’ve delivered your technical presentation, hoping executives in the audience will decide. But at the end of your presentation, no decision is made.  How frustrating.

Without a decision, you can’t move forward with your recommended action. What can you do?

In this podcast, you will discover three ways to steer an executive audience to a decision.

References 

• McKinsey & Company. “The Limits of RACI—and a Better Way to Make Decisions.” McKinsey & Company, 2022. Discusses explicitly identifying meetings as decision, discussion, or information meetings and defining decision-making roles. 
• McKinsey & Company. “Untangling Your Organization’s Decision Making.” McKinsey Quarterly, June 21, 2017. Recommends focusing decision meetings on solutions, using prework, bringing the necessary facts to the table, and clearly assigning ownership after decisions.  
• McKinsey & Company. “Want a Better Decision? Plan a Better Meeting.” McKinsey Quarterly, May 8, 2019. Defines the roles of decision makers, advisers, recommenders, and execution partners and emphasizes recommendations based on analysis of alternatives and trade-offs. 
• McKinsey & Company. “What Is an Effective Meeting?” McKinsey Explainers, January 17, 2023. Explains that decision-making meetings require clarity about who makes the decision and should produce a final decision rather than simply additional discussion. 
• McKinsey & Company. “If We’re All So Busy, Why Isn’t Anything Getting Done?” McKinsey Quarterly, January 10, 2022. Describes the DARE decision-rights model and the recommender's responsibility to analyze alternatives, explain pros and cons, and recommend a course of action. 

 ___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparatory time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience; and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.

 “Plans are worthless, but planning is everything.” — Dwight D. Eisenhower, General of the Army and 34th President of the United States

You deal with risk every day.

You deal with risk when you drive to work. You deal with risk every time your son or daughter plays soccer. You deal with risk as an airline passenger.

And you deal with risk every day as an engineer.  Risk management is part and parcel of your job. 

You face major risks when you embark on hardware and/or software development.  Your ability to identify, analyze, and recommend how to proceed with these risks determines your performance as an engineer.

So how can you present these risks without sounding alarmist?

In this podcast, you will discover three ways to do this.

References

• NASA. NASA Systems Engineering Handbook, Section 6.4: Technical Risk Management. Defines risk through scenarios, likelihood, consequences, and uncertainties and discusses mitigation, contingency actions, trigger thresholds, monitoring, and communication. NASA Technical Risk Management  
• Institute of Medicine. (2013). Environmental Decisions in the Face of Uncertainty, Chapter 6, “Communication of Uncertainty.” Washington, DC: National Academies Press. DOI: 10.17226/12568. Discusses numerical, verbal, and graphical communication of probability and notes the ambiguity inherent in terms such as “likely” and “unlikely.” National Academies — Communication of Uncertainty 
• National Research Council. (2006). Completing the Forecast: Characterizing and Communicating Uncertainty for Better Decisions Using Weather and Climate Forecasts. Washington, DC: National Academies Press. DOI: 10.17226/11699. Explains problems with verbal probability expressions and the advantages of numerical probabilities and relative frequencies. 
• National Academies of Sciences, Engineering, and Medicine. (2017). Communicating Science Effectively: A Research Agenda. Washington, DC: National Academies Press. DOI: 10.17226/23674. Reviews evidence on communicating scientific uncertainty and how audiences interpret numerical and probabilistic information. 
• McGuire, M. (2023). Lessons Learned With Risk Management: A Systems Engineer’s Perspective. NASA Technical Reports Server. Emphasizes risk management as a communication mechanism that allows engineering teams to identify concerns early and implement mitigation before risks become failures. 

___________________________________

Being a confident, engaging, and effective technical speaker is a vital personal and professional asset.  With more than 40 years of engineering experience and more than 30 years of award-winning public speaking experience, I can help you reduce your presentation preparatory time by 50%, overcome your fear of public speaking and be completely at ease, deliver your presentations effectively, develop your personal presence with your audience; and apply an innovative way to handle audience questions deftly. 

Working closely with you, I provide a customized protocol employing the critical skills and tools you need to create, practice, and deliver excellent technical speeches and presentations.  Let's connect and explore how I can help you become the exceptional speaker you were meant to be.  Please reach out to me at [email protected] or 703-509-4424 for a complimentary consultation.  Schedule a meeting with me at calendly.com/frankdibartolomeospeaks.   

© 2026 DiBartolomeo Consulting International (DCI), LLC. All Rights Reserved. May not be used without permission.