{ "schema_version": "core-reviewed-term-ai-handoff-v2", "version": "core-reviewed-term-ai-handoff-v2", "compat": { "backward_compatible_schema_versions": [ "core-reviewed-term-ai-handoff-v1" ], "v1_fields_preserved": true }, "contract_status": "preview", "distribution": "per_term_read_only_ai_handoff", "no_write_operations": true, "content_tier": "db_backed", "canonical": { "url": "https://core.yogoq.com/ko-KR/core/customer-journey-mapping", "slug": "customer-journey-mapping", "locale": "ko-KR" }, "summary": { "schema_version": "core-reviewed-term-summary-v1", "term_id": "c0734780-b964-5509-a8a0-2e64cd3ae710", "canonical_slug": "customer-journey-mapping", "canonical_url": "https://core.yogoq.com/ko-KR/core/customer-journey-mapping", "locale": "ko-KR", "display_name": "カスタマージャーニーの可視化", "english_name": "Customer Journey Mapping", "abbreviation": null, "short_definition": "Customer Journey Mapping is a practical decision page for shaping customer path evidence map. It helps teams visualize the customer path so teams can decide where friction, risk, and value moments need action while maki…", "content_tier": "db_backed", "quality": "reviewed", "publication_status": "published_reviewed", "version": "core-reviewed-term-summary-v1", "last_reviewed_at": "2026-05-14T00:00:00.000Z", "sources_count": 2, "limitations_key": "core-trust-policy-v1-2026-06-22" }, "aliases": [ { "text": "カスタマージャーニーの可視化", "type": "display_name", "locale": "ko-KR" }, { "text": "Customer Journey Mapping", "type": "english_name", "locale": "en-US" }, { "text": "カスタマー・ジャーニー・マッピング", "type": "katakana", "locale": "ko-KR" }, { "text": "カスタマージャーニーの可視化", "type": "localized_title", "locale": "ja-JP" } ], "content": { "definition": { "key": "definition", "title": "一言でいうと", "text": "Customer Journey Mapping is a practical decision page for shaping customer path evidence map. It helps teams visualize the customer path so teams can decide where friction, risk, and value moments need action while making customer goal, touchpoints, handoffs, emotions, evidence, and operational owners visible before resources are committed.", "items": [] }, "formula": null, "boundary": null, "usage": [ { "key": "meaning", "title": "意味", "text": "Customer Journey Mapping defines the working concept used to manage journey map. In practice, it helps leaders visualize the customer path so teams can decide where friction, risk, and value moments need action, and it sets a boundary between mapping to decide and mapping as workshop theater. The page should be used as decision support: it names the evidence, trade-offs, owners, and review points needed to avoid drawing a beautiful map that does not change ownership or priorities.", "items": [] }, { "key": "usage", "title": "役立つ場面", "text": "Customer Journey Mapping changes decisions by making customer goal, touchpoints, handoffs, emotions, evidence, and operational owners explicit before teams commit budget, roadmap, sales, or customer resources. It clarifies between mapping to decide and mapping as workshop theater, so teams can decide what is in scope, what is deferred, and what evidence is still missing. For Customer Journey Mapping, this reduces rework because teams compare adjacent concepts, record assumptions, and review whether the chosen action changed customer or business behavior.", "items": [ "Customer Journey Mapping changes decisions by making customer goal, touchpoints, handoffs, emotions, evidence, and operational owners explicit before teams commit budget, roadmap, sales, or customer resources.", "It clarifies between mapping to decide and mapping as workshop theater, so teams can decide what is in scope, what is deferred, and what evidence is still missing.", "For Customer Journey Mapping, this reduces rework because teams compare adjacent concepts, record assumptions, and review whether the chosen action changed customer or business behavior." ] }, { "key": "usage", "title": "使い方のポイント", "text": null, "items": [ "Map a specific customer goal and time period.", "Use evidence from customers and operations, not only internal guesses.", "Mark moments of truth, handoffs, and failure points.", "Assign owners to fixes before the map becomes stale.", "Refresh the map after product, policy, or segment changes." ] } ], "misunderstandings": [ { "key": "misunderstandings", "title": "よくある誤解 / 落とし穴", "text": null, "items": [ "Journey maps are not personas with arrows.", "A map is weak if it does not identify decisions or owners.", "The internal process and the customer journey are often different things." ] } ], "examples": [ { "key": "examples", "title": "最小例", "text": "A team maps the first 30 days after purchase and discovers that billing confusion, not product setup, causes most support contacts. The team writes the decision boundary, gathers evidence on customer goal, touchpoints, handoffs, emotions, evidence, and operational owners, compares adjacent concepts, and chooses one operating change to test. In the Customer Journey Mapping review, the team keeps the parts that changed customer behavior and retires assumptions that were only internally persuasive.", "items": [] } ], "comparisons": [ { "key": "comparisons", "title": "似ている言葉との違い", "text": "Customer experience management | Runs the improvement system | Journey mapping supplies the evidence map for that system Service blueprint | Adds backstage processes | Journey map emphasizes the customer-facing path Customer segmentation | Defines groups | Journey mapping may need separate maps for priority segments", "items": [ "Customer experience management | Runs the improvement system | Journey mapping supplies the evidence map for that system", "Service blueprint | Adds backstage processes | Journey map emphasizes the customer-facing path", "Customer segmentation | Defines groups | Journey mapping may need separate maps for priority segments" ] } ], "faq": [ { "question": "What should a journey map include?", "answer": "It should include customer goal, stages, touchpoints, emotions, evidence, handoffs, pain points, owners, and candidate fixes." }, { "question": "How detailed should it be?", "answer": "Detailed enough to reveal decisions and failure points, but not so detailed that teams cannot act on it." }, { "question": "When should it be updated?", "answer": "Update it when the segment, product, channel, policy, or observed customer behavior changes materially." } ] }, "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "sources": { "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "visible_sources": [ { "label": "Principles of Marketing (OpenStax)", "url": "https://openstax.org/details/books/principles-marketing", "kind": "tier_s" }, { "label": "Wikipedia reference: Customer Journey Mapping", "url": "https://en.wikipedia.org/wiki/Customer_journey", "kind": "supplemental" } ] }, "related_terms": [ { "topic_id": "1129f5aa-90e5-57c3-b8c3-d751fd673c71", "canonical_slug": "value-proposition", "canonical_url": "https://core.yogoq.com/ko-KR/core/value-proposition", "title": "価値提案（バリュープロポジション）", "relation_type": "used_together" }, { "topic_id": "c70d8ad3-e8d8-5e81-b74a-d99374725f73", "canonical_slug": "customer-segmentation", "canonical_url": "https://core.yogoq.com/ko-KR/core/customer-segmentation", "title": "顧客セグメンテーション", "relation_type": "used_together" }, { "topic_id": "da88c0dd-0a6d-5bd5-9cab-e6abd1dbcea1", "canonical_slug": "customer-experience-management", "canonical_url": "https://core.yogoq.com/ko-KR/core/customer-experience-management", "title": "カスタマーエクスペリエンス管理（CX）", "relation_type": "related" } ], "relations": [ { "term_id": "1129f5aa-90e5-57c3-b8c3-d751fd673c71", "canonical_slug": "value-proposition", "canonical_url": "https://core.yogoq.com/ko-KR/core/value-proposition", "display_name": "価値提案（バリュープロポジション）", "relation_type": "related", "source_relation_type": "used_together" }, { "term_id": "c70d8ad3-e8d8-5e81-b74a-d99374725f73", "canonical_slug": "customer-segmentation", "canonical_url": "https://core.yogoq.com/ko-KR/core/customer-segmentation", "display_name": "顧客セグメンテーション", "relation_type": "related", "source_relation_type": "used_together" }, { "term_id": "da88c0dd-0a6d-5bd5-9cab-e6abd1dbcea1", "canonical_slug": "customer-experience-management", "canonical_url": "https://core.yogoq.com/ko-KR/core/customer-experience-management", "display_name": "カスタマーエクスペリエンス管理（CX）", "relation_type": "related", "source_relation_type": "related" } ], "chunk_ids": [ "core:chunk:customer-journey-mapping:ko-KR:definition:8df0320b220d511b", "core:chunk:customer-journey-mapping:ko-KR:meaning:6260de4ac1809789", "core:chunk:customer-journey-mapping:ko-KR:usage:acfa408c1c03107e", "core:chunk:customer-journey-mapping:ko-KR:usage:ea8c1387d7c6949c", "core:chunk:customer-journey-mapping:ko-KR:misunderstandings:d7ff4ae862be0bf0", "core:chunk:customer-journey-mapping:ko-KR:examples:f3af38ebb51605b9", "core:chunk:customer-journey-mapping:ko-KR:comparisons:7dcc9b901be81035", "core:chunk:customer-journey-mapping:ko-KR:faq:ea9215334dafb50a", "core:chunk:customer-journey-mapping:ko-KR:faq:b41f9bbe131eb645", "core:chunk:customer-journey-mapping:ko-KR:faq:a26c1f1799c5921e" ], "chunks": [ { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:definition:8df0320b220d511b", "section_key": "definition", "heading": "一言でいうと", "text": "Customer Journey Mapping is a practical decision page for shaping customer path evidence map. It helps teams visualize the customer path so teams can decide where friction, risk, and value moments need action while making customer goal, touchpoints, handoffs, emotions, evidence, and operational owners visible before resources are committed.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "8df0320b220d511ba9bf29e1fe46f676e9bde2c5c14e81099e169ab2c1c05124" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:meaning:6260de4ac1809789", "section_key": "meaning", "heading": "意味", "text": "Customer Journey Mapping defines the working concept used to manage journey map. In practice, it helps leaders visualize the customer path so teams can decide where friction, risk, and value moments need action, and it sets a boundary between mapping to decide and mapping as workshop theater. The page should be used as decision support: it names the evidence, trade-offs, owners, and review points needed to avoid drawing a beautiful map that does not change ownership or priorities.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "6260de4ac1809789510240d170b1fb6a6bbb0b0984bb44b4903bcc5e1b222593" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:usage:acfa408c1c03107e", "section_key": "usage", "heading": "役立つ場面", "text": "Customer Journey Mapping changes decisions by making customer goal, touchpoints, handoffs, emotions, evidence, and operational owners explicit before teams commit budget, roadmap, sales, or customer resources. It clarifies between mapping to decide and mapping as workshop theater, so teams can decide what is in scope, what is deferred, and what evidence is still missing. For Customer Journey Mapping, this reduces rework because teams compare adjacent concepts, record assumptions, and review whether the chosen action changed customer or business behavior. Customer Journey Mapping changes decisions by making customer goal, touchpoints, handoffs, emotions, evidence, and operational owners explicit before teams commit budget, roadmap, sales, or customer resources. It clarifies between mapping to decide and mapping as workshop theater, so teams can decide what is in scope, what is deferred, and what evidence is still missing. For Customer Journey Mapping, this reduces rework because teams compare adjacent concepts, record assumptions, and review whether the chosen action changed customer or business behavior.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "acfa408c1c03107ee512b0ef76060cfe1616130b289287d3b04838aecce06297" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:usage:ea8c1387d7c6949c", "section_key": "usage", "heading": "使い方のポイント", "text": "Map a specific customer goal and time period. Use evidence from customers and operations, not only internal guesses. Mark moments of truth, handoffs, and failure points. Assign owners to fixes before the map becomes stale. Refresh the map after product, policy, or segment changes.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "ea8c1387d7c6949c31ea93459e4c62c09774ca54087553cd641fc6f06967f04d" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:misunderstandings:d7ff4ae862be0bf0", "section_key": "misunderstandings", "heading": "よくある誤解 / 落とし穴", "text": "Journey maps are not personas with arrows. A map is weak if it does not identify decisions or owners. The internal process and the customer journey are often different things.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "d7ff4ae862be0bf0f747cd33d43fac1f8050a83aa500d810c8ad960bd204b8cc" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:examples:f3af38ebb51605b9", "section_key": "examples", "heading": "最小例", "text": "A team maps the first 30 days after purchase and discovers that billing confusion, not product setup, causes most support contacts. The team writes the decision boundary, gathers evidence on customer goal, touchpoints, handoffs, emotions, evidence, and operational owners, compares adjacent concepts, and chooses one operating change to test. In the Customer Journey Mapping review, the team keeps the parts that changed customer behavior and retires assumptions that were only internally persuasive.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "f3af38ebb51605b9beec7630649a603330e5fc962dea3efda42fd42395fb03e7" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:comparisons:7dcc9b901be81035", "section_key": "comparisons", "heading": "似ている言葉との違い", "text": "Customer experience management | Runs the improvement system | Journey mapping supplies the evidence map for that system Service blueprint | Adds backstage processes | Journey map emphasizes the customer-facing path Customer segmentation | Defines groups | Journey mapping may need separate maps for priority segments Customer experience management | Runs the improvement system | Journey mapping supplies the evidence map for that system Service blueprint | Adds backstage processes | Journey map emphasizes the customer-facing path Customer segmentation | Defines groups | Journey mapping may need separate maps for priority segments", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "7dcc9b901be81035e5554c1ebe47f10dcfa7fc9a25428037790908ec3eee4767" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:faq:ea9215334dafb50a", "section_key": "faq", "heading": "What should a journey map include?", "text": "What should a journey map include? It should include customer goal, stages, touchpoints, emotions, evidence, handoffs, pain points, owners, and candidate fixes.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "ea9215334dafb50a121c77b1cf8f7d72165fdc5e79ffa1bb48d4a3726412db96" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:faq:b41f9bbe131eb645", "section_key": "faq", "heading": "How detailed should it be?", "text": "How detailed should it be? Detailed enough to reveal decisions and failure points, but not so detailed that teams cannot act on it.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "b41f9bbe131eb6454e2d7660491fb029a01308eaf3162467b9dc473c8fefba4b" }, { "chunk_id": "core:chunk:customer-journey-mapping:ko-KR:faq:a26c1f1799c5921e", "section_key": "faq", "heading": "When should it be updated?", "text": "When should it be updated? Update it when the segment, product, channel, policy, or observed customer behavior changes materially.", "source_refs": [ "concept:business-concept-0105:en-US", "concept:business-concept-0105:ja-JP", "manual_promotion_packet:synthetic-business-concepts-batch2-2026-04-28" ], "content_hash": "a26c1f1799c5921eaaf845fe50f063f90882e16c550390fb35e2fd906f45efc5" } ], "content_hash": "e8fbef2dabf42370ace9412f6b1b24715444bec0960aba4c211efb3751da2633", "hash_algorithm": "sha256", "rag": { "chunk_id_policy": "core:chunk:{canonical_slug}:{locale}:{section_key}:{sha256_16}", "content_hash_policy": "sha256_stable_json", "source_refs_precision": "source_object_ref_or_source_key_current_snapshot" }, "quality": { "content_tier": "db_backed", "quality": "reviewed", "publication_status": "published_reviewed", "source_count": 2, "last_reviewed_at": "2026-05-14T00:00:00.000Z", "trust_policy_version": "core-trust-policy-v1-2026-06-22" }, "limitations": { "policy_version": "core-trust-policy-v1-2026-06-22", "professional_advice_boundary": "reference_only_not_professional_advice", "text": "이 페이지는 조사와 학습을 위한 참조 정보입니다. 회계, 법무, 금융, 의료, 보안 등 개별 판단은 1차 출처나 전문가 확인을 우선하세요.", "items": [ "공개 페이지는 일반 이해와 실무 맥락을 돕는 자료이며, 개별 사안의 전문 조언이 아닙니다.", "제도, 가격, 규제, 회계 기준, 제품 사양처럼 빠르게 변하는 정보는 최종 판단 전에 1차 출처를 확인해야 합니다.", "AI 지원 제작·감사 흐름을 사용하더라도 공개 여부는 품질 게이트와 사람이 읽을 수 있는 증거에 기반해 다룹니다." ] } }