# Improving Your Technical Content Delivery

> Technical presentation skills training for engineers and tech leaders, from the boardroom to the main stage. Delivered by Boaz Ziniman of SpeakUp as a talk for the whole team, a workshop for up to 12 people or coaching on one talk, on-site anywhere or online. Quoted per engagement.

Page: https://speakup.dev/technical-presentation-training/

## Why it matters

Great engineering deserves talks people remember: your team’s best work, told so the room remembers it, and your company with it.

## The idea

Three things decide whether a technical talk lands:

- Narrative earns attention: start where they are.
- Precision earns trust: details they can see.
- Performance earns impact: you, on purpose.

The detailed content of the session is not published.

## One slide, before and after

A typical slide from an engineering review, and the same idea after one round of work.

- The title says what they get. Before, the title names the topic. After, it states the result: the 3am pages stopped.
- One statement, one visual. Eight bullets in full sentences make the room read instead of listen. The speaker tells the details, so the slide doesn’t have to.
- Show the detail, don’t describe it. “Reduced on-call load” becomes the night pages themselves, counted before and after.

## Why teams bring it in

- Founders and executives: keynotes, investor pitches and launches that have to land the first time.
- Engineering leaders: talks and demos that show developers and buyers what your team built.
- Learning and development: participants work on their own talks, so it shows in their next one.
- HR and employer brand: engineers who speak well attract the people you want to hire.
- Event organizers: speaker training that lifts every talk on your agenda.

## Formats

### Talk: Improving Your Technical Content Delivery (20 or 45 min)

- Group: Any size: a team or a whole event
- What happens: The three ideas, shown on real before-and-after examples.
- What you get: A shared language for the team, and the first fixes everyone can make.
- Your team’s time: The session only.
- Choose it when: you want to raise the bar across a team or an event, in one slot.

### Workshop (2 hours to half a day)

- Group: Up to 12 people
- What happens: We warm up on examples, then everyone works on a talk of their own. I review selected talks in front of the group, so everyone learns from each one. The more time we have, the more we practice: more talks reviewed, and with half a day, everyone delivers part of their talk and gets my feedback.
- What you get: Everyone leaves with part of their own talk already reworked.
- Your team’s time: The session. Everyone brings a talk they’re working on.
- Choose it when: a group has talks coming up: a conference, a launch, quarterly reviews.

### Coaching (2 or 3 sessions of 2 hours)

- Group: One speaker
- What happens: One talk from first draft to stage: the story, the slides, then rehearsal.
- What you get: One talk, ready for the stage it was written for.
- Your team’s time: 4 to 6 hours with me, plus the speaker’s own work between sessions.
- Choose it when: one talk really matters: a keynote, a board pitch, a key customer demo.

They work well together: a talk for the whole team, and coaching for the 2 or 3 people going on stage. Every participant leaves with a checklist for their next talk.

Every engagement is quoted, based on the level and length, the group size and the location: online, in Israel or abroad.

## About the speaker

Boaz Ziniman, founder of SpeakUp and Claude Community Ambassador, in his words: I founded SpeakUp after more than 30 years in tech, nine of them at AWS as a Principal Developer Advocate. I’ve given over 1,000 talks, from internal boardrooms to AWS Summit keynotes in front of thousands, and mentored dozens of technical speakers along the way. This session is the method I use with them. LinkedIn: https://www.linkedin.com/in/bziniman/

Teams he has worked with include CAST AI, Datafy, AWS, Automat-it and Reversim Summit.

## Frequently asked questions

### Who is it for?
Anyone who presents technical work: engineers, engineering managers, developer advocates, solution architects and founders. It helps first-time speakers and people who already speak often.

### Which format fits our team?
A talk raises the bar for everyone at once. A workshop gives up to 12 people time to work on their own talks. Coaching takes one important talk from first draft to stage. Not sure? Tell me about your team and I’ll suggest one.

### What kinds of talks does it cover?
Conference talks, product demos, presentations to leadership, investor pitches and booth demos. The same three ideas apply to all of them.

### What do participants leave with?
A checklist for their next talk. In a workshop, they also rework part of a talk of their own, so the change shows in the very next one.

### Where does it run, and in which language?
On-site at your office or your event, or online. Private coaching works well over video. Sessions run in English or Hebrew.

### How much does it cost?
Every engagement is quoted, based on the level and length, the group size and the location: online, in Israel or abroad. Send me a few details and I’ll reply with a quote.

## Get started

Send a few details about the team, the event or the talk, and Boaz will reply with the format that fits and a quote.

- Start here: https://speakup.dev/technical-presentation-training/
- Email: contact@speakup.dev
- Phone: +972-54-7999-502