発見 · For teams · Early access
The training you'd build for your team if you had a spare week. Built from your docs, in minutes.
Hakken interviews each learner and builds a course pitched at what they already know, checking understanding as it goes. That's live today, for individuals. For teams we're exploring the next step: start from your material and a bar you set, and let Hakken build and adapt the course for each person against it.
It isn't live yet. We're talking to a handful of teams first — if that could be yours, tell us about it.
01
Why bother
Most teams don't have training because training is absurdly expensive to make
$10k–$50k
to build one finished hour of e-learning by hand
The industry benchmark puts a single hour of self-paced training at 79 to 490 hours of work depending on how interactive it is. Most teams never start; the ones that do build it once and can't afford to keep it current.
Chapman Alliance benchmark, 249 organisations (2010, nominal USD)
18 hours
for a six-minute training video or podcast
Even the fastest format is a two-day job. Hakken writes a whole module — lessons, exercises, a checkpoint and a two-host podcast episode — in about the time it takes to make coffee.
ATD, 264 training professionals (2020)
1 in 10
say mandatory training changed how they work
Completion is what gets measured because completion is what the tools can measure. A course that checks understanding and writes a review lesson when someone misses produces a different kind of record.
Gallup, 13,583 U.S. employees (fielded 2018)
02
What it would look like
Half of this exists. The other half is what we want to build with you.
Live today, for individuals
It starts by interviewing each person
Text or voice, a few minutes: what they already know, what they need to be able to do, how much time they have. What they know gets a paragraph, not a module.
A checkpoint per module, and a review lesson when someone misses
Fail a checkpoint and Hakken writes a short lesson on the one idea the misses clustered around, then lets them retake. Understanding, not a click-through.
A tutor that rides along — typed or out loud
Ask when something isn't landing and Hakken answers, or proposes a change to the course itself. Each module can become a podcast episode for the commute.
What we're exploring for teams
Your material, not a library
Start from the SOP, the policy, the product doc — the thing your team actually has to know. The course is built from it, and shows you which passage each lesson came from and what it left out.
A bar you set
Say what good looks like at day 30. Checkpoints measure against that, not against a generic quiz — so what you get back is evidence someone can do the thing, per person.
Rebuilt when the doc changes
The process changed on Tuesday. Update the source and the course follows; nobody re-records a video or re-opens an authoring tool.
Learning for yourself rather than a team? Hakken is in open beta — no form needed.
03
Tell us about your team
Four questions. A person reads the answers.
We'll reply ourselves, not with a sequence. If you send us a doc — an onboarding guide, a process, a policy — we'll build a course from it and show you what came out.