Creating a Narrative Arc in Training Presentations

Many amazing presenters fall into the trap of believing their data will speak for itself. But it never does… Our brains aren't spreadsheets, they're story processors. You may understand the importance of your data, but don't assume others do too. The truth is, data alone doesn't persuade…but the impact it has on your audience's lives does. Your job is to tell that story in your presentation. Here are a few steps to help transform your data into a story: 1. Formulate your Data Point of View. Your "DataPOV" is the big idea that all your data supports. It's not a finding; it's a clear recommendation based on what the data is telling you. Instead of "Our turnover rate increased 15% this quarter," your DataPOV might be "We need to invest $200K in management training because exit interviews show poor leadership is causing $1.2M in turnover costs." This becomes the north star for every slide, chart, and talking point. 2. Turn your DataPOV into a narrative arc. Build a complete story structure that moves from "what is" to "what could be." Open with current reality (supported by your data), build tension by showing what's at stake if nothing changes, then resolve with your recommended action. Every data point should advance this narrative, not just exist as isolated information. 3. Know your audience's decision-making role. Tailor your story based on whether your audience is a decision-maker, influencer, or implementer. Executives want clear implications and next steps. Match your storytelling pattern to their role and what you need from them. 4. Humanize your data. Behind every data point is a person with hopes, challenges, and aspirations. Instead of saying "60% of users requested this feature," share how specific individuals are struggling without it. The difference between being heard and being remembered comes down to this simple shift from stats to stories. Next time you're preparing to present data, ask yourself: "Is this just a data dump, or am I guiding my audience toward a new way of thinking?" #DataStorytelling #LeadershipCommunication #CommunicationSkills

Everyone loves a good story. You should be using your data to tell one every chance you get. The importance of narrative in scientific communication cannot be understated. And that includes communication in traditionally technical environments! One thing that gets beaten into you in graduate school is that a scientific presentation is a technical affair. Communicating science is fact based, it's black and white, here's the data, this is the conclusion, do you have any questions? Actually, I do. Did you think about what story your data could tell before you put your slides together? I know this is a somewhat provocative question because a lot of scientists overlook the importance of telling a story when they present results. But if you want to keep your audience engaged and interested in what you have to say, you should think about your narrative! This is true for a presentation at 'The Mountain Lake Lodge Meeting on Post-Initiation Activities of RNA Polymerases,' the 'ACMG Annual Clinical Genetics Meeting,' or to a class of 16 year old AP Biology Students. The narrative doesn't need to be the same for all of those audiences, BUT IT SHOULD EXIST! There is nothing more frustrating to me than seeing someone give a presentation filled with killer data only to watch them blow it by putting the entire audience to sleep with an arcane technical overview of the scientific method. Please. Tell. A. Story. With. Your. Data. Here's how: 1. Plot - the series of events that drive the story forward to its resolution. What sets the scene, the hypothesis or initial observation? How can the data be arranged to create a beginning, middle, and end? 2. Theme - Good vs Evil, Human vs Virus, Day in the life of a microbe? Have fun with this (even just as a thought experiment) because it makes a big difference. 3. Character development - the team, the protein, gene, or model system 4. Conflict - What were the blockers and obstacles? Needed a new technique? Refuting a previous finding? 5. Climax - the height of the struggle. Use your data to build to a climax. How did one question lead to another and how were any problems overcome? 6. Resolution - What's the final overall conclusion and how was the conflict that was setup in the beginning resolved by what you found? By taking the time to work through what story you can tell, you can engage your entire audience and they'll actually remember what you had to say!

Steve Jobs said: “The most powerful person in the world is the storyteller.” I come back to Jobs’ 2007 iPhone launch again and again. In it, he uses a narrative throughline to tie the entire presentation together. I've pulled my favorite examples into this video so you can see what I mean. Here’s the framework Jobs used (that you can too): *** 1. Make a promise A tantalizing statement to draw the audience in. This is his 'hook.' A few guidelines: • Short • Punchy • 'Big if true' Jobs promises “a revolutionary product that changes everything.” Now you, as the audience, know what his intention is. This is important. He gives himself and Apple a big goal to chase after. It's falsifiable -- it either happens, or it doesn't. *** 2. Create the buildup Set the context by using comparisons on the scale you hope to achieve. Jobs compares what he’s revealing to the Macintosh 1 and the iPod. Two products that, as he reminds you, changed entire industries. *** 3. Introduce conflict Conflict is simply tension between where you are and where you want to be. Here, Jobs uses the smart phone to introduce that tension: “The problem with smartphones is they’re not so smart.” He implies, "There's gotta be a better option..." *** 4. Raise the stakes Bring on the drama. Jobs says, “Apple is going to reinvent the phone.” Now we read that and it sounds obvious. But think about how bold that claim was in 2007 before anyone had heard the word “iPhone.” Blackberry dominated and, well, Apple made music players. *** 5. Demonstrate it Show your audience why your product – your story – is important. Jobs does a great job injecting humor here. *** 6. Bring back the problem When you watch Jobs, he never raises the stakes just once. Instead, he drills home how frustrating the current state is over and over. It’s painful — and that’s why your product is needed. *** 7. Wrap it up Position your product as a the savior, the painkiller. In 30 seconds, Jobs lists 13 features of the iPhone that traditional phones don’t have. Include your Call to Action — what you want people to do. Then end your story. *** You’ll notice it’s similar to the classic “Hero’s journey.” He didn’t reinvent the wheel. Instead, he mastered it. Tldr 1. Make a promise 2. Create the buildup 3. Introduce conflict 4. Raise the stakes 5. Demonstrate it 6. Bring back the problem 7. Wrap it up