{"id":1778,"date":"2026-02-25T10:46:03","date_gmt":"2026-02-25T10:46:03","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/"},"modified":"2026-02-25T10:46:03","modified_gmt":"2026-02-25T10:46:03","slug":"multi-team-story-workshops","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/","title":{"rendered":"Facilitating Story Workshops in Multi-Team Settings"},"content":{"rendered":"<p>When I first led a story workshop across five teams, I expected alignment through shared documents. What I found instead was a cascade of assumptions, conflicting interpretations, and stories that failed acceptance because no one had actually discussed the real user needs. The biggest lesson? Alignment isn&#8217;t achieved by documenting requirements\u2014it&#8217;s built in real time, through dialogue.<\/p>\n<p>That moment taught me something fundamental: in large-scale Agile, story workshops must be less about reviewing work and more about creating shared understanding. The real challenge isn\u2019t volume\u2014it\u2019s coherence.<\/p>\n<p>This chapter gives you a field-tested framework for running story workshops that actually work across teams. You\u2019ll learn how to structure sessions that minimize friction, prevent dependency traps, and keep the focus on user value. These are not theoretical models\u2014they\u2019re methods I\u2019ve used in financial services, healthcare, and SaaS platforms where misalignment cost millions in wasted effort.<\/p>\n<p>By the end, you\u2019ll have actionable tools to run collaborative story writing sessions that reduce rework, improve estimation accuracy, and strengthen cross-team trust. No more siloed refinement. No more rework. Just shared understanding.<\/p>\n<h2>Preparing for the Workshop: The Foundation of Alignment<\/h2>\n<p>Start with intent, not agenda. A multi-team story workshop isn\u2019t a status meeting\u2014it\u2019s a collaborative design session. The goal isn\u2019t to decide what\u2019s in scope. It\u2019s to ensure everyone understands *why* it matters.<\/p>\n<p>Begin by identifying the story\u2019s **value objective**. Is it delivering a new onboarding flow? Enabling compliance reporting? Reducing latency for a critical system? Frame it as a business outcome, not a feature.<\/p>\n<p>Then, define the **workshop scope**: one story, one feature, or a cluster of related stories with overlapping dependencies. Don\u2019t try to cover more than three stories per session. Anything beyond that overwhelms the group and dilutes focus.<\/p>\n<p>Assign a facilitator from a team that has no ownership stake in the story. This prevents bias and ensures neutral leadership. The facilitator\u2019s role is to guide dialogue, not drive decisions.<\/p>\n<p>Ensure you have access to the following:<\/p>\n<ul>\n<li>A shared digital whiteboard<\/li>\n<li>Story templates pre-populated with fields: \u201cAs a\u2026 I want\u2026 so that\u2026\u201d<\/li>\n<li>Access to product backlog items, acceptance criteria, and dependency maps<\/li>\n<li>Real-time collaboration tools with voting or prioritization features<\/li>\n<\/ul>\n<p>Don\u2019t underestimate the power of a simple rule: only one person speaks at a time. This simple guardrail prevents dominance by a single voice and ensures quieter contributors are heard.<\/p>\n<h3>Pre-Workshop Checklist<\/h3>\n<p>Before the session, run through this checklist:<\/p>\n<ol>\n<li>Identify which teams must participate (only those with shared ownership or dependency)<\/li>\n<li>Share the story and acceptance criteria 24 hours in advance<\/li>\n<li>Confirm facilitator and timekeeper are assigned<\/li>\n<li>Set up a shared workspace with clear roles: writer, note-taker, timekeeper<\/li>\n<li>Define the decision-making threshold (e.g., consensus, majority, or SME sign-off)<\/li>\n<\/ol>\n<p>When these are in place, the workshop is not just prepared\u2014it\u2019s set up to succeed.<\/p>\n<h2>Running the Workshop: Dialogue Over Documentation<\/h2>\n<p>Start with silence. Give everyone 5 minutes to read the story and acceptance criteria independently. This prevents cognitive bias from groupthink.<\/p>\n<p>Then, ask: \u201cWhat does this story mean to you?\u201d Let each participant respond in turn, without interruption. Capture their thoughts on the shared board using sticky notes\u2014no editing, no summarizing.<\/p>\n<p>Look for patterns. If multiple people mention \u201csecurity\u201d or \u201ccompliance,\u201d that\u2019s a signal. If one team speaks of \u201cAPIs\u201d while another focuses on \u201cUI flow,\u201d there\u2019s a gap in understanding.<\/p>\n<p>Now, run a **What If?** exercise. Ask: \u201cWhat if the user is a third-party auditor? What if this runs on mobile only?\u201d Explore edge cases, failure modes, and boundary conditions. This is where collaboration shines\u2014it uncovers hidden risks before development starts.<\/p>\n<p>Next, assign roles:<\/p>\n<ul>\n<li><strong>Implementation Owner<\/strong>: who will build it<\/li>\n<li><strong>Validation Owner<\/strong>: who will test it<\/li>\n<li><strong>Deployment Owner<\/strong>: who will release it<\/li>\n<\/ul>\n<p>These roles don\u2019t need to be individuals\u2014they can be teams. But they must be named, and their responsibilities must be visible to all.<\/p>\n<p>Use the <strong>Three-Question Rule<\/strong>:<\/p>\n<ol>\n<li>What does the user actually need?<\/li>\n<li>How will we know it\u2019s done?<\/li>\n<li>What could go wrong?<\/li>\n<\/ol>\n<p>Answer each in turn. Capture responses directly on the board. This keeps the conversation focused on value, acceptance, and risk\u2014exactly where it belongs.<\/p>\n<h3>Facilitation Techniques That Work<\/h3>\n<p>Here are three story workshop methods that have proven effective across enterprise settings:<\/p>\n<ul>\n<li><strong>Rotating Roundtable<\/strong>: Each team shares one insight per round. No overlapping, no interruptions. Ensures even contribution and prevents dominance.<\/li>\n<li><strong>Dot Voting for Acceptance Criteria<\/strong>: After generating options, allow each participant to vote on the top 3 criteria. Clarifies what matters most to the group.<\/li>\n<li><strong>Story Mapping with Dependency Anchors<\/strong>: Map the story on a timeline, then mark where dependencies exist. Visualizing time and dependency together prevents misalignment.<\/li>\n<\/ul>\n<p>These aren\u2019t just techniques\u2014they\u2019re tools for building shared mental models. They work because they force people to speak, listen, and adjust in real time.<\/p>\n<h2>Managing Dependencies Without Stalling Flow<\/h2>\n<p>Dependencies are the silent killers of Agile flow. A story blocked by another team isn\u2019t just delayed\u2014it\u2019s now a risk.<\/p>\n<p>When you identify a dependency during a story workshop, immediately label it on the board as:<\/p>\n<ul>\n<li><strong>Blocked<\/strong>: needs action<\/li>\n<li><strong>Unconfirmed<\/strong>: needs validation<\/li>\n<li><strong>Confirmed<\/strong>: agreed, next steps defined<\/li>\n<\/ul>\n<p>Assign an owner to each dependency. This isn\u2019t bureaucracy\u2014it\u2019s accountability. If no one owns it, it won\u2019t get resolved.<\/p>\n<p>Use a <strong>Dependency Heatmap<\/strong> to track risk:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Dependency Type<\/th>\n<th>High Risk<\/th>\n<th>Medium Risk<\/th>\n<th>Low Risk<\/th>\n<\/tr>\n<tr>\n<td>Interface not defined<\/td>\n<td>\u274c<\/td>\n<td>\u26a0\ufe0f<\/td>\n<td>\u2714\ufe0f<\/td>\n<\/tr>\n<tr>\n<td>Timeline overlap<\/td>\n<td>\u26a0\ufe0f<\/td>\n<td>\u2714\ufe0f<\/td>\n<td>\u274c<\/td>\n<\/tr>\n<tr>\n<td>Shared data model<\/td>\n<td>\u274c<\/td>\n<td>\u26a0\ufe0f<\/td>\n<td>\u2714\ufe0f<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Review this heatmap at the start of each refinement session. It helps teams proactively address risks before they become roadblocks.<\/p>\n<p>Remember: dependency management isn\u2019t a task\u2014it\u2019s a practice. The goal isn\u2019t to eliminate all dependencies. It\u2019s to make them visible, manageable, and resolvable.<\/p>\n<h2>Post-Workshop: From Agreement to Action<\/h2>\n<p>Don\u2019t end the workshop with decisions. End with a clear path forward.<\/p>\n<p>Summarize the outcome in three parts:<\/p>\n<ol>\n<li><strong>What\u2019s agreed?<\/strong> List the final story text, acceptance criteria, and ownership roles.<\/li>\n<li><strong>What\u2019s pending?<\/strong> Name all open dependencies, unresolved questions, and assumptions.<\/li>\n<li><strong>Next steps?<\/strong> Define who does what, by when, and how progress will be reported.<\/li>\n<\/ol>\n<p>Share this summary in writing. Include links to the shared board and any supporting artifacts. Do not rely on memory.<\/p>\n<p>Assign a follow-up owner to track progress on pending items. This is not a second-level task\u2014it\u2019s part of the workshop outcome.<\/p>\n<p>After 48 hours, check in with all teams. Did the story move into the sprint? Were dependencies resolved? If not, why not?<\/p>\n<p>These short loops are where real agility lives\u2014not in ceremonies, but in consistent follow-through.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do you handle teams that don\u2019t show up to the story workshop?<\/h3>\n<p>First, understand why. If a team is missing due to conflicting timelines, reschedule the session. But if the gap is due to disengagement, treat it as a warning sign. Missing participation means missing alignment. At that point, pause the story until ownership is confirmed.<\/p>\n<h3>What if teams disagree on acceptance criteria?<\/h3>\n<p>Disagreement is not a problem\u2014it\u2019s data. Use a dot voting system to surface consensus. If no clear agreement emerges, escalate to a joint SME meeting. The goal isn\u2019t to force agreement\u2014it\u2019s to surface the root of misalignment.<\/p>\n<h3>How often should we run multi-team story workshops?<\/h3>\n<p>Not more than once per sprint. Too many workshops create fatigue. Instead, use the workshop to refine stories that will be in the next sprint. For ongoing stories, rely on regular refinement and dependency syncs.<\/p>\n<h3>Should I include non-technical stakeholders in story workshops?<\/h3>\n<p>Yes\u2014but with clear boundaries. Product owners, business analysts, and compliance officers bring essential context. But avoid inviting too many. A group of 6\u20138 members works best. If you need broader input, run a separate alignment session.<\/p>\n<h3>What\u2019s the difference between story refinement and story workshop?<\/h3>\n<p>Refinement is a routine, team-level activity. A story workshop is a cross-team, facilitator-led session focused on complex or high-risk stories. Think of it as a deep-dive for stories that span teams or involve significant risk.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first led a story workshop across five teams, I expected alignment through shared documents. What I fou [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1776,"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-1778","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>Multi-Team Story Workshops: Align &amp; Deliver at Scale<\/title>\n<meta name=\"description\" content=\"Master multi-team story workshops with proven facilitation methods and collaborative story writing techniques. Improve alignment, reduce rework, and sustain flow in large-scale Agile environments.\" \/>\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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Multi-Team Story Workshops: Align &amp; Deliver at Scale\" \/>\n<meta property=\"og:description\" content=\"Master multi-team story workshops with proven facilitation methods and collaborative story writing techniques. Improve alignment, reduce rework, and sustain flow in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/\" \/>\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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/\",\"name\":\"Multi-Team Story Workshops: Align & Deliver at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:46:03+00:00\",\"description\":\"Master multi-team story workshops with proven facilitation methods and collaborative story writing techniques. Improve alignment, reduce rework, and sustain flow in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Cross-Team Collaboration and Flow\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Facilitating Story Workshops in Multi-Team Settings\"}]},{\"@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":"Multi-Team Story Workshops: Align & Deliver at Scale","description":"Master multi-team story workshops with proven facilitation methods and collaborative story writing techniques. Improve alignment, reduce rework, and sustain flow in large-scale Agile environments.","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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/","og_locale":"ja_JP","og_type":"article","og_title":"Multi-Team Story Workshops: Align & Deliver at Scale","og_description":"Master multi-team story workshops with proven facilitation methods and collaborative story writing techniques. Improve alignment, reduce rework, and sustain flow in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/","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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/","name":"Multi-Team Story Workshops: Align & Deliver at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:46:03+00:00","description":"Master multi-team story workshops with proven facilitation methods and collaborative story writing techniques. Improve alignment, reduce rework, and sustain flow in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/multi-team-story-workshops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Cross-Team Collaboration and Flow","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/"},{"@type":"ListItem","position":4,"name":"Facilitating Story Workshops in Multi-Team Settings"}]},{"@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\/1778","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\/1778\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1776"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=1778"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=1778"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}