{"id":1159,"date":"2026-02-25T10:36:51","date_gmt":"2026-02-25T10:36:51","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/"},"modified":"2026-02-25T10:36:51","modified_gmt":"2026-02-25T10:36:51","slug":"stakeholder-data-flow-mapping-workshops","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/","title":{"rendered":"Capturing Data Flows During Stakeholder Workshops"},"content":{"rendered":"<p>Too many analysts rush into diagramming during stakeholder sessions, only to realize later that flows were misinterpreted or critical data points were omitted. This often stems from treating the workshop as a data collection event rather than a collaborative modeling session. I\u2019ve seen teams waste hours rebuilding diagrams because they didn\u2019t anchor flows to real-world process logic, not just terminology.<\/p>\n<p>The real shift isn\u2019t in tools\u2014it\u2019s in mindset. Stakeholder data flow mapping is less about drawing boxes and arrows and more about translating business narratives into structured system behavior. When done well, it builds shared understanding, reduces rework, and ensures that the final DFD reflects operational truth, not just abstract theory.<\/p>\n<p>This chapter shares actionable workshop modeling techniques that I\u2019ve refined over years of leading cross-functional sessions. You\u2019ll learn how to guide stakeholders through collaborative diagram sessions that produce accurate, balanced, and maintainable DFDs\u2014without overwhelming non-technical participants.<\/p>\n<h2>Preparing for a Collaborative Modeling Session<\/h2>\n<h3>Define the Workshop\u2019s Strategic Objective<\/h3>\n<p>Start by clarifying the purpose: Are you building a context diagram? Decomposing a high-level process? Clarifying data ownership? One client once tried to map Level 2 flows in a 90-minute session with finance and operations teams\u2014chaos ensued. After reframing the goal to \u201cmap data movement for customer order processing,\u201d clarity emerged quickly.<\/p>\n<p>Use a simple statement: \u201cOur goal is to model how customer order data moves through the system from receipt to fulfillment.\u201d This focuses attention on data, not systems or roles.<\/p>\n<h3>Set the Stage with a Shared Context<\/h3>\n<p>Before any diagramming begins, walk stakeholders through the domain problem. For example: \u201cWe\u2019re modeling how a customer order triggers actions across sales, inventory, and shipping.\u201d This frames the conversation around real workflows, not abstract processes.<\/p>\n<p>Use a whiteboard or digital canvas to sketch a rough flow: customer \u2192 sales system \u2192 inventory check \u2192 shipping. This visual anchor prevents off-track discussions and aligns expectations.<\/p>\n<h2>Guiding the Workshop: Practical Facilitation Techniques<\/h2>\n<h3>Start with the Flow, Not the Process<\/h3>\n<p>Begin not with the process, but with the data flow. Ask: \u201cWhat data moves from sales to inventory when an order is placed?\u201d This shifts focus from \u201cwhat happens\u201d to \u201cwhat moves.\u201d It forces clarity about inputs, outputs, and data content.<\/p>\n<p>When stakeholders say \u201cthe order,\u201d challenge gently: \u201cDoes that mean the order ID? The product list? The customer address? What\u2019s actually being sent?\u201d This uncovers assumptions and prevents ambiguous flows like \u201ccustomer data\u201d or \u201cinformation.\u201d<\/p>\n<h3>Use Real-World Examples to Anchor Abstraction<\/h3>\n<p>Instead of saying, \u201cWe need to model the customer data store,\u201d say: \u201cWhen we place an order, what do we already know about the customer? Name? Address? Past purchases?\u201d Then map those specific data elements.<\/p>\n<p>This approach transforms vague data stores into named, purposeful assets: \u201cCustomer Master Record (CRM),\u201d \u201cOrder History Log.\u201d Stakeholders recognize these\u2014it\u2019s their language, not a technical abstraction.<\/p>\n<h3>Map Flows in Sequence, Not Isolation<\/h3>\n<p>Break the system into stages: receipt, validation, fulfillment, dispatch. At each stage, ask: \u201cWhat data arrives? What data leaves? What happens to it?\u201d This builds a chronological data journey.<\/p>\n<p>For example, in a logistics platform:<br \/>\n  <strong>Stage 1 (Receipt)<\/strong>: Order ID, product list, customer ID \u2192<br \/>\n  <strong>Stage 2 (Validation)<\/strong>: Check inventory \u2192<br \/>\n  <strong>Stage 3 (Fulfillment)<\/strong>: Ship confirmation, tracking number \u2192<br \/>\n  <strong>Stage 4 (Notification)<\/strong>: Email update with tracking info.<\/p>\n<p>Each step becomes a process in the DFD, with flows that reflect real-world data handoffs.<\/p>\n<h2>Tools and Visualization Strategies<\/h2>\n<h3>Choose the Right Live Diagramming Tool<\/h3>\n<p>Not all tools are equal for collaborative diagram sessions. Avoid static diagrams. Use platforms like Visual Paradigm with collaboration. These allow multiple people to edit simultaneously and keep a shared history.<\/p>\n<p>For stakeholder engagement, use color-coded elements:\n  <\/p>\n<ul>\n<li><strong>Blue<\/strong>: Data flows (input\/output)<\/li>\n<li><strong>Green<\/strong>: Internal processes<\/li>\n<li><strong>Orange<\/strong>: Data stores<\/li>\n<li><strong>Red<\/strong>: External entities<\/li>\n<\/ul>\n<p>  This visual schema helps non-technical members identify roles instantly.<\/p>\n<h3>Facilitate with a \u201cFlow First\u201d Protocol<\/h3>\n<p>Follow this simple sequence during collaborative diagram sessions:<\/p>\n<ol>\n<li>Identify the first data flow (e.g., \u201cOrder data from sales to inventory\u201d)<\/li>\n<li>Label it with a descriptive name: \u201cOrder Details for Inventory Check\u201d<\/li>\n<li>Assign source and destination<\/li>\n<li>Ask: \u201cWhat does this data include?\u201d \u2192 List elements (Order ID, Product Code, Quantity)<\/li>\n<li>Repeat for the next flow<\/li>\n<\/ol>\n<p>This minimizes ambiguity and builds a coherent flow map incrementally.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<h3>Overloading Flows with Too Much Data<\/h3>\n<p>One team tried to capture \u201call order information\u201d as a single flow. This led to confusion and untraceable data. Instead, split flows by meaning:\n  <\/p>\n<ul>\n<li>\u201cOrder Header\u201d (ID, date, customer ID)<\/li>\n<li>\u201cOrder Line Items\u201d (product, quantity, unit price)<\/li>\n<li>\u201cPayment Details\u201d (method, amount, status)<\/li>\n<\/ul>\n<p>  Each flow has a clear purpose and content.<\/p>\n<h3>Ignoring Data Store Ownership<\/h3>\n<p>Stakeholders often say, \u201cWe store orders.\u201d But where? Who maintains it? Which team is responsible? Use a simple table to clarify ownership:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Data Store<\/th>\n<th>Owner<\/th>\n<th>Update Frequency<\/th>\n<th>Access Level<\/th>\n<\/tr>\n<tr>\n<td>Order Master<\/td>\n<td>Sales<\/td>\n<td>Real-time<\/td>\n<td>Full<\/td>\n<\/tr>\n<tr>\n<td>Inventory Ledger<\/td>\n<td>Warehouse<\/td>\n<td>Daily<\/td>\n<td>Read-only<\/td>\n<\/tr>\n<tr>\n<td>Customer Profile<\/td>\n<td>CRM Team<\/td>\n<td>On-demand<\/td>\n<td>Role-based<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This prevents data redundancy and ensures accountability.<\/p>\n<h2>Post-Workshop Validation: Ensuring Quality and Consistency<\/h2>\n<p>After the session, don\u2019t assume the diagram is ready. Apply a quick validation checklist:<\/p>\n<ul>\n<li>Every data flow has a clear source and destination.<\/li>\n<li>All flows are named with a noun-verb structure: \u201cPayment Confirmation,\u201d \u201cOrder Status Update.\u201d<\/li>\n<li>Each process transforms input data into output data\u2014no black boxes.<\/li>\n<li>Data stores are updated only when a process writes to them.<\/li>\n<li>External entities appear only where data enters or leaves the system.<\/li>\n<\/ul>\n<p>These checks prevent the most common DFD errors: orphaned flows, missing data stores, and unbalanced inputs\/outputs.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I keep stakeholders engaged during a collaborative diagram session?<\/h3>\n<p>Use real examples from their work. Ask: \u201cWhen was the last time this flow broke?\u201d or \u201cWhat happens if this data is missing?\u201d These questions make the model feel relevant, not academic.<\/p>\n<h3>What if stakeholders disagree on data flow names?<\/h3>\n<p>Use consensus: \u201cWhich name best captures what actually moves?\u201d If no agreement, try multiple labels temporarily and test clarity. Remove ambiguous terms like \u201cinformation\u201d or \u201cdetails.\u201d Be specific: \u201cOrder ID and product list\u201d is better than \u201corder data.\u201d<\/p>\n<h3>Can I use DFDs in agile environments with frequent changes?<\/h3>\n<p>Absolutely. DFDs are not static. Use them as living documents: update flows when requirements change, and maintain traceability via the data dictionary. This supports both agile sprints and long-term system maintenance.<\/p>\n<h3>What if the team includes people with no technical background?<\/h3>\n<p>Use metaphors they understand: \u201cImagine the data flow like a package being handed from one person to another.\u201d Focus on the journey of data, not its structure. Avoid jargon. Use icons, colors, and real-world examples.<\/p>\n<h3>Should I capture every data flow during the workshop?<\/h3>\n<p>No. Capture only flows that are essential to the current model\u2019s scope. Use the \u201cso what?\u201d test: \u201cIf we remove this flow, does the system still work as intended?\u201d If not, keep it.<\/p>\n<h3>How do I handle flows that span multiple departments?<\/h3>\n<p>Map the entire journey, then use a dotted line or color to indicate handoff points. Label the flow with a location tag: \u201cSales \u2192 Inventory (Handoff: 2:00 PM).\u201d This maintains clarity while acknowledging organizational boundaries.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many analysts rush into diagramming during stakeholder sessions, only to realize later that flows were misinterpreted or critical data points were omitted. This often stems from treating the workshop as a data collection event rather than a collaborative modeling session. I\u2019ve seen teams waste hours rebuilding diagrams because they didn\u2019t anchor flows to real-world [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1157,"menu_order":1,"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-1159","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>Stakeholder Data Flow Mapping in Workshops<\/title>\n<meta name=\"description\" content=\"Master workshop modeling techniques to capture data flows during collaborative diagram sessions. Learn expert facilitation strategies for accurate, stakeholder-driven DFDs that align with system goals.\" \/>\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\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Stakeholder Data Flow Mapping in Workshops\" \/>\n<meta property=\"og:description\" content=\"Master workshop modeling techniques to capture data flows during collaborative diagram sessions. Learn expert facilitation strategies for accurate, stakeholder-driven DFDs that align with system goals.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/\",\"name\":\"Stakeholder Data Flow Mapping in Workshops\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:36:51+00:00\",\"description\":\"Master workshop modeling techniques to capture data flows during collaborative diagram sessions. Learn expert facilitation strategies for accurate, stakeholder-driven DFDs that align with system goals.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering Data Flow Diagram Levels and Balancing\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Application and Governance\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Capturing Data Flows During Stakeholder Workshops\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Stakeholder Data Flow Mapping in Workshops","description":"Master workshop modeling techniques to capture data flows during collaborative diagram sessions. Learn expert facilitation strategies for accurate, stakeholder-driven DFDs that align with system goals.","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\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/","og_locale":"id_ID","og_type":"article","og_title":"Stakeholder Data Flow Mapping in Workshops","og_description":"Master workshop modeling techniques to capture data flows during collaborative diagram sessions. Learn expert facilitation strategies for accurate, stakeholder-driven DFDs that align with system goals.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/","name":"Stakeholder Data Flow Mapping in Workshops","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:36:51+00:00","description":"Master workshop modeling techniques to capture data flows during collaborative diagram sessions. Learn expert facilitation strategies for accurate, stakeholder-driven DFDs that align with system goals.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/stakeholder-data-flow-mapping-workshops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Mastering Data Flow Diagram Levels and Balancing","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/"},{"@type":"ListItem","position":3,"name":"Real-World Application and Governance","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/"},{"@type":"ListItem","position":4,"name":"Capturing Data Flows During Stakeholder Workshops"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1159","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1159\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1157"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1159"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1159"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}