What You Hand Over, and What You Keep

What has to be handed over is smaller than it sounds, and most of it already exists without being called material: the procedure as it is performed, and whatever was written down last time somebody had to explain it. Nothing has to be authored before there is a first draft to react to.

The real cost is attention, not production time. The person who knows the exceptions spends an hour on a draft, and the corrected file coming back is itself the record of what was approved, so the sign-off exists as a document instead of as somebody’s memory of a meeting.

What is left at the end is the source, not only the render. Slides, narration and video are outputs of a text that stays readable and in the company’s hands: the difference between a deliverable and a finished file that can only be replaced, never corrected.

What the Second Class Costs

The number that decides whether an internal course programme survives is never the cost of the first class. It is the cost of the second. The first one pays for the platform once, everything after pays only for its own content, and that turns the tenth into a scheduling question, not a budget question.

Underneath sits an ordinary application, not a viewer: courses, modules, slides and quiz questions as real entities, a catalogue and a player, all running on the same stack as the rest of the work. Hosting and extending it are not a separate specialism to hire for.

The local account list is a deliberate trade, not an oversight. Learners live inside the platform, which lets a class start this month; the price is one more place a leaver has to be removed from. Naming it now is cheaper than discovering it in month four.

Failures Recorded Once and Kept as Rules

A production line is worth buying mainly because it has already failed somewhere that was not your project. This one kept the record: a version-control checkout swapping video takes for pointer files, a credit-routing setting starving the avatar narration budget, and a prompting recipe for garbled text on generated frames. Three expensive afternoons, three rules.

That record is why a late change stays affordable. On the in-house run the opening act was cut after production and the rest re-merged without going back to camera. Sunk time keeps a weak segment; an act that can be regenerated removes that argument.

What stays manual belongs in the same breath: somebody still assembles, still watches end to end, still decides it is good enough to send. What was automated is the repetition, not the judgement, so the honest reading is that this buys production capacity, not removing someone from the job.

5
rungs, climbed only as far as the subject deserves
Zero
code changes needed to add a class to the player
12:32.5
runtime of one merged in-house video deliverable
Since 2000
Microsoft Certified Trainer standing behind every rung

One Ladder From a Written Guide to a Course With a Final Exam

Start on the Bottom Rung 3 steps
01

The Process Lives in One Head, and That Head Takes Holidays

The process everyone depends on usually lives in one person's head, so every question becomes a message to whoever is currently away. The entry rung is deliberately small: one written guide on one process, in the company's own vocabulary, produced from the artifacts that process already leaves behind. No filming, no studio, no production schedule. If a written guide is all the subject deserves, the ladder stops right there.
02

A Bought Course Teaches the Product, Not the Way You Use It

Generic course material teaches the vendor's product with the vendor's example data, the vendor's screenshots and the vendor's vocabulary, so every learner still has to translate it into how things run here. Material produced for a customer is made from their own processes, their own systems and their own words. The screens shown are the screens the team actually opens, and the exceptions covered are the ones that actually occur.
03

A Reviewer Who Never Opens a Repository Still Owns the Content

The person who genuinely owns the subject matter rarely works in a repository, so corrections arrive as mail and quietly never reach the material. The pipeline exports the draft to Word and imports the corrected file back, a full round trip. A subject-matter reviewer who is not technical edits in the tool they already use, and those corrections flow back into the source the slides and the narration are generated from.
Climb Only as Far as It Pays 3 steps
04

Decks Built by Hand Drift, and Overflow Is Found by the Audience

Slides built by hand drift out of step with the process within a quarter, and text that overflows a slide is found by the audience rather than the author. Composition runs as code instead: slides are generated with overflow checks, and a rebuild pipeline regenerates a deck rather than patching it. Photos are extracted, annotated and composited, with an acceptance step before anything ships.
05

Nobody Books a Recording Day for a Wording Change

Recorded narration needs a quiet room, a willing speaker and a full re-record every time a sentence changes, which is why most internal material never gets a voice track at all. Narration audio is generated instead, by the same pipeline that composes the slides. A corrected sentence costs a regeneration rather than a session, so the spoken version stays in step with the written one instead of falling a release behind it.
06

The Avatar Rung, and the Honest Rule for Skipping It

An avatar video costs real money and real production time, and spending both on a note three people will watch once is waste dressed as modernity. Avatar renders earn their cost only for material that will be watched repeatedly, so a one-off internal process note stays a written guide and the ladder stops there. Naming the rung that is not worth climbing is what makes every rung above it believable.
A Real Course, Not a Video Folder 3 steps
07

A Video Folder Proves Material Exists, Never That Anyone Learned It

A folder of videos on a share drive proves that material exists, never that anyone learned anything from it, and the first time that distinction matters is an audit or an onboarding gone wrong. Interactions are the difference: checkpoint quizzes sitting between the modules and a final exam at the end, both delivered inside a course player rather than as files to download. That is the enterprise bar, cleared at a size a KMU can carry.
08

The Whole Course Ships as a Folder, Not as a Release

Most learning platforms need a developer every time a class is added, which is exactly why internal course programmes stop after the first one. The platform code here knows nothing about any class. A complete course, its modules, slides, narration audio, checkpoint quizzes and final exam, ships as a data folder with its own course.json and its media. The second class and the tenth need no code change.
09

Learners Managed Without Waiting for an Identity Project

Rolling out a learning platform usually stalls on identity: somebody wants directory integration settled first, and the material waits months behind a project nobody budgeted for. The platform carries local-login access control of its own, with users, roles and permissions. A customer's learners are created and managed directly, so the first class runs while the identity question is still open rather than long after it closes.
Material That Cannot Go Stale 1 steps
10

A Changed Process Means a Regeneration, Not a Reshoot

Material filmed once becomes a sunk cost the moment the process changes, so it is quietly kept in service long after it went wrong. Because everything here is produced by a pipeline, a changed process means a regenerated deck, a regenerated narration track and a regenerated video rather than a fresh production. The same line produced two complete promo videos in-house and published one through its own publishing path.

Frequently Asked Questions

Where does this start, and how much effort does the first step cost us?
One process, one written guide, and the effort on your side is a conversation and a review. Somebody who performs the process talks it through once, and whoever owns it corrects the draft afterwards in Word. Nothing has to be installed, nobody has to be booked, no filming is scheduled, and no decision about a platform is needed at this point. If the guide turns out to be everything that process deserves, that is where it stops.
Why not just buy a generic course off the shelf?
Often you should, and nothing here competes with that. A product thousands of companies use the same way is cheaper to buy than to build, and a public course covers it better. The case for custom material is narrower than the market implies: the subject is a process only your house runs, or the exceptions that matter are ones no vendor sees. If a bought course plus one internal page on the local differences does the job, that is the cheap answer and the right one.
What does 'with interactions' actually mean?
It means the course does not only play. Checkpoint questions sit between the modules and an exam closes it, both answered inside the player rather than in a separate quiz tool, and the whole thing arrives as a data folder with its own course.json instead of as a platform release. A video file can do none of that, and the distinction is what an audit or an onboarding turns on: watching runs to the end by itself, answering does not.
When is an avatar video not worth making?
Apply one test before anything else: multiply the people who will watch it by the number of times each of them will. A process note for three colleagues fails that test, and the right output there is a written guide, sometimes with narrated slides above it. The rung matters because its cost is front-loaded. A render is paid for before anyone has watched anything, which makes it the one decision on the ladder that is expensive to get wrong.