{"id":1206,"date":"2026-02-25T10:37:30","date_gmt":"2026-02-25T10:37:30","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/"},"modified":"2026-02-25T10:37:30","modified_gmt":"2026-02-25T10:37:30","slug":"attaching-cx-insights-to-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/","title":{"rendered":"Attaching Journey Insights: Pain Points, KPIs, and Voice of Customer"},"content":{"rendered":"<p>Too many BPMN diagrams start life as clean, elegant flows\u2014only to become cluttered with overlapping notes and annotations that obscure rather than clarify. I&#8217;ve seen teams add every pain point, every KPI, and every quote from customer interviews directly into the diagram itself, only to lose sight of the journey\u2019s core logic.<\/p>\n<p>But here\u2019s what most miss: the power of BPMN lies not in how many insights you cram into a single diagram, but in how clearly you connect those insights to the actual process steps. The goal isn\u2019t to make the diagram \u201cfull\u201d\u2014it\u2019s to make it actionable.<\/p>\n<p>Attaching CX insights to BPMN isn\u2019t about decoration. It\u2019s about creating a bridge between experience and execution\u2014where a moment of frustration, a delay in response, or a customer quote becomes a visible trigger for real change.<\/p>\n<p>Over the next few sections, I\u2019ll show you how to do this with precision: using annotations, linked documentation, and layered views that keep the process clean while preserving rich contextual intelligence. You\u2019ll learn when to annotate, when to reference external data, and how to make insights visible at a glance\u2014without sacrificing clarity.<\/p>\n<h2>Why Attach CX Insights to BPMN?<\/h2>\n<p>Every journey step is not just a process event\u2014it\u2019s an experience. A customer\u2019s frustration during a long wait isn\u2019t just a feeling. It\u2019s a signal that a process step is taking too long, a handoff is delayed, or a system is unresponsive.<\/p>\n<p>When you attach insights like pain points on process models directly to BPMN elements, you shift from abstract mapping to actionable intelligence. You transform a diagram from a static artifact into a living feedback loop.<\/p>\n<p>Consider this: a queue waiting to be processed may show a 24-hour SLA, but a customer quote says, \u201cI didn\u2019t expect to wait that long.\u201d That insight, when linked to the activity, becomes a direct call to action for process optimization.<\/p>\n<p>That\u2019s the power of attaching CX insights to BPMN: not just visibility, but purpose.<\/p>\n<h3>Three Core Principles for Effective Insight Attachment<\/h3>\n<p>Not all attachments are created equal. The best ones follow three simple principles:<\/p>\n<ul>\n<li><strong>Relevance over volume:<\/strong> Only attach insights that directly relate to a specific process step or decision.<\/li>\n<li><strong>Clarity over clutter:<\/strong> Use annotations, icons, or color-coding to make insights visible without overwhelming the diagram.<\/li>\n<li><strong>Traceability over tangents:<\/strong> Ensure every insight can be traced back to a real source\u2014whether a survey, interview, or analytics report.<\/li>\n<\/ul>\n<p>When applied, these principles turn BPMN into a decision-making tool, not just a documentation exercise.<\/p>\n<h2>Practical Methods to Attach CX Insights<\/h2>\n<p>There\u2019s no one-size-fits-all method. The best approach depends on your audience, your tooling, and the maturity of your process modeling culture.<\/p>\n<h3>1. Annotations: The Lightweight Approach<\/h3>\n<p>Most BPMN tools support annotations\u2014text boxes that can be attached to any activity, gateway, or event. Use them to highlight:<\/p>\n<ul>\n<li>Customer frustration during a wait<\/li>\n<li>Confusion about next steps<\/li>\n<li>Discrepancies between promised and actual service times<\/li>\n<\/ul>\n<p>Example: An annotation on a \u201cWait for approval\u201d activity could read: \u201cVoice of customer: \u2018I thought the system would auto-approve\u2014why did I have to wait 3 days?\u2019\u201d<\/p>\n<p>This isn\u2019t just feedback\u2014it\u2019s a direct challenge to the process. And because it\u2019s visibly tied to the step, it becomes impossible to ignore.<\/p>\n<h3>2. External Documentation with Hyperlinks<\/h3>\n<p>When a single insight spans multiple steps or involves complex context, hyperlinking to a separate document is cleaner than cluttering the diagram.<\/p>\n<p>Create a central CX insights repository with:<\/p>\n<ul>\n<li>A named section for each process step<\/li>\n<li>Short summaries of pain points on process models<\/li>\n<li>Direct links to recordings, transcripts, or survey data<\/li>\n<\/ul>\n<p>For example, a \u201cPayment Processing\u201d step might have a hyperlink to: \u201c<a href=\"#\">See customer complaints about delayed refunds (Q3 CX Report)<\/a>\u201d<\/p>\n<p>This keeps the BPMN diagram clean while still making insights accessible to stakeholders.<\/p>\n<h3>3. Visual Overlays: Highlighting Impact<\/h3>\n<p>For cross-functional teams, consider using overlays\u2014semi-transparent layers that can be toggled on\/off in digital tools.<\/p>\n<p>One overlay could show:<\/p>\n<ul>\n<li>Red icons on steps where KPIs linked to BPMN steps are being missed<\/li>\n<li>Yellow icons where voice of customer in BPMN diagrams indicates confusion or delay<\/li>\n<li>Green icons where customer satisfaction is high<\/li>\n<\/ul>\n<p>These aren\u2019t part of the process logic\u2014they\u2019re decision aids. They allow teams to quickly identify high-impact areas without altering the original flow.<\/p>\n<h3>4. KPIs and SLAs: Anchoring Performance to Process Steps<\/h3>\n<p>Performance metrics should not be listed in a table. They should live directly on the BPMN step they measure.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>Activity:<\/strong> \u201cProcess refund request\u201d<\/li>\n<li><strong>KPIs linked to BPMN steps:<\/strong> Average resolution time: 48 hrs (target: 24 hrs)<\/li>\n<li><strong>Customer feedback:<\/strong> \u201cIt took 72 hours\u2014I was told it would be fast.\u201d<\/li>\n<\/ul>\n<p>When KPIs linked to BPMN steps are displayed this way, they become part of the process design\u2014not an afterthought.<\/p>\n<h3>5. Pain Points on Process Models: The Silent Red Flags<\/h3>\n<p>Pain points on process models are not just complaints\u2014they are diagnostic indicators.<\/p>\n<p>When you see a pain point like \u201cI can\u2019t track my order,\u201d and it\u2019s linked to a \u201cCheck order status\u201d step, the answer isn\u2019t to add more features. It\u2019s to ask: Is there a missing message flow? Is the data not visible in real time? Is the user being sent to a system without status visibility?<\/p>\n<p>That\u2019s where the real insight lives: in the gap between customer expectation and process reality.<\/p>\n<h3>6. The Power of Voice of Customer in BPMN Diagrams<\/h3>\n<p>Direct quotes from customers are gold. But they should never be dropped into a diagram verbatim.<\/p>\n<p>Instead, use them as context:<\/p>\n<ul>\n<li>\u201cI don\u2019t know what happens next.\u201d \u2192 Add to a \u201cWait for response\u201d step.<\/li>\n<li>\u201cWhy did I get charged for something I canceled?\u201d \u2192 Link to \u201cPayment confirmation\u201d activity.<\/li>\n<li>\u201cThe system didn\u2019t tell me I needed to upload documents.\u201d \u2192 Associate with \u201cDocument upload\u201d step.<\/li>\n<\/ul>\n<p>These aren\u2019t just annotations. They\u2019re empathy triggers.<\/p>\n<p>When a stakeholder sees a quote like \u201cI felt ignored\u201d next to a step where no confirmation is sent, they don\u2019t just see a gap\u2014they feel it.<\/p>\n<h2>When to Use What: A Decision Guide<\/h2>\n<p>Not every insight needs the same treatment. Use this simple decision matrix to choose the right attachment method:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Insight Type<\/th>\n<th>Best Attachment Method<\/th>\n<th>Why?<\/th>\n<\/tr>\n<tr>\n<td>Short, direct quotes<\/td>\n<td>Annotations<\/td>\n<td>Immediate impact; visible in context.<\/td>\n<\/tr>\n<tr>\n<td>Complex feedback (e.g., survey data)<\/td>\n<td>Hyperlinked documentation<\/td>\n<td>Keeps flow clean; preserves data integrity.<\/td>\n<\/tr>\n<tr>\n<td>Performance trends (e.g., missed SLAs)<\/td>\n<td>KPIs on process step<\/td>\n<td>Directly ties experience to performance.<\/td>\n<\/tr>\n<tr>\n<td>High-impact pain points<\/td>\n<td>Visual overlay icons<\/td>\n<td>Enables quick scanning across multiple diagrams.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Remember: The goal is not to document every emotion. It\u2019s to highlight what matters\u2014where the process fails the customer.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with the best intentions, teams fall into traps. Here\u2019s how to stay clear:<\/p>\n<ul>\n<li><strong>Over-annotating:<\/strong> Only annotate steps where the insight changes the outcome or triggers improvement.<\/li>\n<li><strong>Using generic labels:<\/strong> Instead of \u201cCustomer unhappy,\u201d say \u201cCustomer frustrated by lack of update after 48 hours.\u201d Be specific.<\/li>\n<li><strong>Forgetting to validate:<\/strong> Regularly review insights with customer-facing teams\u2014what seems like a pain point to a user might be a design choice in the process.<\/li>\n<li><strong>Isolating insights:<\/strong> Ensure every insight is traceable. A quote without a source becomes noise.<\/li>\n<\/ul>\n<p>Insights are only valuable when they\u2019re actionable. And the only way they become actionable is when they\u2019re properly anchored to the process.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I keep BPMN diagrams from becoming too cluttered when adding CX insights?<\/h3>\n<p>Use layered approaches: keep core process logic clean, and move insights into annotations, hyperlinks, or visual overlays. Limit annotations to one per step unless the insight is critical. Use icons to signal high-impact moments\u2014red for pain, green for satisfaction.<\/p>\n<h3>Should I include voice of customer in BPMN diagrams directly?<\/h3>\n<p>Yes\u2014but not verbatim. Use concise, representative quotes that capture the essence of the feedback. Always tie them to a specific step. Avoid long quotes that break the flow.<\/p>\n<h3>How do I link KPIs to BPMN steps without cluttering the model?<\/h3>\n<p>Display the KPI directly on the step: \u201cResolution Time: 48 hrs (goal: 24).\u201d Use color coding (e.g., red if missed). If more detail is needed, link to a dashboard or report.<\/p>\n<h3>Can I use BPMN to model both the journey and the underlying process logic?<\/h3>\n<p>Absolutely. Use a single BPMN model to show both the customer\u2019s path and the internal process. Annotate key handoffs and decision points with CX feedback. This creates a single source of truth for both customer experience and operational design.<\/p>\n<h3>What if different teams disagree on how to interpret a pain point?<\/h3>\n<p>Use the BPMN model as a collaboration canvas. Host workshops where CX, operations, and IT teams walk through the model together, using real quotes and KPIs as discussion points. Disagreement often reveals missing steps or unmet expectations.<\/p>\n<h3>How often should I review and update CX insights in BPMN models?<\/h3>\n<p>At minimum, during each major review cycle\u2014every 3\u20136 months. But also update when new customer feedback emerges or when a process change is made. Treat the model as a living document, not a one-time deliverable.<\/p>\n<p>Attaching CX insights to BPMN isn\u2019t about adding more information. It\u2019s about making the right information visible at the right time. When done well, it turns a process diagram into a compass for improvement\u2014guiding teams not just to fix what\u2019s broken, but to build what customers truly value.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many BPMN diagrams start life as clean, elegant flows\u2014only to become cluttered with overlapping notes and annotations that obscure rather than clarify. I&#8217;ve seen teams add every pain point, every KPI, and every quote from customer interviews directly into the diagram itself, only to lose sight of the journey\u2019s core logic. But here\u2019s what [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1203,"menu_order":2,"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-1206","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>Attaching CX Insights to BPMN<\/title>\n<meta name=\"description\" content=\"Learn how to attach journey insights\u2014pain points, KPIs, and voice of customer\u2014directly to BPMN models without clutter. Practical strategies for meaningful, action-oriented CX improvement.\" \/>\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\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Attaching CX Insights to BPMN\" \/>\n<meta property=\"og:description\" content=\"Learn how to attach journey insights\u2014pain points, KPIs, and voice of customer\u2014directly to BPMN models without clutter. Practical strategies for meaningful, action-oriented CX improvement.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-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\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/\",\"name\":\"Attaching CX Insights to BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:37:30+00:00\",\"description\":\"Learn how to attach journey insights\u2014pain points, KPIs, and voice of customer\u2014directly to BPMN models without clutter. Practical strategies for meaningful, action-oriented CX improvement.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Linking Journey Maps and BPMN in Practice\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Attaching Journey Insights: Pain Points, KPIs, and Voice of Customer\"}]},{\"@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":"Attaching CX Insights to BPMN","description":"Learn how to attach journey insights\u2014pain points, KPIs, and voice of customer\u2014directly to BPMN models without clutter. Practical strategies for meaningful, action-oriented CX improvement.","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\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/","og_locale":"ru_RU","og_type":"article","og_title":"Attaching CX Insights to BPMN","og_description":"Learn how to attach journey insights\u2014pain points, KPIs, and voice of customer\u2014directly to BPMN models without clutter. Practical strategies for meaningful, action-oriented CX improvement.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-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\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/","name":"Attaching CX Insights to BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:37:30+00:00","description":"Learn how to attach journey insights\u2014pain points, KPIs, and voice of customer\u2014directly to BPMN models without clutter. Practical strategies for meaningful, action-oriented CX improvement.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/attaching-cx-insights-to-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Linking Journey Maps and BPMN in Practice","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/linking-journey-maps-and-bpmn\/"},{"@type":"ListItem","position":4,"name":"Attaching Journey Insights: Pain Points, KPIs, and Voice of Customer"}]},{"@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\/1206","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\/1206\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1203"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=1206"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=1206"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}