{"id":1124,"date":"2026-02-25T10:36:05","date_gmt":"2026-02-25T10:36:05","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/"},"modified":"2026-03-02T09:12:12","modified_gmt":"2026-03-02T09:12:12","slug":"enterprise-user-stories-clarity-at-scale","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/","title":{"rendered":"Evolving User Story Practices in Large Enterprises"},"content":{"rendered":"<p>Too many teams assume that writing user stories gets easier when you scale \u2014 but the opposite is true. In large enterprises, stories that work well in a single team can become tangled, misaligned, or lost in translation across departments, programs, and systems. The real challenge isn\u2019t volume \u2014 it\u2019s coherence.<\/p>\n<p>Enterprise user stories aren\u2019t a new format. They\u2019re a new expectation: stories that must reflect not just one person\u2019s need, but the collective impact across multiple teams, stakeholders, and domains. The goal remains the same \u2014 deliver value \u2014 but the path requires discipline, structure, and transparency.<\/p>\n<p>I\u2019ve worked with product teams across banking, healthcare, and SaaS platforms where story clarity collapsed under the weight of siloed priorities. What I learned? A story that doesn\u2019t answer \u201cwho gains what, and why?\u201d fails \u2014 even if it\u2019s perfectly sized and estimated.<\/p>\n<p>This chapter guides you through practical strategies to maintain story quality and business alignment in complex environments. You\u2019ll learn how to apply governance without bureaucracy, scale storytelling without losing empathy, and ensure that every user story \u2014 regardless of where it lives in the backlog \u2014 still begins with a real person, a real goal, and a real reason.<\/p>\n<h2>Scaling Without Sacrificing Clarity<\/h2>\n<p>Agile frameworks like SAFe and LeSS help coordinate multiple teams, but they don\u2019t automatically solve story ambiguity. If your teams are writing stories that read like technical specs, or if acceptance criteria are never reviewed across teams, then scaling isn\u2019t helping \u2014 it\u2019s amplifying confusion.<\/p>\n<p>The key is not to abandon story format, but to embed it within a larger governance model that ensures consistency, traceability, and value alignment.<\/p>\n<h3>Adopt a Unified Story Format Across Teams<\/h3>\n<p>One of the most common failures in large-scale Agile is inconsistent story writing. A story in Team A might read: \u201cAs a user, I want to log in with my email,\u201d while Team B writes: \u201cLogin via email address \u2014 mandatory field.\u201d The difference isn\u2019t just style \u2014 it\u2019s purpose.<\/p>\n<p>Start by defining a <strong>standard story format<\/strong> that all teams must follow \u2014 not as a rigid rule, but as a shared language. Use:<\/p>\n<ul>\n<li><strong>As a [role], I want [functionality] so that [benefit]<\/strong><\/li>\n<li>Keep the \u201cso that\u201d clause tied to measurable impact \u2014 e.g., \u201cso that I can access my account within 3 seconds\u201d<\/li>\n<\/ul>\n<p>Enforce this not through audits, but through backlog refinement workshops where teams review and align stories together.<\/p>\n<h3>Use Story Governance to Preserve Value<\/h3>\n<p>Enterprise user stories require <strong>user story governance<\/strong> \u2014 a lightweight but structured approach to ensuring every story answers:<\/p>\n<ul>\n<li>Who is the user?<\/li>\n<li>What outcome does this drive?<\/li>\n<li>How does this connect to the product vision?<\/li>\n<li>Is it independent enough to be delivered by one team?<\/li>\n<\/ul>\n<p>Implement this via a <strong>story governance checklist<\/strong> that\u2019s reviewed during sprint planning and refinement.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Criteria<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Clear user role<\/td>\n<td>Prevents technical assumptions and ensures empathy<\/td>\n<\/tr>\n<tr>\n<td>Measurable outcome<\/td>\n<td>Enables verification and prioritization<\/td>\n<\/tr>\n<tr>\n<td>Traceable to epics or business goals<\/td>\n<td>Ensures alignment and impact tracking<\/td>\n<\/tr>\n<tr>\n<td>Independent of other stories<\/td>\n<td>Supports parallel delivery across teams<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t requirements \u2014 they\u2019re guardrails. When teams apply them consistently, stories become tools for conversation, not documents to check off.<\/p>\n<h2>Integrating Scaled Agile User Stories<\/h2>\n<p>Frameworks like SAFe and LeSS introduce new layers \u2014 PI planning, program increments, dependencies. But these don\u2019t replace user stories \u2014 they demand that they be <em>more<\/em> precise, not less.<\/p>\n<h3>Break Down Epics with Purpose<\/h3>\n<p>Large epics often get split based on technical boundaries: \u201cBackend login,\u201d \u201cFrontend form,\u201d \u201cAuthentication service.\u201d But that\u2019s not how users experience it.<\/p>\n<p>Instead, split epics along user journeys. For example, the epic \u201cUser Login and Access\u201d should be broken into stories like:<\/p>\n<ul>\n<li>As a customer, I want to sign in with my email so that I can access my dashboard within 2 seconds.<\/li>\n<li>As a customer, I want to reset my password via email so that I can regain access if I forget it.<\/li>\n<li>As a customer, I want to see my last login time so that I can verify my account\u2019s security.<\/li>\n<\/ul>\n<p>Each story now reflects a user need, not a system component \u2014 and that\u2019s what enables cross-team collaboration.<\/p>\n<h3>Align Stories Across Teams Using Value Streams<\/h3>\n<p>In large organizations, a single user journey often spans multiple teams. A purchase flow might involve inventory, payment, and shipping teams.<\/p>\n<p>To keep stories aligned, map the <strong>end-to-end value stream<\/strong> and break it into user stories that reflect the actual user experience. Then, assign ownership to each story based on which team owns the value \u2014 not just the code.<\/p>\n<p>For example:<\/p>\n<ul>\n<li>Story: \u201cAs a buyer, I want to see real-time inventory availability so that I don\u2019t place orders for unavailable items.\u201d<\/li>\n<li>Owned by: Inventory team<\/li>\n<li>Dependencies: Payment team\u2019s \u201cprocess order\u201d story<\/li>\n<\/ul>\n<p>This way, dependency tracking isn\u2019t reactive \u2014 it\u2019s built into the story.<\/p>\n<h2>Practical Strategies for Enterprise Story Quality<\/h2>\n<p>At scale, even well-formed stories can lose meaning. Here are four practices that made a real difference in enterprise settings.<\/p>\n<ol>\n<li><strong>Host cross-team story reviews before sprint planning<\/strong>. Have product owners and tech leads from adjacent teams co-review high-impact stories to flag ambiguity or misalignment.<\/li>\n<li><strong>Use \u201cas a\u201d role templates tied to personas<\/strong>. Create a shared persona library so teams don\u2019t default to vague roles like \u201cuser\u201d or \u201cadmin\u201d but instead reference real-world users (e.g., \u201cAs a hospital nurse, I want\u2026\u201d).<\/li>\n<li><strong>Define story acceptance criteria using behavior-driven examples<\/strong>. Instead of \u201cThe system must validate email,\u201d use: \u201cGiven I\u2019m on the login page, when I enter an invalid email, then I see a red error message.\u201d<\/li>\n<li><strong>Run quarterly story health checks<\/strong>. Review 10\u201315 top-performing stories to assess: Did they deliver value? Was the story clear? Did it align with business outcomes?<\/li>\n<\/ol>\n<p>These aren\u2019t just checklists \u2014 they\u2019re diagnostics. If a story fails the \u201cvalue test\u201d 3 out of 5 times, it\u2019s a signal that your team needs to retrain or reframe.<\/p>\n<h2>Common Pitfalls in Enterprise Story Writing<\/h2>\n<p>Even with the best intentions, enterprise user stories fall into traps. I\u2019ve seen teams:<\/p>\n<ul>\n<li>Write stories without a defined user \u2014 \u201cAs a system, I want to process requests.\u201d<\/li>\n<li>Split stories based on technical components, not user value.<\/li>\n<li>Use acceptance criteria that describe features, not outcomes.<\/li>\n<li>Leave story ownership undefined, leading to handoff delays.<\/li>\n<\/ul>\n<p>These aren\u2019t just bad habits \u2014 they\u2019re systemic risks. Fix them by anchoring every story to a real person and a real business goal.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I ensure enterprise user stories stay aligned across multiple teams?<\/h3>\n<p>Use a shared story framework and governance model. Hold regular cross-team refinement sessions, use a centralized backlog with clear epics and personas, and ensure each story links back to a business outcome.<\/p>\n<h3>Can I use story mapping in large enterprises?<\/h3>\n<p>Absolutely. Story mapping helps visualize user journeys across teams. Use it during PI planning to align all teams around a single user flow \u2014 even if the work is distributed.<\/p>\n<h3>What\u2019s the difference between a user story and a feature in an enterprise Agile context?<\/h3>\n<p>A user story describes a specific user need with a clear business outcome. A feature is a larger capability that may include multiple stories. Features are useful for grouping but should never replace the user-centric focus of stories.<\/p>\n<h3>How do I balance governance with agility in enterprise user stories?<\/h3>\n<p>Use lightweight governance: a shared format, a review checklist, and regular joint refinement. Avoid over-documenting. The goal isn\u2019t to approve stories \u2014 it\u2019s to ensure they\u2019re clear, valuable, and aligned.<\/p>\n<h3>What should I do if my team keeps writing technical stories?<\/h3>\n<p>Refrain from telling them \u201cjust write a user story.\u201d Instead, invite them to co-write with a business analyst or product owner. Use a simple prompt: \u201cWhat does the user gain? What changes in their experience?\u201d If the answer isn\u2019t about behavior or outcome, the story isn\u2019t user-focused.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many teams assume that writing user stories gets ea [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1121,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-1124","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>Enterprise User Stories: Clarity at Scale<\/title>\n<meta name=\"description\" content=\"Master enterprise user stories with practical techniques for clarity, governance, and scalability in large Agile environments. Learn how to maintain value and collaboration across teams using proven practices.\" \/>\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\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Enterprise User Stories: Clarity at Scale\" \/>\n<meta property=\"og:description\" content=\"Master enterprise user stories with practical techniques for clarity, governance, and scalability in large Agile environments. Learn how to maintain value and collaboration across teams using proven practices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:12:12+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\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\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/\",\"name\":\"Enterprise User Stories: Clarity at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:36:05+00:00\",\"dateModified\":\"2026-03-02T09:12:12+00:00\",\"description\":\"Master enterprise user stories with practical techniques for clarity, governance, and scalability in large Agile environments. Learn how to maintain value and collaboration across teams using proven practices.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Mastery and Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Evolving User Story Practices in Large Enterprises\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Enterprise User Stories: Clarity at Scale","description":"Master enterprise user stories with practical techniques for clarity, governance, and scalability in large Agile environments. Learn how to maintain value and collaboration across teams using proven practices.","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\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/","og_locale":"zh_CN","og_type":"article","og_title":"Enterprise User Stories: Clarity at Scale","og_description":"Master enterprise user stories with practical techniques for clarity, governance, and scalability in large Agile environments. Learn how to maintain value and collaboration across teams using proven practices.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","article_modified_time":"2026-03-02T09:12:12+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"6 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/","name":"Enterprise User Stories: Clarity at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:36:05+00:00","dateModified":"2026-03-02T09:12:12+00:00","description":"Master enterprise user stories with practical techniques for clarity, governance, and scalability in large Agile environments. Learn how to maintain value and collaboration across teams using proven practices.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/enterprise-user-stories-clarity-at-scale\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Mastery and Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/"},{"@type":"ListItem","position":4,"name":"Evolving User Story Practices in Large Enterprises"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1124","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1124\/revisions"}],"predecessor-version":[{"id":2419,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1124\/revisions\/2419"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1121"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=1124"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=1124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}