{"id":919,"date":"2026-02-25T10:26:52","date_gmt":"2026-02-25T10:26:52","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/"},"modified":"2026-02-25T10:26:52","modified_gmt":"2026-02-25T10:26:52","slug":"evaluate-fishbone-analysis-success","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/","title":{"rendered":"Evaluating the Success of a Fishbone Analysis"},"content":{"rendered":"

Too many teams treat the completed Fishbone diagram as a finish line. They draw the bones, assign causes, and walk away\u2014only to see the same problem return in a month. The real work begins after the diagram is full. I\u2019ve seen this play out across manufacturing floors, software sprints, and healthcare operations. The missing piece? A structured way to evaluate whether the analysis truly solved the problem.<\/p>\n

Simply identifying causes is not enough. What matters is whether those causes were validated<\/strong>, whether the corrective actions<\/strong> worked, and whether the problem solving outcomes<\/strong> were measurable. Without evaluation, you\u2019re just collecting ideas\u2014no different from a brainstorming session with no follow-through.<\/p>\n

This chapter walks you through the critical steps to evaluate fishbone analysis. You\u2019ll learn how to define success, track measurable outcomes, and close the loop with feedback. No theory. Just field-tested methods I\u2019ve used in over 200 root cause sessions across industries.<\/p>\n

Why Evaluation Is the Hidden Step in Problem Solving<\/h2>\n

Most guides stop at \u201cdraw the diagram.\u201d But the power of Fishbone thinking lies in its ability to generate insight, not just structure. Without evaluation, you risk building on assumptions.<\/p>\n

I once facilitated a session for a logistics team that identified \u201cinadequate training\u201d as a root cause of delivery delays. They implemented training\u2014but delays persisted. A year later, we re-evaluated the analysis and discovered the real issue: scheduling software not aligned with warehouse capacity. The original cause was real, but not the primary one.<\/p>\n

Evaluation ensures you\u2019re not just solving a symptom, but verifying the actual root cause<\/strong>. Here\u2019s how:<\/p>\n

    \n
  • Revisit the problem statement<\/strong>\u2014was it clear, measurable, and actionable?<\/li>\n
  • Trace each selected cause<\/strong> to real data or evidence, not just opinion.<\/li>\n
  • Link corrective actions directly to validated causes<\/strong>\u2014no guesswork.<\/li>\n
  • Measure impact over time<\/strong>\u2014before, during, and after implementation.<\/li>\n<\/ul>\n

    Without this, you\u2019re not conducting an analysis. You\u2019re just documenting what people believed.<\/p>\n

    Key Metrics for Root Cause Validation<\/h2>\n

    Quantitative feedback is the best way to evaluate fishbone analysis. You need metrics that answer: Did the fix actually reduce the problem?<\/p>\n

    Here are five core root cause validation metrics<\/strong> I use in every evaluation:<\/p>\n

      \n
    1. Problem frequency reduction<\/strong>\u2014track how often the issue occurs before and after the fix (e.g., defects per day, service tickets per week).<\/li>\n
    2. Time to resolution<\/strong>\u2014did incident resolution get faster? (e.g., average repair time dropped from 4 hours to 1.2 hours).<\/li>\n
    3. Cost of non-conformance<\/strong>\u2014did waste, rework, or returns decrease? (e.g., $50k\/month to $12k\/month).<\/li>\n
    4. Repeat occurrence rate<\/strong>\u2014if the problem reappeared, was it due to incomplete action or a new root cause?<\/li>\n
    5. Team confidence score<\/strong>\u2014on a scale of 1\u20135, how confident are team members the issue is resolved? (A drop in confidence is a red flag.)<\/li>\n<\/ol>\n

      These aren\u2019t just checkboxes. They\u2019re signals. If frequency drops 70% but cost remains high, you may have fixed one symptom but not the core inefficiency.<\/p>\n

      Creating a Fishbone Effectiveness Review Process<\/h2>\n

      Start with a simple review framework. I recommend a 30-day post-implementation check-in\u2014no more, no less. Here\u2019s how to structure it:<\/p>\n\n\n\n\n\n\n\n\n
      Review Step<\/th>\nAction<\/th>\nOwner<\/th>\n<\/tr>\n
      Revisit original problem statement<\/td>\nCompare current state to initial definition<\/td>\nFacilitator<\/td>\n<\/tr>\n
      Verify cause-action alignment<\/td>\nCheck if each action responds to a validated cause<\/td>\nTeam<\/td>\n<\/tr>\n
      Evaluate metric progress<\/td>\nCompare pre\/post data for all key indicators<\/td>\nData Analyst<\/td>\n<\/tr>\n
      Identify lingering issues<\/td>\nDocument any recurring incidents or new patterns<\/td>\nTeam<\/td>\n<\/tr>\n
      Update the Fishbone diagram<\/td>\nMark validated causes, add outcome status<\/td>\nFacilitator<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      This process turns a static diagram into a living document. It shows not just what was done, but whether it worked.<\/p>\n

      Measuring Problem Solving Outcomes<\/h2>\n

      Not all outcomes are quantitative. Some are qualitative, but still measurable. For example:<\/p>\n

        \n
      • Customer satisfaction scores increased from 3.4 to 4.6 post-fix.<\/li>\n
      • Team morale improved\u2014measured via anonymous pulse survey.<\/li>\n
      • Incident reports decreased by 60%, and no new cases cited the same root cause.<\/li>\n<\/ul>\n

        These outcomes confirm that the fix wasn\u2019t just applied\u2014it was effective.<\/p>\n

        Use this checklist to assess your problem solving outcomes<\/strong>:<\/p>\n

          \n
        • Did the primary measure show improvement?<\/li>\n
        • Did team members report confidence in the solution?<\/li>\n
        • Was the fix sustainable beyond 30\u201360 days?<\/li>\n
        • Did it prevent related issues from emerging?<\/li>\n
        • Can the solution be replicated in similar processes?<\/li>\n<\/ul>\n

          If you answer \u201cno\u201d to any of these, the analysis isn\u2019t fully successful\u2014yet.<\/p>\n

          Iterating for Lasting Improvement<\/h2>\n

          Evaluation isn\u2019t a one-time event. It\u2019s part of a cycle.<\/p>\n

          When the data shows the fix didn\u2019t work, don\u2019t discard the Fishbone. Use it again. Go back to the diagram and ask: Was the right cause selected? Was the action incomplete? Did we miss a dependency?<\/p>\n

          I once worked with a software team who implemented a fix for slow deployment times. The Fishbone showed \u201cinadequate automation\u201d as a root cause. They added CI\/CD pipelines\u2014but builds still lagged. Re-evaluation revealed the real issue: server resource contention during peak hours. The original cause was valid, but incomplete.<\/p>\n

          That\u2019s why iteration is critical. Every evaluation is a new opportunity to refine your understanding. Use the same Fishbone template to document:<\/p>\n

            \n
          • What worked<\/li>\n
          • What didn\u2019t<\/li>\n
          • What new data emerged<\/li>\n
          • What to test next<\/li>\n<\/ul>\n

            Think of it as a quality feedback loop, not a one-off report.<\/p>\n

            Frequently Asked Questions<\/h2>\n

            How do I know if I\u2019ve found the real root cause?<\/h3>\n

            Ask: Would the problem disappear if this cause were eliminated? If yes, and data confirms it, it\u2019s a strong candidate. Test with a controlled experiment if possible. Never rely on consensus alone\u2014validate with metrics.<\/p>\n

            What if the problem comes back after a fix?<\/h3>\n

            Re-evaluate the Fishbone. The cause may have been partially correct but not comprehensive. Look for hidden dependencies, process handoffs, or environmental factors. Re-apply the analysis using updated data.<\/p>\n

            Can I evaluate a Fishbone without data?<\/h3>\n

            Not reliably. Data gives credibility. If data isn\u2019t available, use proxy indicators\u2014e.g., customer complaints, team feedback, or incident frequency. But always aim for measurable outcomes.<\/p>\n

            How often should I review a fishbone analysis?<\/h3>\n

            Do a formal review 30 days after implementation. Then re-check every 90 days. Adjust frequency based on risk or complexity. High-impact problems need monthly reviews.<\/p>\n

            What if multiple causes were selected but only one was fixed?<\/h3>\n

            Track outcomes for each cause independently. If the fix worked, the data will show a reduction in the problem metric. If not, the unaddressed causes are likely still in play. Prioritize based on impact.<\/p>\n

            How do I communicate evaluation results to leadership?<\/h3>\n

            Use a simple summary: \u201cProblem: X. Fix: Y. Outcome: Z% reduction in X. Recommendation: Sustain.\u201d Lead with the impact. Avoid jargon. Show the before-and-after data. Leadership wants results, not diagrams.<\/p>\n","protected":false},"excerpt":{"rendered":"

            Too many teams treat the completed Fishbone diagram as a finish line. They draw the bones, assign causes, and walk away\u2014only to see the same problem return in a month. The real work begins after the diagram is full. I\u2019ve seen this play out across manufacturing floors, software sprints, and healthcare operations. The missing piece? […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":916,"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-919","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nEvaluate Fishbone Analysis Success<\/title>\n<meta name=\"description\" content=\"Learn how to evaluate fishbone analysis success using root cause validation metrics, fishbone effectiveness review, and measurable problem solving outcomes to ensure lasting improvement.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Evaluate Fishbone Analysis Success\" \/>\n<meta property=\"og:description\" content=\"Learn how to evaluate fishbone analysis success using root cause validation metrics, fishbone effectiveness review, and measurable problem solving outcomes to ensure lasting improvement.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/\",\"name\":\"Evaluate Fishbone Analysis Success\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:26:52+00:00\",\"description\":\"Learn how to evaluate fishbone analysis success using root cause validation metrics, fishbone effectiveness review, and measurable problem solving outcomes to ensure lasting improvement.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fishbone Diagram Fundamentals for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Overcoming Challenges and Gaining Mastery\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Evaluating the Success of a Fishbone Analysis\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Evaluate Fishbone Analysis Success","description":"Learn how to evaluate fishbone analysis success using root cause validation metrics, fishbone effectiveness review, and measurable problem solving outcomes to ensure lasting improvement.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/","og_locale":"pl_PL","og_type":"article","og_title":"Evaluate Fishbone Analysis Success","og_description":"Learn how to evaluate fishbone analysis success using root cause validation metrics, fishbone effectiveness review, and measurable problem solving outcomes to ensure lasting improvement.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/","name":"Evaluate Fishbone Analysis Success","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:26:52+00:00","description":"Learn how to evaluate fishbone analysis success using root cause validation metrics, fishbone effectiveness review, and measurable problem solving outcomes to ensure lasting improvement.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/evaluate-fishbone-analysis-success\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Fishbone Diagram Fundamentals for Beginners","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Overcoming Challenges and Gaining Mastery","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-analysis-best-practices\/"},{"@type":"ListItem","position":4,"name":"Evaluating the Success of a Fishbone Analysis"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/919","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/919\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/916"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=919"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=919"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}