Adept — Curio for teams.

Where Adept fits — the designer lane

Two paths into Adept

Companies adopt Adept from one of two starting points. Both end up in the same SME workbench and ship through the same deploy action — they differ only in where the first draft comes from.

• General library — pre-approved by Curio L&D

  Pre-approved · swap-and-deploy

  Baseline content companies adopt as-is (workplace comms, security awareness, new-manager basics, …). Your SME swaps any concept via the workbench without rewriting from scratch. Fastest path to a deployed pack.

• Company-specific — drafted from your material

  Company-specific · tenant-only

  One-tenant content authored against your policies, tooling, and source-of-truth docs. Acme Co. onboarding is the shipped example. Longer pilot, but the pack matches your reality exactly.

See both live on the Adept demo workspace.

How it works

1. 1

   Scope with the journey decoder

   Start in the designer lane on the home page. Two questions — the capability gap and the business driver — feed the journey decoder, which produces a structured brief: section spine, audience cues, success signals, and the source documents you'll need to upload. That brief is what your SME signs off on before drafting begins.

2. 2

   Draft in the SME workbench

   Same content-pack engine as the consumer Curio product, opened inside the SME workbench at /adept. We seed it with your source-of-truth material (SOPs, policies, code docs, training decks) and the workbench renders a draft pack — sections, concept lessons, quizzes, section tests, optional mock exam — ready for SME review.

3. 3

   SME elicit + verify in the workbench

   Your subject-matter expert works through the workbench concept-by-concept: accept, edit, or revert. Each approval is signed with the SME's name and timestamped, giving the pack a per-concept sign-off trail. A pack-level Deploy action snapshots the approved state, and deploying clears prior signatures so re-verification is explicit.

4. 4

   Roll out to learners

   The same consumer Curio shell, now serving your branded, SME-approved content. Per-learner progress, optional cohort grouping, SSO on the roadmap. Learners run the same backward-design prompts on first touch, so each one names their own success criteria — and you can compare those against the SME-defined ones from step 1.

5. 5

   Effectivity report + next steps

   After each cohort: mastery curves per concept, time-to-pass distribution, drill-trigger frequency, and the concepts most learners stalled on. The SME uses that to rewrite weak concepts in the workbench; the loop closes. We propose the next pack only when the data says the current one is landing.

What the demo pilot looks like

What we measure (the effectivity layer)

Self-report “completed” isn't evidence. We instrument the learning loop end-to-end and surface only the metrics that map back to the SME-defined success criteria from step 1.

• Mastery curve

  % of concepts each learner has scored at or above the pass-gate, over time. Per cohort and per role.

• Time-to-pass

  Median + p95 from first-touch to mastered, per concept. Identifies the concepts that drag the whole cohort.

• Drill frequency

  Concepts that triggered the below-60% drill recommendation. High drill rates flag content that needs an SME rewrite.

• Section-test pass rate

  Pass-gate is configurable per pack. We report first-attempt and best-attempt.

• Stalled-concept heatmap

  Which concepts learners read but never quiz. Surface for the SME so they can shorten or restructure.

• Pre/post delta

  Optional baseline assessment at pack start vs. section-test at end. The strongest evidence of transfer.

Try it before you brief us

Next steps