{"id":649,"date":"2026-02-25T10:21:37","date_gmt":"2026-02-25T10:21:37","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/"},"modified":"2026-02-25T10:21:37","modified_gmt":"2026-02-25T10:21:37","slug":"dfd-for-different-audiences","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/","title":{"rendered":"One Diagram for Everyone: Ignoring Audience Needs"},"content":{"rendered":"<p>Too many analysts treat a single DFD as a universal truth, expecting it to serve both the executive sponsor needing a high-level view and the developer debugging a microservice. This is a recipe for miscommunication. I\u2019ve seen teams spend hours refining a single diagram only to find it ignored by stakeholders who don\u2019t see their concerns reflected. The real issue isn\u2019t complexity\u2014it\u2019s relevance.<\/p>\n<p>Data flow diagrams aren\u2019t meant to be exhaustive. They\u2019re communication tools, and every audience interprets them differently. Executives care about value streams and risk exposure. Developers need detail on inputs, transformations, and data store access. Analysts want traceability and consistency. Forcing all these needs into one diagram distorts intent, creates noise, and diminishes trust in the model.<\/p>\n<p>My advice? Stop trying to satisfy everyone with one view. Instead, build a narrative around the system\u2014then slice it differently for each audience. A well-structured DFD suite doesn\u2019t dilute clarity. It multiplies understanding.<\/p>\n<h2>Why One Diagram Fails Every Time<\/h2>\n<p>Let\u2019s be clear: a single DFD cannot simultaneously be a strategic overview and a technical blueprint. Yet this is what many teams default to\u2014especially under time pressure or when tooling doesn&#8217;t support multiple views.<\/p>\n<p>Consider a retail ordering system. A Level 0 DFD might show data flowing from &#8220;Customer&#8221; to &#8220;Order Processing&#8221; to &#8220;Payment Gateway&#8221; and back. That\u2019s useful for business stakeholders. But for a developer, it hides critical details: how is order validation performed? What\u2019s in the &#8220;Order&#8221; data flow? Which database holds the inventory records?<\/p>\n<p>When you compress all these layers into one diagram, you&#8217;re not simplifying. You&#8217;re obfuscating. The result? A visual mess that no one truly understands\u2014and no one dares to question.<\/p>\n<h3>The Cost of Generic Diagrams<\/h3>\n<ul>\n<li><strong>Executives<\/strong> skim for key flows and control points. A cluttered DFD with 12 processes and 18 flows loses them immediately.<\/li>\n<li><strong>Analysts<\/strong> need to trace requirements to processes and data elements. Ambiguous labels like &#8220;Process Data&#8221; or &#8220;Handle Info&#8221; break this traceability.<\/li>\n<li><strong>Developers<\/strong> need to know inputs, outputs, and data store access patterns. Missing data store annotations or unbalanced flows make implementation risky.<\/li>\n<\/ul>\n<p>The same DFD fails all three roles because it wasn\u2019t designed for any of them. It was designed to look complete, not to serve a purpose.<\/p>\n<h2>How to Build Audience-Specific Data Flow Diagrams<\/h2>\n<p>Instead of one monolithic DFD, think in terms of viewpoints. Each viewpoint answers a set of questions for a specific role. The key is consistency\u2014same system, different lenses.<\/p>\n<h3>1. Executive-Level View: The Big Picture<\/h3>\n<p>For leadership, focus on high-level data flows that reflect business value, risk, and ownership. Highlight key external entities, major data transformations, and critical data stores.<\/p>\n<p>Example: In a customer onboarding system, the executive DFD might show:<\/p>\n<ul>\n<li>Customer \u2192 Onboarding Portal \u2192 Customer Data Store<\/li>\n<li>Onboarding Portal \u2192 Credit Check Service \u2192 Decision<\/li>\n<li>Decision \u2192 Approval Notification \u2192 Customer<\/li>\n<\/ul>\n<p>Only processes with business impact are included. Internal data stores and minor transformations are collapsed. This view answers: Where does data originate? Where does it go? What\u2019s the critical path?<\/p>\n<h3>2. Analyst-Level View: Traceability and Logic<\/h3>\n<p>Analysts need to validate that every requirement maps to a process and that data flows are consistent across levels.<\/p>\n<p>Here, you include:<\/p>\n<ul>\n<li>More granular processes (e.g., \u201cValidate Customer Identity,\u201d \u201cCheck Credit Score\u201d)<\/li>\n<li>Clear data flow names (e.g., \u201cCustomer Application Form,\u201d \u201cApproved Credit Decision\u201d)<\/li>\n<li>Data stores labeled with purpose (e.g., \u201cCustomer Profile DB,\u201d \u201cAudit Log\u201d)<\/li>\n<li>References to business rules or requirements<\/li>\n<\/ul>\n<p>Use a Level 1 DFD to break down core processes from the executive view. This layer supports impact analysis, change requests, and gap identification.<\/p>\n<h3>3. Developer-Level View: Technical Implementation<\/h3>\n<p>For engineers, the DFD must reflect implementation reality. This is where you introduce technical details without abandoning logical modeling.<\/p>\n<p>Refine the analyst-level DFD by adding:<\/p>\n<ul>\n<li>Specific data store types (e.g., \u201cPostgreSQL: Orders Table\u201d)<\/li>\n<li>APIs or service names (e.g., \u201cCall CreditCheck API\u201d)<\/li>\n<li>Batch vs real-time data flows (e.g., \u201cDaily Batch Update\u201d)<\/li>\n<li>Security considerations (e.g., \u201cEncrypted Data Flow\u201d)<\/li>\n<\/ul>\n<p>These aren\u2019t deviations from DFD principles\u2014they\u2019re enhancements for technical clarity. The process still represents a logical transformation, but the labels and context reflect operational reality.<\/p>\n<h2>How to Link the Views Together<\/h2>\n<p>One DFD does not replace another. They are part of a layered communication strategy. Here\u2019s how to connect them:<\/p>\n<ol>\n<li><strong>Start with the context diagram<\/strong> to establish system boundaries.<\/li>\n<li><strong>Build the executive DFD<\/strong> from the context, simplifying flows and processes.<\/li>\n<li><strong>Decompose key processes<\/strong> into analyst-level DFDs.<\/li>\n<li><strong>Refine selected processes<\/strong> into developer-level diagrams.<\/li>\n<li><strong>Use labels or annotations<\/strong> to link related diagrams (e.g., \u201cSee Level 1: Validate Identity\u201d).<\/li>\n<\/ol>\n<p>Use tooling like Visual Paradigm to create \u201cviews\u201d or \u201cperspectives\u201d that share the same model but highlight different elements. This keeps consistency while enabling audience-specific clarity.<\/p>\n<h3>Comparison: Tailoring DFD to Stakeholders<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Audience<\/th>\n<th>Focus<\/th>\n<th>Viewpoint<\/th>\n<th>Key Characteristics<\/th>\n<\/tr>\n<tr>\n<td>Executives<\/td>\n<td>Value, risk, ownership<\/td>\n<td>High-level overview<\/td>\n<td>1\u20133 key processes, minimal data stores, symbolic flows<\/td>\n<\/tr>\n<tr>\n<td>Analysts<\/td>\n<td>Traceability, consistency<\/td>\n<td>Logical decomposition<\/td>\n<td>Level 1 DFD, clear process names, data flow references<\/td>\n<\/tr>\n<tr>\n<td>Developers<\/td>\n<td>Implementation, access, timing<\/td>\n<td>Technical detail<\/td>\n<td>Service names, data store types, timing indicators<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Practical Tips for Success<\/h2>\n<p>Here\u2019s how to make audience-specific DFDs work in real projects:<\/p>\n<ul>\n<li><strong>Define your audience before drawing.<\/strong> Who will use this diagram? What decisions will they make with it?<\/li>\n<li><strong>Use consistent naming conventions<\/strong> across all views so processes and flows remain identifiable.<\/li>\n<li><strong>Document assumptions<\/strong> in a legend or sidebar. For example: \u201cThis view excludes third-party audit logs.\u201d<\/li>\n<li><strong>Link diagrams with traceability<\/strong>\u2014e.g., \u201cProcess P3 in this diagram corresponds to \u2018Validate Identity\u2019 in Level 1.\u201d<\/li>\n<li><strong>Use tools that support multiple views<\/strong> so you can generate different versions from the same model.<\/li>\n<\/ul>\n<p>Don\u2019t force a technical diagram into an executive presentation. Don\u2019t expect a one-page overview to guide a full system integration. Let the purpose guide the design.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Why can&#8217;t I use one DFD for all stakeholders?<\/h3>\n<p>Because each audience has a different cognitive load. Executives process big picture; developers parse technical details. A single DFD tries to satisfy both and fails both. It becomes too dense for leadership and too vague for implementation.<\/p>\n<h3>How do I decide what to include in an executive DFD?<\/h3>\n<p>Ask: What\u2019s the key business outcome? What are the main data dependencies that affect risk or performance? Include only those flows that directly impact decisions\u2014especially if they involve external systems, compliance, or revenue.<\/p>\n<h3>Can I make a DFD that works for both analysts and developers?<\/h3>\n<p>Yes\u2014but only if you separate the concerns. Use a single model, but create two views: one for analysis (emphasizing logic and traceability), and another for implementation (emphasizing services, data stores, and timing). This is tailoring DFD to stakeholders, not inconsistency.<\/p>\n<h3>What if my team insists on one &#8220;final&#8221; DFD?<\/h3>\n<p>Explain that a single DFD is a compromise. It hides complexity, not truth. Instead, propose a suite: context \u2192 executive \u2192 analyst \u2192 developer. Show how this improves clarity and reduces rework. Frame it as a quality improvement, not an extra step.<\/p>\n<h3>How do I keep DFDs aligned across multiple views?<\/h3>\n<p>Use a central model with shared elements. Tools like Visual Paradigm  allow you to define a single process and reference it across views. Use consistent naming and versioning to avoid drift.<\/p>\n<h3>Is it acceptable to label a process \u201cSystem\u201d in an executive DFD?<\/h3>\n<p>Only if it\u2019s clearly a placeholder. Better to name it after the function: \u201cCustomer Onboarding System\u201d or \u201cPayment Processing Engine.\u201d Vague labels like \u201cSystem\u201d or \u201cProcess\u201d break traceability and breed confusion.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many analysts treat a single DFD as a universal truth, expecting it to serve both the executive sponsor needing a high-level view and the developer debugging a microservice. This is a recipe for miscommunication. I\u2019ve seen teams spend hours refining a single diagram only to find it ignored by stakeholders who don\u2019t see their [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":646,"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-649","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>DFD for Different Audiences<\/title>\n<meta name=\"description\" content=\"Learn how to tailor DFD for different audiences: executives, analysts, and developers. Discover why one-size-fits-all diagrams fail and how to create audience-specific data flow diagrams that communicate effectively.\" \/>\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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD for Different Audiences\" \/>\n<meta property=\"og:description\" content=\"Learn how to tailor DFD for different audiences: executives, analysts, and developers. Discover why one-size-fits-all diagrams fail and how to create audience-specific data flow diagrams that communicate effectively.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/\" \/>\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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/\",\"name\":\"DFD for Different Audiences\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:21:37+00:00\",\"description\":\"Learn how to tailor DFD for different audiences: executives, analysts, and developers. Discover why one-size-fits-all diagrams fail and how to create audience-specific data flow diagrams that communicate effectively.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DFD Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Readability, Layout, and Communication Issues\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"One Diagram for Everyone: Ignoring Audience Needs\"}]},{\"@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":"DFD for Different Audiences","description":"Learn how to tailor DFD for different audiences: executives, analysts, and developers. Discover why one-size-fits-all diagrams fail and how to create audience-specific data flow diagrams that communicate effectively.","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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/","og_locale":"id_ID","og_type":"article","og_title":"DFD for Different Audiences","og_description":"Learn how to tailor DFD for different audiences: executives, analysts, and developers. Discover why one-size-fits-all diagrams fail and how to create audience-specific data flow diagrams that communicate effectively.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/","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\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/","name":"DFD for Different Audiences","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:21:37+00:00","description":"Learn how to tailor DFD for different audiences: executives, analysts, and developers. Discover why one-size-fits-all diagrams fail and how to create audience-specific data flow diagrams that communicate effectively.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/dfd-for-different-audiences\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Common DFD Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Readability, Layout, and Communication Issues","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-readability-issues\/"},{"@type":"ListItem","position":4,"name":"One Diagram for Everyone: Ignoring Audience Needs"}]},{"@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\/649","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\/649\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/646"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=649"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}