When I was in graduate school I was very lucky. I was fully supported the entire time. The funding level wasn’t great, but it wasn’t all that bad either. Still Here Too worked full time in a field reasonably related to her chosen field. So our life was pretty good. I was basically paid to perform the research required to complete my PhD. The first year, all students were required to serve as teaching assistants. This included teaching laboratory classes and tutoring sessions for the, as we in our less-than politically correct manner referred to, “Physics for Dum-Dums†classes (this was way before the “…for Dummies†book series came along). As you might guess, the higher-ranked (note: big-ego, top-scoring, we know we are the smartest in this bunch) graduate students (pat myself on the back now) could not wait to get this requirement out of the way so we could get on with real business of becoming big-shot scientists.
Now that that I am older and wiser (just older many would say), wait a minute, I am not that old! Now that I have used my many talents in many different scenarios (yeah, I like that better), I must admit, that I actually learned some very valuable lessons from my time as a teaching assistant. While at the time, I was definitely anxious to finish the mandatory assignment and get on with the fun stuff (research), I did take the assignment seriously and tried to communicate with the students in ways that they would actually understand the basic concepts behinds the subject. Physics, or at least the parts of Physics that really interests me, is essentially trying to explain behaviors of the universe with mathematical models. (To be perfectly honest, I really “get my kicksâ€Â by using computer models of mathematical models to explain behaviors of the universe – but that is probably a personal problem) The majority of the students in these classes would be what you would call mathematically challenged. Many of them were quite intelligent, just not very strong in math. They were taking the Physics class because it was a requirement for their degree. So, I had to work to communicate without using the terms that I would use if I were discussing the topic with another physicist. In fact, I had to communicate using analogies that would get the concept across in ways that often actually described the workings of the mathematics as much as the Physics.
For the remainder of my academic career, I really was not faced with having to communicate to audiences not expert in the field. As I have said, I was one of the higher-ranked graduate students who was supported totally by research. After completion of my doctorate, my faculty positions were entirely research and graduate-level teaching focused. One certainly did not use explanations that avoided the use of mathematics at that level.
Once I made the great escape from the ivy-covered institution (and there actually was a lot of ivy at my last institution) to the world of corporate America, I was immediately faced once again with having to explain complicated technical results to intelligent but not necessarily-technical or mathematically inclined managers. My first position when I left academics was to provide oversight of a remotely-located R&D center. So I had one foot in the world of third-order, coupled differential equations, and non-linear optics (a topic I was learning on the fly, but that is what you do in industry, plus it is fun) and the other foot in business requirements, planning, and financial consequences (another subject I was learning on the fly – also fun) where you have to get the point across quickly without resorting to jargon, tech-speak, equations, math, etc. I very quickly realized that what I really had to do to succeed, more than anything else, was figure out how to communicate to the R&D center what the business requirements were in terms they could understand and communicate to upper management the results of the R&D Center and how it impacts the business in terms they could understand. Basically the same communication issue I faced when I was a teaching assistant in both directions, from me to the students and from the students to me. And quite honestly, I found that the same techniques worked.
Before every presentation you make, but especially every presentation to management, make sure
You can clearly express to yourself what point you wish your audience wants to leave understanding – I made a point of thinking through what the students really needed to understand before each lab or class session. If I could not express this to myself, in one or two simple sentences, then I knew I was going to be scrambling once I got started with the session. The same is true with any presentation you make in industry. Before you stand up, if you cannot summarize the point you are trying to make in one or two sentences, you will stumble somewhere in your presentation.- Keep the jargon, buzz-words, equations to a minimum – they have their place and are appropriate for use when communicating to management, but only if they terms or simple equations are ones that are likely to be used repeatedly in non-technical discussions and if simple definitions either have already been giving to your audience or if you have the opportunity to slowly walk through the definition.
- If you are asked a question to which you do not know the answer, SAY YOU DO NOT KNOW! Say you will get the answer. Commit to when you will have the answer or when you will be able to commit to a date for providing the answer. But NEVER, NEVER, NEVER make up an answer on the fly. Fastest way to sent your career down in flames!
- Take your time! Probably the biggest mistake I see young scientist make when briefing management is trying to present too much information. Pace your presentation to your audience. Pay close attention to how they are reacting to the presentation.
- I can assure you that there is a greater chance that you will finish with no questions, be thanked, and find that for some reason your career ends up relegated to being just one of the middle-of-the-road positions if the first few times you brief management you buzz through page after page filled minute detail.
- On-the-other-hand, I am fairly certain that if in your first few opportunities to brief management, you present a clear statement supported by easy to follow, clear supporting detail presented at a summary level; when asked any questions, you answer directly, taking time to make sure the person asking the question feels they understand the answer to their satisfaction; that you are very careful not to deviate you discussion off into topics unrelated to the issue being discussed; then you will finish, be thanked, and find that you are asked to brief management again, likely asked to take addition responsibilities, and if you continue to perform well, advance to higher and higher levels within your company.ÂÂ
Never forget, you are being paid to do the technical work. Management expects your work to be accurate and complete. In general, you will find that when you enter into a position, you enter being trusted. If you give management reason to believe this trust is justified, you will be drawn further and further into the trusted circle. If you give management reason not to trust you, you will find they have the memory of elephants, very long! This is actually easy to understand. Your input is used to make decisions. Bad information leads to bad decisions, Bad decisions leads to bad business performance. Bad business performance costs management, and you, their jobs.









