Nina Vogt

The structure is usable but missing clear ownership markers. For each improvement area, I need to know who's responsible and by when. Without that, this stays a presentation rather than a plan. Add an owner/date column or slide footer.

The density of numbers is acceptable if they support a single narrative point per section. Right now it feels like equal weight everywhere. Front-load the headline, then optionally back it with data for those who want to dig deeper.

The narrative arc question is straightforward for me: can I explain this to my site leads in under two minutes after the talk? If not, it's too complex. Operations people need a clear 'here's what changes on Monday' takeaway. The current structure sounds like it might be more conference-style than operational. That's not bad, but it's not useful for my team.

Numbers density depends entirely on what they're tied to. Show me a number, then immediately show me the action we take based on it. Numbers without owners and deadlines are just decoration. Too many of those and I stop listening entirely.

The skeptics will be the site leads and shift supervisors. They see AI as something that gets announced and then never actually helps their daily problems. They've been burned before by initiatives that add admin instead of reducing it. That's the audience segment you need to win over.

Add one slide per section that says exactly what the audience should do differently starting tomorrow. Not 'understand AI better' — actual behavioral changes. That's what makes a talk worth attending rather than just interesting.

I would pilot it if every pulse item ends with an owner and a date; otherwise it becomes another sentiment chart.