Many technical talks fail because the slides are the script, the code is unreadable from the back and only the successful path is shown. This deck gives a speaker a structure that works: a hook with a real number, the problem and why it was hard, a journey that includes the failed attempts, guidance on code slides and lessons the audience can apply. It fits roughly one slide a minute.

The sample is a talk by a fictional engineer at Fallowfield Digital on cutting checkout p95 latency from 480 ms to 140 ms, with a cost saving of 35% and the hardware noted. Replace the title and promise, the hook incident, the journey, the benchmark environment and your three lessons, and cut every code sample to the smallest fragment that makes your point.