Adept workbench
Effective workplace communication
General B2B pack — pre-approved baseline content on async writing, status updates, productive 1:1s, and feedback that lands. Customers swap any concept via the SME workbench.
SME workbench
Edit AI-drafted concepts, sign each as approved, then deploy the verified snapshot to learners. Changes save automatically in this browser.
How do I know what to edit and approve?
Every AI-drafted concept below carries a short list of review hints — short prompts pointing you at the part most worth scrutinising (lesson length, missing summaries, single-question quizzes, etc.). Use them as a checklist, not a finish line.
- Check facts against the source documentsyou uploaded — your signature means “this matches that source today”.
- Edit before you approve— saved edits move a concept to “edited — needs approval”; an explicit Approve click signs and timestamps it.
- Reject anything you can't validate. Rejected concepts don't ship in the next deploy.
- Deploys reset signatures— every new deploy needs fresh sign-offs across the approval chain. Old signatures never apply to a new snapshot.
Approval chain
A demo of the multi-level sign-off a production rollout uses. Each level signs against what they own — content, structure, policy. Deploying clears every signature.
Subject-matter expert
Signs that the content is factually accurate against the source documents.
Not yet signed.
L&D lead
Signs that the structure, success criteria, and applied practice are sound.
Not yet signed.
Compliance reviewer
Signs (for compliance / regulated journeys) that wording matches the controlling policy.
Not yet signed.
Live-since & expiration
When did the current snapshot go live to learners — and when must it be refreshed? Compliance and certification journeys typically expire after a year; others stay live until the source material changes.
Source documents — what to upload, and for whom
The pack is only as accurate as the source material the SME signs against. Upload the documents that anchor each section, and tag the audienceeach one is for — the same word “policy” means different things to L1 support, to engineers, and to the compliance team.
Pick the right document for the audience
- Compliance/regulated — upload the *policy text + revision date*, plus your internal control mapping. Generic vendor whitepapers don't count as source-of-truth.
- Role onboarding — upload SOPs the role actually uses, the runbooks they follow, and the 30/60/90-day checklist. Not the job-ad text.
- Tool adoption — vendor docs plus your internal config decisions (which features are on/off in your tenant).
- Coding skill — redacted production code samples, internal style guide, and review comments from real PRs.
- Certification — official exam blueprint, past scenarios, and the vendor reference for the version learners will sit.
Add a source
Section 1: Communicating async + running 1:1s
Four high-leverage habits — when to skip the meeting, how to write a status update that doesn't need one, how a 1:1 earns its slot, and how to give feedback that actually changes behaviour.
- AI draft
C1.1
Async vs sync — when to use which
- AI draft
C1.2
Writing a status update that doesn't need a meeting
- AI draft
C1.3
Running a productive 1:1 — IC + manager view
- AI draft
C1.4
Giving feedback that lands