{"id":602,"date":"2026-02-25T10:20:49","date_gmt":"2026-02-25T10:20:49","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/"},"modified":"2026-02-25T10:20:49","modified_gmt":"2026-02-25T10:20:49","slug":"customer-journey-gaps-in-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/","title":{"rendered":"Ignoring Customer Journeys in Collaboration Models"},"content":{"rendered":"<p>One of the most persistent sources of misalignment between process models and actual business outcomes is the silent omission of customer touchpoints in collaboration diagrams. I\u2019ve seen teams spend weeks refining back-office workflows\u2014only to realize the process they\u2019ve mapped doesn\u2019t reflect how customers experience the service. The real cost isn\u2019t just in miscommunication; it\u2019s in designing performance metrics that don\u2019t matter to the user.<\/p>\n<p>Here\u2019s the shift that eliminates most of this waste: treat every collaboration model as a journey, not a function. When you model the process from the customer\u2019s perspective\u2014their entry, actions, expectations, and exit\u2014you automatically expose gaps in service logic, handoff delays, and unmet needs.<\/p>\n<p>This chapter guides you through identifying customer journey gaps in BPMN, then correcting them with clear, actionable steps. You\u2019ll learn how to add customer lanes, define meaningful touchpoints, and align internal steps with customer-facing interactions\u2014so your process models reflect both operational reality and customer experience.<\/p>\n<h2>Why Customer Journeys Matter in BPMN Collaboration Models<\/h2>\n<p>Too many BPMN collaboration diagrams start with a back-office process and stop there. They show internal tasks\u2014\u201cvalidate claim,\u201d \u201cassign to agent\u201d\u2014but never show the customer placing the claim, receiving confirmation, or waiting for resolution.<\/p>\n<p>That\u2019s not a process model. That\u2019s a system log, stripped of context.<\/p>\n<p>Customer journey gaps in BPMN lead to models that are technically correct but irrelevant to business outcomes. If your process performance is measured in \u201cminutes to resolve,\u201d but customers are waiting days for updates, you\u2019re measuring the wrong thing.<\/p>\n<p>When you map the full customer journey, you uncover real bottlenecks: long wait times between steps, unclear communication, or lack of feedback loops. These aren\u2019t just inefficiencies\u2014they\u2019re experience problems.<\/p>\n<h3>Modeling Customer in BPMN: The First Step<\/h3>\n<p>Start by asking: who owns the customer\u2019s experience? Not IT, not operations. It\u2019s the process itself\u2014when modeled correctly.<\/p>\n<p>Always begin collaboration diagrams with a customer pool. Even if the customer doesn\u2019t perform any active tasks, their journey must be visible. Use a dedicated lane labeled \u201cCustomer\u201d or \u201cEnd Customer\u201d to reflect their presence.<\/p>\n<p>When you see a process that starts with \u201cAgent receives request,\u201d but never shows the customer sending it, you\u2019ve found a classic customer journey gap in BPMN.<\/p>\n<p>Adding a customer lane forces you to ask: what did the customer do before this step? Did they submit a form? Call a number? Log in? The answer shapes not just the flow, but the entire service model.<\/p>\n<h2>Adding Customer Touchpoints to BPMN: A Step-by-Step Approach<\/h2>\n<p>Customer touchpoints are not just activities\u2014they\u2019re moments of interaction, perception, and expectation. They\u2019re where the process meets the user.<\/p>\n<p>Here\u2019s how to embed them meaningfully into BPMN collaboration models.<\/p>\n<h3>Step 1: Define the Customer Journey Sequence<\/h3>\n<p>Before touching a tool, sketch the customer\u2019s journey on paper:<br \/>\n    &#8212; What did they do before the process started?<br \/>\n    &#8212; What do they expect at each stage?<br \/>\n    &#8212; How do they receive updates?<\/p>\n<p>Use this to identify critical touchpoints: submission, confirmation, feedback, resolution, complaint, follow-up.<\/p>\n<h3>Step 2: Add a Customer Pool or Lane<\/h3>\n<p>In your BPMN tool, add a new pool labeled \u201cCustomer\u201d or \u201cEnd User.\u201d If the customer interacts with multiple departments, use lanes within that pool.<\/p>\n<p>For example:<br \/>\n    &#8212; Lane 1: \u201cCustomer\u201d (initiates request)<br \/>\n    &#8212; Lane 2: \u201cCustomer\u201d (receives confirmation)<br \/>\n    &#8212; Lane 3: \u201cCustomer\u201d (provides feedback)<\/p>\n<p>This visual separation makes responsibility and timing much clearer.<\/p>\n<h3>Step 3: Map Touchpoints with Message Flows<\/h3>\n<p>Use message flows to connect customer actions to internal processes:<\/p>\n<ul>\n<li>\u201cCustomer sends form\u201d \u2192 \u201cSystem receives application\u201d<\/li>\n<li>\u201cCustomer receives email\u201d \u2192 \u201cCustomer reviews status\u201d<\/li>\n<li>\u201cCustomer replies with documents\u201d \u2192 \u201cAgent reviews submission\u201d<\/li>\n<\/ul>\n<p>Message flows clearly show who initiates what, and when.<\/p>\n<h3>Step 4: Use Send and Receive Tasks to Model Interaction<\/h3>\n<p>Instead of generic \u201cTask\u201d nodes, use:<\/p>\n<ul>\n<li><strong>Send Task<\/strong>: \u201cSend confirmation email to customer\u201d<\/li>\n<li><strong>Receive Task<\/strong>: \u201cWait for customer confirmation\u201d<\/li>\n<li><strong>User Task<\/strong>: \u201cCustomer completes form\u201d<\/li>\n<\/ul>\n<p>These tasks are not just about what the system does\u2014they signal a moment of interaction.<\/p>\n<h3>Step 5: Align Internal Timing with Customer Experience<\/h3>\n<p>Now, ask: how long does it take the system to respond after the customer acts? If the customer submits a form, does the system send a confirmation in 5 seconds or 3 days?<\/p>\n<p>Model this delay explicitly. Use a delay event or a message flow with a timestamp to show real-world latency.<\/p>\n<p>This turns a technical workflow into a live experience model.<\/p>\n<h2>Common Mistakes in Adding Customer Touchpoints<\/h2>\n<p>Even with good intentions, teams often fall into traps that undermine the purpose of including customers in BPMN.<\/p>\n<h3>Mistake 1: Treating the Customer as a Passive Observer<\/h3>\n<p>Some modelers add the customer lane but make it contain only \u201cWait\u201d or \u201cReceive\u201d steps. That\u2019s not a journey\u2014it\u2019s a placeholder.<\/p>\n<p>Instead, model what the customer <em>does<\/em>: submits data, reviews a document, confirms an action, gives feedback. Every action should be a visible task.<\/p>\n<h3>Mistake 2: Overlooking Asynchronous Touchpoints<\/h3>\n<p>Not all customer interactions happen in real time. Emails, SMS, or portal updates may take hours or days. But these delays are part of the journey.<\/p>\n<p>Use a \u201cWait for Customer Response\u201d task, with a timer or message event. This makes the delay visible and quantifiable.<\/p>\n<h3>Mistake 3: Modeling the Customer\u2019s Journey as a Sub-Process<\/h3>\n<p>Some teams create a \u201cCustomer Experience\u201d sub-process and hide it inside the main process. That\u2019s a red flag.<\/p>\n<p>Customer journey steps should be in the same model, not buried. If a sub-process is needed, use it only to group internal actions\u2014never to hide the customer.<\/p>\n<h3>Mistake 4: Ignoring Emotional or Behavioral Triggers<\/h3>\n<p>Customers don\u2019t just act\u2014they react. A rejected application may trigger frustration, which leads to a complaint.<\/p>\n<p>Add event sub-processes to model these reactions:<\/p>\n<ul>\n<li>\u201cCustomer complains\u201d \u2192 Trigger a complaint process<\/li>\n<li>\u201cCustomer abandons form\u201d \u2192 Trigger a recovery email<\/li>\n<li>\u201cCustomer rates service\u201d \u2192 Trigger feedback processing<\/li>\n<\/ul>\n<p>These aren\u2019t just error paths\u2014they\u2019re part of the experience.<\/p>\n<h2>When to Use Black-Box vs White-Box Customer Pools<\/h2>\n<p>Not every customer interaction needs full detail.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Purpose<\/th>\n<th>Use Black-Box Pool<\/th>\n<th>Use White-Box Pool<\/th>\n<\/tr>\n<tr>\n<td>High-level overview<\/td>\n<td>\u2713<\/td>\n<td>\u2717<\/td>\n<\/tr>\n<tr>\n<td>Internal team alignment<\/td>\n<td>\u2713<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<tr>\n<td>Customer experience design<\/td>\n<td>\u2717<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<tr>\n<td>Compliance or audit<\/td>\n<td>\u2713<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use a black-box pool when the customer\u2019s internal steps are unknown or irrelevant\u2014e.g., in a high-level process view.<\/p>\n<p>Use a white-box pool when you\u2019re modeling the full journey, especially for UX design, support optimization, or automation.<\/p>\n<p>Never mix both in the same diagram unless you\u2019re clearly separating layers.<\/p>\n<h2>How BPMN Process and Customer Experience Are Connected<\/h2>\n<p>There\u2019s no such thing as a process without a customer. Even internal processes serve a user\u2014whether it\u2019s a manager, a department, or a system.<\/p>\n<p>But if that user is not represented in the model, you\u2019re not mapping a process\u2014you\u2019re mapping a technical workflow.<\/p>\n<p>When you model the customer journey in BPMN, you\u2019re not just documenting steps. You\u2019re connecting process performance to real user satisfaction. Every delay, every error, every unmet expectation becomes visible.<\/p>\n<p>That\u2019s why adding customer touchpoints to BPMN is not an extra step. It\u2019s the foundation of any meaningful process model.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I start modeling customer in BPMN when there\u2019s no direct interaction?<\/h3>\n<p>Even if the customer doesn\u2019t perform an action, they\u2019re still part of the journey. Model the \u201cWait for Customer\u201d or \u201cReceive Input\u201d step using a receive task. If they receive a communication (e.g., email), show it as a message flow from the customer pool.<\/p>\n<h3>Should I model customer feedback as a separate process or part of the main flow?<\/h3>\n<p>Model feedback as a loop or event subprocess. If feedback is rare, use a boundary event on the end task. If it\u2019s a major phase, treat it as a separate subprocess that branches from the main flow.<\/p>\n<h3>Can I use BPMN to model customer journey for digital services like apps or websites?<\/h3>\n<p>Absolutely. Use pools for \u201cUser\u201d and \u201cSystem.\u201d Model navigation steps as message flows. Use user tasks for actions like \u201center email,\u201d \u201cselect option,\u201d or \u201csubmit form.\u201d This makes UX and process alignment seamless.<\/p>\n<h3>What if the customer is external, like a partner or supplier?<\/h3>\n<p>Treat them as a separate pool, just like a customer. Use message flows to model their actions and responses. This preserves contractual boundaries and clarifies responsibilities.<\/p>\n<h3>How do I handle customer delays (e.g., a customer takes 3 days to reply)?<\/h3>\n<p>Use a \u201cWait for Customer Response\u201d task with a timer event. Define the expected response window. If no reply, trigger a follow-up or escalation.<\/p>\n<h3>Is it okay to simplify the customer journey in a high-level BPMN diagram?<\/h3>\n<p>Yes\u2014but only if you\u2019re intentional. Remove details in a way that doesn\u2019t hide responsibility or key touchpoints. Use a black-box pool and clearly label the interaction, e.g., \u201cCustomer provides input via portal.\u201d<\/p>\n<p>When you model the customer journey in BPMN, you\u2019re not just adding steps. You\u2019re restoring the human element to process design. Every model should answer: who is this for? What do they experience? How does this affect their trust, satisfaction, or decision to continue?<\/p>\n<p>Fixing customer journey gaps in BPMN isn\u2019t about adding more elements\u2014it\u2019s about re-anchoring your process models in reality. When you do, you create diagrams that don\u2019t just run\u2014 they resonate.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the most persistent sources of misalignment between process models and actual business outcomes is the silent omission of customer touchpoints in collaboration diagrams. I\u2019ve seen teams spend weeks refining back-office workflows\u2014only to realize the process they\u2019ve mapped doesn\u2019t reflect how customers experience the service. The real cost isn\u2019t just in miscommunication; it\u2019s in [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":597,"menu_order":4,"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-602","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>Customer Journey Gaps in BPMN<\/title>\n<meta name=\"description\" content=\"Fix customer journey gaps in BPMN by modeling customer touchpoints and lanes to align process performance with real user experience. Learn to add customer-facing steps correctly.\" \/>\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\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Customer Journey Gaps in BPMN\" \/>\n<meta property=\"og:description\" content=\"Fix customer journey gaps in BPMN by modeling customer touchpoints and lanes to align process performance with real user experience. Learn to add customer-facing steps correctly.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/\",\"name\":\"Customer Journey Gaps in BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:20:49+00:00\",\"description\":\"Fix customer journey gaps in BPMN by modeling customer touchpoints and lanes to align process performance with real user experience. Learn to add customer-facing steps correctly.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Collaboration and Interaction Mistakes\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Ignoring Customer Journeys in Collaboration Models\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Customer Journey Gaps in BPMN","description":"Fix customer journey gaps in BPMN by modeling customer touchpoints and lanes to align process performance with real user experience. Learn to add customer-facing steps correctly.","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\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/","og_locale":"ru_RU","og_type":"article","og_title":"Customer Journey Gaps in BPMN","og_description":"Fix customer journey gaps in BPMN by modeling customer touchpoints and lanes to align process performance with real user experience. Learn to add customer-facing steps correctly.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"8 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/","name":"Customer Journey Gaps in BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:20:49+00:00","description":"Fix customer journey gaps in BPMN by modeling customer touchpoints and lanes to align process performance with real user experience. Learn to add customer-facing steps correctly.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/customer-journey-gaps-in-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Collaboration and Interaction Mistakes","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/"},{"@type":"ListItem","position":4,"name":"Ignoring Customer Journeys in Collaboration Models"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/602","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/602\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/597"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=602"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}