AI for Leaders.
Set the strategy, choose the stack, drive adoption.
- Duration 4 hours
- Audience COO, CIO, CFO, founder-CEO, BU head
- Format Live remote co-creation
- Prerequisite None
When to take this module.
- The board is asking your AI position and you do not have a clean answer.
- Procurement, legal, and IT are raising AI Act questions you cannot close.
- You are choosing between centralized AI ops and a federated model.
- You need to decide which teams take which module, in which order.
What the session covers.
01 Decider Literacy
What an LLM actually is, the five failure modes that matter for business risk, and a working read of the EU AI Act for deployers.
02 AI Strategy Fundamentals
Where AI is competitive advantage and where it is commodity. A portfolio exercise that surfaces 10 to 30 candidates from the business, ranked by stakes and fit.
03 Operating Model Design
Centralized versus federated AI ops. The AI Council pattern, roles to add and avoid, and a first-draft GenAI policy you can take to legal.
04 Technology Choices
Four enterprise-friendly agent surfaces. A vendor-evaluation lens for residency and training-on-data clauses. A build versus buy versus rent matrix.
05 Adoption
Five adoption levers, a first-90-days playbook, and pilot design that produces real evidence.
What you walk away with.
- 01 A one-page AI strategy and prioritized portfolio.
- 02 An operating model sketch your AI Council can take to its first meeting.
- 03 A tech-stack decision matrix you can defend in procurement.
- 04 A 90-day adoption pilot with success criteria and measurement.
Built for procurement, legal, and IT review.
M1 covers EU AI Act deployer obligations under Articles 4, 50, 26, and Annex III. Every participant leaves with an OpenBadge 3.0 credential plus an engagement certificate, cross-walked to your governance scope.
LiftWork does not certify compliance on your behalf. We supply structured evidence to support your legal and L&D attestation.
Questions teams ask first.
01 Is this for non-technical leaders?
Yes. The module assumes decision-making authority, not technical depth. Frameworks are written for non-technical leaders to read and use.
02 Can we bring multiple decision-makers from one company?
Yes. Single-company sessions are the default, up to 15 deciders. Cross-functional groups produce the strongest outputs.
03 Do we leave with documentation procurement can read?
Yes. The strategy on a page, the operating model sketch, and the tech-stack matrix are written for cross-functional reading.
04 How does this connect to the team modules?
The session closes with a sequencing recommendation. Most companies pair M1 with M2 for foundational team literacy, then M3 or M4 by department workload.
Ready when you are.
A 30-minute call. We listen for the trigger pain, sketch the scope, and tell you whether the right shape is this module, another one, or neither.