tom

Method

How I design courses and train the trainers, with the work that proves it.

Most "train the trainer" isn't training anyone.

Ask what it means and you'll get the same answer: take someone who knows the subject, walk them through the slides, maybe do a dry run. They're a trainer now.

Call it what it is: content transfer. It's efficient, it scales, and it's where most organizations stop.

You haven't trained a trainer. You've briefed a narrator.

One level up is methodology transfer. You stop handing over slides and start explaining the structure: why this exercise comes before that concept, why there's a silence at minute twelve, why assessment runs through the session instead of sitting at the end. Rarer, but it exists. It's what I'm building at Scaleway.

Then there's a third level almost nobody works on in corporate training, though it's been central to teacher education in France for decades. Posture. Not what you do in a session — who you are when the session stops going to plan.

The level you can't hand over.

Here's the paradox. The trainers who read a room best are the ones least able to explain how they do it.

There's a well-documented model of competence with four stages, ending in unconscious competence — you do the thing well without thinking about it. That's the goal everywhere else. In teaching, it's a trap: to transmit something, you first have to make it visible again, which means traveling back from stage four to stage two. You have to remember what it felt like not to know. It's disorienting, because the whole point of stage four is that you stopped paying attention.

Take the most ordinary moment there is. You ask a question and the room goes quiet. The problem isn't the silence — it's that you don't know what it means. Are they thinking, or are they lost? Same silence, opposite meanings, opposite responses, and you have about two seconds. Push, or wait. Rephrase, or say nothing.

Nothing in the content or the plan tells you which. Experienced trainers get it right most of the time and can rarely say why.

What I've found so far is that it starts with naming the invisible — putting words on decisions that were never conscious, so they can be discussed at all.

It's the part of the work I spend the most time on and understand the least.

What it looks like when it's done.

A school hired me to teach teenagers to program. What they actually needed was someone to rebuild the curriculum — three years of material with no real progression, not across a year and not across the three. Topics showed up because they existed, not because anything before them made them necessary.

I spent the first year rebuilding it from zero: deciding what to teach, in what order, and what to leave out entirely. The second year, with the progression in place, it held.

The same act as designing one session — one scale up.

And it's the work I'm doing now at Scaleway, one scale up again — building the program that teaches engineers to teach, and designing the trainings myself so there's something to point at.

Selected courses

Eight courses for OpenClassrooms, two for NX Academy. Here are three.

Containerize Your Applications with Docker

NX Academy · French · see the course ↗

Everything a Docker course is supposed to contain is in there. Almost none of it is in the first hour. Networks show up three weeks later, the day you hit a problem they solve.

Master CI/CD Pipelines with GitHub Actions

NX Academy · French · see the course ↗

One project runs through the entire course and is live by chapter two. Nothing gets introduced that the project doesn't need yet.

Make Your Web Content Accessible

OpenClassrooms · English · see the course ↗

WCAG is a specification, not a curriculum. Follow its order and you've written a compliance document. This one starts from the people affected; the criteria arrive as answers.

The work.

Three shapes it usually takes.

01

Building the program

An organization has engineers who know their subject and train badly, and no one whose job it is to fix that. This is the Scaleway shape: standards for how content gets made, a way to say why a training works or doesn't, and enough structure that it survives the person who built it.

02

Training the trainers

Working with engineers who already teach — on methodology first, then on posture. Slower than a workshop and the only version that changes anything.

03

Designing the course

Sometimes what's needed is just the course, done properly. Curriculum, sequence, exercises, assessment.

I do this full-time at Scaleway. Outside of it, I take on a small number of programs and courses through NX Academy — enough to keep the practice honest, not enough to become an agency.