Designing Journeys: Best Practices
Follow

May 27, 2026 20:40

Journeys give you four design levers — section order, section completion, test-outs, and delays — plus the ability to edit a Journey after it’s live. The right combination depends entirely on the learning you’re designing. This article covers how to think about each lever and the patterns that work across program types.

Three principles

Three ideas run through every good Journey design.

Match the structure to the learning intent. Lock order when sequence is a real requirement. Leave it open when learners can sensibly approach the material in any order. The structure is a tool, not a default.

Respect the learner’s time. Don’t force completion of content people already know. Don’t force a 7-day delay when 2 days would do. Don’t make every section required when some are deep-dives. Every constraint you add should pay for itself in learning outcomes.

Plan for change. Journeys you’ll edit live for months or years should be designed differently from one-off cohort programs. Think about who’s mid-Journey when you make a change, and decide up front how you’ll handle that.

Choose your section order

The Journey-level Section Order decision (locked vs. open) is the first big design call.

Lock order when sequence is genuinely required:

Foundational material must be understood before advanced material
Compliance frameworks expect sign-off at each step
Cohort onboarding programs where everyone moves together
Multi-step processes being taught end-to-end

Leave order open when sections are independent:

Resource libraries — collections where every section is its own topic
Self-paced enablement — learners pick what fits their current work
Continuing education — long-running content where learners return for what’s relevant

The trap to avoid: locking order out of habit. If your sections work as standalone topics, an open order respects learner autonomy and reduces support friction.

See Section Order: Locked vs. Open for the full mechanics.

Choose your section completion mode

Inside each section, the Completion Requirements mode shapes how learners engage with the content.

All Content — every item required. Use when each piece is genuinely essential or when compliance requires full completion.

Some Content — you set the required number of items. Use when the section is a menu of related material and any subset gives the learner what they need. Pick a count that reflects the actual learning intent, not the lowest possible number.

Optional — section doesn’t count toward Journey completion. Reserve for true deep-dives. If most of your sections are optional, the Journey is probably doing a job better suited to an open content library.

The trap to avoid: defaulting to All Content when Some Content would respect learner choice without compromising the outcome. The reverse trap: choosing Some Content when full coverage is actually required.

See Section Completion: All, Some, or Optional for the full mechanics.

Use test-outs sparingly

A section test-out lets learners pass an assessment to mark the section complete — bypassing the content. The right use cases are narrow.

Test-outs work well for:

Veterans of the topic — long-tenured employees taking refresh content they already know
Mixed-experience cohorts — one Journey serving multiple skill levels
Compliance refreshers — proving you still know the material without re-watching the same video
Mandatory training where some learners already have the knowledge

Test-outs are wrong for:

Skill-building content — if the value is in doing the work, don’t let learners skip the work
Onboarding fundamentals — culture, brand, and company-specific framing benefits everyone
Cohort experiences — the point is the shared experience
Sequential prerequisites — letting a learner skip Section 1 leaves them unprepared for Section 2

The trap to avoid: adding a test-out because it’s available. Default to no test-out unless you have a specific reason — and calibrate the assessment to reflect real competence, not just the ability to guess.

See Skip-Ahead (Test-Out) Assessments for retake behavior and configuration.

Use delays for spacing, not throttling

Delays between sections enforce pacing in calendar days. Use them when spacing serves the learning. Avoid them when they just slow learners down.

Delays serve the learning when:

Spaced repetition would improve retention (the research is clear on this)
The next section requires reflection or practice time
A cohort needs to move at a shared pace
Compliance pacing requires training spread over time

Delays just slow learners down when:

The Journey is reference material — delays block access without benefit
Learners need the content to do their job tomorrow
A learner joined late and is trying to catch up
The Journey is designed for a single sitting

The trap to avoid: adding 7-day delays between every section by reflex. Each delay should have a reason. If you can’t articulate why a learner shouldn’t proceed today, drop the delay.

See Delays Between Sections for the per-learner timing model.

Plan for editing live Journeys

Long-running Journeys get edited. Plan how you’ll handle that from the start.

The model: when you edit a published Journey, existing learners stay on the version they started. New learners see the updated Journey.

Design implications:

For one-off cohort programs, edits between cohorts are clean — every cohort starts fresh on the latest version
For always-on Journeys, edits affect new learners only. Major changes need a communication plan or a re-assignment to reach existing learners
For a major redesign, the cleaner pattern is to archive the old Journey and create a new one — not edit the existing one out of recognition
Small content updates (typo fixes, link replacements, a single piece swapped out) are safe in-place edits

The trap to avoid: making a significant structural change via in-place edit and expecting all learners — including those mid-Journey — to see it. They won’t. They’re on the version they started.

See Editing a Live Journey for the versioning model.

Common design patterns

A few combinations that come up often.

Cohort onboarding (6–12 weeks). Locked section order, All Content per section, delays of 7 days between sections, no test-outs. Every learner moves through the same path at the same pace.

Certification path with prerequisites. Locked section order, All Content per section, test-out available on the foundational sections so experienced candidates can move quickly. No delays — pace is up to the learner.

Resource library by topic. Open section order, Some Content per section (offering choice), several sections marked Optional for deep-dives. No delays. Learners pick what’s relevant.

Mixed-level enablement. Open section order, Some Content per section, test-outs on a few key sections so advanced learners can demonstrate competence quickly. Reserve delays only where reflection time genuinely matters.

Quarterly cadence program. Locked section order, All Content per section, delays of 90 days between sections. Content is released across the year on a predictable cadence.

Common pitfalls

Pitfall	Symptom	Fix
Locking section order out of habit	Learners feel boxed in; engagement drops on content where order didn’t matter	Lock only when sequence is genuinely required
Requiring all content when some content would do	Learners disengage when forced through material they already understand	Use Some Content with a number that reflects the actual learning intent
Adding test-outs because they exist	Learners skip content that was actually valuable	Default to no test-out unless you have a specific reason
Stacking long delays	Programs feel artificially slow	Each delay should serve the learning, not pace for pacing’s sake
Editing a live Journey and assuming everyone sees the change	Support tickets from in-progress learners who don’t see the new content	Plan for the versioning model: new starts see edits, in-progress learners don’t
Optional sections everywhere	Journey completes without core learning happening	At least one section must be required (All Content or Some Content)
Confusing Tracks and Journeys	Wrong product chosen for the use case	Tracks are linear-only; Journeys give you order rules, completion modes, test-outs, and delays

Designing Journeys: Best Practices Follow