Skip to main content

🗺️ User Journeys

User journeys provide a comprehensive view of how different personas interact with the DeepSkill platform. Each journey maps the complete experience from start to finish, connecting to relevant features, processes, and API documentation.

What are User Journeys?​

User journeys are interactive flow diagrams that show:

  • The complete path a user takes through the platform
  • Key touchpoints and decision points along the way
  • Connected documentation for each step (features, processes, APIs)
  • Tips and prerequisites for each action
  • Visual flow navigation to understand relationships

Available Journeys​

📚 Learner Journeys​

Hierarchical journey structure with high-level overview and detailed micro-journeys.

JourneyStepsDescription
Hub Overview6High-level view of complete learner experience
🚀 Onboarding11From invitation to dashboard access
🤝 Coach Matching13Review and accept coach match
📅 Session Booking14Booking 1:1 coaching via Calendly
🎥 Attending Sessions15Joining and completing video sessions
📖 Learning Modules13Navigating e-learning content
📊 Progress & Feedback19Tracking progress and rating sessions
🎓 Program Completion13Final assessments and certification
📰 Newsfeed5Staying updated with program announcements

Duration: Typically 3-6 months depending on program

Legacy: The full learner journey is also available as a single comprehensive view.

🧭 Team Learning Journeys​

Internal workflows for Team Learning and Team Sales when operating GrowthKit and related tools.

JourneyStepsDescription
Create/Edit Batch12Configure a batch: settings, schedule, surveys, coach dates, publish

The hub also lists placeholders for future Team Learning journeys.

🎯 Coach Journey (Coming Soon)​

The experience of coaches from onboarding through conducting sessions.

PhaseKey Actions
OnboardingRegistration, certification upload
SetupAvailability configuration, profile
Active CoachingSession management, learner support
ReportingSession notes, feedback collection

👔 HR Journey (Coming Soon)​

How HR administrators manage programs and track organizational impact.

PhaseKey Actions
Program SetupConfiguration, budget allocation
Participant ManagementInvitations, enrollments
MonitoringProgress dashboards, attendance
ReportingImpact analysis, ROI measurement

💼 Sales Journey (Coming Soon)​

The sales team's workflow from lead to program handover.

PhaseKey Actions
Lead ManagementCRM integration, qualification
ProposalProgram configuration, pricing
ClosingContract, handover to operations
SuccessCustomer success transition

How to Use Journey Maps​

1. Navigate the Flow​

Click on any step node in the journey diagram to see detailed information:

  • What happens at this step
  • Who is involved (actor)
  • Prerequisites and tips
  • Connected features and processes

2. Follow Connections​

Each step shows connected documentation:

  • ⚡ Features - Platform capabilities involved
  • 🔄 Processes - Detailed process documentation
  • 🔌 APIs - Backend endpoints used

Click any connection to navigate directly to that documentation.

3. Explore Flow Navigation​

Use the Previous/Next navigation in the detail panel to follow the journey sequentially or jump to related steps.

Journey Map Structure​

Each journey is organized into phases that represent major stages:

┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│   Phase 1   │ →  │   Phase 2   │ →  │   Phase 3   │
│  (Onboard)  │    │  (Active)   │    │ (Complete)  │
└──────┬──────┘    └──────┬──────┘    └──────┬──────┘
       │                  │                  │
   ┌───┴───┐          ┌───┴───┐          ┌───┴───┐
   │ Steps │          │ Steps │          │ Steps │
   └───────┘          └───────┘          └───────┘

Step Types​

IconTypeDescription
✅ActionUser-initiated action
◇DecisionChoice point with multiple paths
⚙️SystemAutomatic system process
🔔NotificationEmail or notification sent
🚩MilestoneKey achievement or checkpoint

Creating New Journeys​

To add a new user journey:

  1. Create YAML manifest in journey-registry/
  2. Run converter script: node scripts/convert-journeys.js
  3. Create MDX page in docs/internal/journeys/
  4. Update sidebar configuration

See the Journey Registry README for schema details.

Linking to Existing Documentation​

Journeys link to rather than duplicate existing documentation:

steps:
  - id: book-session
    features:
      - type: feature
        id: session-booking
        title: "Session Booking System"
        link: "/docs/users/learners/book-session"  # ← Links to existing doc

This ensures:

  • No content duplication across the documentation
  • Single source of truth for each feature/process
  • Easy maintenance when details change

Best Practices​

For Documentation Writers​

  1. Keep steps granular - Each step should be a single action
  2. Link generously - Connect to all relevant features, processes, APIs
  3. Add tips - Help users succeed at each step
  4. Document prerequisites - What must happen before this step?

For Developers​

  1. Update journeys when features change significantly
  2. Add API links for new endpoints
  3. Review process connections when backend logic changes

Feedback​

Journey maps are living documents. If you notice:

  • Missing steps or phases
  • Incorrect flow connections
  • Outdated information
  • Missing feature/process links

Please open an issue or submit a PR to the documentation repository.

User journeys are part of the DeepSkill documentation system. See Process Documentation for detailed backend process flows.