{"id":905,"date":"2026-02-25T10:26:47","date_gmt":"2026-02-25T10:26:47","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/"},"modified":"2026-02-25T10:26:47","modified_gmt":"2026-02-25T10:26:47","slug":"when-to-use-fishbone-diagram","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/","title":{"rendered":"Recognizing When a Fishbone Diagram Adds Value"},"content":{"rendered":"

Too many teams jump into problem-solving without asking the right question: Is this the right tool for this issue? The Fishbone Diagram isn’t a miracle fix for every failure. It\u2019s a structured way to uncover hidden causes behind recurring problems, especially when the root cause isn\u2019t obvious. You\u2019ll know it\u2019s time to pull out the Fishbone when symptoms keep returning, teams can\u2019t agree on what\u2019s really going wrong, or the problem spans multiple departments.<\/p>\n

Over 20 years of guiding teams through quality improvement has taught me one truth: you can\u2019t fix what you don\u2019t understand. A Fishbone Diagram helps you move beyond surface-level blame and surface-level fixes. It turns vague complaints into a shared, visual map of possible causes. You gain clarity, alignment, and a foundation for lasting change.<\/p>\n

This chapter will show you exactly when Fishbone analysis adds real value\u2014using real-world scenarios\u2014to help you decide not just what to do, but when to do it, and when another tool might be better.<\/p>\n

When Fishbone Diagrams Shine<\/h2>\n

Not every problem needs a Fishbone. But when you’re facing complex, recurring, or cross-functional failures, it\u2019s one of the most effective starting points for root cause analysis.<\/p>\n

1. Recurring Process Failures<\/h3>\n

When a defect, delay, or error keeps showing up\u2014even after fixes\u2014the issue isn\u2019t just a one-off. You\u2019re likely dealing with a systemic failure pattern. Fishbone Diagrams help expose the underlying structure that allows the same problem to persist.<\/p>\n

For example, a software team sees the same deployment failure every third sprint. They fix the symptom each time, but the root cause\u2014like inconsistent environment configurations\u2014remains unaddressed. A Fishbone reveals the real culprits across people, process, tools, and environment.<\/p>\n

This is where the root cause analysis benefits<\/strong> become tangible. You stop reacting and start preventing.<\/p>\n

2. Unclear Cause Relationships<\/h3>\n

When multiple causes might be at play, and the team can\u2019t agree on which one is primary, Fishbone provides a shared framework. It forces clarity by organizing potential causes into categories\u2014like People, Methods, Machines, Materials, Measurement, and Environment (the 6Ms).<\/p>\n

I once worked with a hospital lab where test result delays were blamed on \u201cstaff shortages\u201d or \u201cbad software.\u201d The Fishbone helped the team see that the real bottleneck was a lack of standardized data flow between departments\u2014something no one had considered before.<\/p>\n

This is a classic problem analysis scenario<\/strong> where the Fishbone turns chaos into structure. It doesn\u2019t eliminate uncertainty, but it makes the assumptions visible and testable.<\/p>\n

3. Cross-Functional or Interdepartmental Confusion<\/h3>\n

When a problem spans departments\u2014like IT, operations, and customer service\u2014blame often gets assigned without evidence. The Fishbone is a neutral map that invites collaboration. It doesn\u2019t care who\u2019s at fault; it only asks: what\u2019s making this happen?<\/p>\n

Consider a customer service department overwhelmed with complaints about late shipments. The warehouse blames logistics; logistics blames warehouse. A Fishbone session reveals that both are suffering from a shared issue: an outdated order tracking system. Now, the fix becomes collaborative instead of confrontational.<\/p>\n

These are ideal fishbone diagram use cases<\/strong>\u2014where siloed thinking hides systemic flaws. The diagram breaks down the mental walls.<\/p>\n

When Other Tools Might Be Better<\/h2>\n

Even the best tool has its place. The Fishbone is excellent for exploring possibilities, but it\u2019s not always the best for measuring impact or making decisions.<\/p>\n

1. The Problem Is Quantitative\u2014Use Pareto Charts<\/h3>\n

If you can measure frequency or cost of defects, and you want to prioritize which issues to fix first, a Pareto Chart is more effective. The Fishbone explores causes, but Pareto shows impact.<\/p>\n

Example: A manufacturing line has 12 types of defects. The Fishbone helps identify why they happen. But if you want to know which 3 defects cause 80% of the rework, Pareto is the better tool. Use them together: Fishbone for deep dive, Pareto for prioritization.<\/p>\n

2. The Cause Is Linear\u2014Try the 5 Whys<\/h3>\n

If the problem has a single, linear chain of events (e.g., \u201cWhy did the machine stop?\u201d \u2192 \u201cBecause the fuse blew\u201d \u2192 \u201cBecause the motor overheated\u201d), the 5 Whys can get you to the root faster. Fishbone is overkill here.<\/p>\n

Use 5 Whys when the issue is clear and traceable. Use Fishbone when the path is ambiguous or multiple factors are at play.<\/p>\n

3. The Root Cause Is Technical or Systemic\u2014Consider Fault Tree Analysis (FTA)<\/h3>\n

If you\u2019re analyzing complex system failures\u2014like a power outage or software crash\u2014FTA builds a logical model from top-down. Fishbone is more lateral, ideal for human or process-side issues.<\/p>\n

Think of Fishbone as a brainstorming scaffold. FTA as a diagnostic engine. Both are powerful, but for different types of problems.<\/p>\n

Decision Matrix: Choosing the Right Tool<\/h2>\n

Use this simple guide to match the problem type to the best analytical approach.<\/p>\n\n\n\n\n\n\n\n\n
Problem Type<\/th>\nBest Tool<\/th>\nWhy?<\/th>\n<\/tr>\n
Recurring process failures<\/td>\nFishbone Diagram<\/td>\nReveals systemic and cross-functional causes<\/td>\n<\/tr>\n
Frequent defects with clear frequency data<\/td>\nPareto Chart<\/td>\nHighlights the vital few causes to address first<\/td>\n<\/tr>\n
Simple, linear sequence of events<\/td>\n5 Whys<\/td>\nQuick, direct exploration of cause-and-effect<\/td>\n<\/tr>\n
Complex technical failure (e.g., system crash)<\/td>\nFault Tree Analysis (FTA)<\/td>\nLogical modeling of failure paths<\/td>\n<\/tr>\n
Unclear why a process is underperforming<\/td>\nFishbone Diagram<\/td>\nStructured brainstorming to explore hidden causes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Remember: tools are not mutually exclusive. Use Fishbone first to generate hypotheses, then apply Pareto or 5 Whys to narrow the focus.<\/p>\n

Key Takeaways<\/h2>\n
    \n
  • Use a Fishbone Diagram when symptoms repeat, causes are unclear, or the problem involves multiple teams or departments.<\/li>\n
  • It\u2019s not for every problem\u2014it shines in scenarios where root cause analysis benefits are significant, especially in non-linear or systemic failures.<\/li>\n
  • When you have clear, measurable data on defect frequency, a Pareto Chart is more efficient for prioritization.<\/li>\n
  • For linear, traceable failures, the 5 Whys can be faster and simpler.<\/li>\n
  • Always consider the context: the goal isn\u2019t just to identify a cause, but to enable a fix that sticks.<\/li>\n<\/ul>\n

    These aren\u2019t rules, but guiding principles. Your job isn\u2019t to follow a checklist\u2014it\u2019s to think critically about when a tool like Fishbone adds real value to your process.<\/p>\n

    Frequently Asked Questions<\/h2>\n

    When is a Fishbone Diagram not the right tool for root cause analysis?<\/h3>\n

    When the problem is simple and the cause is clear, like a broken lightbulb or a software bug with a known error log. In such cases, 5 Whys or direct troubleshooting is faster. Fishbone is better suited for complex, recurring, or ambiguous problems where multiple factors may be at play.<\/p>\n

    Can a Fishbone Diagram be used in software development?<\/h3>\n

    Absolutely. It\u2019s widely used in agile teams to analyze bugs, deployment failures, or slow sprint velocity. For example, if builds keep failing, a Fishbone helps explore whether the issue is with the code, environment, CI\/CD pipeline, or team process. It\u2019s a powerful tool for retrospectives.<\/p>\n

    What\u2019s the difference between a Fishbone Diagram and a cause-and-effect diagram?<\/h3>\n

    They are the same. Fishbone Diagram is a nickname derived from its shape. Cause-and-effect diagram is the formal name. Ishikawa Diagram is another name, named after Professor Kaoru Ishikawa, who developed it.<\/p>\n

    How many categories should I use in a Fishbone Diagram?<\/h3>\n

    The standard is 6Ms: Man (People), Machine, Method, Material, Measurement, and Mother Nature (Environment). But you can adapt the categories to your industry\u2014like 5S, People, Process, Technology, People, and Culture for service teams. The key is to have enough categories to explore all possible dimensions without overcrowding.<\/p>\n

    Is the Fishbone Diagram only for quality control?<\/h3>\n

    No. While it originated in manufacturing, it\u2019s now used in healthcare, IT, education, and customer service. Any process with a measurable outcome can benefit from Fishbone analysis when improvement is needed.<\/p>\n

    Can I use Fishbone Diagrams for personal problem-solving?<\/h3>\n

    Yes. While designed for teams, the framework applies to individual challenges like poor time management, recurring procrastination, or difficulty maintaining habits. Ask: What factors\u2014mental, environmental, or behavioral\u2014are affecting my ability to act? The Fishbone helps structure introspection just as effectively as team discussions.<\/p>\n

    When you understand when to use the Fishbone Diagram, you stop guessing and start solving.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

    Too many teams jump into problem-solving without asking the right question: Is this the right tool for this issue? The Fishbone Diagram isn’t a miracle fix for every failure. It\u2019s a structured way to uncover hidden causes behind recurring problems, especially when the root cause isn\u2019t obvious. You\u2019ll know it\u2019s time to pull out the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":904,"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-905","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nWhen to Use Fishbone Diagram<\/title>\n<meta name=\"description\" content=\"Discover the ideal situations for using a fishbone diagram\u2014when root cause analysis benefits, problem analysis scenarios, and fishbone diagram use cases will drive real improvement in processes and team collaboration.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"When to Use Fishbone Diagram\" \/>\n<meta property=\"og:description\" content=\"Discover the ideal situations for using a fishbone diagram\u2014when root cause analysis benefits, problem analysis scenarios, and fishbone diagram use cases will drive real improvement in processes and team collaboration.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/\",\"name\":\"When to Use Fishbone Diagram\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:26:47+00:00\",\"description\":\"Discover the ideal situations for using a fishbone diagram\u2014when root cause analysis benefits, problem analysis scenarios, and fishbone diagram use cases will drive real improvement in processes and team collaboration.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fishbone Diagram Fundamentals for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Preparing to Analyze Problems Effectively\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Recognizing When a Fishbone Diagram Adds Value\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"When to Use Fishbone Diagram","description":"Discover the ideal situations for using a fishbone diagram\u2014when root cause analysis benefits, problem analysis scenarios, and fishbone diagram use cases will drive real improvement in processes and team collaboration.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/","og_locale":"pt_PT","og_type":"article","og_title":"When to Use Fishbone Diagram","og_description":"Discover the ideal situations for using a fishbone diagram\u2014when root cause analysis benefits, problem analysis scenarios, and fishbone diagram use cases will drive real improvement in processes and team collaboration.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/","name":"When to Use Fishbone Diagram","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:26:47+00:00","description":"Discover the ideal situations for using a fishbone diagram\u2014when root cause analysis benefits, problem analysis scenarios, and fishbone diagram use cases will drive real improvement in processes and team collaboration.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/when-to-use-fishbone-diagram\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Fishbone Diagram Fundamentals for Beginners","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Preparing to Analyze Problems Effectively","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/"},{"@type":"ListItem","position":4,"name":"Recognizing When a Fishbone Diagram Adds Value"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/905\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/904"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=905"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}