AI Fluency Training

Overview

Most teams now have AI access and no method — so they get plausible-looking noise instead of real work. This is structured, hands-on training that fixes that. Built on the open AI Fluency framework, it teaches the four capabilities that separate people who get genuine value out of AI from people who just generate text. Cohorts are role-tracked: sales, operations, engineering, marketing, and legal each work their own real examples.

The timing is not accidental. Since February 2025 the EU AI Act has required companies that use AI systems to ensure their staff have a sufficient level of AI literacy, and by now most teams have Claude or a comparable assistant within reach. What is still missing is a shared way of working: which tasks to hand over, how to brief the model, how to check the result, and what must never be pasted into a chat window. Fluency training closes that gap in days, not quarters, and leaves a written standard behind.

The 4-D framework

Delegation — deciding what to hand to AI, what to keep human, and how to split the work. Description — communicating with AI clearly enough to get what you actually need. Discernment — judging AI output critically instead of trusting it by default. Diligence — using AI responsibly, transparently, and accountably. Get these four right and everything else follows.

In the room, each D becomes a concrete practice. Delegation becomes a task map for the role — what goes to Claude, what stays human, what gets a human review step. Description becomes a briefing pattern people can reuse: context, goal, constraints, format, examples. Discernment becomes a short checklist for judging an answer — sources, omissions, confident-sounding errors — applied to real outputs from the participants' own work. Diligence becomes the house rules: data that never leaves the company, disclosure when AI touches customer-facing text, and who signs off.

How it runs

Half-day to two-day cohorts, hands-on from the start. People work in Claude on tasks from their own week, not toy exercises. We tailor the prompting playbooks to each role and build a shared prompt library your team keeps and grows. The right tool matters too — we show where Claude leads and where a specialist model fits better.

Three formats cover most needs. A half-day fundamentals session gives a whole department the framework and the house rules. A one-day role track goes deep on one function's workflows and ends with that team's playbook drafted. A two-day programme adds a build lab, where participants set up Projects, connectors and reusable skills for their own recurring tasks. We deliver onsite in Athens or remotely, in Greek or English, with materials in both languages.

What you get

A trained team, role-specific playbooks, a reusable prompt and template library, and an output-quality rubric so standards hold after we leave.

Concretely: the slide deck and exercises for your internal reuse, a prompt and template library organised by role, the output-quality rubric, a one-page acceptable-use summary aligned with your AI policy, attendance records for your compliance file, and a short readout for management on where the team is strong and where a follow-up would pay off.

How an engagement runs

Training is short, but the preparation is what makes it land:

1. Intro call. We hear which teams are involved, what tools they already have, and what "better" would look like in their week. We tell you honestly whether training is the right next step or whether a readiness assessment should come first.
2. Role mapping and baseline (week 1). Short interviews with two or three people per role, a look at the tasks they actually repeat, and a baseline of how they use AI today. This is where the role tracks and the real-world exercises come from.
3. Cohort sessions (weeks 2–3). Half-day to two-day formats, hands-on in Claude from the first hour, with each cohort working on its own material. Cohorts stay at eight to sixteen people so everyone gets feedback on their prompts and outputs.
4. Playbooks and library handover (weeks 3–4). We consolidate what the cohorts produced into role playbooks, the shared prompt library and the quality rubric, and hand them over with a walkthrough for the people who will own them.
5. Follow-up (optional, day 30). A short session per cohort to review what stuck, fix what didn't, and update the library — the point where usage typically stops being individual and becomes a team habit.

A single-cohort engagement runs about three weeks end to end; a multi-department programme four to six. Fees are scoped per cohort after the intro call.

The tools we teach with

Claude is the primary tool, in the form your company already has or is about to buy: Claude Team or Enterprise seats for most roles, Projects and connectors for shared context, Cowork for multi-step office work, and Claude Code for the engineers. Where a team's stack is different we adapt the exercises — the framework is tool-agnostic, and part of discernment is knowing when a specialist model for images, video, transcription or data analysis does the job better than a general assistant. The curriculum follows Anthropic's open AI Fluency framework and Mental Bound's own delivery experience from Cowork & Agentic Adoption rollouts, and the house rules are written to sit inside the policy work of our AI governance practice, so training and compliance say the same thing.

FAQs

Do you train non-technical teams?
Yes — that's most of the demand. Operations, marketing, legal, finance, and HR get the most out of this. No coding required.

Is this tied to one AI vendor?
We teach Anthropic's Claude as the primary tool because it's where we have the deepest expertise, but the framework is universal and we're honest about when another model is the better fit.

Can you combine it with a tool rollout?
Yes. Fluency training pairs naturally with Cowork & Agentic Adoption — we train the people and deploy the tools together so adoption actually sticks.

Does the training satisfy the EU AI Act's AI-literacy requirement?
It is designed to. Article 4 of the EU AI Act has required providers and deployers to ensure a sufficient level of AI literacy among their staff since February 2025, taking roles and context into account. The role-tracked curriculum, attendance records and written house rules give you the documented, proportionate programme regulators expect. It is not legal advice; for the wider obligations we bring in our AI governance practice.

How big are the cohorts, and can you run it in Greek?
Eight to sixteen people per cohort, grouped by role. We deliver in Greek or English, onsite in Athens or remotely, with all materials available in both languages.

How quickly do teams see results?
Most participants leave the first session with two or three tasks they now delegate well, and the playbooks make that repeatable across the team. The 30-day follow-up is where we measure it: hours saved on the mapped tasks, quality against the rubric, and which prompts the library actually uses.