From Audience to Action: How AWS New Voices Shaped My Journey
This article describes my journey to becoming a confident speaker and how New Voices program helped.
Stepping onto the stage at AWS Community Day East Canada in Montréal on June 20, 2026, was a defining moment in my career. Looking out at a packed room of cloud architects and builders waiting to hear my session, "Scaling GenAI on AWS: Turning POCs into Production Systems," a wave of calm washed over me.
If you had told me two months ago that I would deliver a high-stakes architectural deep dive with complete confidence, I wouldn't have believed you. Like many Senior Cloud Architects, I felt completely at home inside a VPC endpoint or an Amazon Bedrock runtime API, but the stage?
That was an entirely different type of non-deterministic environment.
The secret behind this transformation wasn't a magic trick—it was my graduation from the intensive 5-week AWS New Voices program. Designed explicitly for AWS Community Builders and user group professionals, this speaker development journey completely changed how I think about technical communication.
If you want to know how we took a real-world AI Fashion Assistant Chatbot from a local prototype to a robust production system—and exactly how the New Voices framework helped me tell that story—this reflection is for you.
The Core Blueprint:
If I had to summarize the entire 5-week AWS New Voices curriculum in a single line, it would be this: Audience → Hook → Message → Visuals → Action. This simple framework forces engineers to stop starting their presentation prep inside PowerPoint or Canva, and instead start with human connection.
Here are some of the important take-aways from the program that directly shaped the talk I delivered in Montréal.
Putting the Audience First
The first week focused on a hard truth: a technical talk is never about the speaker; it is always about the audience. It is important to know your audience and present according to their level of interest and their level of understanding. A technical presentation can get boring and overbearing very fast. So it is important to know your audience, presenting yourself as a credible speaker to share the information and to clearly state the problem you are trying to solve and how you can help them.
Grabbing Attention with a Powerful "Hook"
A great talk cannot begin with a dry corporate greeting. You need to arrest the room's attention using storytelling, bold statistics, or provocative statements. That one statement should be powerful enough to become the focus of your presentation.
I built my entire opening around the brutal truth slide: 95% of investments in Generative AI have produced 0 returns. By highlighting high-profile industry failures like Claude AI allegedly deleting a database and its backups in 9 seconds, or Air Canada’s chatbot hallucinating refund policies, I immediately hooked the crowd. Suddenly, the stakes were real.
Defining the Core Message (The AI Fashion Assistant Case Study)
This week focused on breaking down complex, bloated information into clear, bite-sized takeaways. When you present your points to an audience, they are going to remember only a part of it. If you present 15 points there is information overload. So it is important to keep focus on few and most important points.
In my talk, the main message was solving the Single-Agent Problem (Context Bloat, No Isolation, and Skyrocketing Costs) by decomposing our application by domain.
Visuals That Support the Message
We also learnt about slide design. Instead of copy-pasting code blocks and dense walls of text, we learned how visuals must guide, not distract, audience attention. This part was an eye-opener because the slide design is the visual aspect and if you get this part wrong, the audience will lose interest. If there is too much information on the slides then that would be a distraction for the audience, if there is too little information then the audience will have nothing to focus on.
I applied this principle to explain complicated technical details to my audience in Montreal.
The slide was stripped of unnecessary text, allowing the audience to listen to my voice while the visual diagram anchored their understanding.
Handling Stage Anxiety & Closing with Action
Then we brought everything together. All that we learnt during the course was put together to prepare a brief presentation. Some of us presented what we had learnt during the course. We also learnt how to calm our nerves and focus on breathing before entering the stage.
I used this techniques right before the stage manager handed me my microphone.
Crucially, New Voices taught us to always end with an explicit Call to Action. I closed my talk by giving engineers a real-world, actionable production checklist based on our mistakes.
My Reflection: Finding My Value as a Storyteller
Before embarking on this AWS New Voices journey, I used to fall back on a common engineering defense mechanism: “If my architecture diagram is technical enough, the presentation will speak for itself.”
New Voices taught me that our community doesn’t just need raw specifications; they need to understand the human experience of engineering—why a configuration failed silently, how a team felt when a system choked without circuit breakers, and what steps prevent it from happening to someone else.
Stepping out of my comfort zone alongside 100+ global Community Builders provided an incredibly supportive space to fail, iterate, and sharpen my presentation craft. Today, I stand not just as an architect who builds data and AI solutions, but as a speaker who can rally an entire room around a vision.
To the New Voices team and my community members — thank you for giving me the toolkit and to turn my technical passion into human connection. The journey from POC to production is a rocky one, but sharing that path with the community makes it entirely worth it. Now, it's time to build!
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article