// About the talk
Presentations don't fail because of bad design - they fail because they start with data instead of conclusion. The audience leaves with a head full of graphs and no answer to 'what do I do tomorrow?' The Reverse Engineering method flips the order: define first what the audience needs to feel, know, and do when they leave - then build backward. That's the difference between a presentation that was 'good' and one that drove an actual decision.
// What your team walks away with
- 01Information Overload: how much information the brain can absorb at once - and how to work with that, not against it
- 02The Curse of Knowledge: why we can't see what the audience doesn't understand
- 03The Red Dot: what the audience must understand right before they reach the conclusion
- 04Reverse Engineering: paving the route from end to beginning - one slide at a time
// Who this talk is for
- 01Managers presenting to executives, boards, and investors who want the message to stick
- 02Product and Engineering presenting at all-hands, demo days, and standups
- 03Anyone who has ever left their own presentation feeling like 'they just didn't get it'
// Organizations that invited me
Technology Companies











Conferences & Community


Organizations & Institutions





//Organizer questions
What organizers ask before booking
In person or online?
Both. Every talk in the catalog is available in person or online.
Can the talk be in English?
Yes. The talks are available in Hebrew and English. (I spoke in English at PyCon UK 2025, for example.)
Is the talk tailored to our team?
Yes. Every talk gets tailored. Your industry, your challenges, your language. I don't do generic. That's the whole point.
What happens after we reach out?
Tell me about the audience and date, and you'll get a personal reply within 48 hours. (If it's not a fit, I'll say so.)
Want to bring this talk to your team?
30 minutes. No pitch. Just a conversation about what your team needs - and how this talk fits.