Welcome!

Why Training Matters

TL;DR; Training is not a nice-to-have. It's the difference between a team that learns once and a team that keeps re-learning the same things every six months. If your organization has any meaningful knowledge inside people's heads, you need a way to get it out of their heads and into a shared format — and Lupo exists to make that cheap.

Most of this documentation is about how to use Lupo. This section is about why you'd bother investing in training at all. It's a condensed version of the much longer masterclass Xavier teaches on Udemy — a trailer, essentially. If the ideas here resonate, the full course goes much deeper.

The obvious case

The obvious case for training is compliance. Safety, privacy, security, harassment — these are things you have to train people on, or the organization is legally exposed. This is why most LMS conversations start with "we need a tool for our compliance courses."

Compliance is a fine reason to adopt an LMS, but it's not a reason to care about training. Compliance is about covering your back, not about making the team better. If compliance is the only use case you can think of, you're leaving most of the value on the table.

The non-obvious case

The more interesting case is the one most organizations ignore: training is how knowledge compounds.

Think about the last time a senior person on your team left. What did they know that no one else did? How long did it take to reconstruct that knowledge from scratch? How many mistakes did the next person make that the senior person would have seen coming?

Every organization leaks knowledge constantly — through attrition, through project handoffs, through people moving to new roles. The only way to stop the leak is to build a habit of capturing what people learn and putting it somewhere the next person can find it.

Training is that habit. Not once-a-year corporate learning modules, but a default behavior: when something goes wrong, when something goes right, when someone figures out a better way — record it, package it, make it findable.

Why it's usually not done

If this argument is so obvious, why doesn't every team do it?

Because producing good training is genuinely hard and expensive. Writing a course, filming videos, designing activities, testing it on real learners — it's a multi-week project for any serious topic. Most organizations do the math, realize it's going to take a senior person two months to produce one course, and quietly drop the idea.

This is the problem Lupo is built to solve. When you can turn a PowerPoint into a video with AI narration in a few minutes, the production cost of training collapses. A topic that used to cost two months now costs an afternoon. And when the cost is an afternoon, you actually do it.

What good training looks like

You'll see this theme repeatedly in this section: good training is not long, and it's not comprehensive. It's specific, it's short, and it targets a real question the learner has right now.

A 90-minute course on "our engineering onboarding process" is hard to write, hard to watch, and hard to update. Ten 5-minute videos on specific topics — "how to set up your dev environment," "how to submit your first PR," "how we do code reviews" — are easier to write, easier to watch, and easy to update individually when something changes.

Lupo is designed to make the short, specific, updatable format cheap. That's the format you should be aiming for.

The rest of this section

The rest of this section walks through the core ideas of Xavier's masterclass:

Each of these is a short teaser — enough to get you started, not enough to replace the full masterclass.

Where to go next