Every developer has faced it: the code review or sprint review that goes sideways, the brilliant idea that fizzles in a meeting, the documentation that nobody reads. What if the missing ingredient isn’t more data—but better storytelling?

In this talk, we’ll explore how narrative techniques can transform the way developers present their work. Whether you're walking your team through a pull request, pitching a new feature to product managers, or writing documentation that actually gets used, Storytelling can help you connect, persuade, and clarify.

We’ll break down how to structure technical communication like a story—with characters (users), conflict (problems), and resolution (your elegant solution). You’ll learn how to make your work memorable, understandable, and even enjoyable to review.

This isn’t about fairy tales—it’s about making your everyday developer communication more effective, more human, and more impactful.
🎯 Key Takeaways
- How to structure a code review presentation like a compelling narrative
- Techniques for pitching new ideas with clarity and emotional resonance
- Story-driven documentation: making technical writing readable and useful
- Using storytelling to build empathy and trust across teams

👥 Target Audience
Software developers and engineers
Tech leads and engineering managers
Technical writers and product designers
Anyone who presents technical work to others