User Journey Map
Purpose
User Journey Map is the frame-level experience artifact, and it is optional. Its unique job is to show the whole experience a task involves, including steps outside the product, so the team can see where the stories cover the experience, where they leave gaps, and which opportunities it owns.
It is not a story, a user flow or a design. Stories own testable behavior; the user flow owns views and transitions; wireframes own layout and states. The map links to them by ID.
Example
Show a worked example of this artifact
---
ddx:
id: example.user-journey-map.depositmatch.import-weekly-files
authoring:
home: repo
depends_on:
- example.feature-specification.depositmatch.csv-import
- example.user-story.depositmatch.upload-csv
---
# UJM-001: Import a Client's Weekly Files
**Feature**: [[FEAT-001]] CSV Import and Column Mapping | **Map kind**: future-state | **Evidence**: research plan `pilot-reviewer-interviews` (6 interviews), pilot support tickets
## Actor and Scenario
- **Person**: Reconciliation lead. Reconciles 12 to 20 clients a week on a desktop; knows each client's books, not their export formats.
- **Task**: Import a client's weekly files (FEAT-001 Task Model).
- **Scenario**: Monday's bank and invoice exports for Acme Dental arrive by email. Maya brings them into DepositMatch, checks the columns and the rejected rows, and confirms the import so matching can start.
- **Trigger**: The client's weekly exports arrive.
- **End state**: The import is confirmed and match suggestions are ready, or Maya knows exactly what to ask the client to fix.
### Goals and Expectations
- Finish each client's import in under five minutes.
- Never let a wrong column produce plausible-looking matches.
- Know before matching which rows were left out and why.
## Journey Phases
| Phase | Actions | Thoughts | Emotion | Touchpoints | Stories / ACs |
|---|---|---|---|---|---|
| Receive | Saves the two attachments from the client's email | "Same format as last week, I hope." | neutral: routine | Email (outside the product) | uncovered: happens outside DepositMatch |
| Upload | Starts a new import and attaches both files | "Did it take both?" | neutral: brisk | upload | US-001-AC1, US-001-AC2 |
| Check columns | Confirms the saved mapping, fixes one renamed column | "If amount is wrong, every match is wrong." | negative: wary | mapping review | US-002-AC1, US-002-AC2 |
| Review rejections | Reads why 14 rows were rejected | "Are these mine to fix or the client's?" | negative: unsure | validation results | US-003-AC1 |
| Confirm | Confirms the import and moves to matching | "Good, that's done." | positive: relieved | import summary | US-003-AC2 |
| Follow up | Emails the client about the rejected rows | "They'll want the row numbers." (assumption) | neutral | Email (outside the product) | uncovered: no story exports the rejected rows |
## Insights
| Insight | Phase | Evidence |
|---|---|---|
| A renamed column is the most common reason an import goes wrong | Check columns | 4 of 6 interviews; 9 pilot support tickets |
| Reviewers copy rejected rows by hand into an email to the client | Follow up | 5 of 6 interviews |
## Opportunities
| Opportunity | Phase | Owner | Metric | Target |
|---|---|---|---|---|
| Flag a saved mapping whose column was renamed, before the reviewer confirms | Check columns | Import squad | Imports corrected after confirmation | hypothesis: under 1% |
| Export rejected rows with their row numbers and reasons | Follow up | Product | Median time from summary to client email | hypothesis: under 2 minutes |
## Story Coverage
| Phase | Covered by | Gap |
|---|---|---|
| Upload to Confirm | US-001, US-002, US-003 | None |
| Follow up | none | No story exports the rejected rows |Reference
| Activity | Frame — Define what the system should do, for whom, and how success will be measured. |
|---|---|
| Default location | docs/helix/01-frame/journey-maps/UJM-{n}-{name}.md |
| Requires | None |
| Enables | None |
| Informs | User Flow Solution Design Story Test Plan Improvement Backlog |
| Generation prompt | Show the full generation prompt |
| Template | Show the template structure |
Innsigle seal: model-primary by HELIX
The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.
- Composition
- model-primary
- Issuer
- HELIX
helix - Signing key
ed25519:b0865d76d834a52c48506414d16f4e5a(build key)- Signed source
artifact-types/frame/user-journey-map.md- Signed
- 2026-11-16T15:52:45Z
- Content digest
sha256:2dd9e37e…c6edbd65
This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-11-16T15:52:45Z",
"issuer": {
"id": "helix",
"name": "HELIX",
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/helix/artifact-types/frame/user-journey-map/",
"digest": {
"alg": "sha256",
"value": "2dd9e37e96b727273541b25a804b4ee9dbb76ce1dcc6391280224d62c6edbd65"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "model-primary",
"ingredients": [
{
"kind": "model",
"name": "Claude",
"role": "draft"
},
{
"kind": "tool",
"name": "sloptimizer",
"role": "rewrite"
},
{
"kind": "human",
"name": "operator",
"role": "structure-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"alg": "ed25519",
"sig": "OUm7jDWJLZYacumeHEhvakKbCgho4QatUVPZNI3lLwK6CGdlQIIa83q4lcDhKcMkXj22Zhx4evKiSlq-P084Bg",
"signed_at": "2026-11-16T15:52:45Z"
}
]
}