CouncilDiscovery
Please react to the following talk content structure for an AI Revolution Day / US AI competition presentation. Evaluate: 1. Whether the narrative arc is clear enough before a live presentation 2. Whether the density of numbers builds trust or creates overload 3. Which audience segment would be skeptical and why 4. The single most useful next improvement before presenting
4 voices · open user research · host-authored
MSNVOLTD4 Personas
Mira Schulz, Nina Vogt, Oskar Lehmann, Tarek Demir
Executive Summary
Mixed reactions from the council. HR (Mira) and Operations (Nina) see value but want clearer audience segmentation and actionable takeaways. Finance (Oskar) is skeptical about unsubstantiated numbers. Warehouse (Tarek) is skeptical about whether AI presentations ever actually help floor operations.
What this council found
The council reveals significant skepticism across operational segments. Narrative arc: Mixed — Mira and Nina see potential but want faster clarity on business outcomes; Tarek is skeptical the talk is even for him. Number density: Generally seen as a risk — Oskar warns unsourced numbers hurt credibility; Tarek tunes out entirely when numbers dominate. Skeptical segments: Operations/shift leads (Tarek, Nina) and finance/procurement leaders (Oskar) are the core skeptics — they've been burned by previous tech initiatives that added complexity without value. Top improvement: Add segment-specific value propositions up front and tie every number to a decision or action. Sentiment skews neutral-to-skeptical due to lack of concrete, audience-specific framing in the current structure.\n\nKey insight: The presentation appears to target a 'mixed audience' but actually risks missing everyone — technical audiences want architecture, business audiences want ROI, operations want practical application. Without explicit 'what's in it for you' framing per segment, the talk will lose the room quickly."
Sentiment of this council
Voices across this session — who supports, who is skeptical.
Skeptical / opposed8
Neutral4
Conditional / partly4
Voices
An open discovery round — we listen to what 4 personas actually experience. No hypothesis, no vote; the answers below are the research data.
Question 1Whether the narrative arc is clear enough before a live presentation
4
Question 1
Whether the narrative arc is clear enough before a live presentation
MSMira Schulz Neutral
HR business partner supporting distributed blue-collar teams; accountable for engagement reporting and employee relations.
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.
NVNina Vogt Skeptical / opposed
Operations lead at a 120-person logistics company; owns shift handovers, field-team escalations, and weekly improvement meetings.
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.
OLOskar Lehmann Neutral
Finance controller reviewing SaaS spend; wants proof that another engagement tool will change behavior, not just produce a nicer c
From a finance controller standpoint, I need to see the business case upfront. The narrative arc should answer 'why should we invest in this' in the first three minutes. If I have to wait until slide 15 to understand the ROI, the presentation has already lost me and my leadership peers.
TDTarek Demir Skeptical / opposed
Shift lead at a warehouse site; coordinates ten workers and hates tools that turn into homework after the late shift.
Let me be honest — when I hear 'AI revolution,' I wonder if this is another thing that's going to make my job more complicated without actually helping. The narrative needs to show it helps the floor, not just the executives. Right now I'm not sure who this talk is actually for.
Question 2Whether the density of numbers builds trust or creates overload
4
Question 2
Whether the density of numbers builds trust or creates overload
MSMira Schulz Skeptical / opposed
HR business partner supporting distributed blue-collar teams; accountable for engagement reporting and employee relations.
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.
NVNina Vogt Neutral
Operations lead at a 120-person logistics company; owns shift handovers, field-team escalations, and weekly improvement meetings.
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.
OLOskar Lehmann Skeptical / opposed
Finance controller reviewing SaaS spend; wants proof that another engagement tool will change behavior, not just produce a nicer c
Number density is a trust test. If I see benchmarks and market sizes, I immediately wonder: what are the assumptions? What's the source? Can I trust this data? Without clear sourcing, numbers actually decrease credibility. I'd rather see fewer numbers with clear methodology than a dense data dump.
TDTarek Demir Skeptical / opposed
Shift lead at a warehouse site; coordinates ten workers and hates tools that turn into homework after the late shift.
I don't really care about numbers in a presentation. What I care about is whether this makes my shift run smoother. Numbers don't tell me that. If there are a lot of statistics, I tune out after the second one.
Question 3Which audience segment would be skeptical and why
4
Question 3
Which audience segment would be skeptical and why
MSMira Schulz Neutral
HR business partner supporting distributed blue-collar teams; accountable for engagement reporting and employee relations.
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.
NVNina Vogt Skeptical / opposed
Operations lead at a 120-person logistics company; owns shift handovers, field-team escalations, and weekly improvement meetings.
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.
OLOskar Lehmann Skeptical / opposed
Finance controller reviewing SaaS spend; wants proof that another engagement tool will change behavior, not just produce a nicer c
Finance and procurement leaders will be the skeptical segment. They've seen too many AI initiatives promised with big numbers and delivered with budget overruns. They need hard numbers tied to specific outcomes, not aspirational projections.
TDTarek Demir Skeptical / opposed
Shift lead at a warehouse site; coordinates ten workers and hates tools that turn into homework after the late shift.
Floor supervisors and shift leads will be skeptical because we've seen tools get announced as 'simplifying' our work and then they add steps instead. Also anyone who has to explain this to their team after a 12-hour shift will be skeptical — they don't have time for new complexity.
Question 4The single most useful next improvement before presenting
4
Question 4
The single most useful next improvement before presenting
MSMira Schulz Conditional / partly
HR business partner supporting distributed blue-collar teams; accountable for engagement reporting and employee relations.
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.
NVNina Vogt Conditional / partly
Operations lead at a 120-person logistics company; owns shift handovers, field-team escalations, and weekly improvement meetings.
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.
OLOskar Lehmann Conditional / partly
Finance controller reviewing SaaS spend; wants proof that another engagement tool will change behavior, not just produce a nicer c
The most useful improvement: add a clear cost-benefit section with assumptions stated explicitly. Finance people will respect the transparency and it builds credibility rather than appearing to hide the investment side.
TDTarek Demir Conditional / partly
Shift lead at a warehouse site; coordinates ten workers and hates tools that turn into homework after the late shift.
Show, don't tell. Instead of talking about AI, show one specific example of how it helps a shift lead with a real problem. Something like scheduling or equipment allocation. Make it concrete. That's the only way to get operational people to pay attention.