{"id":1016,"date":"2026-02-25T10:34:48","date_gmt":"2026-02-25T10:34:48","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/"},"modified":"2026-02-25T10:34:48","modified_gmt":"2026-02-25T10:34:48","slug":"defining-rca-problem","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/","title":{"rendered":"Defining the Problem and Setting Boundaries"},"content":{"rendered":"<p>Too many teams jump straight into a Fishbone diagram with a vague statement like \u201cOur process is broken.\u201d That approach leads to wasted time, misaligned efforts, and often, no real insight. I\u2019ve seen this happen in manufacturing, software delivery, and healthcare\u2014dozens of times. The real danger isn\u2019t the diagram itself, but the assumption that a poorly defined problem will yield useful results.<\/p>\n<p>The truth is, any RCA effort begins not with tools, but with clarity. A precise, measurable, and scoped problem statement is the foundation. Without it, you&#8217;re not investigating\u2014you\u2019re guessing.<\/p>\n<p>This chapter walks you through how to define the problem with rigor, set firm boundaries, and avoid common pitfalls that derail investigations. You\u2019ll learn how to transform vague complaints into focused, actionable challenges. By the end, you\u2019ll have a method to ensure every RCA project starts with the right question\u2014so you end with the right answer.<\/p>\n<h2>Why Problem Scoping Is Your First Real Step<\/h2>\n<p>A weak problem statement invites ambiguity. A strong one prevents it.<\/p>\n<p>Consider this: \u201cThe customer is unhappy.\u201d Vague. Open to interpretation. You could spend hours investigating shipping delays, billing errors, or poor support\u2014when the real issue might be a single failed feature in the app.<\/p>\n<p>Now consider: \u201cCustomer retention dropped 18% in Q2 due to login failures on mobile devices.\u201d That\u2019s specific. Measurable. Time-bound. It tells you where to focus.<\/p>\n<p>Problem scoping in RCA isn\u2019t about being overly restrictive. It\u2019s about being precise. A poorly scoped investigation wastes energy chasing symptoms instead of uncovering causes.<\/p>\n<h3>Common Pitfalls in Problem Definition<\/h3>\n<ul>\n<li><strong>Too broad:<\/strong> \u201cOur operations need improvement.\u201d No clear target. No way to measure progress.<\/li>\n<li><strong>Too narrow:<\/strong> \u201cThe error log shows line 42 failed.\u201d Missing context. May lead to fixing a symptom, not the root cause.<\/li>\n<li><strong>Blaming language:<\/strong> \u201cThe team didn\u2019t follow protocol.\u201d This invites defensiveness and distracts from systemic issues.<\/li>\n<li><strong>Emotion-driven:<\/strong> \u201cThe system keeps crashing and it\u2019s driving me crazy.\u201d Emotion clouds objectivity.<\/li>\n<\/ul>\n<p>Instead, use objective, data-backed language. Ask: \u201cWhat exactly changed? When? Where? How much?\u201d These questions help isolate the real issue.<\/p>\n<h2>Setting Investigation Boundaries<\/h2>\n<p>Boundaries define the \u201cwhat\u201d and \u201cwhere\u201d of your investigation. They prevent scope creep and ensure your team stays focused.<\/p>\n<p>For example: \u201cWhy did the monthly audit fail?\u201d\u2014is too broad. \u201cWhy did the June 2024 compliance audit fail for the logistics branch in Denver?\u201d\u2014is specific. You can now define the boundary: only that location, only the June 2024 data, only compliance-related processes.<\/p>\n<p>Think of boundaries as a fence. They don\u2019t limit your insights\u2014they channel them. Without them, a team can spend two days drawing Fishbone branches that apply to a different project entirely.<\/p>\n<h3>Key Questions to Set Boundaries<\/h3>\n<ol>\n<li>What is the exact event or failure?<\/li>\n<li>When did it occur (or how often)?<\/li>\n<li>Where did it occur (location, system, process step)?<\/li>\n<li>What is the measurable impact (e.g., downtime, cost, error rate)?<\/li>\n<li>What is NOT in scope (to prevent drift)?<\/li>\n<\/ol>\n<p>Answering these ensures consistency. It also makes reporting and follow-up far easier.<\/p>\n<h2>Using the 5W1H Framework for Clarity<\/h2>\n<p>I\u2019ve used this framework in over 100 RCA sessions. It turns ambiguity into precision.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Question<\/th>\n<th>Example<\/th>\n<th>Use in RCA<\/th>\n<\/tr>\n<tr>\n<td>What?<\/td>\n<td>Customer order processing fails after 2 PM<\/td>\n<td>Defines the failure mode<\/td>\n<\/tr>\n<tr>\n<td>Who?<\/td>\n<td>Field service team in Chicago<\/td>\n<td>Identifies responsible unit<\/td>\n<\/tr>\n<tr>\n<td>When?<\/td>\n<td>Every Tuesday and Thursday between 2:00\u20135:00 PM, June 1 to June 15<\/td>\n<td>Pinpoints timing and frequency<\/td>\n<\/tr>\n<tr>\n<td>Where?<\/td>\n<td>Order Entry System (OES), version 3.4.2<\/td>\n<td>Specifies system and environment<\/td>\n<\/tr>\n<tr>\n<td>Why?<\/td>\n<td>Failed to validate customer status in real time<\/td>\n<td>Prepares for cause analysis<\/td>\n<\/tr>\n<tr>\n<td>How?<\/td>\n<td>System timeout after 30 seconds of inactivity<\/td>\n<td>Provides observable behavior<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use this to draft your problem statement. Example:<\/p>\n<p><strong>\u201cThe OES fails to process 12% of orders from 2:00\u20135:00 PM on Tuesdays and Thursdays (June 1\u201315), due to a 30-second timeout when verifying customer status, impacting the Chicago field service team.\u201d<\/strong><\/p>\n<p>This is measurable, traceable, and focused\u2014exactly what a root cause project definition requires.<\/p>\n<h2>When to Expand or Narrow the Scope<\/h2>\n<p>Some problems are interconnected. You may need to break a large investigation into phases.<\/p>\n<p>For example: \u201cOur customer satisfaction score dropped.\u201d This could involve support, delivery, billing, and product quality. Don\u2019t tackle all at once.<\/p>\n<p>Start with the highest-impact area. Use data to prioritize. If delivery delays explain 60% of the drop, focus your initial RCA there. Once resolved, expand to other areas.<\/p>\n<p>That\u2019s how you turn a mountain into manageable steps. It\u2019s not about doing everything\u2014it\u2019s about doing the right thing first.<\/p>\n<h2>Template: Building a Strong Problem Statement<\/h2>\n<p>Use this format to standardize your RCA start:<\/p>\n<p><strong>What happened?<\/strong> [Specific event or failure]<\/p>\n<p><strong>When?<\/strong> [Date, time, or frequency]<\/p>\n<p><strong>Where?<\/strong> [System, location, team, or process]<\/p>\n<p><strong>Extent?<\/strong> [Impact: % failure rate, cost, downtime, error count]<\/p>\n<p><strong>Why it matters?<\/strong> [Business or operational consequence]<\/p>\n<p>Example:<\/p>\n<p><strong>What happened?<\/strong> Failed to generate invoices for 147 customers.<\/p>\n<p><strong>When?<\/strong> Between June 3 and June 5, 2024.<\/p>\n<p><strong>Where?<\/strong> Finance system, batch job #124.<\/p>\n<p><strong>Extent?<\/strong> 147 of 1,200 customers affected. 2.3% error rate.<\/p>\n<p><strong>Why it matters?<\/strong> Delayed payments, customer complaints, and potential audit risk.<\/p>\n<p>Use this template to ensure every RCA begins with clarity. It prevents wasted time, ensures alignment, and sets the stage for effective analysis.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if my problem statement is too broad?<\/h3>\n<p>If your investigation requires more than three weeks to complete, or involves five or more departments, you likely need to narrow the scope. Ask: \u201cIs this one issue, or a cluster of issues?\u201d Split it into smaller, focused problems.<\/p>\n<h3>Can I change the problem statement during the RCA?<\/h3>\n<p>Yes\u2014but only if evidence shows the original was incorrect. Never change it to fit a desired outcome. Document the shift and why it happened. This maintains integrity and transparency.<\/p>\n<h3>What if multiple teams are affected?<\/h3>\n<p>Start with the most impacted area. Use the 80\/20 rule: focus on the 20% of causes that explain 80% of the impact. Once resolved, address secondary issues.<\/p>\n<h3>How do I avoid blame when defining the problem?<\/h3>\n<p>Use neutral, system-focused language. Instead of \u201cThe team didn\u2019t update the form,\u201d say \u201cThe system rejected 42 forms due to missing validation fields.\u201d Focus on process, not people.<\/p>\n<h3>Is it okay to include multiple issues in one RCA?<\/h3>\n<p>Only if they are causally related. If two issues have different root causes, separate them. Trying to solve both at once leads to confusion and incomplete solutions.<\/p>\n<h3>What if the data is incomplete or conflicting?<\/h3>\n<p>Be honest. State: \u201cThe data is limited. We are investigating under uncertainty, with the goal of validating assumptions.\u201d Document gaps. Don\u2019t speculate. Let the investigation proceed with transparency.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many teams jump straight into a Fishbone diagram with a vague statement like \u201cOur process is broken.\u201d That approach leads to wasted time, misaligned efforts, and often, no real insight. I\u2019ve seen this happen in manufacturing, software delivery, and healthcare\u2014dozens of times. The real danger isn\u2019t the diagram itself, but the assumption that a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1015,"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-1016","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>Defining the Problem in RCA<\/title>\n<meta name=\"description\" content=\"Learn how to define the problem and set boundaries in Root Cause Analysis. Master problem scoping in RCA, setting investigation boundaries, and root cause project definition for precise, actionable results.\" \/>\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\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Defining the Problem in RCA\" \/>\n<meta property=\"og:description\" content=\"Learn how to define the problem and set boundaries in Root Cause Analysis. Master problem scoping in RCA, setting investigation boundaries, and root cause project definition for precise, actionable results.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/\" \/>\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=\"5 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\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/\",\"name\":\"Defining the Problem in RCA\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:34:48+00:00\",\"description\":\"Learn how to define the problem and set boundaries in Root Cause Analysis. Master problem scoping in RCA, setting investigation boundaries, and root cause project definition for precise, actionable results.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Perform Root Cause Analysis with Fishbone Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Preparing for Effective Root Cause Work\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Defining the Problem and Setting Boundaries\"}]},{\"@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":"Defining the Problem in RCA","description":"Learn how to define the problem and set boundaries in Root Cause Analysis. Master problem scoping in RCA, setting investigation boundaries, and root cause project definition for precise, actionable results.","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\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/","og_locale":"id_ID","og_type":"article","og_title":"Defining the Problem in RCA","og_description":"Learn how to define the problem and set boundaries in Root Cause Analysis. Master problem scoping in RCA, setting investigation boundaries, and root cause project definition for precise, actionable results.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"5 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/","name":"Defining the Problem in RCA","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:34:48+00:00","description":"Learn how to define the problem and set boundaries in Root Cause Analysis. Master problem scoping in RCA, setting investigation boundaries, and root cause project definition for precise, actionable results.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/defining-rca-problem\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"How to Perform Root Cause Analysis with Fishbone Diagrams","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/"},{"@type":"ListItem","position":3,"name":"Preparing for Effective Root Cause Work","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/root-cause-analysis-preparation\/"},{"@type":"ListItem","position":4,"name":"Defining the Problem and Setting Boundaries"}]},{"@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\/1016","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\/1016\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1015"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1016"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}