{"id":1182,"date":"2026-02-25T10:37:20","date_gmt":"2026-02-25T10:37:20","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/"},"modified":"2026-02-25T10:37:20","modified_gmt":"2026-02-25T10:37:20","slug":"why-model-customer-journeys-with-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/","title":{"rendered":"Why Model Customer Journeys with BPMN?"},"content":{"rendered":"<p>\u201cStart with a journey map and then build the process.\u201d It sounds simple. But in practice, that\u2019s where most initiatives stall.<\/p>\n<p>Storytelling alone doesn\u2019t change operations. Journey maps capture emotions, touchpoints, and perceptions\u2014but they don\u2019t specify who does what, when, or how work is handed off.<\/p>\n<p>I\u2019ve worked with organizations that spent months on detailed journey maps\u2014only to find no one knew how to act on them. The gap between empathy and execution remains wide if you don\u2019t formalize what happens behind the scenes.<\/p>\n<p>That\u2019s where BPMN steps in. It\u2019s not just a diagramming tool. It\u2019s a language for connecting customer experience with operational reality.<\/p>\n<p>By modeling customer journeys with BPMN, you transform insights into actionable workflows. You make responsibilities explicit, sequences traceable, and handoffs unambiguous.<\/p>\n<p>This chapter shows how BPMN adds rigor to journey thinking\u2014turning vague empathy into concrete process design. You\u2019ll learn why this integration is essential, not optional, for lasting improvement in customer experience.<\/p>\n<h2>Why Journey Maps Fall Short Without BPMN<\/h2>\n<p>Customer journey maps are invaluable for understanding the human side of service delivery. They show where customers feel frustrated, delighted, or anxious.<\/p>\n<p>But they rarely answer: Who owns the next step? How long should it take? What happens when something goes wrong?<\/p>\n<p>Without a structured model, journey insights stay isolated. Teams can\u2019t act on them. Leaders can\u2019t measure impact. Automations can\u2019t be triggered.<\/p>\n<p>I\u2019ve seen teams spend weeks designing emotional journeys\u2014only to realize their call center, IT support, and billing systems were working in parallel with no shared understanding of the flow.<\/p>\n<p>The missing layer? Responsibility mapping. Sequence clarity. Decision logic.<\/p>\n<p>BPMN fills that gap. It doesn\u2019t replace empathy\u2014it makes it operational.<\/p>\n<h3>The Limits of Visual Storytelling<\/h3>\n<p>Journey maps are excellent for storytelling. They show the customer\u2019s path across channels, moments of truth, and emotional highs and lows.<\/p>\n<p>But they\u2019re not process models. They don\u2019t define:<br \/>\n    &#8211; Who performs each activity?<br \/>\n    &#8211; When does the next step begin?<br \/>\n    &#8211; What triggers a handoff or escalation?<\/p>\n<p>These are the questions that determine whether a journey is sustainable, scalable, and measurable.<\/p>\n<p>Consider a customer trying to resolve a payment error. The journey map may show \u201cfrustration\u201d at the \u201csupport wait time\u201d stage. But without BPMN, no one knows if the delay is due to a backlog, a misrouted ticket, or lack of access to the right systems.<\/p>\n<h2>How BPMN Transforms Journey Thinking<\/h2>\n<p>BPMN doesn\u2019t replace journey maps. It extends them\u2014adding precision, accountability, and automation potential.<\/p>\n<p>Here\u2019s what BPMN brings to the table:<\/p>\n<ul>\n<li><strong>Clear roles and responsibilities:<\/strong> BPMN\u2019s lanes (swimlanes) assign processes to specific teams or systems, making ownership visible.<\/li>\n<li><strong>Defined sequences:<\/strong> Every activity, decision, and event follows a logical order. You see the path from trigger to outcome.<\/li>\n<li><strong>Traceable handoffs:<\/strong> Message flows show how information moves between teams, revealing delays and bottlenecks.<\/li>\n<li><strong>Exception handling:<\/strong> Boundary events capture failures, escalations, and timeouts\u2014so you can plan for them, not just react.<\/li>\n<\/ul>\n<p>Now, when a journey map shows \u201ccustomer frustration during long wait,\u201d the BPMN model reveals *why*: a queue in the support system, a missing escalation rule, or a lack of automated response.<\/p>\n<h3>Beyond the Happy Path: Real-World Complexity<\/h3>\n<p>Most journey maps only show the ideal flow. But customers don\u2019t always follow the script.<\/p>\n<p>BPMN lets you model:<br \/>\n    &#8211; Abandoned carts<br \/>\n    &#8211; Failed verifications<br \/>\n    &#8211; Escalated complaints<br \/>\n    &#8211; Duplicate submissions<\/p>\n<p>These aren\u2019t anomalies. They\u2019re data points. And BPMN turns them into actionable conditions.<\/p>\n<p>Example: A customer enters the wrong password three times. The journey map might label it \u201cfrustration.\u201d The BPMN model shows:<br \/>\n    &#8211; <code>Activity: Login attempt<\/code><br \/>\n    &#8211; <code>Gateway: Failed more than 3 times?<\/code> \u2192 Yes \u2192 <code>Send email: Account locked<\/code> \u2192 <code>Activity: Unlock request<\/code><br \/>\n    &#8211; No \u2192 Continue to next step.<\/p>\n<p>Now the team doesn\u2019t just know *what* happened\u2014they know *how* it will be handled.<\/p>\n<h2>Key Benefits of BPMN for Customer Journeys<\/h2>\n<p>Aligning journey thinking with BPMN delivers tangible value. Here are the core benefits of BPMN for customer journeys:<\/p>\n<ul>\n<li><strong>Improved cross-functional alignment:<\/strong> When CX, operations, and IT collaborate on the same model, miscommunication drops.<\/li>\n<li><strong>Identifiable automation candidates:<\/strong> Clear process steps with defined inputs and outputs are perfect targets for workflow automation or RPA.<\/li>\n<li><strong>Traceability from pain points to process change:<\/strong> Each customer complaint can be linked back to a specific activity or decision point in the BPMN model.<\/li>\n<li><strong>Consistent modeling across touchpoints:<\/strong> Whether a journey starts online or in-store, BPMN ensures the logic remains the same.<\/li>\n<li><strong>Shared language for innovation:<\/strong> Teams from different functions can debate process changes using the same diagram, reducing confusion.<\/li>\n<\/ul>\n<p>These are not hypothetical advantages. They\u2019re practical outcomes from real implementations.<\/p>\n<h3>Case Example: Onboarding That Actually Works<\/h3>\n<p>A SaaS company had a journey map showing onboarding as \u201ctoo slow.\u201d But no one knew where the delay was.<\/p>\n<p>They modeled the onboarding process in BPMN. The model revealed:<br \/>\n    &#8211; Step 1: Customer submits application (1 minute)<br \/>\n    &#8211; Step 2: Manual review by support team (average 48 hours)<br \/>\n    &#8211; Step 3: Auto-verification via internal tool (15 seconds)<br \/>\n    &#8211; Step 4: Email sent to customer (instant)<\/p>\n<p>It wasn\u2019t the system\u2014it was the manual review. The team prioritized automating that step, reducing onboarding time from 3 days to 4 hours.<\/p>\n<p>Only BPMN made this visible.<\/p>\n<h2>CX and BPMN Integration: A Strategic Advantage<\/h2>\n<p>When you integrate CX and BPMN, you\u2019re not just drawing a picture\u2014you\u2019re creating a living system.<\/p>\n<p>This integration enables:<\/p>\n<ul>\n<li>Shared ownership between CX and process teams<\/li>\n<li>Real-time feedback loops\u2014improvements are validated through process changes<\/li>\n<li>Consistent KPIs tied to specific process steps<\/li>\n<\/ul>\n<p>For example:<br \/>\n    <code>Activity: Send confirmation email<\/code> \u2192 KPI: <em>Time to send: \u2264 1 minute<\/em><br \/>\n    <code>Activity: Support ticket response<\/code> \u2192 KPI: <em>First response within 4 hours<\/em><\/p>\n<p>Now, every time a customer reports a delay, the team can check the BPMN model and see if the process is on track.<\/p>\n<p>That\u2019s the power of integration: insight becomes action.<\/p>\n<h2>Practical Guidance: When to Use BPMN for Journeys<\/h2>\n<p>Not every journey needs a full BPMN model. But when you\u2019re aiming to:<\/p>\n<ul>\n<li>Improve a critical journey (e.g., purchase, onboarding, support)<\/li>\n<li>Align multiple teams around a shared process<\/li>\n<li>Identify automation opportunities<\/li>\n<li>Measure or report on journey performance<\/li>\n<\/ul>\n<p>then BPMN is the right tool.<\/p>\n<p>Start small. Pick a high-impact journey. Model the main path first. Add exceptions later.<\/p>\n<p>Use lanes to separate customer, frontline, and back-office roles. Make the customer\u2019s path clear\u2014either as a dedicated lane or by highlighting their touchpoints.<\/p>\n<p>Don\u2019t overcomplicate. Focus on clarity and actionability.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intentions, BPMN models can go off track. Watch for these:<\/p>\n<ul>\n<li><strong>Overloading the diagram:<\/strong> Too many events, gateways, or lanes make it unreadable. Keep it focused on the customer flow.<\/li>\n<li><strong>Ignoring the customer\u2019s perspective:<\/strong> If the customer isn\u2019t clearly represented, the model becomes a back-office process, not a journey.<\/li>\n<li><strong>Modeling too early:<\/strong> Don\u2019t build BPMN before the journey is understood. Use journey maps first to define the scope.<\/li>\n<li><strong>Forgetting exceptions:<\/strong> The happy path is only part of the story. Always model failure, escalation, and abandonment paths.<\/li>\n<\/ul>\n<p>Every time you add a branch for a failure, you\u2019re not complicating the model\u2014you\u2019re making it realistic.<\/p>\n<h2>Why This Matters for Customer Experience<\/h2>\n<p>At its core, customer experience isn\u2019t just about touchpoints or emotions. It\u2019s about how well your organization delivers value.<\/p>\n<p>BPMN turns experience into performance. It answers:<br \/>\n    <em>Can we deliver on time?<br \/>\n    Can we handle the unexpected?<br \/>\n    Can we scale without losing quality?<\/em><\/p>\n<p>When you model customer journeys with BPMN, you\u2019re not just documenting processes. You\u2019re designing for reliability, responsiveness, and empathy\u2014all at once.<\/p>\n<p>The customer doesn\u2019t care about your internal org chart. They care about whether the service works, when it works, and how they\u2019re treated when it doesn\u2019t.<\/p>\n<p>BPMN makes that visible. It gives you a roadmap\u2014not just to improve, but to prove.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the main difference between a journey map and a BPMN model?<\/h3>\n<p>A journey map shows the emotional and experiential flow from the customer\u2019s point of view. A BPMN model shows the operational sequence, responsibilities, and decision logic behind that flow. Together, they cover both &#8220;what&#8221; the customer feels and &#8220;how&#8221; it\u2019s delivered.<\/p>\n<h3>Can BPMN be used for complex, multi-channel journeys?<\/h3>\n<p>Absolutely. Use pools for each channel (web, mobile, call center), and message flows to show handoffs. Keep the customer visible as a lane or use annotations to track their journey across channels.<\/p>\n<h3>Is BPMN too technical for CX teams?<\/h3>\n<p>Not if you keep it simple. Focus on core elements: events, activities, gateways, lanes. Use color coding and clear labels. The goal isn\u2019t to make everyone a BPMN expert\u2014it\u2019s to create a shared visual language.<\/p>\n<h3>How do I start modeling a journey with BPMN?<\/h3>\n<p>Begin with a journey map. Extract key steps, triggers, and decision points. Use a BPMN tool to build the model: start with the customer\u2019s path, assign roles to lanes, and add exceptions. Validate with stakeholders.<\/p>\n<h3>Do I need a BPMN expert to create these models?<\/h3>\n<p>No. Start with a facilitator who understands both CX and basic BPMN. Use templates, keep the model focused, and validate with cross-functional teams. Expertise grows through practice.<\/p>\n<h3>How does BPMN support automation in customer journeys?<\/h3>\n<p>BPMN models define clear steps, inputs, outputs, and decision rules\u2014exactly what automation tools need. Activities with consistent inputs and outputs are ideal candidates for workflow automation, chatbots, or RPA.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u201cStart with a journey map and then build the process.\u201d  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1181,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1182","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Why Model Customer Journeys with BPMN<\/title>\n<meta name=\"description\" content=\"Discover why customer journey maps alone aren&#039;t enough. Learn how BPMN adds precision, clarity, and traceability to improve CX and operational alignment.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why Model Customer Journeys with BPMN\" \/>\n<meta property=\"og:description\" content=\"Discover why customer journey maps alone aren&#039;t enough. Learn how BPMN adds precision, clarity, and traceability to improve CX and operational alignment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/\",\"name\":\"Why Model Customer Journeys with BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:37:20+00:00\",\"description\":\"Discover why customer journey maps alone aren't enough. Learn how BPMN adds precision, clarity, and traceability to improve CX and operational alignment.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Connecting Customer Journeys and BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Why Model Customer Journeys with BPMN?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why Model Customer Journeys with BPMN","description":"Discover why customer journey maps alone aren't enough. Learn how BPMN adds precision, clarity, and traceability to improve CX and operational alignment.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/","og_locale":"zh_CN","og_type":"article","og_title":"Why Model Customer Journeys with BPMN","og_description":"Discover why customer journey maps alone aren't enough. Learn how BPMN adds precision, clarity, and traceability to improve CX and operational alignment.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"8 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/","name":"Why Model Customer Journeys with BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:37:20+00:00","description":"Discover why customer journey maps alone aren't enough. Learn how BPMN adds precision, clarity, and traceability to improve CX and operational alignment.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/why-model-customer-journeys-with-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Connecting Customer Journeys and BPMN","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/modeling-customer-journeys-with-bpmn\/connecting-customer-journeys-and-bpmn\/"},{"@type":"ListItem","position":4,"name":"Why Model Customer Journeys with BPMN?"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1182","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1182\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1181"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=1182"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=1182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}