AI strategy

AI Strategy Keynote or Workshop: Choose the Format Before the Speaker

Match your AI strategy event format to audience readiness, decision needs, and the work that must happen afterward.

Top One Percent AI · Practical guidance with linked sources.

A keynote and a workshop solve different problems. A keynote can establish shared language across a large audience. A workshop can help a smaller group examine choices and produce a working output. Booking an impressive speaker before choosing between those outcomes can leave the organizer with a strong performance and an unresolved business need.

Diagnose the audience gap

Start with the obstacle. If attendees use the same terms to mean different things, a structured introductory talk may be appropriate. If they agree on the basics but disagree about which initiatives deserve funding, the event needs discussion and comparison. If nobody has authority to act, a workshop cannot manufacture that authority.

Ask the sponsor what attendees should do differently the following week. “Feel inspired” is a legitimate conference objective, but it is not an implementation objective. For strategy work, name an observable action such as revising a use-case brief, identifying a process owner, or gathering baseline performance data.

Use a keynote when reach matters

A keynote is useful when the audience is large, mixed in seniority, or early in its understanding. Give the speaker a narrow central question and ask for examples that make tradeoffs visible. Reserve time for moderated questions rather than packing every minute with slides.

Screen candidates for their ability to explain limits. A talk about opportunity should distinguish capabilities, proposed applications, and verified results. Ask whether case studies are independently documented, client-approved, or hypothetical. Those labels should remain visible in the presentation.

Use a workshop when comparison matters

A strategy workshop needs preparation and a defined artifact. Ask participants to bring short, nonconfidential descriptions of business processes rather than lists of preferred tools. Each description should include the current workflow, the people affected, a known friction point, and the evidence available to evaluate improvement.

The facilitator should help groups compare options using consistent questions. What is the intended benefit? What could go wrong? What information is missing? Who can authorize a test? What would make the organization abandon the idea?

The NIST AI RMF Playbook provides suggested actions aligned with the framework’s risk-management functions. An organizer can use it as a preparation reference, while keeping the workshop focused on the organization’s own decisions rather than treating a framework as a ready-made agenda.

Consider a hybrid, but protect working time

A short common briefing followed by facilitated tables can serve a mixed audience. The tradeoff is operational complexity. You may need table leads, clear instructions, accessible materials, and a way to consolidate outputs without exposing sensitive information.

Ask the candidate to show how their agenda changes when attendance doubles or preparation is incomplete. A serious workshop proposal should include a fallback plan, not simply a promise of interaction.

Contract for the appropriate result

For a keynote, specify audience level, central question, examples, and Q&A arrangements. For a workshop, add required inputs, group size, facilitation responsibilities, output format, and ownership of the resulting materials.

Evaluate the event against its chosen purpose. A keynote can succeed by making the next conversation more precise. A workshop should leave a usable record of options, uncertainties, and next steps. Neither format should be sold as a substitute for sustained strategy work.