
59. How to Get Management to Understand Technical Concerns
“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.
Flere episoder fra "Successful Speaking for Technical Professionals"



Gå ikke glip af nogen episoder af “Successful Speaking for Technical Professionals” - abonnér på podcasten med gratisapp GetPodcast.








