AWS Builder Center

I Didn't Have a Talk, I Had a Topic — My Time at AWS New Voices

After going through AWS New Voices training, I went on to give one of the hardest talks of my career: explaining artificial intelligence to a room full of people with no technical background — and several of them were friends of mine.

I've been working in technology for many years, and over the last few years I've given quite a few talks. Meetups, user groups, Nerdearla, community events, training sessions. My way of preparing a presentation was pretty simple: open the laptop, start building slides, organize what I knew about the topic, and then go out and talk about it.
I thought I was doing reasonably well.
Then I joined AWS New Voices and realized there were some pretty basic questions about public speaking that I had never really stopped to think about.



How I got there

When I applied to the AWS New Voices 2026 program, the first thing I thought was, "What a great opportunity to learn something non-technical." And when I got the confirmation, I was genuinely surprised — and very grateful for the opportunity.
Speaking in public wasn't something I found particularly difficult, but I never completely understood why some talks worked really well while others didn't.
I had the feeling that a lot of what I was doing came from experience and intuition.
Of course, experience helps a lot. But improvising based on experience isn't exactly the same as understanding what you're doing.
I was part of the first cohort of the year with colleagues from different parts of the world.
Sharing experiences with people from all over the world was amazing. It helped a lot, and somehow made the world feel a little smaller and closer.



What changed

I won't go into the details of the program itself because I think it's something worth experiencing firsthand. What I can share is what changed for me.
For years, when I prepared a talk, my starting point was basically:
What do I want to explain?
I knew the topic, created a structure, added some examples and probably an architecture diagram, and that became the presentation.
During New Voices, I started thinking about a different question:
What do I want people to leave the talk with?
It sounds like a small change, but it isn't.
Once I started thinking that way, I began questioning parts of my presentations that I had always considered important. Sometimes that architecture diagram I had spent two hours working on wasn't really helping the story. Meanwhile, a very simple analogy could be exactly what helped someone understand an idea.
I also realized that some of the things I called "content" were there because I wanted to show that I knew the subject, not necessarily because the audience needed them.
That was useful to recognize.
I also started paying much more attention to things I hadn't really noticed before: the voice, the pauses, the breathing, and the intention behind what one says. These are the kinds of things that, as an engineer, I probably would have placed in the "soft skills" category.
But there is technique behind all of them.
And after so many years of giving presentations, nobody had ever really taught me that technique.



The real test

To graduate from New Voices, you have to deliver a talk at a public event.
The easy option for me would have been a technical talk at a user group. Something about AWS, cloud, or security, in front of an audience that already understood most of the vocabulary.
Instead, I decided to try something completely different.
I gave a talk called "More Than Data: Artificial Intelligence in the Light of Magnifica Humanitas."
It was a talk about artificial intelligence and Pope Leo XIV's encyclical, for an audience with almost no technical background.
Adults who hear about artificial intelligence all the time — on television, social media, in newspapers, and in conversations at work — but who don't necessarily have someone they can ask what all of this actually means.
That completely changed the way I had to prepare.
There was no point in talking about architectures or filling the presentation with acronyms. In fact, I gave myself a rule:
I had to explain everything without abbreviations or acronyms, in a way that my grandmother and my eight-year-old daughter could understand.
Preparing that talk was much harder than I expected.
I removed a lot of material. Some things were technically interesting, but they simply weren't important for that audience. I spent much more time thinking about examples. I also had to find a way to start that wasn't the classic, "Today I'm going to talk to you about..."
And there was another problem: artificial intelligence moves ridiculously fast.
Between preparing different parts of the presentation and actually giving the talk, new models and announcements kept coming out. Numbers or examples that seemed current when I added them could already feel old a few days later.
At some point, I realized I couldn't build the talk around the latest model or the latest statistic.
The technology was going to keep changing anyway.
The more important question was what all of this means for us and what we decide to do with it.
The talk went really well.
But that's not actually what I remember most.
What stayed with me was that, probably for the first time in many years of giving talks, I was much more aware of why each part of the presentation was there.



What I'm taking away from all of this

There are three things, in particular, that I'm taking with me:
  • Pick the hard audience.
Talking about technology with people who already work in technology is comfortable. Trying to explain something you know well to people who don't share your vocabulary forces you to understand the subject in a different way.
  • Know where you want to end before you start building slides.
Try to complete this sentence:
"When these people leave the talk, I want them to..."
If you still don't know how to finish it, you probably have a topic, but you don't have a talk yet.
  • Practice out loud, preferably in front of someone.
Going through the presentation in your head is useful, but it isn't the same thing. Some things sound great in your head and feel completely different when you actually say them out loud.
I don't know if five weeks of New Voices suddenly made me a better speaker. It's probably not that simple.
But they did change the way I prepare a presentation.
Now I spend less time thinking only about what I want to tell people, and more time thinking about what I hope they will take away when it's over.
If you're thinking about applying to AWS New Voices, don't hesitate.
And when the time comes to choose the audience for your graduation talk, don't automatically choose the easiest one.
Choose a room that makes you uncomfortable.
You may end up learning more from that room than they learn from you.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article