WorkCase study

AI Training · Full-day workshop, Dubai · 2026

Getting a leadership team fluent in AI

A five-module AI fundamentals curriculum for NEFC Group's leadership team. Built around their business, delivered in a day, closed with a reveal that the deck itself was AI-generated.

One day, one room, decision-ready fluency — not a slide tour.

Leadership cohort

Mixed technical literacy, same shared vocabulary

Five modules

Mechanics, risk, prompts, tools, governance

Policy they own

Governance skeleton, not a borrowed template

The problem I was solving

Everyone had heard the AI pitch. Almost nobody could explain what the technology does, where it fails, or which calls still belong to a human.

Fluency gap

Leadership could not distinguish hype from mechanics, so every tooling conversation started from guesswork.

Mixed literacy

One room, wildly different technical backgrounds — the material had to land for all of them without watering down.

Slow decisions

Without a shared vocabulary for risk and fit, vendor and tool choices stalled.

Before and after

Same user intent. Different product experience.

Before
  • AI as abstract pitch, not operating knowledge
  • No shared language for risk or verification
  • Tool decisions stalled by uncertainty
  • Governance treated as an afterthought
After
  • Mechanics intuition they can reuse on new tools
  • Prompt structure they rewrote live from their own work
  • Clearer cost/effort trade-offs across build vs buy
  • A policy skeleton the team owns

How it works

How I structured the day

  1. 1

    How LLMs actually work

    Tokens, prediction, context windows, and why the model forgets you between sessions. Enough mechanics to carry everything after it.

  2. 2

    Hallucination and where risk sits

    Why confident wrong answers happen, which tasks are most exposed, and what verification looks like day to day — framed in NEFC's operating context.

  3. 3

    Prompting frameworks

    Role, context, constraint, format. Repeatable structure over clever tricks. We rewrote prompts the room brought with them, live.

  4. 4

    Tool selection

    Chat interface, embedded copilot, or custom build. What each costs in money and effort — and when the right answer is to leave a process alone.

  5. 5

    Governance

    Data handling, approval paths, what gets logged, what never goes near a public model. They left with a policy skeleton they own.

MechanicsRiskPromptsToolsGovernance

What I built

Decision-maker curriculum, shipped as a branded deck — and a close that proved the claim on the screen in front of them.

Deliverable 01

Five-module leadership curriculum

Aimed at decision makers. Every module closed with something the room could use on Monday.

  • Mechanics before tools so intuition outlasts product cycles
  • Examples drawn from NEFC’s own operating context
  • Built for mixed literacy without diluting the substance

Illustrative UI

Deliverable 02

44-slide branded deck

NEFC Group’s brand throughout, with ROQ CX on the title and closing slides.

  • Generated in code — every slide, layout, chart, and brand token
  • No clicking around in PowerPoint
  • Built in a fraction of a normal design cycle

Illustrative UI

Deliverable 03

Live prompt clinic

Repeatable structure over clever tricks.

  • Role, context, constraint, format as the shared frame
  • Prompts the room brought rewritten in session
  • Patterns they could take back to Monday’s work

Illustrative UI

Deliverable 04

Governance they own

Risk got its own module instead of a closing disclaimer.

  • Data handling and approval paths made explicit
  • Clear boundary for what never touches a public model
  • A policy skeleton the leadership team keeps, not a template from me

Illustrative UI

Outcomes

What the room took away from the day.

Shared AI vocabulary for leadership decisions

44-slide deck built as live proof of the claim

Prompt patterns rewritten from their own work

Governance skeleton ready for internal ownership

Building these skills for automating tasks is going to save us all weekend work and hours of time spent in Excel.
Finance DirectorNEFC Group

Key insights

What made the day land.

Business-specific examples meant nobody had to translate a generic case study into their own world.
Insight 01
Mechanics before tools: product comparisons expire; knowing why a model behaves the way it does does not.
Insight 02
Governance belongs as its own module — risk is the part leadership actually owns.
Insight 03
Every claim in the room came with a real build behind it. The deck on screen was the proof.
Insight 04

What makes this different

Three lenses: the old default, the common shortcut, and the product bet.

Generic AI briefings

Vendor demos and hype, thin on mechanics

Off-the-shelf courses

Useful vocabulary, weak fit to their operating context

This workshop

Their business, their prompts, their policy — plus a live build as proof

Want this for your team?

I run these across the UAE and the wider region, built around your business and your data constraints — not a recycled deck with your logo swapped in.

Book an AI workshop
  • Built around your business
  • UAE and wider region
  • Leadership-ready fluency