Crafting the ABI Keynote Audience Profile, Questions, and Promise

Hello, and welcome. This course will help you prepare a conference keynote on autonomous vehicles for an insurance audience: first by identifying what the room needs from you, then by building sound technical and regulatory understanding, and finally by shaping and rehearsing the talk.

Before choosing slides or collecting facts, decide whom the keynote is for and what useful change it should produce. For a large conference audience, “insurers” is not yet an audience profile; it is an industry label. Your task in this lesson is to turn the ABI brief into a practical design brief containing:

1. A concise audience profile.
2. Three questions the audience is likely bringing into the room.
3. A clear promise of what they will leave able to understand or do.

Because the actual ABI conference brief is not included here, we will distinguish facts you can extract from it from working hypotheses you must validate with the organiser.

---

Start with the audience’s job, not their demographics

Demographics and job titles are useful, but they are rarely enough to shape a keynote. A room may include claims leaders, underwriters, actuaries, legal and policy specialists, innovation teams, brokers, and senior executives. What unites them is not simply that they work in insurance; it is the decisions and uncertainties they face.

A useful audience profile answers five questions:

Dimension	What to establish from the ABI brief and organiser	Why it changes the keynote
Who is in the room?	Roles, organisations, seniority, geography, and approximate size	Determines examples, vocabulary, and the level of explanation needed
Why are they attending?	Conference theme, session title, what the agenda promises	Reveals the problem they expect you to address
What do they already know?	Familiarity with automation, insurance implications, UK policy, and your organisation	Prevents both oversimplifying and drowning the room in detail
What decisions do they influence?	Underwriting, claims, risk, investment, policy engagement, product strategy	Turns a general technology talk into a decision-relevant talk
What are the stakes?	Costs, safety, liability, customer trust, data access, competitive timing	Determines the central tension and the opening stakes

The audience is likely to be mixed, even when the event is specialist. Some attendees may understand motor insurance and liability deeply while having limited knowledge of automated-driving systems. Others may be technically informed but less familiar with insurance operations. Do not solve this by aiming at an imaginary “average” attendee. Instead:

• define essential terms once, in plain language;
• use credible evidence and careful distinctions for specialists;
• anchor each technical point in an insurance consequence;
• avoid assuming that a technical demonstration proves commercial readiness or insurability.

This respects the whole room while focusing most sharply on the people who are open to being moved: the interested but not yet settled group. They are often the attendees asking, “How seriously should we take this, and what should we do about it?”

The most productive source is usually the conference organiser. The organiser has already decided why this session belongs on the programme and may have registration data, previous-event feedback, session descriptions, and knowledge of the audience mix.

Ask concise, decision-oriented questions:

1. Who has registered or is expected in the room? Ask for role mix, seniority, organisations, countries represented, and whether the audience includes non-insurer stakeholders.
2. Why did the programme place this session here? Ask what question or concern the session is intended to resolve.
3. What will attendees have heard before this keynote? This prevents repetition and lets you build a coherent narrative.
4. What do attendees most want to be able to discuss afterwards? This helps identify an action-oriented ending.
5. What claims, examples, or company positions require prior approval? For a topic involving Wayve and automated vehicles, this is essential for credibility and governance.

Research is not a license to stereotype. Treat roles and sectors as clues about probable needs, then validate them. A chief underwriting officer and a claims specialist may both be interested in autonomous mobility, yet need very different evidence to make decisions.

---

Convert the brief into a one-paragraph audience profile

A usable profile is short enough to guide every content decision. It is not a biography of the audience and it is not a generic statement such as “industry professionals interested in innovation.”

Use this structure:

[Audience] are attending [event/session] because [their immediate purpose]. They have [relevant knowledge level] and are deciding how to respond to [decision or uncertainty]. They need [kind of evidence or clarity], and they are likely to be concerned about [stakes or constraint].

For the ABI keynote, the following is a provisional profile, based only on the course context. Replace bracketed parts when you inspect the conference brief.

Provisional profile: The audience is likely to be a mixed group of UK insurance and related-sector leaders attending an ABI conference session on increasingly automated transport. They are looking for a realistic account of what automation means now, rather than a distant technology forecast. Their knowledge of insurance is likely to be stronger than their knowledge of vehicle automation, and they need to judge implications for risk, liability, data, products, and public trust. They will expect evidence, careful qualification, and practical relevance to UK deployment.

Notice what this profile does not assume:

• It does not claim that every attendee is an insurance executive.
• It does not assume that fully driverless services are already common in the UK.
• It does not promise certainty about outcomes that remain uncertain.
• It does not presume that the audience wants a product pitch.

A profile becomes operational when it can veto material. For example, if a planned slide explains a perception model in technical depth but does not help the audience understand a risk, readiness, liability, data, or policy implication, it probably does not earn its place in a 20-minute keynote.

---

Find the three questions beneath the brief

The three audience questions are not simply the questions you want to answer. They are the questions attendees are likely to be asking themselves, perhaps silently, as they enter the room. Good questions expose a decision, a concern, or a tension. Weak questions merely name a topic.

For example:

• Weak: “What are autonomous vehicles?”
• Stronger: “What level of vehicle automation matters for our risk decisions now, and what remains premature?”

A strong set of three questions should cover:

1. Present reality: What is genuinely changing now?
2. Business consequence: Why does it matter for insurance, customers, or society?
3. Practical response: What should the audience do differently?

For this keynote, use these as a starting hypothesis until the ABI brief confirms or changes them:

1. What is the difference between today’s driver-assistance systems, increasingly automated driving, and truly autonomous mobility—and why do those distinctions matter to insurers?
2. As automation changes who controls driving and how vehicles operate, how might safety, liability, claims, underwriting, and vehicle data change?
3. What should insurers and policymakers do now to prepare responsibly without treating near-term capability, pilot activity, and large-scale deployment as the same thing?

These questions work together because each prepares the next:

• The first establishes conceptual clarity.
• The second makes the topic commercially and socially relevant.
• The third gives the audience a reason to stay engaged through the conclusion.

They also foreshadow the course sequence without forcing your keynote to answer every detail at once. Later work will provide the UK regulatory framework, insurance liability routes, evidence standards, and recommendations needed to answer them rigorously.

---

Write a keynote promise that is useful and defensible

A keynote promise is a compact agreement with the room. It tells attendees what value they will receive if they give you their attention. It should be specific enough to create expectation, but careful enough that you can fulfil it within twenty minutes.

Avoid promises that are either too vague or too grand:

Weak promise	Problem
“Today I’ll talk about autonomous vehicles.”	A topic, not a benefit
“Autonomous vehicles will transform insurance.”	Overconfident and unsupported
“I’ll explain the technology.”	Focuses on your content, not their decision
“We will solve the future of mobility.”	Not credible for one keynote

Use this formula instead:

By the end of this keynote, you will be able to [understand or assess a specific issue], distinguish [important boundary], and identify [practical next step].

A well-scoped draft promise for the ABI keynote is:

By the end of this keynote, you will have a clearer way to distinguish current automated-driving realities from future claims, understand why that distinction changes insurance risk and responsibility, and identify practical areas where insurers and policymakers can prepare now.

This promise has three strengths:

• It is audience-centred. It names clarity, relevance, and action rather than the speaker’s expertise.
• It is defensible. “Clearer way to distinguish” and “identify practical areas” are realistic outcomes for a conference talk.
• It establishes intellectual discipline. You are promising to separate evidence from prediction, and present capability from scale.

The promise should guide your opening, not merely appear on a planning document. Later in the course, you will turn it into a 90-second opening and a timed narrative. For now, test every planned message against one question: Does this help fulfil the promise?

---

Your audience-design worksheet

Complete this document after reading the ABI brief and speaking with the event contact. Keep the final version to one page.

1. Evidence extracted from the brief

• Conference and session:
• Stated theme or purpose:
• Expected audience roles and organisations:
• Audience size and format:
• Session position in the agenda:
• What the organiser wants attendees to take away:
• Constraints: timing, approved examples, sensitive claims, Q&A format, slide requirements.

2. Audience profile

Write 70 to 100 words using the five-part profile structure. Label any statement that is an assumption and list how you will validate it.

3. Audience questions

Write three questions in the audience’s voice. Check that they are:

• answerable in the keynote;
• relevant to insurance decisions rather than merely technical curiosity;
• distinct from one another;
• neither leading nor exaggerated.

4. Keynote promise

Write one or two sentences beginning:

“By the end of this keynote, you will…”

Then remove any claim you cannot realistically deliver in the allotted time or support with evidence and approved examples.

A final quality check is simple: give the profile, three questions, and promise to someone uninvolved in the talk. They should be able to tell you, in under a minute, who the keynote is for, why it matters to them, and what they will leave with.

---

Key takeaways

An audience profile should describe the room’s purpose, knowledge, decisions, and stakes—not merely its demographics. For the ABI keynote, begin with the likely mixed insurance audience, but validate the role mix and expectations with the organiser rather than relying on assumptions.

Your three audience questions should move from present reality, to insurance consequence, to practical response. Your keynote promise should offer a valuable and achievable transformation: clearer distinctions, sounder judgement, and practical preparation.

Next, you will establish the technical language that makes the promise credible by distinguishing driver assistance, automated driving, and autonomous mobility through the ideas of operational design domain and fallback in the UK context.