{"id":1196,"date":"2026-02-25T10:37:25","date_gmt":"2026-02-25T10:37:25","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/"},"modified":"2026-02-25T10:37:25","modified_gmt":"2026-02-25T10:37:25","slug":"modeling-customer-journey-exceptions-in-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/","title":{"rendered":"Modeling Exceptions: Abandonment, Complaints, and Recovery"},"content":{"rendered":"<p>Most process models focus on the ideal path\u2014what happens when everything goes right. But real customer journeys rarely follow a smooth, linear flow. Abandonment, complaints, and service failures are not anomalies; they\u2019re integral parts of experience design. Modeling customer journey exceptions in BPMN isn&#8217;t about adding complexity\u2014it&#8217;s about showing where the system must respond with empathy, speed, and clarity.<\/p>\n<p>As someone who\u2019s spent two decades helping organizations connect experience strategy with operational reality, I\u2019ve seen too many teams embed exceptions as afterthoughts: hidden in footnotes, buried in decision trees, or lost in poorly structured diagrams. That\u2019s why I\u2019ve developed a consistent, visual approach to modeling exceptions, using BPMN\u2019s built-in mechanisms to keep the main flow clean while making failures visible, traceable, and actionable.<\/p>\n<p>This chapter walks you through how to represent abandonment, complaint escalation, and recovery processes\u2014not as distractions, but as first-class components of a customer-centric model. You\u2019ll learn to use boundary events, event subprocesses, and alternative paths to capture exceptions without sacrificing readability.<\/p>\n<h2>Why Exceptions Matter in Customer-Centric BPMN<\/h2>\n<p>Customers don\u2019t just abandon a journey because of a software bug\u2014they abandon when they feel ignored, misunderstood, or frustrated by delays. A model that ignores these moments is incomplete, no matter how elegant the happy path.<\/p>\n<p>Think of every exception as a moment of truth. When a customer abandons a purchase, it\u2019s not failure\u2014it\u2019s feedback. When a complaint escalates, it\u2019s not a breakdown\u2014it\u2019s a chance to rebuild trust. Modeling these moments correctly means your BPMN model becomes not just a process map, but a living reflection of your brand\u2019s promise.<\/p>\n<p>Abandoned journey modeling isn\u2019t about managing failure\u2014it\u2019s about designing resilience. The goal isn\u2019t to prevent every issue, but to ensure that when it happens, the organization responds in a way that aligns with your customer experience strategy.<\/p>\n<h2>Mapping Abandonment with Boundary Events<\/h2>\n<p>Cart abandonment is one of the most common and impactful forms of journey failure. In BPMN, the best way to represent it is with a <strong>boundary event<\/strong> on a key activity\u2014like checkout or payment confirmation.<\/p>\n<p>Here\u2019s how it works:<\/p>\n<ul>\n<li>Place a boundary event on the <em>Payment Processing<\/em> task.<\/li>\n<li>Set the trigger to a <em>Timer Intermediate Event<\/em> with a duration (e.g., 10 minutes).<\/li>\n<li>Link the event path to a new subprocess: <em>Abandoned Journey Recovery<\/em>.<\/li>\n<\/ul>\n<p>This approach keeps the main flow uncluttered. The customer\u2019s decision to walk away is only captured when the timer fires, preserving the integrity of the happy path.<\/p>\n<h3>Best Practices for Abandoned Journey Modeling<\/h3>\n<ul>\n<li><strong>Use timers, not message events<\/strong>: Abandonment is time-based, not triggered by external input.<\/li>\n<li><strong>Keep the trigger realistic<\/strong>: 5\u201315 minutes is typical for shopping carts. Adjust based on customer behavior data.<\/li>\n<li><strong>Don\u2019t model every abandonment<\/strong>: Focus on high-value or high-failure scenarios to avoid clutter.<\/li>\n<li><strong>Link to follow-up actions<\/strong>: Recovery may include email alerts, discounts, or re-engagement campaigns.<\/li>\n<\/ul>\n<h2>Handling Complaints with Event Subprocesses<\/h2>\n<p>Complaints aren\u2019t just errors\u2014they are signals that a process has failed to meet customer expectations. In BPMN, the most effective way to model complaint handling in BPMN is with an <strong>event subprocess<\/strong> attached to the main flow.<\/p>\n<p>This allows the system to detect a complaint (e.g., via a feedback form, support ticket, or negative sentiment flag) and respond immediately, even if the main process is still running.<\/p>\n<p>Create a dedicated event subprocess like this:<\/p>\n<ol>\n<li>Attach a <em>Message Start Event<\/em> to an <em>Event Subprocess<\/em> on the process boundary.<\/li>\n<li>Use a <em>Conditional Event<\/em> to check for keywords like &#8222;frustrated,&#8220; &#8222;disappointed,&#8220; or &#8222;not working.&#8220;<\/li>\n<li>Route to a <em>Complaint Escalation<\/em> path, which may include a human agent, apology message, or compensation.<\/li>\n<\/ol>\n<p>This structure ensures that complaints are addressed without blocking the main workflow\u2014something essential in real-time systems.<\/p>\n<h3>Key Design Principles for Complaint Handling in BPMN<\/h3>\n<ul>\n<li><strong>Use event subprocesses, not gateways<\/strong>: They allow asynchronous handling without derailing the main process.<\/li>\n<li><strong>Filter complaints by severity<\/strong>: A minor complaint may trigger a notification; a major one should escalate to a manager.<\/li>\n<li><strong>Link to CRM or support tools<\/strong>: Use message flows to pass complaint data to external systems.<\/li>\n<li><strong>Include time-to-response metrics<\/strong>: Track how quickly complaints are acknowledged and resolved.<\/li>\n<\/ul>\n<h2>Designing Service Recovery Processes BPMN<\/h2>\n<p>Service recovery is where the experience truly turns around. Whether it\u2019s a billing error, delivery delay, or failed system update, the recovery path must be faster, fairer, and more empathetic than the original failure.<\/p>\n<p>In BPMN, use a <strong>subprocess<\/strong> for service recovery, triggered by a <em>Boundary Event<\/em> or a <em>Message Event<\/em> from a monitoring system.<\/p>\n<p>Example scenario: A customer receives a delivery that\u2019s late. The recovery process should include:<\/p>\n<ul>\n<li>A <em>Notification<\/em> to the customer.<\/li>\n<li>An <em>Automatic Compensation<\/em> (e.g., refund of delivery fee).<\/li>\n<li>A <em>Human Review<\/em> of the root cause (if needed).<\/li>\n<li>A <em>Follow-Up Email<\/em> with an apology and discount.<\/li>\n<\/ul>\n<p>These steps should be isolated in a subprocess so that the main flow remains focused on the original task\u2014delivery.<\/p>\n<h3>Service Recovery Processes BPMN: Checklist<\/h3>\n<ul>\n<li>\u2714\ufe0f Define clear triggers (e.g., delivery delay &gt; 48 hours).<\/li>\n<li>\u2714\ufe0f Use a subprocess to keep recovery separate from main process.<\/li>\n<li> \u2714\ufe0f Include both automated and human steps.<\/li>\n<li> \u2714\ufe0f Measure response and resolution times.<\/li>\n<li> \u2714\ufe0f Ensure the customer feels heard and compensated.<\/li>\n<\/ul>\n<h2>Choosing the Right Exception Pattern: A Comparison<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Scenario<\/th>\n<th>Best BPMN Pattern<\/th>\n<th>Why<\/th>\n<\/tr>\n<tr>\n<td>Cart abandonment<\/td>\n<td>Boundary event with timer<\/td>\n<td>Time-based, no external trigger; keeps main flow clean.<\/td>\n<\/tr>\n<tr>\n<td>Complaint received via form<\/td>\n<td>Event subprocess with message start<\/td>\n<td>Asynchronous handling; doesn\u2019t block main process.<\/td>\n<\/tr>\n<tr>\n<td>Delivery delay detected<\/td>\n<td>Boundary event with conditional trigger<\/td>\n<td>Real-time monitoring; immediate response.<\/td>\n<\/tr>\n<tr>\n<td>System error during payment<\/td>\n<td>Event subprocess with error signal<\/td>\n<td>Handles exceptions without breaking the flow.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Common Mistakes to Avoid<\/h2>\n<ul>\n<li><strong>Don\u2019t use gateways to model exceptions<\/strong>: They imply a choice, but exceptions are not decisions\u2014they are events.<\/li>\n<li><strong>Avoid overusing exceptions<\/strong>: Too many boundary events make the diagram hard to read. Prioritize high-impact, high-frequency failures.<\/li>\n<li><strong>Never hide the recovery path<\/strong>: If the customer can\u2019t see the response, the model fails the human-centered test.<\/li>\n<li><strong>Don\u2019t model exceptions in isolation<\/strong>: They must connect back to the main journey to show continuity and accountability.<\/li>\n<\/ul>\n<h2>Real-World Example: E-Commerce Checkout Abandonment<\/h2>\n<p>Consider a customer who adds a product to their cart, enters shipping details, but leaves before payment. The BPMN model should:<\/p>\n<ul>\n<li>Have a <em>Boundary Event<\/em> on <em>Payment Processing<\/em> with a 10-minute timer.<\/li>\n<li>Trigger a subprocess: <em>Abandonment Response<\/em>.<\/li>\n<li>Include steps: Send email with cart reminder, offer 10% off, log abandonment reason.<\/li>\n<li>Link to a <em>Customer Feedback<\/em> task if the customer returns.<\/li>\n<\/ul>\n<p>This model is clear, actionable, and supports marketing, support, and product teams in understanding and improving the journey.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I decide when to use a boundary event vs an event subprocess?<\/h3>\n<p>Use a boundary event when the exception is attached to a single task and time-based (e.g., cart abandonment). Use an event subprocess when the exception can occur at any point in the process and relies on external triggers like messages or signals (e.g., complaint, error).<\/p>\n<h3>Can I model multiple exception types in one diagram?<\/h3>\n<p>Yes\u2014but keep them organized. Use distinct subprocesses or lanes to separate complaint handling, recovery, and abandonment paths. Avoid mixing them in a single flow.<\/p>\n<h3>How do I avoid making the BPMN model too complex when showing exceptions?<\/h3>\n<p>Apply the 80\/20 rule: focus on the top 20% of exceptions that cause 80% of customer frustration. Use annotations or a legend to explain patterns. If needed, create a separate exception model for deep analysis.<\/p>\n<h3>Should I model the customer\u2019s emotional state in the exception flow?<\/h3>\n<p>Not in the diagram itself, but you can annotate the process with emotions (e.g., \u201cfrustrated,\u201d \u201cconfused\u201d) or link to journey maps. The model should reflect actions, not feelings.<\/p>\n<h3>What if the exception doesn\u2019t trigger immediately?<\/h3>\n<p>Use a <em>Timer Intermediate Event<\/em> with a delay or a <em>Conditional Event<\/em> based on data (e.g., \u201cif resolution time &gt; 24 hours\u201d). Link to a monitoring subprocess if needed.<\/p>\n<h3>How do I ensure stakeholders understand the exception paths?<\/h3>\n<p>Use consistent colors, labels, and icons. Include a legend. Run walkthroughs with CX, operations, and IT teams. The goal is not just clarity\u2014it\u2019s shared understanding.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most process models focus on the ideal path\u2014what happens when everything goes right. But real customer journeys rarely follow a smooth, linear flow. Abandonment, complaints, and service failures are not anomalies; they\u2019re integral parts of experience design. Modeling customer journey exceptions in BPMN isn&#8217;t about adding complexity\u2014it&#8217;s about showing where the system must respond with [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1191,"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-1196","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>Modeling Customer Journey Exceptions in BPMN<\/title>\n<meta name=\"description\" content=\"Learn how to accurately model cart abandonment, complaint escalation, and service recovery in BPMN using boundary events, event subprocesses, and exception paths to improve customer experience without cluttering the main flow.\" \/>\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\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Modeling Customer Journey Exceptions in BPMN\" \/>\n<meta property=\"og:description\" content=\"Learn how to accurately model cart abandonment, complaint escalation, and service recovery in BPMN using boundary events, event subprocesses, and exception paths to improve customer experience without cluttering the main flow.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/\",\"name\":\"Modeling Customer Journey Exceptions in BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:37:25+00:00\",\"description\":\"Learn how to accurately model cart abandonment, complaint escalation, and service recovery in BPMN using boundary events, event subprocesses, and exception paths to improve customer experience without cluttering the main flow.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Designing Customer-Centric BPMN Models\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Modeling Exceptions: Abandonment, Complaints, and Recovery\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Modeling Customer Journey Exceptions in BPMN","description":"Learn how to accurately model cart abandonment, complaint escalation, and service recovery in BPMN using boundary events, event subprocesses, and exception paths to improve customer experience without cluttering the main flow.","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\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/","og_locale":"de_DE","og_type":"article","og_title":"Modeling Customer Journey Exceptions in BPMN","og_description":"Learn how to accurately model cart abandonment, complaint escalation, and service recovery in BPMN using boundary events, event subprocesses, and exception paths to improve customer experience without cluttering the main flow.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/","name":"Modeling Customer Journey Exceptions in BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:37:25+00:00","description":"Learn how to accurately model cart abandonment, complaint escalation, and service recovery in BPMN using boundary events, event subprocesses, and exception paths to improve customer experience without cluttering the main flow.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/modeling-customer-journey-exceptions-in-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Designing Customer-Centric BPMN Models","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/"},{"@type":"ListItem","position":4,"name":"Modeling Exceptions: Abandonment, Complaints, and Recovery"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1196\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1191"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1196"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}