Mira Schulz

The narrative arc needs a clearer 'why now' hook. Before a live presentation, the audience needs to know in the first 90 seconds why this matters to their day job, not just why AI is historically significant. I'd want to see a concrete business problem stated upfront, then the solution arc follows naturally.

Numbers can build trust when they're tied to specific outcomes - like 'this process saved 15 hours per week' - but too many benchmarks without context feel like data dumping. I'd recommend 2-3 anchor metrics max, explained simply.

From an HR perspective, I'm thinking about whether this presentation will feel relevant to the whole room. A 'mixed business/technical audience' sounds good on paper, but in practice I've seen technical talks lose operational managers, and business talks lose the technical team. The narrative arc needs to anchor every section in a concrete business outcome, not just technical capability. Without that, I'm already anticipating people checking their phones during the second half.

On numbers: in my experience with engagement surveys, more data doesn't automatically mean more trust. It often means more questions. I'd want to see the numbers tied to decisions we can actually make, not just benchmarks. If the deck is full of statistics without clear 'so what,' that creates overload rather than credibility.

The skeptical segment here would be the non-technical business leaders who are already skeptical about AI. They need to see clear business value before they'll engage. They're not going to be won over by technical architecture slides.

The single most useful improvement: add a 'what's in it for you' slide for each audience segment right up front. Business people need ROI language; technical people need architecture clarity; operations need practical application. One-size-fits-all won't work.

The anonymity threshold has to be visible before anyone answers. Trust is built before the first question.