{"id":1021,"date":"2026-02-25T10:34:50","date_gmt":"2026-02-25T10:34:50","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/"},"modified":"2026-02-25T10:34:50","modified_gmt":"2026-02-25T10:34:50","slug":"define-fishbone-problem","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/","title":{"rendered":"Defining the Problem Visually within the Fishbone"},"content":{"rendered":"<p>When I walk into a room where a Fishbone diagram is being built, the first thing I check is not the branches, but the head: the effect written on the right. That single line can determine whether the session becomes a productive investigation or a drift toward speculation. A well-defined fishbone problem turns ambiguity into focus. It turns a vague complaint like \u201cOur customer service is bad\u201d into a measurable, unambiguous statement such as \u201cCustomer complaint resolution time exceeds 48 hours.\u201d This clarity is the foundation of real improvement.<\/p>\n<p>Over two decades of leading RCA workshops taught me one truth: the quality of your problem statement directly shapes the quality of your findings. A poor effect definition leads to unfocused causes, wasted time, and decisions based on assumption. The goal isn&rsquo;t to solve everything \u2014 it\u2019s to solve the right thing. This chapter guides you through how to define the fishbone problem with precision, using a structured, evidence-based approach.<\/p>\n<h2>Why the Effect Must Be Specific and Measurable<\/h2>\n<p>A strong problem statement answers: What is the deviation? From what benchmark? When and where did it occur?<\/p>\n<p>Consider these two examples:<\/p>\n<ul>\n<li>\u201cOur team is late on deliveries\u201d \u2014 too vague.<\/li>\n<li>\u201cDelivery order completion rate dropped below 85% in Q3 2024, with 12% of orders delayed by more than 48 hours.\u201d \u2014 measurable and specific.<\/li>\n<\/ul>\n<p>The second statement allows you to define boundaries, set data collection goals, and anchor the Fishbone to facts, not feelings.<\/p>\n<p>Ask yourself: Can I measure this? Can I verify it with logs, data, or observations? If not, you\u2019ve not defined the fishbone problem correctly. The effect must be a clear, objective deviation from expected performance.<\/p>\n<h3>Checklist: Is Your Effect Statement Ready?<\/h3>\n<ul>\n<li>\u2705 It describes a real, observable deviation (e.g., dropped conversion rate, increased downtime)<\/li>\n<li>\u2705 It includes a timeframe or context (e.g., \u201cduring peak load\u201d, \u201cin August 2024\u201d)<\/li>\n<li>\u2705 It\u2019s quantifiable \u2014 can you track it with data?<\/li>\n<li>\u2705 It avoids blaming individuals or departments<\/li>\n<li>\u2705 It\u2019s concise \u2014 one sentence, no jargon<\/li>\n<\/ul>\n<p>When I review a Fishbone, I use this checklist. If the effect fails even one item, I pause the session to clarify.<\/p>\n<h2>Creating the Ishikawa Diagram Head: The Cause-Effect Definition<\/h2>\n<p>The Ishikawa diagram head is not just a place to write a problem \u2014 it\u2019s the invitation to investigate. It must reflect a clear cause-effect relationship.<\/p>\n<p>Think of it this way: the effect is the outcome. The causes are the variables that contributed to it. If you can\u2019t name the cause, you can\u2019t fix it. If you can\u2019t measure the effect, you can\u2019t prove the fix worked.<\/p>\n<p>Common mistakes when writing the effect include:<\/p>\n<ul>\n<li>Using emotional language: \u201cThe process is broken.\u201d<\/li>\n<li>Assigning blame: \u201cThe warehouse team caused the delay.\u201d<\/li>\n<li>Being too broad: \u201cWe\u2019re not doing well.\u201d<\/li>\n<\/ul>\n<p>Instead, write effects using a simple structure:<\/p>\n<p><strong>\u201c[Outcome] has [deviation] in [context] during [timeframe].\u201d<\/strong><\/p>\n<p>This format forces objectivity. It removes emotion and positions the investigation as a system check, not a blame game.<\/p>\n<h3>Examples of Strong Fishbone Problem Statements<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Weak Effect<\/th>\n<th>Strong Effect (Cause-Effect Definition)<\/th>\n<\/tr>\n<tr>\n<td>\u201cCustomers are unhappy.\u201d<\/td>\n<td>\u201cCustomer satisfaction score dropped to 3.2\/5 in Q2, down from 4.1 in Q1.\u201d<\/td>\n<\/tr>\n<tr>\n<td>\u201cWe keep missing deadlines.\u201d<\/td>\n<td>\u201cProject delivery deadlines were missed in 15 out of 20 tasks in June 2024.\u201d<\/td>\n<\/tr>\n<tr>\n<td>\u201cThe system crashes.\u201d<\/td>\n<td>\u201cThe order processing system crashed 12 times in the last 72 hours during peak load.\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Each strong effect allows you to define the scope of your investigation \u2014 and that scope is critical. A problem that\u2019s too broad leads to a fishbone with too many causes. A problem too narrow may miss systemic links.<\/p>\n<h2>Aligning the Scope: What You Include (and Exclude)<\/h2>\n<p>Defining the fishbone problem isn\u2019t just about wording \u2014 it\u2019s about setting boundaries. I once facilitated a session where the team tried to analyze \u201call quality issues in production.\u201d That spanned six departments, five systems, and three product lines. We couldn\u2019t even finish the first category before the meeting ended.<\/p>\n<p>Instead, I asked: \u201cFor this investigation, what are we really trying to fix?\u201d After discussion, we narrowed it to: \u201cWhy did 22% of orders shipped late in the central warehouse last week?\u201d That scope was manageable, data-rich, and actionable.<\/p>\n<p>Use these filters to clarify scope:<\/p>\n<ol>\n<li><strong>Timeframe:<\/strong> Limit to a clear window (e.g., \u201cJuly 1\u201310, 2024\u201d).<\/li>\n<li><strong>Location or system:<\/strong> Specify the process, line, department, or software module.<\/li>\n<li><strong>Impact:<\/strong> Define the measurable outcome (e.g., delay, defect rate, cost overrun).<\/li>\n<li><strong>Exclusions:<\/strong> State what\u2019s <em>not<\/em> in scope to prevent scope creep.<\/li>\n<\/ol>\n<p>When I run sessions, I write the problem statement on a whiteboard and ask: \u201cIf this were a newspaper headline, would it make sense to someone outside the team?\u201d If not, we revise.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intentions, teams fall into traps when defining the fishbone problem.<\/p>\n<h3>Trap 1: Confusing Symptoms with Causes<\/h3>\n<p>Example: \u201cWe have too many support tickets.\u201d This is a symptom \u2014 not the effect.<\/p>\n<p>Root cause: \u201cSupport ticket volume increased by 60% in July 2024 compared to June.\u201d That\u2019s the effect.<\/p>\n<p>Now, you can investigate what caused the spike \u2014 maybe a new feature rollout, a bug, or training gap.<\/p>\n<h3>Trap 2: Using Passive or Vague Verbs<\/h3>\n<p>\u201cThe system isn\u2019t working.\u201d \u201cThe process is off.\u201d These are not measurable.<\/p>\n<p>Replace with active, observable verbs: \u201cFailed to process orders\u201d, \u201cRejection rate increased to 14%\u201d, \u201cResponse time exceeded 10 seconds.\u201d<\/p>\n<h3>Trap 3: Including Too Many Effects<\/h3>\n<p>Don\u2019t try to solve \u201cdelays, poor quality, and customer complaints\u201d in one diagram. Pick one primary effect. If you have multiple problems, run multiple Fishbones.<\/p>\n<p>Remember: each fishbone is a focused investigation, not a catch-all.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the best way to write a fishbone problem statement?<\/h3>\n<p>Use a clear, measurable format: \u201c[Outcome] deviated from expected [benchmark] in [context] during [timeframe].\u201d Avoid emotion, blame, and ambiguity. Example: \u201cCall center first-call resolution dropped to 62% in Q3, down from 80% in Q2.\u201d<\/p>\n<h3>Can I use the same fishbone problem statement for multiple RCA sessions?<\/h3>\n<p>Only if the issue is identical. If you\u2019re analyzing different timeframes, locations, or product lines, revise the statement. Two different effects require two separate diagrams, even if they seem similar.<\/p>\n<h3>How do I handle a problem that has multiple effects?<\/h3>\n<p>Start with the most severe or impactful effect. If you need to analyze multiple outcomes, create separate Fishbones. You can later map relationships across diagrams using cause-effect chains or matrix analysis.<\/p>\n<h3>Is it okay to change the problem statement mid-process?<\/h3>\n<p>Yes \u2014 but only after review. If data shows the original effect was misidentified, adjust it with team agreement. Document the change and justify it. Never force a mismatch between problem and causes.<\/p>\n<h3>What if the team disagrees on the problem definition?<\/h3>\n<p>Use data to resolve conflict. Bring in logs, metrics, or customer feedback. Ask: \u201cWhat does the evidence say?\u201d Focus on facts, not opinions. This is where the fishbone problem statement becomes your anchor.<\/p>\n<h3>How does defining the fishbone problem affect the rest of the RCA process?<\/h3>\n<p>A precise problem statement ensures that brainstorming stays focused, cause validation is data-driven, and corrective actions are relevant. It prevents wasted effort, misaligned solutions, and recurring issues. The quality of your outcome is a direct function of the quality of your problem definition.<\/p>\n<p>When I started using the fishbone method, I thought the branches were the hard part. I\u2019ve learned that getting the head right \u2014 the effect \u2014 is where real power begins. A well-defined fishbone problem doesn\u2019t just guide your analysis \u2014 it shapes your team\u2019s thinking, ensures alignment, and builds trust in the process.<\/p>\n<p>Go back to your last RCA meeting. Look at the effect. Ask: Is it measurable? Is it specific? Can someone else verify it? If not, revise it. That small step will save you hours of misdirected effort and bring you one step closer to lasting improvement.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I walk into a room where a Fishbone diagram is being built, the first thing I check is not the branches, but the head: the effect written on the right. That single line can determine whether the session becomes a productive investigation or a drift toward speculation. A well-defined fishbone problem turns ambiguity into [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1020,"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-1021","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>Define Fishbone Problem for Effective RCA<\/title>\n<meta name=\"description\" content=\"Learn how to define the fishbone problem clearly with a precise effect statement. Master the cause-effect definition to align your RCA scope and avoid common pitfalls in root cause analysis.\" \/>\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\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Define Fishbone Problem for Effective RCA\" \/>\n<meta property=\"og:description\" content=\"Learn how to define the fishbone problem clearly with a precise effect statement. Master the cause-effect definition to align your RCA scope and avoid common pitfalls in root cause analysis.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/\",\"name\":\"Define Fishbone Problem for Effective RCA\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:34:50+00:00\",\"description\":\"Learn how to define the fishbone problem clearly with a precise effect statement. Master the cause-effect definition to align your RCA scope and avoid common pitfalls in root cause analysis.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Perform Root Cause Analysis with Fishbone Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"The Fishbone Method in Root Cause Analysis\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Defining the Problem Visually within the Fishbone\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Define Fishbone Problem for Effective RCA","description":"Learn how to define the fishbone problem clearly with a precise effect statement. Master the cause-effect definition to align your RCA scope and avoid common pitfalls in root cause analysis.","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\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/","og_locale":"fr_FR","og_type":"article","og_title":"Define Fishbone Problem for Effective RCA","og_description":"Learn how to define the fishbone problem clearly with a precise effect statement. Master the cause-effect definition to align your RCA scope and avoid common pitfalls in root cause analysis.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/","name":"Define Fishbone Problem for Effective RCA","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:34:50+00:00","description":"Learn how to define the fishbone problem clearly with a precise effect statement. Master the cause-effect definition to align your RCA scope and avoid common pitfalls in root cause analysis.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/define-fishbone-problem\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"How to Perform Root Cause Analysis with Fishbone Diagrams","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/"},{"@type":"ListItem","position":3,"name":"The Fishbone Method in Root Cause Analysis","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/how-to-perform-root-cause-analysis-with-fishbone-diagram\/fishbone-method-root-cause-analysis\/"},{"@type":"ListItem","position":4,"name":"Defining the Problem Visually within the Fishbone"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1021","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1021\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1020"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=1021"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=1021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}