{"id":915,"date":"2026-02-25T10:26:51","date_gmt":"2026-02-25T10:26:51","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/"},"modified":"2026-02-25T10:26:51","modified_gmt":"2026-02-25T10:26:51","slug":"fishbone-diagram-service-industry","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/","title":{"rendered":"Fishbone Diagrams for Service and Customer Experience Design"},"content":{"rendered":"<p>Teams often jump to optimizing workflows after a customer complaint, assuming the fix lies in faster response times or better staffing. But that\u2019s like replacing a broken belt without checking why the engine seized. In service industries, symptoms like long wait times or poor resolution rates rarely point to the real issue.<\/p>\n<p>Over twenty years of guiding support teams through root cause analysis has taught me one thing: the real problem isn&#8217;t always where the pain is felt. Too often, teams treat service gaps as isolated incidents, when they\u2019re often symptoms of systemic failures in training, tools, or cross-functional communication.<\/p>\n<p>This chapter shows how to use the <strong>fishbone diagram for service industry<\/strong> to dig deeper. You\u2019ll learn how to structure a service improvement analysis that reveals hidden causes behind customer dissatisfaction, using a method grounded in real-world examples from hospitality, telecom, and IT support.<\/p>\n<h2>Why Service Teams Need Fishbone Analysis<\/h2>\n<p>Service delivery isn\u2019t just about people or speed\u2014it\u2019s about consistency, clarity, and coordination. A single lost customer can stem from dozens of small failures across departments.<\/p>\n<p>Traditional tools like surveys or KPI dashboards show <em>what<\/em> went wrong\u2014but not <em>why<\/em>. That\u2019s where the fishbone diagram comes in. It turns vague frustration into structured cause discovery.<\/p>\n<p>When support teams use a fishbone for support teams, they stop reacting and start understanding. The goal isn\u2019t to assign blame but to expose weak links in the service chain.<\/p>\n<h3>Common Pitfalls in Service Root Cause Analysis<\/h3>\n<p>Many teams fail prematurely because they focus on immediate causes\u2014like \u201cagent was unavailable\u201d or \u201csystem was slow.\u201d But these are symptoms, not root causes.<\/p>\n<p>Here\u2019s what I\u2019ve seen in hundreds of sessions:<\/p>\n<ul>\n<li>Teams rush to brainstorm without a focused problem statement<\/li>\n<li>They use generic categories like \u201cpeople\u201d or \u201cprocess\u201d without tailoring them to service workflows<\/li>\n<li>They stop after listing causes, skipping validation with real data<\/li>\n<li>They treat the diagram as a one-off exercise instead of a living tool for continuous improvement<\/li>\n<\/ul>\n<p>These mistakes undermine the entire analysis. The fishbone diagram for service industry must be more than a poster\u2014it must drive change.<\/p>\n<h2>Setting Up Your Fishbone for Service Excellence<\/h2>\n<p>Begin with a well-defined problem statement. Instead of \u201cCustomers are unhappy,\u201d ask: \u201cWhy did 42% of support tickets receive a negative CSAT score in Q2?\u201d<\/p>\n<p>This specificity forces you to consider the full context: Was it timing? Communication? Escalation paths? The problem statement shapes the entire analysis.<\/p>\n<h3>Choosing the Right Categories<\/h3>\n<p>Standard fishbone categories (People, Process, Equipment, Environment) work in manufacturing\u2014but not always in service. For customer experience, adapt the framework to reflect real-world dynamics:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Category<\/th>\n<th>Service-Focused Examples<\/th>\n<\/tr>\n<tr>\n<td><strong>People<\/strong><\/td>\n<td>Agent availability, training level, shift patterns, empowerment limits<\/td>\n<\/tr>\n<tr>\n<td><strong>Process<\/strong><\/td>\n<td>Escalation workflow, ticket routing rules, resolution time benchmarks<\/td>\n<\/tr>\n<tr>\n<td><strong>Technology<\/strong><\/td>\n<td>CRM system accessibility, API failures, knowledge base search speed<\/td>\n<\/tr>\n<tr>\n<td><strong>Communication<\/strong><\/td>\n<td>Internal handoff clarity, customer update frequency, tone consistency<\/td>\n<\/tr>\n<tr>\n<td><strong>Expectations<\/strong><\/td>\n<td>Customer understanding of resolution timelines, support SLA transparency<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These categories guide your team to think beyond \u201cthe agent didn\u2019t know\u201d and toward \u201cthe system doesn\u2019t flag critical issues in time.\u201d<\/p>\n<h2>Conducting the Brainstorming Session<\/h2>\n<p>Facilitate a 60-minute session with your support team, service designers, and frontline managers. Use silent brainstorming to avoid groupthink\u2014give everyone 10 minutes to list causes independently.<\/p>\n<p>Then, group similar ideas under the categories. Look for patterns: Are multiple causes tied to knowledge base access? Is response time consistently high after 3 PM?<\/p>\n<p>Use the <strong>customer experience root cause<\/strong> as your north star. Ask: \u201cWhich of these causes would explain why 30% of customers never get a resolution?\u201d<\/p>\n<h3>Validating Causes with Data<\/h3>\n<p>Not all causes are equal. Use metrics to filter and prioritize. For example:<\/p>\n<ul>\n<li>If 70% of negative feedback mentions \u201clong wait time,\u201d check call center data<\/li>\n<li>If 60% of unresolved tickets involve a specific product line, investigate backend tooling<\/li>\n<li>If communication errors spike during shift changes, audit handoff procedures<\/li>\n<\/ul>\n<p>Pairing the fishbone with real data transforms it from a brainstorming tool into a decision engine.<\/p>\n<h2>From Insight to Service Improvement<\/h2>\n<p>Once you\u2019ve identified likely root causes, don\u2019t stop at diagnosis. Use the fishbone as a roadmap for change.<\/p>\n<p>Here\u2019s a simple action plan:<\/p>\n<ol>\n<li><strong>Rank causes<\/strong> by impact and feasibility (e.g., \u201cTraining gaps\u201d vs. \u201cSystem overhaul\u201d)<\/li>\n<li><strong>Assign ownership<\/strong> to one person per cause, with a clear deadline<\/li>\n<li><strong>Define measurable outcomes<\/strong>: \u201cReduce average wait time from 12 to 7 minutes by end of quarter\u201d<\/li>\n<li><strong>Revisit the fishbone<\/strong> in 4 weeks to validate improvements<\/li>\n<\/ol>\n<p>This turns the diagram into a living document that evolves with your service.<\/p>\n<h2>Real-World Example: Reducing Customer Escalation in Telecom<\/h2>\n<p>A telecom support team noticed a rising trend in escalations. The problem statement: \u201cWhy did 25% of Tier 1 tickets require escalation to Tier 2 in Q1?\u201d<\/p>\n<p>Using the fishbone with adapted categories, they uncovered:<\/p>\n<ul>\n<li><strong>People<\/strong>: Tier 1 agents lacked training on broadband diagnostics<\/li>\n<li><strong>Technology<\/strong>: No real-time access to customer network diagnostics<\/li>\n<li><strong>Process<\/strong>: Escalation required manual ticket reassignment<\/li>\n<li><strong>Communication<\/strong>: No standard handoff script between tiers<\/li>\n<\/ul>\n<p>They didn\u2019t just fix training\u2014they redesigned the escalation workflow, integrated diagnostic tools into the CRM, and created a handoff checklist. Within three months, escalations dropped 40%.<\/p>\n<h2>Best Practices for Support Teams<\/h2>\n<p>Even the best fishbone fails without discipline. These practices have proven essential in my work:<\/p>\n<ul>\n<li><strong>Limit categories to 5<\/strong>\u2014too many overwhelm teams. Focus on what matters in service delivery.<\/li>\n<li><strong>Use real examples<\/strong>\u2014show the diagram with actual complaints or tickets. This keeps the analysis grounded.<\/li>\n<li><strong>Invite frontline agents<\/strong>\u2014they see the pain points others miss. Their input reveals hidden system flaws.<\/li>\n<li><strong>Revisit quarterly<\/strong>\u2014service needs evolve. Reassess the fishbone to ensure it still reflects reality.<\/li>\n<li><strong>Integrate with feedback loops<\/strong>\u2014link the fishbone to CSAT, NPS, and ticket resolution data.<\/li>\n<\/ul>\n<h2>FAQs<\/h2>\n<h3>How do I know if the fishbone diagram for service industry is working?<\/h3>\n<p>Track the impact of your actions. If key metrics like resolution time, escalation rate, or CSAT improve within 60\u201390 days, the root cause was likely identified correctly. Use data, not opinion.<\/p>\n<h3>Can a fishbone for support teams be used in digital service design?<\/h3>\n<p>Absolutely. It\u2019s ideal for mapping pain points in self-service portals, chatbot flows, or mobile app onboarding. Use categories like \u201cUser Interface,\u201d \u201cNavigation Logic,\u201d and \u201cFeedback Mechanism\u201d to uncover friction points.<\/p>\n<h3>What should I do if the team says \u201cThe problem is just bad agents\u201d?<\/h3>\n<p>Challenge that assumption with data. Ask: \u201cWhat\u2019s the same across all agents who failed?\u201d If multiple agents struggle with the same issue, it\u2019s likely a training, tool, or process problem\u2014not an individual one.<\/p>\n<h3>How often should we re-run a fishbone analysis?<\/h3>\n<p>Reassess every quarter, or after a major change in service delivery. As customer behavior or technology evolves, so do root causes.<\/p>\n<h3>Can fishbone diagrams be used for proactive service improvement?<\/h3>\n<p>Yes. Use them before launching a new service or feature. Ask: \u201cWhat could go wrong?\u201d Identify potential failure points early, then build safeguards.<\/p>\n<h3>Is it okay to use digital tools for fishbone diagrams in service teams?<\/h3>\n<p>Highly recommended. Tools like Visual Paradigm allow team collaboration, version tracking.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Teams often jump to optimizing workflows after a customer complaint, assuming the fix lies in faster response  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":912,"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-915","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>Fishbone Diagram for Service Industry<\/title>\n<meta name=\"description\" content=\"Use a fishbone diagram for service industry to uncover root causes of customer dissatisfaction, delays, and service breakdowns. Perform service improvement analysis with actionable insights for support teams.\" \/>\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\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fishbone Diagram for Service Industry\" \/>\n<meta property=\"og:description\" content=\"Use a fishbone diagram for service industry to uncover root causes of customer dissatisfaction, delays, and service breakdowns. Perform service improvement analysis with actionable insights for support teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/\",\"name\":\"Fishbone Diagram for Service Industry\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:26:51+00:00\",\"description\":\"Use a fishbone diagram for service industry to uncover root causes of customer dissatisfaction, delays, and service breakdowns. Perform service improvement analysis with actionable insights for support teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fishbone Diagram Fundamentals for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Applying Fishbone Analysis in Business and Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Fishbone Diagrams for Service and Customer Experience Design\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Fishbone Diagram for Service Industry","description":"Use a fishbone diagram for service industry to uncover root causes of customer dissatisfaction, delays, and service breakdowns. Perform service improvement analysis with actionable insights for support teams.","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\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/","og_locale":"ja_JP","og_type":"article","og_title":"Fishbone Diagram for Service Industry","og_description":"Use a fishbone diagram for service industry to uncover root causes of customer dissatisfaction, delays, and service breakdowns. Perform service improvement analysis with actionable insights for support teams.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"6\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/","name":"Fishbone Diagram for Service Industry","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:26:51+00:00","description":"Use a fishbone diagram for service industry to uncover root causes of customer dissatisfaction, delays, and service breakdowns. Perform service improvement analysis with actionable insights for support teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/fishbone-diagram-service-industry\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Fishbone Diagram Fundamentals for Beginners","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Applying Fishbone Analysis in Business and Projects","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/fishbone-diagram-fundamentals-for-beginners\/fishbone-diagram-examples\/"},{"@type":"ListItem","position":4,"name":"Fishbone Diagrams for Service and Customer Experience Design"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/915","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/915\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/912"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=915"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}