Mnemos AI
Product

Onboarding journeys

Personalized ramp plans built from the memory graph, with milestones, copilot support, and manager visibility.

Note

Mnemos onboarding is generated from your graph, not a generic template. The new hire's journey is built from the entities, SOPs, and decisions that touch their seat.

How a journey is built

When a new hire is provisioned, Mnemos walks the graph from their assigned role and team. It identifies:

  • SOPs the role is expected to own or contribute to
  • Systems the role accesses and the people who administer them
  • Recurring decisions the role participates in
  • Critical relationships (escalation paths, peers, stakeholders)

The journey is a sequenced list of learning units, each backed by a real artifact in the workspace. Units are not slide decks; they are live SOPs, transcripts, and graph snapshots.

Milestones

WhenFocusOutcome
Week 1ContextOrg map, role-specific SOPs, top relationships, and the systems they'll touch.
Week 2ShadowRecorded shadowing sessions with the seat's predecessor or peer.
Week 4First ownsIdentified workflows where the new hire becomes the named owner.
Week 6Decision authorityDecisions the new hire is now authorized to make alone.
Week 12Fully rampedCoverage of all critical workflows for the role, validated by manager sign-off.

The copilot

Every new hire has an in-product copilot tuned to their journey. It can answer questions cited from the workspace memory, surface the next milestone, and escalate gaps to the hire's manager when a dependency can't be answered from existing knowledge.

curl
curl -X POST https://api.mnemos.ai/v1/onboarding/journeys \
  -H "Authorization: Bearer $MNEMOS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "user_id": "usr_01HZX...",
    "role": "revops-analyst",
    "start_date": "2026-06-01"
  }'

Manager visibility

Managers see ramp progress per milestone, time-to-first-own metrics, and the questions their new hires are asking the copilot. The dashboard exposes unanswered-question rate as a leading indicator of knowledge gaps in the role's graph slice.