{"id":687,"date":"2026-02-25T10:22:48","date_gmt":"2026-02-25T10:22:48","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/"},"modified":"2026-02-25T10:22:48","modified_gmt":"2026-02-25T10:22:48","slug":"fixing-untestable-user-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/","title":{"rendered":"Writing Stories That Can\u2019t Be Tested"},"content":{"rendered":"<p>A user story that can\u2019t be tested is a story that has already failed. I\u2019ve seen teams commit to features that no one can verify, only to discover weeks later that the outcome didn\u2019t match the intent. The root cause? Vague acceptance criteria. The fix? Rewriting with concrete, testable conditions.<\/p>\n<p>Testability isn\u2019t a bonus\u2014it\u2019s the baseline. If a story can\u2019t be tested, it can\u2019t be delivered. I\u2019ve worked with teams who thought \u201cI\u2019ll know it when I see it\u201d was enough. It\u2019s not. The moment you say that, you\u2019ve invited ambiguity, rework, and misaligned expectations.<\/p>\n<p>This chapter shows you how to diagnose a story that can\u2019t be tested, rewrite it using criteria-based story writing, and ensure test scenario coverage from day one. You\u2019ll learn how to define acceptance not as a wish, but as a contract.<\/p>\n<h2>Why stories become untestable<\/h2>\n<p>Untestable stories aren\u2019t born\u2014they\u2019re built. They start with a vague goal, a fuzzy \u201cI want it to work,\u201d and a lack of shared understanding. The problem isn\u2019t the story format. It\u2019s the absence of measurable outcomes.<\/p>\n<p>When acceptance conditions are missing or ambiguous, developers guess. QA tests become heuristic. The product owner can\u2019t say \u201cyes\u201d or \u201cno.\u201d The team ships something that doesn\u2019t solve the real problem.<\/p>\n<p>Here\u2019s a common pattern: a story says \u201cThe system should be fast.\u201d That\u2019s not testable. Speed is relative. What\u2019s fast? 1 second? 500ms? On what device? With what load?<\/p>\n<p>Another red flag: stories that rely on subjective terms like \u201cuser-friendly,\u201d \u201cseamless,\u201d or \u201cintuitive.\u201d These may describe experience, but they can\u2019t be tested. A story must define success in objective, observable terms.<\/p>\n<h3>Common traits of untestable user stories<\/h3>\n<ul>\n<li>Uses vague verbs: \u201cimprove,\u201d \u201cenhance,\u201d \u201coptimize\u201d<\/li>\n<li>Relies on subjective adjectives: \u201ceasy,\u201d \u201cfast,\u201d \u201cbeautiful\u201d<\/li>\n<li>Lacks measurable outcomes or acceptance criteria<\/li>\n<li>Describes behavior but not the expected result<\/li>\n<li>Implies a feature without defining what \u201cworking\u201d means<\/li>\n<\/ul>\n<h2>How to rewrite untestable stories with testable acceptance<\/h2>\n<p>Every user story must answer one question: \u201cHow will we know it\u2019s done?\u201d If you can\u2019t answer that, the story isn\u2019t testable.<\/p>\n<p>Start by asking: \u201cWhat does success look like?\u201d Then write it down. Use the <strong>Given-When-Then<\/strong> format to structure testable acceptance criteria.<\/p>\n<p>Here\u2019s a real example from my experience: a team wrote:<\/p>\n<pre><code>As a user, I want the dashboard to load quickly so I can see my data.<\/code><\/pre>\n<p>That\u2019s untestable. Now, here\u2019s how we fixed it:<\/p>\n<h3>Step-by-step rewrite using criteria-based story writing<\/h3>\n<ol>\n<li><strong>Identify the core behavior<\/strong>: The dashboard must load after a user logs in.<\/li>\n<li><strong>Define measurable outcomes<\/strong>: Load time must be under 2 seconds on a standard desktop.<\/li>\n<li><strong>Create acceptance criteria using Given-When-Then<\/strong>:\n<ul>\n<li><strong>Given<\/strong> the user is logged in and on the dashboard page,<\/li>\n<li><strong>When<\/strong> the page loads,<\/li>\n<li><strong>Then<\/strong> the total load time must be less than 2 seconds.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Validate testability<\/strong>: Can a QA engineer run this test? Yes. Is the threshold clear? Yes.<\/li>\n<\/ol>\n<p>This version is now testable. It allows for precise measurement, automated testing, and clear pass\/fail logic.<\/p>\n<h3>Key principles for testable acceptance criteria<\/h3>\n<ul>\n<li><strong>Be specific, not broad<\/strong>: \u201cShow all data\u201d \u2192 \u201cDisplay at least 100 rows of transaction history.\u201d<\/li>\n<li><strong>Use clear metrics<\/strong>: \u201cFast\u201d \u2192 \u201cunder 1.5 seconds,\u201d \u201cmany\u201d \u2192 \u201cat least 5 items.\u201d<\/li>\n<li><strong>Focus on observable results<\/strong>: \u201cThe user gets help\u201d \u2192 \u201cThe help modal appears within 0.5 seconds of clicking the help icon.\u201d<\/li>\n<li><strong>Separate functionality from experience<\/strong>: \u201cThe system feels responsive\u201d is not a testable condition. \u201cThe button changes color within 0.1 seconds of hover\u201d is.<\/li>\n<\/ul>\n<h2>Checklist: Is your story testable?<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Check<\/th>\n<th>Yes\/No<\/th>\n<th>Why?<\/th>\n<\/tr>\n<tr>\n<td>Does the story state a measurable outcome?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<td>Example: \u201cLoad in under 2 seconds.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Are acceptance criteria written in Given-When-Then format?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<td>Helps structure testable scenarios.<\/td>\n<\/tr>\n<tr>\n<td>Could a tester execute this without asking for clarification?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<td>If yes, it\u2019s testable.<\/td>\n<\/tr>\n<tr>\n<td>Does the story avoid subjective terms like \u201ceasy,\u201d \u201cfast,\u201d \u201cnice\u201d?<\/td>\n<td><input type=\"checkbox\"><\/td>\n<td>Subjective language = untestable.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Trade-offs in testability and practicality<\/h2>\n<p>Not every acceptance must be automated. But every acceptance must be testable. The goal isn\u2019t automation\u2014it\u2019s verification.<\/p>\n<p>Some teams over-engineer acceptance criteria with micro-conditions. That leads to bloated, fragile tests. The sweet spot? Focus on the <strong>critical path<\/strong> of validation.<\/p>\n<p>Ask: \u201cIf this fails, will the user be blocked?\u201d If yes, it needs a test. If no, maybe it\u2019s a nice-to-have and can be verified manually.<\/p>\n<p>Here\u2019s a real-world trade-off: a story says \u201cThe form should validate inputs.\u201d That\u2019s vague. But \u201cWhen the user submits the form with an invalid email, an error message appears in red text within 0.3 seconds\u201d is testable and actionable.<\/p>\n<p>Don\u2019t confuse complexity with comprehensiveness. Testable doesn\u2019t mean detailed. It means clear, objective, and repeatable.<\/p>\n<h2>Integrating test scenario coverage into story writing<\/h2>\n<p>Test scenario coverage is not a QA task\u2014it\u2019s a team responsibility. Every story should come with at least one testable scenario that covers the main success condition.<\/p>\n<p>Use this simple rule: For every story, ask, \u201cWhat\u2019s the one test that proves it\u2019s working?\u201d If you can\u2019t name it, the story isn\u2019t ready.<\/p>\n<p>Here\u2019s how to embed coverage early:<\/p>\n<ol>\n<li><strong>Write acceptance criteria during story creation<\/strong>, not after.<\/li>\n<li><strong>Review with QA from day one<\/strong>. They\u2019ll spot gaps.<\/li>\n<li><strong>Use the \u201cthree amigos\u201d session<\/strong> to align on what \u201cdone\u201d means.<\/li>\n<li><strong>Mark stories as \u201ctestable\u201d in the backlog<\/strong>\u2014no exceptions.<\/li>\n<\/ol>\n<p>Teams that skip this step pay the cost in rework, late defects, and missed sprints. The fix isn\u2019t more effort\u2014it\u2019s better upfront clarity.<\/p>\n<h2>Real-world example: From untestable to testable<\/h2>\n<p>Original (untestable):<\/p>\n<pre><code>As a customer, I want the payment system to work so I can complete my purchase.<\/code><\/pre>\n<p>Issues: \u201cWork\u201d is undefined. No metric. No behavior.<\/p>\n<p>Revised (testable):<\/p>\n<pre><code>As a customer, I want to complete a payment so that I can receive immediate confirmation.\n\nAcceptance Criteria:\n- Given I\u2019m on the checkout page,\n- When I click \u201cPay Now\u201d with valid credit card details,\n- Then the system must display \u201cPayment successful\u201d within 2 seconds.\n- And the order status must change to \u201cConfirmed\u201d in the database.\n- And I must receive a confirmation email within 1 minute.<\/code><\/pre>\n<p>Now, every part is testable. The team knows exactly what to build and how to verify it.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if a story is testable?<\/h3>\n<p>Ask: Can a tester run a test based on this? If yes, and it has a clear pass\/fail condition, it\u2019s testable. If the answer depends on opinion, it\u2019s not.<\/p>\n<h3>What if the acceptance criteria are too complex?<\/h3>\n<p>Break it into smaller, focused scenarios. One story, one main test case. Use multiple criteria to cover edge cases, but keep the primary condition simple.<\/p>\n<h3>Should acceptance criteria be automated?<\/h3>\n<p>Not every one. But every testable criterion should be automatable if possible. Automation isn\u2019t the goal\u2014verification is. If a test can be run reliably, automate it.<\/p>\n<h3>Who should write acceptance criteria?<\/h3>\n<p>Collaboratively. The product owner defines the goal, the developer defines feasibility, and QA verifies testability. The three amigos should review together.<\/p>\n<h3>Can a story be testable without automation?<\/h3>\n<p>Yes. Testability means the outcome can be verified. Automation improves speed and consistency, but a manual test with clear steps counts as testable.<\/p>\n<h3>How do I teach my team to write testable stories?<\/h3>\n<p>Start with examples. Show bad vs good versions. Run workshops where teams rewrite untestable stories. Use the checklist above. Make testability a non-negotiable part of Definition of Ready.<\/p>\n<h2>Final takeaway<\/h2>\n<p>Untestable user stories are the most expensive kind. They promise value but deliver uncertainty. The fix is simple: write acceptance criteria that are specific, measurable, and verifiable. Use criteria-based story writing and ensure test scenario coverage from day one.<\/p>\n<p>When every story can be tested, teams ship faster, with fewer defects, and with confidence. That\u2019s not a dream. It\u2019s the reality of disciplined Agile.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A user story that can\u2019t be tested is a story that has already failed. I\u2019ve seen teams commit to features that  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":682,"menu_order":4,"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-687","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>Fixing untestable user stories<\/title>\n<meta name=\"description\" content=\"Learn how to identify and rewrite untestable user stories with test scenario coverage and criteria-based story writing to ensure every story can be validated in Agile development.\" \/>\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\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fixing untestable user stories\" \/>\n<meta property=\"og:description\" content=\"Learn how to identify and rewrite untestable user stories with test scenario coverage and criteria-based story writing to ensure every story can be validated in Agile development.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/\" \/>\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=\"7\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\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/\",\"name\":\"Fixing untestable user stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:22:48+00:00\",\"description\":\"Learn how to identify and rewrite untestable user stories with test scenario coverage and criteria-based story writing to ensure every story can be validated in Agile development.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Strategic and Conceptual Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Writing Stories That Can\u2019t Be Tested\"}]},{\"@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":"Fixing untestable user stories","description":"Learn how to identify and rewrite untestable user stories with test scenario coverage and criteria-based story writing to ensure every story can be validated in Agile development.","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\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/","og_locale":"ja_JP","og_type":"article","og_title":"Fixing untestable user stories","og_description":"Learn how to identify and rewrite untestable user stories with test scenario coverage and criteria-based story writing to ensure every story can be validated in Agile development.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/","name":"Fixing untestable user stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:22:48+00:00","description":"Learn how to identify and rewrite untestable user stories with test scenario coverage and criteria-based story writing to ensure every story can be validated in Agile development.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/fixing-untestable-user-stories\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Strategic and Conceptual Errors","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/"},{"@type":"ListItem","position":4,"name":"Writing Stories That Can\u2019t Be Tested"}]},{"@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\/687","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\/687\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/682"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=687"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=687"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}