Guided Content Journeys

Instructions

Design structured exploration paths that guide users through large content domains in a logical, progressive sequence. Journeys transform overwhelming content libraries into curated, completable experiences.

1. Journey Architecture

Define the structural model for journeys:

• Journey: A named, themed path through 5-15 steps covering a coherent topic
• Step: A single content interaction — read, watch, explore, or complete a task
• Milestone: A checkpoint after 3-5 steps that summarizes progress and unlocks the next segment
• Prerequisites: Steps or journeys that must be completed before starting
• Branching: Optional paths within a journey based on user interest or skill level

Data model:

Journey
├── id, title, description, difficulty, estimated_time
├── prerequisites: [journey_id, ...]
├── steps[]
│   ├── id, order, title, content_ref, step_type
│   ├── discovery_prompt (question or challenge)
│   ├── completion_criteria (viewed, answered, time_spent)
│   └── optional: true/false
└── milestones[]
    ├── after_step, title, summary_prompt
    └── unlocks: [journey_id, ...]

2. Journey Design Principles

Follow these when creating journey content:

• Progressive complexity: Start with foundational concepts, build to advanced topics
• Spaced variety: Alternate content types (read, interact, reflect) to maintain engagement
• Achievable steps: Each step should take 2-10 minutes; never exceed 15 minutes
• Clear purpose: Every step has a visible “why” — users should know what they’ll gain
• Discovery prompts: End each step with a question or challenge that connects to the next step
• Exit points: Users can pause and resume without losing progress

3. Step Types

Type	Description	Completion Criteria
read	View an article, guide, or reference page	Page viewed for 30+ seconds
explore	Browse a collection, map, or gallery	Visited 3+ items in the collection
interact	Chat with AI, answer a quiz, complete a form	Submitted a response
reflect	Journal prompt or self-assessment	Text entered (minimum 20 characters)
task	Complete a real-world action	User marks complete (honor system)

4. Progression and Tracking

Track user progress through journeys:

• State per user per journey: not_started, in_progress, completed, abandoned
• Step completion: Binary per step, stored with timestamp
• Milestone unlocks: Computed from step completion; triggers notification
• Resume logic: On return, show last incomplete step with context summary
• Completion rate: Track funnel metrics per journey (started → milestone 1 → milestone 2 → completed)

Storage pattern (WordPress):

• User meta: _journey_progress — serialized array of {journey_id, current_step, completed_steps[], started_at, last_active}
• Transient cache for leaderboard-style “users completing this journey” counts

5. Discovery Prompts

Discovery prompts are the connective tissue between steps. They:

• Pose a question that the next step will answer
• Challenge the user to notice something specific in the next content
• Connect the current topic to a broader theme
• Create curiosity gaps that motivate progression

Examples:

• “You’ve learned the basics of coral identification. But how do environmental conditions change what you see? Next, we’ll explore…”
• “Now that you know the Dead’s early sound, what happened when they added a second drummer in 1967?”
• “You’ve mastered the classic French mother sauces. What happens when you break the rules on purpose?”

6. Journey Templates

Provide starter templates for common journey patterns:

Linear journey (beginner): Steps flow A → B → C → D with one milestone at the midpoint.

Branching journey (intermediate): Steps A → B → [choose C1 or C2] → D with branches converging at a shared milestone.

Hub-and-spoke journey (advanced): Central hub topic with 3-5 optional spokes. Complete any 3 spokes to unlock the final synthesis step.

7. Content Domain Mapping

Before building journeys, map the content domain:

1. Inventory all available content pieces
2. Classify by difficulty (beginner, intermediate, advanced)
3. Identify natural prerequisite relationships
4. Group into thematic clusters (these become journey candidates)
5. Identify gaps where new content is needed to complete a journey

Inputs Required

• Content domain description (what the knowledge base covers)
• Inventory of existing content pieces with difficulty classification
• Target audience personas and their starting knowledge level
• Desired journey length and time commitment
• Product platform (WordPress, Tauri, web app)
• Whether journeys are standalone or integrated with AI chatbot interactions

Output Format

• Journey definition (JSON or structured markdown) with all steps, milestones, and prerequisites
• Discovery prompts for each step
• Data model specification for progress tracking
• Content gap analysis (missing pieces needed to complete the journey)
• Implementation plan for the target platform

Anti-Patterns

• Too many steps: Journeys longer than 15 steps feel like a slog. Split into multiple journeys with prerequisites instead.
• No discovery prompts: Steps without forward-looking prompts feel like a disconnected reading list, not a journey.
• All one content type: Ten “read” steps in a row is a textbook, not a journey. Vary the step types.
• Hidden prerequisites: If a journey requires prior knowledge, make prerequisites explicit and link to them.
• No resume capability: Users who can’t pick up where they left off won’t come back.
• Completion without synthesis: Finishing a journey should include a summary or reflection step, not just “you’re done.”
• Designing journeys without content inventory: Building journey structures before knowing what content exists leads to aspirational paths full of gaps.