{"id":1219,"date":"2026-02-25T10:37:35","date_gmt":"2026-02-25T10:37:35","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/"},"modified":"2026-02-25T10:37:35","modified_gmt":"2026-02-25T10:37:35","slug":"modeling-standards-for-customer-centric-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/","title":{"rendered":"Modeling Standards for Customer-Centric BPMN"},"content":{"rendered":"<p>Every time I walk into a workshop, I see the same pattern: a room full of smart people, each with their own way of drawing BPMN, even when modeling the same journey. The result? Diagrams that confuse rather than clarify. Too many different colors, inconsistent naming, or lanes that hide the customer behind a wall of internal processes.<\/p>\n<p>After two decades of guiding CX teams through complex modeling work, I\u2019ve come to believe that **modeling standards for customer-centric BPMN** aren\u2019t about rigid rules\u2014they\u2019re about shared language. When everyone agrees on what a blue box means or how to name a step, we stop debating what the diagram says and start focusing on what it can do.<\/p>\n<p>These standards are not for perfection. They\u2019re for consistency. For clarity. For trust. This chapter gives you a lightweight, practical style guide\u2014not a checklist, but a compass. It\u2019s built from real workshops, flawed diagrams, and the feedback I\u2019ve gathered across industries. You\u2019ll learn how to make BPMN work for CX, not against it.<\/p>\n<h2>Core Principles for Customer-Centric Standards<\/h2>\n<p>Before diving into specifics, let\u2019s clarify the ethos. Modeling standards aren\u2019t about control\u2014they\u2019re about clarity. They exist to reduce cognitive load, not add process overhead.<\/p>\n<p>Here are the foundational principles I\u2019ve seen work best:<\/p>\n<ul>\n<li><strong>Clarity over complexity.<\/strong> If a reader must squint to understand the flow, the model fails.<\/li>\n<li><strong>Customer visibility.<\/strong> The customer must be visible\u2014not just as a flow node, but as a first-class participant.<\/li>\n<li><strong>Consistency across journeys.<\/strong> A \u201cCheck Account Balance\u201d in one model should be structured the same way in another.<\/li>\n<li><strong>Scalable simplicity.<\/strong> A standard should grow with your team, not become a burden.<\/li>\n<\/ul>\n<p>These aren\u2019t optional. They\u2019re the foundation on which trust is built. When stakeholders can expect the same pattern across diagrams, they stop reading and start acting.<\/p>\n<h2>Guidelines for Consistent Modeling<\/h2>\n<h3>Naming Conventions: Clarity That Speaks to Everyone<\/h3>\n<p>Name your activities and events using plain, active verbs. Avoid jargon. Instead of \u201cCustomer Request Received,\u201d write \u201cSubmit account update request.\u201d<\/p>\n<p>For customer-facing actions, use the customer\u2019s perspective: \u201cSelect shipping method\u201d instead of \u201cProcess delivery option.\u201d<\/p>\n<p>Use consistent formatting:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Element<\/th>\n<th>Recommended Format<\/th>\n<th>Example<\/th>\n<\/tr>\n<tr>\n<td>Activity<\/td>\n<td>Present tense, active verb<\/td>\n<td>Verify identity<\/td>\n<\/tr>\n<tr>\n<td>Event<\/td>\n<td>Verb + \u201c-ed\u201d or \u201c-ing\u201d<\/td>\n<td>Payment confirmed<\/td>\n<\/tr>\n<tr>\n<td>Gateway<\/td>\n<td>Question ending in \u201c?\u201d<\/td>\n<td>Is payment successful?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t arbitrary. They help non-technical stakeholders instantly grasp the sequence. A product manager should understand your model without a glossary.<\/p>\n<h3>Color Use: Signal, Not Decoration<\/h3>\n<p>Color should signal meaning, not decorate. Too many teams use red for \u201cerror,\u201d blue for \u201ccustomer,\u201d and green for \u201cdone\u201d\u2014but they vary wildly between projects.<\/p>\n<p>Here\u2019s my recommended palette:<\/p>\n<ul>\n<li><strong>Blue<\/strong>: Customer actions or touchpoints \u2014 e.g., \u201cSubmit form,\u201d \u201cCall support.\u201d<\/li>\n<li><strong>Green<\/strong>: Internal processes \u2014 e.g., \u201cVerify payment,\u201d \u201cUpdate CRM.\u201d<\/li>\n<li><strong>Orange<\/strong>: Decisions or gateways \u2014 e.g., \u201cIs identity verified?\u201d<\/li>\n<li><strong>Red<\/strong>: Exceptions or failures \u2014 e.g., \u201cPayment declined,\u201d \u201cNo agent available.\u201d<\/li>\n<\/ul>\n<p>Apply these consistently across all models. When stakeholders see orange, they know: \u201cThis is where we decide.\u201d When they see red, they know: \u201cThis is where things go sideways.\u201d No guessing.<\/p>\n<h3>Lane Structure: Show the Customer as a First-Class Citizen<\/h3>\n<p>Never hide the customer behind a lane labeled \u201cTeam A\u201d or \u201cBack Office.\u201d The customer must be in the swimlane diagram\u2014either as a full pool or a prominent lane.<\/p>\n<p>Best practice: Use a <strong>Customer Pool<\/strong> at the top or left, with internal teams as lanes below. This immediately signals that the journey begins and ends with the customer.<\/p>\n<p>When you can\u2019t use a full pool (e.g., in a legacy system), make the customer\u2019s lane clearly distinct. Use a bold border, different background shade, or a label like \u201c(Customer Perspective).\u201d<\/p>\n<p>Remember: If your audience has to ask, \u201cWhere\u2019s the customer?\u201d\u2014your model has failed.<\/p>\n<h3>Annotations: Where Insight Meets Clarity<\/h3>\n<p>Annotations are not footnotes. They\u2019re the bridge between process logic and customer experience.<\/p>\n<p>Use them to answer three questions:<\/p>\n<ul>\n<li>Why does this step matter to the customer?<\/li>\n<li>What emotional state does this trigger?<\/li>\n<li>What happens if this takes longer than expected?<\/li>\n<\/ul>\n<p>Example:<\/p>\n<pre><code>Activity: Wait for response from support\nAnnotation: Customer feels anxious if no update in 24h. SLA = 2 business hours.<\/code><\/pre>\n<p>Keep annotations brief\u20141\u20132 sentences. Place them near the activity or gateway they explain. Avoid wall-of-text annotations.<\/p>\n<p>Annotate exceptions, not just the happy path. When a customer abandons a form, or gets stuck in a loop, document why. These are the moments that shape loyalty.<\/p>\n<h3>Handling Multi-Channel Journeys<\/h3>\n<p>Not all journeys happen in one place. A customer may start on mobile, switch to web, and finish a call with support.<\/p>\n<p>Create a <strong>Channel Lane<\/strong> within the pool or use a consistent icon system:<\/p>\n<ul>\n<li><strong>\ud83d\udcf1<\/strong> Mobile app<\/li>\n<li><strong>\ud83d\udcbb<\/strong> Web browser<\/li>\n<li><strong>\ud83d\udcde<\/strong> Phone call<\/li>\n<li><strong>\ud83d\udccd<\/strong> In-person visit<\/li>\n<\/ul>\n<p>Apply the icon to the activity or use a small label. This makes it easy to spot channel shifts and identify where friction might occur.<\/p>\n<p>For example:<\/p>\n<p><code>Submit form (\ud83d\udcf1)<\/code> \u2192 <code>Verify identity (\ud83d\udcbb)<\/code> \u2192 <code>Wait for approval (\ud83d\udcde)<\/code><\/p>\n<p>Now you can see the journey across touchpoints. Not every channel needs its own lane\u2014but every shift should be visible.<\/p>\n<h2>Why Standards Matter Over Time<\/h2>\n<p>Without standards, your models become a graveyard of interpretations. A model from last quarter might be unreadable today because the naming changed, the colors were swapped, or the customer vanished from the flow.<\/p>\n<p>Standards ensure longevity. They allow new team members to join and understand the journey instantly. They let CX teams compare models across products. They help IT teams see automation opportunities without needing a translator.<\/p>\n<p>Even more importantly, **consistent customer centric BPMN** reduces debate. When everyone uses the same structure, disputes shift from \u201cWhat does this mean?\u201d to \u201cIs this the right decision?\u201d That\u2019s where real innovation happens.<\/p>\n<p>Think of standards as the architecture of trust. They don\u2019t prevent mistakes\u2014but they make it easy to spot them early.<\/p>\n<h2>Practical Checklist for Your Team<\/h2>\n<p>Use this to audit your models\u2014or to onboard a new team.<\/p>\n<ol>\n<li>Is the customer clearly visible in every diagram?<\/li>\n<li>Are all activities named with active verbs and plain language?<\/li>\n<li>Do colors follow the same meaning across diagrams?<\/li>\n<li>Are annotations used to explain customer impact, not just process steps?<\/li>\n<li>Are channel shifts marked or labeled?<\/li>\n<\/ol>\n<p>Run this checklist on one model. If it takes more than 60 seconds, you\u2019ve got work to do.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I handle a journey that spans multiple departments?<\/h3>\n<p>Use a single pool with multiple lanes: one for the customer, one for each department involved. Keep the customer lane top or left. Use message flows to show handoffs. Avoid splitting the journey across multiple diagrams unless absolutely necessary.<\/p>\n<h3>Should I model every detail, or keep it high-level?<\/h3>\n<p>Start simple. Focus on the customer\u2019s perspective and key decision points. Add details only if they impact experience or automation. A model that tries to show every internal step will obscure the journey.<\/p>\n<h3>Can I use different standards for different customer segments?<\/h3>\n<p>Yes\u2014but with care. Use the same core conventions (color, naming, lane structure). Adjust only where needed for context (e.g., B2B vs B2C). Keep a note explaining the variation.<\/p>\n<h3>What if my team resists standardization?<\/h3>\n<p>Start with a single example. Show how a standardized version reduces confusion. Use feedback from a workshop. Lead by example, not enforcement.<\/p>\n<h3>Do I need to use BPMN 2.0 or later?<\/h3>\n<p>Yes. Older versions lack key features like event subprocesses and data objects, which are essential for modeling customer journeys accurately. Stick to BPMN 2.0+ for consistency and clarity.<\/p>\n<h3>How do I keep my BPMN models up to date?<\/h3>\n<p>Assign ownership. Schedule quarterly reviews. Link models to journey maps and KPI dashboards. Use versioning. When a change occurs, update the model first\u2014then inform stakeholders.<\/p>\n<p>Modeling standards for customer-centric BPMN aren\u2019t about perfection. They\u2019re about alignment. When your team speaks the same visual language, your customer journeys become not just clearer\u2014but actionable.<\/p>\n<p>Start with one rule. Apply it to one model. Let it show you the way.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every time I walk into a workshop, I see the same pattern: a room full of smart people, each with their own way of drawing BPMN, even when modeling the same journey. The result? Diagrams that confuse rather than clarify. Too many different colors, inconsistent naming, or lanes that hide the customer behind a wall [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1218,"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-1219","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 Standards for Customer-Centric BPMN<\/title>\n<meta name=\"description\" content=\"Establish lightweight, consistent modeling standards for customer-centric BPMN to ensure clarity across CX, business, and IT teams. Learn naming, color, lane, and annotation best practices for lasting impact.\" \/>\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\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Modeling Standards for Customer-Centric BPMN\" \/>\n<meta property=\"og:description\" content=\"Establish lightweight, consistent modeling standards for customer-centric BPMN to ensure clarity across CX, business, and IT teams. Learn naming, color, lane, and annotation best practices for lasting impact.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/\",\"name\":\"Modeling Standards for Customer-Centric BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:37:35+00:00\",\"description\":\"Establish lightweight, consistent modeling standards for customer-centric BPMN to ensure clarity across CX, business, and IT teams. Learn naming, color, lane, and annotation best practices for lasting impact.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Governance, Standards, and Advanced Topics\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Modeling Standards for Customer-Centric BPMN\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Modeling Standards for Customer-Centric BPMN","description":"Establish lightweight, consistent modeling standards for customer-centric BPMN to ensure clarity across CX, business, and IT teams. Learn naming, color, lane, and annotation best practices for lasting impact.","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\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/","og_locale":"pt_PT","og_type":"article","og_title":"Modeling Standards for Customer-Centric BPMN","og_description":"Establish lightweight, consistent modeling standards for customer-centric BPMN to ensure clarity across CX, business, and IT teams. Learn naming, color, lane, and annotation best practices for lasting impact.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/","name":"Modeling Standards for Customer-Centric BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:37:35+00:00","description":"Establish lightweight, consistent modeling standards for customer-centric BPMN to ensure clarity across CX, business, and IT teams. Learn naming, color, lane, and annotation best practices for lasting impact.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/modeling-standards-for-customer-centric-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Governance, Standards, and Advanced Topics","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/governance-standards-advanced-topics\/"},{"@type":"ListItem","position":4,"name":"Modeling Standards for Customer-Centric BPMN"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1219","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1219\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1218"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1219"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}