{"id":906,"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\/defining-problem-statement-fishbone-analysis\/"},"modified":"2026-02-25T10:26:47","modified_gmt":"2026-02-25T10:26:47","slug":"defining-problem-statement-fishbone-analysis","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/","title":{"rendered":"How to Define a Focused Problem Statement"},"content":{"rendered":"<p>Never start a fishbone session without a clear problem statement. A vague or overly broad goal will scatter your team\u2019s focus and lead straight to surface-level fixes.<\/p>\n<p>One of the most common mistakes I\u2019ve observed in over two decades of guiding teams is treating a problem like a headline: \u201cOur customer support is slow.\u201d That\u2019s not an issue\u2014it\u2019s a symptom. You can\u2019t diagnose a symptom. You need to diagnose the cause.<\/p>\n<p>The real value of a fishbone diagram lies not in the drawing, but in how precisely it\u2019s anchored. A strong problem statement cuts through noise and sets boundaries for real analysis. It tells your team: \u201cWe\u2019re not solving everything. We\u2019re solving this.\u201d<\/p>\n<p>By the end of this chapter, you\u2019ll know how to write a problem statement that\u2019s measurable, specific, and grounded in data\u2014so you\u2019re not just chasing symptoms, but uncovering real root causes.<\/p>\n<h2>Why Your Problem Statement Matters More Than You Think<\/h2>\n<p>Most root cause failures don\u2019t stem from poor diagrams. They begin with a bad problem statement.<\/p>\n<p>If your problem is \u201cOur system keeps crashing,\u201d the team will start listing factors under \u201cPeople,\u201d \u201cProcess,\u201d or \u201cTechnology\u201d without knowing what\u2019s actually happening. Is it daily? Hourly? Only during peak load? The lack of clarity invites assumptions.<\/p>\n<p>Let\u2019s be clear: a well-defined problem statement isn\u2019t just helpful\u2014it\u2019s the difference between a productive session and wasted time. It ensures every discussion stays on track and every cause is evaluated within the right scope.<\/p>\n<h3>The One-Liner Rule for Clarity<\/h3>\n<p>Every strong problem statement should pass the \u201cone-liner test.\u201d It must be concise enough to fit in a single sentence, yet complete enough to define the who, what, when, and where.<\/p>\n<p>Here\u2019s the formula:<\/p>\n<ul>\n<li><strong>What<\/strong> is happening (the observable issue)<\/li>\n<li><strong>When<\/strong> it occurs (frequency, time, or trigger)<\/li>\n<li><strong>Where<\/strong> it occurs (process, system, location)<\/li>\n<li><strong>How much<\/strong> (a measurable impact)<\/li>\n<\/ul>\n<p>Use this to guide your thinking. Don\u2019t skip any element\u2014each one helps limit ambiguity.<\/p>\n<h2>Problem Statement Examples That Work<\/h2>\n<p>Let\u2019s look at how to apply this in real scenarios. These are actual examples from manufacturing, software, and customer service teams.<\/p>\n<h3>Example 1: Manufacturing<\/h3>\n<p><strong>Weak:<\/strong> \u201cWe\u2019re making defective parts.\u201d<\/p>\n<p><strong>Strong:<\/strong> \u201cThe welding defect rate in Line 3 rose from 0.2% to 1.8% over the past two weeks, affecting 12% of units delivered to Customer X.\u201d<\/p>\n<p>This version includes: the defect (welding), the location (Line 3), the timeframe (two weeks), and the measurable impact (1.8% defect rate, customer delivery impact).<\/p>\n<h3>Example 2: Software Development<\/h3>\n<p><strong>Weak:<\/strong> \u201cThe app crashes too often.\u201d<\/p>\n<p><strong>Strong:<\/strong> \u201cMobile app crashes increased by 60% over the last 48 hours, affecting 1,200 users per day, mostly during login and payment processing.\u201d<\/p>\n<p>Now you\u2019re not just chasing \u201ccrashes\u201d \u2014 you\u2019re focused on specific user actions and timing. That narrows the fishbone categories and fuels deeper thinking.<\/p>\n<h3>Example 3: Customer Service<\/h3>\n<p><strong>Weak:<\/strong> \u201cCustomers are unhappy.\u201d<\/p>\n<p><strong>Strong:<\/strong> \u201cCustomer satisfaction scores dropped from 88% to 72% over the past month, primarily due to delayed responses on support tickets with unresolved technical issues.\u201d<\/p>\n<p>Now your team knows exactly what to analyze: response time, ticket resolution quality, and agent workload\u2014not vague \u201chappiness\u201d.<\/p>\n<h2>Common Phrasing Mistakes to Avoid<\/h2>\n<p>Even experienced teams slip into poor phrasing. Here are the top five pitfalls\u2014and how to fix them.<\/p>\n<ul>\n<li><strong>Using vague verbs:<\/strong> \u201cWe have problems with quality\u201d \u2192 Replace with \u201cDefects in final inspection increased by 40% over the last quarter.\u201d<\/li>\n<li><strong>Blaming people too early:<\/strong> \u201cThe operator made a mistake\u201d \u2192 Shift to \u201cOperator errors in calibration led to 15% of units failing calibration checks.\u201d<\/li>\n<li><strong>Overloading the statement:<\/strong> \u201cOur production line is failing due to machines, staff, and poor planning\u201d \u2192 Split into two distinct statements: one for machine downtime, one for training gaps.<\/li>\n<li><strong>Focusing on solutions:<\/strong> \u201cWe need better software\u201d \u2192 Reframe to \u201cSoftware errors during data export rose from 2 to 12 incidents per day.\u201d<\/li>\n<li><strong>Using \u201cand\u201d to connect unrelated issues:<\/strong> \u201cCustomers are angry and support is slow\u201d \u2192 Split into two focused problems: one on customer sentiment, one on response time.<\/li>\n<\/ul>\n<p>These mistakes may seem minor, but they\u2019re the invisible traps that derail entire analysis sessions.<\/p>\n<h2>How to Refine Your Problem Statement<\/h2>\n<p>Once you draft a statement, test it with three questions:<\/p>\n<ol>\n<li><strong>Can it be measured?<\/strong> If you can\u2019t track change over time, it\u2019s not actionable.<\/li>\n<li><strong>Could someone else reproduce the problem?<\/strong> If two people can\u2019t understand your goal, your statement is too vague.<\/li>\n<li><strong>Does it fit the fishbone scope?<\/strong> If the issue spans multiple unrelated areas (e.g., customer complaints and data breaches), it\u2019s too broad.<\/li>\n<\/ol>\n<p>If you answer \u201cno\u201d to any, revise.<\/p>\n<p><strong>Pro tip:<\/strong> Always write the problem statement on a whiteboard before the meeting. If the team can\u2019t agree on it in under 60 seconds, you\u2019re not ready to draw the fishbone.<\/p>\n<h2>Problem Statement Checklist<\/h2>\n<p>Use this checklist before starting your fishbone session:<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Check<\/th>\n<th>Yes\/No<\/th>\n<\/tr>\n<tr>\n<td>Is the problem specific to one process, system, or location?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<\/tr>\n<tr>\n<td>Is there a measurable metric (e.g., defect rate, response time, error count)?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<\/tr>\n<tr>\n<td>Does it include a time frame (e.g., past 7 days, since the update)?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<\/tr>\n<tr>\n<td>Is it phrased as an observable issue, not a solution?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<\/tr>\n<tr>\n<td>Can the team agree on it in under 60 seconds?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If you can\u2019t check all boxes, go back. A flawed problem statement ruins the entire analysis.<\/p>\n<h2>Why Scope Matters: The Fishbone Problem Definition<\/h2>\n<p>Every fishbone diagram has a scope. If your problem statement drifts beyond that scope, the causes you find may be irrelevant.<\/p>\n<p>Think of scope like a sandbox. The diagram only works if you stay inside the boundaries. If your problem is \u201cOur customer service is bad,\u201d you might end up analyzing marketing, delivery, and billing\u2014none of which are part of the support process.<\/p>\n<p>But if your problem is \u201cAverage response time in the support portal increased from 2 hours to 6 hours since the new system launch,\u201d you\u2019re focused on a single channel, a known trigger, and a clear metric. That\u2019s fishbone-ready.<\/p>\n<p>When in doubt, ask: \u201cIs this cause related to the specific issue I defined?\u201d If not, remove it.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between a problem statement and a goal?<\/h3>\n<p>A problem statement describes the current issue\u2014what\u2019s broken. A goal describes what you want to achieve\u2014e.g., \u201cReduce response time to under 2 hours.\u201d The statement focuses on diagnosis. The goal focuses on improvement.<\/p>\n<h3>Can a problem statement be a question?<\/h3>\n<p>No. While questions can guide exploration, the fishbone process requires a declarative statement. A question like \u201cWhy is customer satisfaction dropping?\u201d invites interpretation. A statement like \u201cCustomer satisfaction dropped from 90% to 76% in three weeks\u201d is objective and measurable.<\/p>\n<h3>Should I involve the entire team in writing the problem statement?<\/h3>\n<p>Yes\u2014but only after a short discussion. Let participants bring in data, but let one person draft the statement first. This avoids agreement fatigue and keeps the focus tight.<\/p>\n<h3>How do I handle multiple problems in one session?<\/h3>\n<p>Don\u2019t. Each problem needs its own fishbone. If you\u2019re analyzing both response time and resolution quality, run two separate sessions. Trying to combine them leads to confusion and diluted insights.<\/p>\n<h3>What if my team disagrees on the problem statement?<\/h3>\n<p>Disagreement is normal. Use data to resolve it. Pull up the metrics. Ask: \u201cWhere does this data show the issue?\u201d Often, the numbers clarify what opinions can\u2019t.<\/p>\n<h3>Can I adjust the problem statement mid-session?<\/h3>\n<p>Yes\u2014but only if you revisit the scope. If new evidence emerges, revise the statement and re-clarify with the team. Never allow the session to drift without re-anchoring.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Never start a fishbone session without a clear problem statement. A vague or overly broad goal will scatter your team\u2019s focus and lead straight to surface-level fixes. One of the most common mistakes I\u2019ve observed in over two decades of guiding teams is treating a problem like a headline: \u201cOur customer support is slow.\u201d That\u2019s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":904,"menu_order":1,"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-906","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 a Problem Statement for Root Cause Analysis<\/title>\n<meta name=\"description\" content=\"Learn how to craft a focused problem statement for fishbone analysis\u2014essential for accurate root cause identification, avoiding symptom-chasing, and improving process quality in business and IT.\" \/>\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\/defining-problem-statement-fishbone-analysis\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Defining a Problem Statement for Root Cause Analysis\" \/>\n<meta property=\"og:description\" content=\"Learn how to craft a focused problem statement for fishbone analysis\u2014essential for accurate root cause identification, avoiding symptom-chasing, and improving process quality in business and IT.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/\" \/>\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=\"6 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\/defining-problem-statement-fishbone-analysis\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/\",\"name\":\"Defining a Problem Statement for Root Cause Analysis\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:26:47+00:00\",\"description\":\"Learn how to craft a focused problem statement for fishbone analysis\u2014essential for accurate root cause identification, avoiding symptom-chasing, and improving process quality in business and IT.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/#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\":\"How to Define a Focused Problem Statement\"}]},{\"@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":"Defining a Problem Statement for Root Cause Analysis","description":"Learn how to craft a focused problem statement for fishbone analysis\u2014essential for accurate root cause identification, avoiding symptom-chasing, and improving process quality in business and IT.","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\/defining-problem-statement-fishbone-analysis\/","og_locale":"pt_PT","og_type":"article","og_title":"Defining a Problem Statement for Root Cause Analysis","og_description":"Learn how to craft a focused problem statement for fishbone analysis\u2014essential for accurate root cause identification, avoiding symptom-chasing, and improving process quality in business and IT.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"6 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\/defining-problem-statement-fishbone-analysis\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/","name":"Defining a Problem Statement for Root Cause Analysis","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:26:47+00:00","description":"Learn how to craft a focused problem statement for fishbone analysis\u2014essential for accurate root cause identification, avoiding symptom-chasing, and improving process quality in business and IT.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-preparation\/defining-problem-statement-fishbone-analysis\/#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":"How to Define a Focused Problem Statement"}]},{"@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\/906","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\/906\/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=906"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=906"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}