6 Comments
User's avatar
Mark Bayer's avatar

Thanks, and your comment is so on-target. Yes, pacing and tone variance is critical. I sometimes say "Give energy, get engagement", understanding the "wattage" needs to modulate.

I really like how you talk about rhythm. Playing guitar, I've become attuned to the similarities between well-crafted stories and songs that stick with us. You may know songs will sometimes change keys (dominant tones, if you're not familiar), particularly if it's a longer song. "Last Resort" by the Eagles is an example (it's more than 7 minutes long). There's a whole section when key changes that feels different within the same song, retaining interest.

I've also noticed another connection between music and the storytelling model - it's the sequencing. Guitar riffs - The Rolling Stones' "Satisfaction" is one example - tend to start and end on the same note. I guess our brains like that closed loop resolution at the end. It's sort of like the Primacy and Recency principle.

Thanks for sharing your excellent addition!

Michał Poczwardowski's avatar

Great & comprehensive guide.

Bookmarked!

I often think of readers as having limited cognitive bandwidth (with all due respect, of course!).

Simple language is key.

Mark Bayer's avatar

Thanks, Michal - and absolutely agree about limited bandwidth. Though not an evolutionary biologist (or any kind of biologist), I think the human operating system is programmed to conserve cognitive energy in case of a life-threatening emergencies. Ironically, it takes a lot of energy to make a complex topic simple to understand. Storytelling can help with that.

Sidwyn Koh's avatar

This is a great guide. I always noticed this in the workplace but never thought of how to express them as techniques. Thank you for sharing Mark.

One thing about allusion that I struggle with: How do we pick and choose "stylistic devices"? Sometimes I worry my own list of these devices is too far-fetched and not popular enough for people to know. Or I'm afraid of using them wrong. Do you identify these "stylistic devices" ahead of time? Do you have a rolodex of them?

I also turned this into a Claude skill to help me with my writing in Claude. (Happy to share Github links if you'd like)

Mark Bayer's avatar

Thanks for your kind comments, Sidwyn, and excellent question.

One thing I do a few weeks before keynotes is ask organizers if a particular allusion, term, or device clicks with them and attendees. For example, a couple years ago, I asked an organizer whether audience members considered themselves scientists, researchers, or physicians. Because not everyone considered themselves a physician (it was a med school audience), I used all 3 terms in the talk. I also ask organizers if I can speak by phone with a few people who'll be in the audience for my talk. During conversations with attendees, I pay attention to the words they use in response to my questions about the speech topic.

Of course, this type of preview isn't necessarily possible in all types of presentations. When there is an opportunity ahead of time to test an allusion or metaphor, etc. with a colleague in the workplace, I suggest doing that. It's like "If I were to describe [technical topic] like this, would it make sense? Be memorable? Would it help listeners get oriented before I go into detail or be a distraction?"

An overall mindset that might help: think about what you have in common with your listeners. It could be a common experience, for example. Sometimes that connection can help point towards an allusion.

Thanks for your question!

Miro - The Tech Metaphorist's avatar

Great framework. The "grab attention immediately" + "remove irrelevant details" combo is essential.

One addition from me - pacing.

Even with perfect structure, if you keep the same rhythm to the end - you lose attention. So vary tempo. Short impact line... then longer explanation... and back to punch! That rhythm shift keeps people engaged through complex explanations.

Stealing this for my tech explainers - I use restaurant metaphors (Stack = order spike, Heap = warehouse, bad recursion = kitchen explosion). Definitely checking if I'm missing something in my own writing style.

Cheers!