A Journey Comparison links two journeys that address the same Job To Be Done — a legacy (baseline) journey and a target (modernized) journey — and stores the step-by-step alignment plus the computed metrics that prove measurable UX improvement.
If Journeys are the evidence of how users work today, Journey Comparisons are the evidence of how much better they will work tomorrow. Comparisons turn modernization from a qualitative claim (“the new system will be easier”) into a quantified one (“38% fewer steps, 54% less friction, 22% faster completion”).
Key Fields
| Field | Purpose |
|---|---|
| title | Human-readable comparison name (auto-generated or user-provided, max 500 chars) |
| status | Comparison lifecycle state: :draft, :completed, :archived |
| jtbd_id | The JTBD both journeys address (required) |
| legacy_journey_id | The baseline journey representing the current state (required) |
| target_journey_id | The modernized journey representing the target state (required) |
| step_mappings | JSON array aligning legacy and target steps (see below) |
| metrics | Cached computed metrics (step count delta, friction delta, time delta, etc.) |
| notes | Free-text observations and caveats |
| owner_id | User responsible for the comparison |
Step Mappings
The step_mappings field is the core alignment data. Each entry links a legacy step to a target step (or marks it as eliminated or new):
[
{
"legacy_step_id": "uuid",
"target_step_id": "uuid",
"status": "mapped"
},
{
"legacy_step_id": "uuid",
"target_step_id": null,
"status": "eliminated"
},
{
"legacy_step_id": null,
"target_step_id": "uuid",
"status": "new"
}
]
Mapping Statuses
- mapped — Legacy step has a direct equivalent in the target journey
- eliminated — Legacy step removed entirely (the target no longer requires it)
- new — Target step has no legacy equivalent (added capability)
- improved — Mapped step that reduces friction, duration, or both compared to its legacy counterpart
Eliminated steps represent friction removed. New steps represent capability added. The ratio between them tells you whether modernization is simplifying the experience or just shifting complexity.
Metrics
The metrics map caches the quantified deltas so dashboards and reports can surface them without recomputing:
| Metric | What It Measures |
|---|---|
| step_count_delta | Change in total step count (negative = fewer steps) |
| friction_delta | Change in total friction score across all steps |
| time_delta | Change in estimated duration (negative = faster) |
| eliminated_count | Number of legacy steps removed |
| improved_count | Number of mapped steps with reduced friction or duration |
| new_count | Number of target steps added |
Metrics are computed from the underlying Journey Steps and cached in the comparison for fast read access. When step data changes, the comparison can be recomputed.
Comparison Lifecycle
Draft
A new comparison starts as draft while you align the steps and review the mappings. Draft comparisons are working documents — you might add or revise mappings as you learn more about the target journey.
Completed
Once the step mappings and metrics have been reviewed and the numbers represent a reliable assessment, mark the comparison completed. Completed comparisons are citeable evidence in executive reviews, investment decisions, and delivery milestones.
Archived
Comparisons become archived when the initiative they belong to ships, or when the target journey is superseded by a newer design. Archived comparisons preserve history and support audit-trail queries via the AshPaperTrail change tracking on this resource.
Example: Quote-to-Cash Modernization
Legacy Journey — “Submit a Quote” in the Oracle EBS system:
- Log into Oracle EBS
- Navigate to Quote Entry
- Manually select customer from dropdown (high friction)
- Enter line items one at a time
- Apply pricing rules manually (high friction)
- Generate PDF
- Email to customer
Target Journey — “Submit a Quote” in the new CPQ system:
- Log in (SSO)
- Customer autocomplete with recent search history
- Bulk line-item import from template
- Auto-applied pricing rules with override indicator
- One-click send (quote delivered via branded portal link)
Comparison Metrics:
- step_count_delta: -2 (7 → 5 steps)
- friction_delta: -14 (reduced high-friction steps)
- time_delta: -8 minutes (estimated median)
- eliminated_count: 2 (manual customer select, PDF + email)
- improved_count: 3
- new_count: 0
This is the kind of evidence that moves stakeholders from “sounds good” to “let’s fund it.”
Relationships at a Glance
| Related Concept | Relationship |
|---|---|
| Journey | Each comparison links exactly two journeys (legacy + target) |
| Journey Step | Step mappings align individual steps across the two journeys |
| JTBD | Both journeys must address the same JTBD — this is the anchor |
| Application Version | Each journey is tied to a specific Application Version, enabling cross-version comparison |
| Initiative | Comparisons are the measurable outcomes initiatives point to |
Best Practices
Pick the right JTBD anchor.
Both journeys must serve the same underlying Job To Be Done. If the legacy and target journeys address different jobs, you’re comparing apples to oranges and the metrics will be misleading.
Capture the legacy journey completely before designing the target.
Accurate eliminated-step counts depend on a full, faithful baseline. Shortcuts in the legacy capture will understate the improvement.
Let the target journey be aspirational but grounded.
If the target journey describes steps that the team has not committed to building, the metrics risk overpromising. Keep target journeys synchronized with what delivery will actually produce.
Recompute metrics before important reviews.
Step data in the underlying journeys may change between the time a comparison is drafted and the time it is cited. Recompute the cached metrics before using them in an executive review or funding decision.
Use archived comparisons as learning artifacts.
Archived comparisons from past modernizations are valuable training data for estimating future efforts. Preserve them rather than deleting.
Next Steps
- Capture Journeys — Both a legacy baseline and a target design
- Align Journey Steps — Granular step data drives the metrics
- Connect to JTBDs — The anchor that validates you are comparing like with like
- Link to an Initiative — Tie the comparison to a funded modernization effort
Pro Tip: If a Journey Comparison’s metrics would not make it into a slide you would show an executive sponsor, the comparison is not done yet. Keep iterating on the step mappings until the numbers both hold up and tell a coherent story.
Support
Questions about Journey Comparisons?
- Documentation: Continue reading about Journeys and Journey Steps
- In-App Help: The AI assistant can help you align steps and interpret metrics
- Email: support@catalio.ai
- Community: Share modernization comparison patterns with other Catalio users