CHAPTER TWELVE: COMMUNICATION

A brief break from the deep subject matter expertise posts, because it has me thinking broadly about scientific communication. Specifically, that formal training (i.e. undergrad and grad school) never prepared me for real scientific communication.

The focus in school was always communicating science to non-scientists, usually children from middle school through high school. While getting kids interested and excited about STEM subjects, this focus on middle/high school scientific communication really did me a disservice in my professional life and probably even my personal life.

There are so many more facets to scientific communication that really don’t get addressed sufficiently in higher education circles. I’m thinking about how I have, professionally, had to figure out communicating very technical, jargon-heavy concepts to a variety of really smart people who have expertise outside of my hyper-focused niche. The way I might approach communicating what I do (mass spectrometry, proteomics, transcription factors, etc) completely depends on the audience. A venture capital investor, for example, is thinking about things from a financial perspective, while a pharmaceutical scientist is thinking about this from a drug discovery perspective, and an oncologist is thinking about the outcome and impact on patients in a clinical trial. Nobody is “wrong”, nobody is smarter than anybody else, everyone’s just thinking about the same thing from a different perspective and with a different lens. 

It follows, then, that communicating the same topic needs to be framed specifically for different audiences. It doesn’t mean that the core concepts are changing, just that the language needs to be different for the most effective communication. Maybe language is an interesting parallel, where translating the same message into different languages shouldn’t change the core message, but using the right language for the right audience is going to make communication much easier than forcing everyone to do the translations themselves, or even worse just zone out and not even listen to the message at all.

None of my undergraduate or graduate school outreach opportunities touched on this concept of science communication to adults, really. As far as I can recall, it always focused on making fun, hands-on “labs” or demonstrations for kids to learn scientific concepts. Then I got into the “real world” and suddenly cute little demonstrations aren’t really working anymore.

An obvious example of where scientific/STEM communication can go really right or insanely wrong is with policy. Policy makers might consult scientists and doctors and other professionals, piece together all of the best expert advice to write into laws or regulations or recommendations, but without effective communication, policies are relying solely on people following guidance based on an appeal to authority. Sometimes that works, but a lot of times it doesn’t. In my own work, appeal to authority has very rarely worked out. I don’t have much authority outside of my hyper-niche specialty, and so the communication (good or bad) is weighed much more heavily.

I think there’s a lot we could learn about communication, as a scientific community, from novelists and screen/scriptwriters. Crafting a story can help hook an audience into a message. This is another place where grad school trained me, but maybe trained me specifically to give scientific talks to scientific audiences; I’ve had to relearn how to build a “story” based on the sort of “plot” or pacing that communicates the message best.  I think there’s parallels between classic literature tropes (e.g. hero’s journey, tragedy, comedy) that could get translated really well through the lens of telling a scientific story. There’s some examples of nonfiction biographies or histories that have done this for biotech stories, like the books Living Medicine and Billion Dollar Molecule, that retell the history of bone marrow transplants and the pharmaceutical company Vertex’s founding respectively, but they do it with a framing that helps tell the historical story and scientific journey in a way that is nice to read.

I’m sure with both of those books that the exact history isn’t perfectly captured, and in part can never be because the way the stories are told involves so many peoples’ specific memories and emotions and motivations, but the general approach is something I really admire from a communication standpoint.

I think the books work so well, in part, because the reader can pattern match the general story arc to other novels. There’s some backstory setting up the scene and the characters, there’s some tension or suspense that puts the main characters through a challenge, and then there’s a resolution by the end of the book. There’s some subplots along the way, maybe some romance or comedy. 

Lack of storytelling is why a lot of scientific communication falls so flat. I’ve sat through a lot of scientific presentations that are just a linear chronology of all the experiments that the presenter has ever done. The right story, though, is almost never the chronological story. Although there’s some contexts where the chronological story is motivational to the audience, I think most audiences are thinking ”Why should I care?” so you need to directly say out loud why they should bother listening and paying attention to you. For startup pitch decks, usually the first slide is either directly stating the problem that the company proposes solving, or it’s the financial opportunity (market size); both of which directly tell the audience why they should care because it’s a problem that they themselves can recognize or it’s an opportunity to make money. For a scientific presentation, usually an element of teaching goes a long way, so that the audience cares because you’ve taught them something new. (Put another way, making the audience feel smart/smarter is a good motivator for a scientific audience, who is probably always looking to learn more.)

In scientific manuscripts for peer reviewed journals, there’s definitely a certain pattern that I’ve come to expect from papers. For a basic four-figure paper, the first figure is some kind of method or overall experimental schematic. The second figure is a high-level visualization of the data, like a heatmap or a dimension reduction like principal component analysis (PCA), t-SNE, UMAP. The third figure is a deep dive into some slice of that big dataset, just visualized differently. And then the final figure is some orthogonal experiment to prove figure three correct, and/or a schematic of some biological mechanism that the data suggests. Pattern matching that template helps get through papers pretty quickly, because I can just flip to the figures and usually they follow some general flow like that.

Having some portion of the communication being predictable helps get the message across. If the message itself is unexpected or difficult, then having the medium be predictable or the presentation be predictable can help, I think. Predictability isn’t a bad thing. There’s something comfortable about knowing what to expect, and when it changes abruptly, it can be jarring. I’m thinking about things like when your favorite band has a particular style of music that they produce, but then there’s that one weird random song that doesn’t fit the vibe and sticks out badly. (Of course, some people are amazing across genres, and there’s some scientists like that, too, who can easily hold their own across multiple fields.)

Something I use almost always in my scientific presentations is a “three-act” structure. My talks almost always start with some brief introduction to set the “scene”, maybe 10-15% of the total talk. Then, I set up three main, take-home messages for the audience, and each of the three is about 25-30% of the talk and somewhat builds on each other. Finally, with the remaining 10-15% of the talk, I have some “cliff-hanger” future work, but not whatever the next obvious logical step would be based on what I’ve said, but some more distant future vision. It’s not something that I happen to do, it’s something that I pointedly intentionally do whenever I sit down to organize a talk. I usually start by deciding on the three main messages, set each of those up, then do a little scene-setting/exposition at the beginning that gives just enough context for the three messages, and then a little bit of forward-thinking “cliff-hanger” at the end. I don’t claim to be the best presenter or anything, but I’ve been invited to speak quite a bit so I figure something must be resonating.

None of this is meant to be an immediate solution to any scientific communication struggles, and again to be clear I don’t mean to imply that I’m a significantly better communicator than anybody else. In part, this is because I don’t think we scientists get enough training on communication, and in part because it’s just hard anyway, even if we did get trained. I’m inspired by writers, though, because I think if we structured scientific communication to lean on common literature, like plot devices and story structure, we’d probably capture a wider audience and have more buy-in and support from policy makers, funding agencies, and even the general public.

CHAPTER NINE: LIMINAL

The purgatory of being in-between naive beginner excitement and rational experienced master is basically where I live for most skills, just right there in the Trough of Disillusionment on the Gartner hype cycle. It feels like there’s a ton of support for “getting started”, and a ton of support for highly niche specialization, but just not a lot that helps you get through the purgatory of “intermediate”. This goes for learning a new language, or how to code, or baking, or entrepreneurship, or writing, or managing, or whatever. There’s so much out there to support the zero-to-one initialization, and then there’s deep subject matter expertise, but the “messy middle” is really hard, seemingly endlessly wandering through a liminal space.

I don’t really feel like I’m hitting “enlightment” in anything, just maybe finding how much farther down the “disillusionment” goes, but I’m also not anywhere near “inflated expectations” for any of my skills so that seems to put me pretty solidly in the “intermediate” range. I love picking up new things – I mentioned before that I challenged myself to learn how to bake macarons, and that I wanted to learn how to code so I joined a machine learning lab – and it’s so frustrating to get the basics down then just have zero resources to get through “intermediate” to “fluent” or “advanced”. There’s the 10,000 hours rule, which says that it takes 10,000 hours to master a skill, but that seems to emphasize the point that there’s always tons of resources to help you with the first 10-100 hours, but after that it’s just supposed to be grinding until you reach near-mastery and can get into the ultra-deep niche groups, I guess.

So how do you get through “intermediate” to be considered a “master”? Although it’s the 10,000 hour rule, realistically that’s more like 5 years of fairly dedicated training, so about the average American science PhD program. The first year is structured classes like high school or college, with more in depth materials, but after the first year or two it’s all unstructured research, largely self-guided with some input from your PhD advisors and thesis committee members. In the end, when you defend and get the “PhD” letters after your name, society generally recognizes you as a “master” in that subject, which is itself a hilariously sub-sub-sub-field specific niche, a tiny drop in the vast vast ocean of human knowledge.

In the things where I’m “intermediate”, I don’t feel like I make a lot of progress after those first 1-2 years of structured learning. Maybe because the rest all needs to be self-guided? I wish there was more structure out there for intermediate anything, to at least learn more about what I need to learn. 

I probably just need to learn to embrace the journey that is being “intermediate” and find ways to enjoy the process more.

CHAPTER ONE: PEDAGOGY

Top of my mind today was getting my lecture slides submitted for the ASMS Fall Workshop on Fundamentals of [Mass Spectrometer] Instrumentation. Although I first got my lecture topic assigned back in June (“Instrumentation for Quantitation of Large Numbers of Analytes”), I honestly didn’t think too deeply about it until early October when we were asked to submit a rough draft on October 14. The rabbit hole here is the theme of “procrastination”, but in an attempt to stay on topic, let’s explore my approach to building lectures.

First, a disclaimer that I’m not formally trained in education or teaching. I got a crash-course on putting together lesson plans and curricula, and general teaching/learning approaches when I first arrived in South Korea for my Fulbright scholarship to teach English, specifically, speaking/listening to English at a rural high school although I also prepped a smaller group of high schoolers for the Test of English as a Foreign Language (TOEFL). (Hello out there, Chungnam Internet High School!) This was back in 2009, so all our materials were paper print outs and chalk boards, and unfortunately I don’t have anything besides my memory to pull from, but a few things did stick with me and I keep them in mind when I’m putting together lectures today.

Second, I never have to teach from a textbook or follow a prewritten curriculum of learning objectives, so I have a lot of freedom on what exactly I deem “important”. I assume that if I had to teach specific exam materials or follow a textbook, a lot of my approach would fall apart. I usually am lucky to get even a general theme/topic to teach about, let alone have specific objectives or test materials.

Third, these days I’m always teaching professionals who are for the most part self-motivated to learn the material, so classroom management isn’t much of a concern. When I was teaching the high schoolers in Korea, classroom management was much more of a challenge. Punishments were handled primarily by their “real” teacher, who accompanied them to my classroom, but it was still expected that I make an effort to maintain the students’ attention and discipline where/when needed. These days, I might teach some undergraduates here and there, but usually I’m working with professionals who are paying good money to take my courses, so my motivation is more my own desire to make sure they get their money’s worth of material.

Finally, all of this is predicated on and influenced by my own personal learning preferences. I think, in general, preferred teaching style complements preferred learning style; similarly, your preferred management style mirrors how you like to be managed, how you mentor others mirrors how you prefer to be mentored yourself, etc. More on that in a later post, I think.

With all that established, here’s how I approach putting together a lecture or workshop.

STEP 1. Decide on the 2-3 main things you want the participants or students to remember.

Generally, starting at the end is always a good idea with any kind of presentation or communication. If you set the objective before you get carried away in the details (or in recycling old material), you can keep that “North Star” in mind in building out the background, proof, and conclusions for each of the main points you need to make. (Note: The idea of having a “North Star” as specific verbiage is something that is talked about a lot in the startup space, in the sense of keeping some guiding principle or vision and tying everything you do back to that singular goal.)

These 2-3 things become your “home slide” (a term I’m shamelessly stealing from the seminar course at the University of Washington’s Genome Sciences department), which is a slide that you’ll use as a recurring anchor point throughout your lecture or presentation. It’s a sort of agenda or syllabus, which reinforces the points that you’ve made, the points that you’re going to make, and then is a summary reminding the participants or audience what you want them to remember from your lecture. (This ties into “Step 3: Repeat everything three times”.) Sometimes I’ve seen this so that each of the points on the home slides is a question that is answered at the end of the section, which also works.

Structuring your lecture around key concepts allows you to set up multiple break points for the participants to check in with themselves and make sure they understand each point before you move on to the next. It also makes it crystal clear what you want the participants to learn so there’s no ambiguity. 

STEP 2. Incorporate more than one learning style.

This whole entry is pretty poorly cited (actually, there’s not really any references) but I recall some learning styles being visual, auditory, and hands-on. (There’s probably real pedagogical terms for these, but again I’m not formally trained.) Personally, I learn best with the “hands-on” approach – I can read a text book until I have it memorized, or listen to hours of lecture, but I won’t really grok something until I have to use/apply/do it myself. For example, learning a new experimental protocol or how to calibrate an instrument. I could read about the theory and watch people do it dozens of times, but it won’t really sink in until I’ve done it myself.

It’s almost always a given that a lecture will consist of a slide deck and presenting said slide deck, so arguably there’s always at least two learning styles accommodated. However, some slide decks seem to be entirely text on slides, which I think goes against the spirit of visual learning. I try to keep text minimal on my slides and use more pictures, schematics, or even just icons to communicate the core vocabulary I’m using verbally. 

And when building a workshop agenda or a lecture that’s more than 30 minutes long, getting at least one “hands on” or applied piece worked in. A lot of workshops I teach involve software usage (specifically, how to use the Skyline software for mass spectrometry data analysis) so there’s a whole slew of step-by-step tutorials and demonstrations I’ve built up over the years. But for conceptual lectures or workshops, sometimes this can be done by posing a thought question that bridges into application. For example, when I’ve taught statistical design of scientific experiments, I’ve posed some sample sets and asked participants to either think for a minute or divide into groups to talk about how they might block and randomize those samples, given a particular experimental question. When I’ve taught day-long workshops, I’ve closed out the day with a good ol’ Kahoot quiz, focusing on the 2-3 main points of each of the day’s lectures to reinforce the most important things I wanted people to remember from the day.

As a super-niche technical aside, I think this is one of the hardest barriers with (almost) all the mass spectrometry and proteomics workshops out there. I can think of only three that include a wet-lab “hands on” component: Cold Spring Harbor’s Proteomics course, MRM Proteomics workshop, and Brett Phinney’s proteomics school at UCD. To my knowledge, there’s no undergraduate, masters, or PhD program specifically for mass spectrometry or proteomics, unlike genetics, so to break into the field the only real options are to start out in analytical chemistry or biology, and pick up the mass spectrometry or proteomics through research experience.

STEP 3. Repeat everything three times.

We were drilled at Fulbright teacher training to repeat everything at least three times, ideally once in each learning style (Step 2). Thinking back, this is also how I was officially trained in assays during my internship at Wyeth Pharma (purchased by Pfizer since then) with a “watch one, do one together, do one being observed” triplicate before I was signed off as being trained. I still try to do training in the Talus lab with that in mind, and don’t expect independence on any task or protocol until we’ve done at least one iteration of “watch one, do one together, do one observed”. This also follows Step 2 of using more than one learning style, with one being visual and one being hands-on.

As a personal aside, it also follows some of the parenting books I’ve read, like Hunt Gather Parent which (although problematic in some ways, in my opinion) raises a good point that toddlers and young kids learn a lot by observing and then mimicking.

This is maybe something I took too much to heart, because some of the faculty feedback I recall receiving during my PhD training was that I repeated myself too often in my research report presentations. Habits die hard, I guess.

FAILURE MODE 1. Firehose of information.

A lot of really smart people seem to have a hard time placing lecture material in context and default to a tidal wave of information. I’m definitely guilty of the firehose approach, especially on super condensed course timelines where I’m trying to cover as much ground as possible in limited time, hoping that my Step 1 2-3 main points per lecture will be an oasis for participants to hang onto while I barrage them with references, rabbit holes, and random factoids that might be jumping off points for them to dive deeper in the future. Without having those 2-3 main points to anchor the core take-home messages and reiterate the high level objectives, getting a deck crammed full of paper citations and heavy content is disorienting and disheartening for participants, in my opinion.

FAILURE MODE 2. Overwhelming jargon.

Mass spectrometry and proteomics is hugely guilty of jargon overload. It becomes almost a second language, and teaching in a “second language” makes it even harder for participants trying to learn core concepts. Lecture material should strip away as many acronyms and jargon as possible, and ideally provide a dictionary or quick reference for participants to keep handy as they navigate the content.

FAILURE MODE 3. Failing to connect to the audience.

The exact same lecture topic should be presented completely differently if the audience changes. A lecture on “figures of merit” given to a room full of analytical chemists looks completely different from a lecture on “figures of merit” to a room full of biologists. And even more so if that room goes science-adjacent, like operations or business development. This kind of reframing is hard to do without empathy – the audience isn’t more or less smart, they just come with a different set of prior knowledge and a different motivation for learning the material. The 2-3 main points that an analytical chemist should walk away with from a lecture on “figures of merit” should be different from the 2-3 main points that a Vice President of business development walks away with. Starting from that very first Step 1, then, the entire content shifts to match the learning objectives.

SUMMARY

I wouldn’t call myself an excellent teacher, but over the last 16 years (yeesh, that math hurt to realize) since I got that initial crash-course on teaching and pedagogy, I’ve continually refined my specific lectures and my overall approach, and I’m getting pretty good course reviews these days. I’ll always be iterating and incorporating new feedback, but I think these core concepts will probably always remain a foundation in how I put together teaching material.

EPILOGUE

On my run today, I let my mind wander and spiral across the idea of “pedagogy” and teaching. Below are some of the things that spun out of the main theme as I jogged through the park on a beautiful autumn afternoon.

I struggled quite a bit in college as I worked for my bachelor’s in biochemistry and molecular biology. My degree required multiple chemistry courses: inorganic, organic, physical (thermo and quantum); however, hilariously, I did not have to take analytical chemistry, which is the one I’ve basically landed in professionally. It also required multiple physics courses: mechanics, electricity and magnetism, wave motion and quantum. My grades were, as the now-classic Chernobyl HBO series meme goes, “Not great, not terrible.” Started pretty strong but more and more C’s as I got deeper into the trenches. I wonder if part of it was that the lab portions got less and less “hands-on” and more abstract as the semesters went by. I love the inorganic and organic chem labs, where you got to “make” things; the physical chem labs were more mathematical proofs and practice problems than the hands-on stuff that helped me learn. (Not that I’m suggesting I know of any hands-on labs for quantum that would have helped me in the exams, but just reflecting back on my own failures and wondering what I could learn from them.)

While having a “hands-on” preference might suggest that I don’t learn well by reading or listening, I do love to read, although I’m not sure I really fully read every word. Instead I kind of skim over the lines and pages and get the general vibe, which is great for leisure reading but pretty terrible for studying. When I applied for the Fulbright to Korea during my senior year of undergrad, I started studying the language with two semesters of Korean classes. Nothing stuck quite as much as when I moved there and was suddenly fully immersed – my home-stay family spoke some English, but obviously used Korean with each other so I was surrounded at home, at work, and going about my day. I picked up so much more Korean with that kind of hands-on practical experience, even things I should have learned during undergrad Korean classes like simply introducing myself. 

It’s no surprise then that when I went to graduate school, under the advice from my excellent post-bacc PI to learn statistics and programming, I ended up with my PhD joint-advised in a machine learning laboratory having only just learned the very first basics of coding ~6 months prior. (I did, technically, take some visual BASIC in high school and then again in college, but that’s a poster for another day.) To learn the language of statistics and computational biology, there was no better method for me, personally, than to go “full immersion”, sink-or-swim by throwing myself directly into the deep end. I wouldn’t say I ended up the strongest computational biologist that ever graduated from that machine learning lab, but I also wouldn’t say that I couldn’t hold my own. I still keep the physical print-outs of my performance reviews from that PI at my desk as a reminder to do hard things.

(PS – I may return to this topic, or branch off it at least, since I already have a few more thoughts about how it relates to science communication. Nevertheless, today I got to ~2300 words, about 3x more than yesterday! Whether it was the theme, or the run, I’ll take it.)