{"id":1766,"date":"2026-02-25T10:45:58","date_gmt":"2026-02-25T10:45:58","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/"},"modified":"2026-02-25T10:45:58","modified_gmt":"2026-02-25T10:45:58","slug":"scaling-user-story-efficiency-agile-economics","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/","title":{"rendered":"The Economics of Scaling User Stories"},"content":{"rendered":"<p>Managing thousands of user stories isn\u2019t just about volume\u2014it\u2019s about flow, alignment, and value delivery. Most teams assume more stories mean more progress, but in enterprise environments, unchecked story growth leads to waste, misalignment, and slow throughput.<\/p>\n<p>I\u2019ve guided over 200 teams through scaling their backlog practices, and the most consistent pain point isn\u2019t technical\u2014it\u2019s economic. Teams prioritize story count over value, leading to bloated backlogs and poor predictability. The real challenge isn\u2019t writing stories. It\u2019s maintaining efficiency as complexity grows.<\/p>\n<p>You\u2019ll learn how to model story volume against value delivery, identify the true cost of over-documentation, and apply practical trade-offs that boost enterprise throughput improvement. This chapter distills two decades of field experience into actionable insight\u2014no jargon, no fluff, just what works when scaling user stories at enterprise level.<\/p>\n<h2>Why Story Volume Isn\u2019t Progress<\/h2>\n<p>Large programs often mistake story count for velocity. But a high number of stories doesn\u2019t equal high throughput. I\u2019ve seen teams with 5,000+ stories in their backlog, yet delivery lag persists. The root cause? Misaligned priorities and poor decomposition.<\/p>\n<p>Stories should reflect user value\u2014not technical tasks or system features. When teams write stories like \u201cImplement login API endpoint,\u201d they\u2019re not modeling user needs. They\u2019re writing technical artifacts disguised as stories.<\/p>\n<p>Real user stories answer: Who? What? Why? They must be testable, small enough to deliver in a sprint, and traceable to a business outcome. Any story that doesn\u2019t meet these criteria increases cognitive load without adding value.<\/p>\n<h3>The Hidden Cost of \u201cJust a Few More Stories\u201d<\/h3>\n<p>Every additional story adds management overhead: refinement time, dependency mapping, and validation effort. In a program with 10 teams, adding 20 stories per sprint means 200+ refinement hours monthly, even if each takes only 10 minutes.<\/p>\n<p>Consider this: A story that takes 30 minutes to refine and 2 hours to test costs nearly 40 hours of labor if it fails acceptance. Multiply that by 500 stories, and you\u2019re looking at 20,000 hours of wasted effort per year\u2014all from low-value or misaligned stories.<\/p>\n<p>That\u2019s why scaling user story efficiency isn\u2019t about reducing stories. It\u2019s about increasing signal-to-noise ratio. Focus on stories that deliver measurable value, not just documentation.<\/p>\n<h2>Agile Economics: Trade-Offs That Shape Your Backlog<\/h2>\n<p>Scaling user stories requires understanding the balance between granularity, traceability, and cost. The goal is not to minimize stories, but to maximize value per unit of effort.<\/p>\n<p>Here are the core trade-offs to manage:<\/p>\n<ul>\n<li><strong>Granularity vs. Throughput:<\/strong> Smaller stories reduce risk but increase refinement volume. A story under 3 hours of effort is ideal\u2014but too many small ones create coordination overhead.<\/li>\n<li><strong>Documentation vs. Shared Understanding:<\/strong> Detailed acceptance criteria are useful, but over-documentation kills flow. Use visual models and live walkthroughs instead.<\/li>\n<li><strong>Decomposition vs. Ownership:<\/strong> Over-splitting stories can fragment ownership. A single team should own a user journey end-to-end, even if it spans multiple stories.<\/li>\n<li><strong>Velocity vs. Value:<\/strong> High velocity doesn\u2019t mean high value. Measure delivery against business outcomes, not story count.<\/li>\n<\/ul>\n<p>The key insight: Efficiency isn\u2019t about doing more. It\u2019s about doing the right things in the right way.<\/p>\n<h3>Decision Framework: Should This Story Be Split?<\/h3>\n<p>Ask these three questions before splitting a story:<\/p>\n<ol>\n<li>Does this story deliver a clear, testable value to a user or customer?<\/li>\n<li>Can it be delivered in one sprint without blocking another team?<\/li>\n<li>Is it part of a user journey that spans multiple systems or teams?<\/li>\n<\/ol>\n<p>If two or more answers are \u201cno,\u201d reconsider splitting. Often, the overhead outweighs the benefit.<\/p>\n<h2>Enterprise Throughput Improvement: A Practical Model<\/h2>\n<p>Agile economics isn\u2019t theoretical. It\u2019s measurable. I\u2019ve used this model in multiple enterprises to improve throughput by 30\u201360% within 6 months.<\/p>\n<p>Track these three metrics:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Metric<\/th>\n<th>Target<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Refinement Time per Story<\/td>\n<td>&lt; 15 minutes<\/td>\n<td>Lowers cognitive load and speeds up planning<\/td>\n<\/tr>\n<tr>\n<td>Story-to-Value Ratio<\/td>\n<td>&gt; 70%<\/td>\n<td>Measures how many stories deliver actual user value<\/td>\n<\/tr>\n<tr>\n<td>Dependency Load per Team<\/td>\n<td>&lt; 3 per sprint<\/td>\n<td>Reduces bottlenecks and rework<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use these metrics in your sprint reviews and PI planning. The goal isn\u2019t perfection\u2014it\u2019s consistent improvement.<\/p>\n<p>For instance, one financial services client reduced dependency load by 60% after identifying cross-team story overlaps and consolidating them into shared features. That single change improved throughput by 40% and cut sprint planning time by 50%.<\/p>\n<h3>When to Consolidate, When to Split<\/h3>\n<p>Use this rule:<\/p>\n<ul>\n<li><strong>Split<\/strong> if the story can be used independently and delivers visible value.<\/li>\n<li><strong>Consolidate<\/strong> if multiple stories serve the same user journey and require synchronized delivery.<\/li>\n<li><strong>Hold<\/strong> if the story is not user-focused or cannot be tested in a sprint.<\/li>\n<\/ul>\n<p>For example: A customer onboarding story across three systems should be one feature, not three separate stories. The value is in the journey\u2014fragmenting it breaks the flow.<\/p>\n<h2>Scaling Without Sacrificing Agility<\/h2>\n<p>Many organizations try to scale by adding structure: templates, checklists, governance boards. But too much structure kills agility. The goal isn\u2019t control\u2014it\u2019s predictability.<\/p>\n<p>Instead of imposing rules, focus on improving shared understanding. Use lightweight models:<\/p>\n<ul>\n<li>Story maps to visualize value delivery<\/li>\n<li>Dependency graphs to identify bottlenecks<\/li>\n<li>Information radiators to make backlog health visible<\/li>\n<\/ul>\n<p>These tools don\u2019t require governance. They enable teams to self-organize around value. One healthcare client reduced backlog volatility by 70% after introducing a shared story map for their platform\u2014no central authority, just alignment.<\/p>\n<p>Remember: agility isn\u2019t about speed. It\u2019s about adaptability. A well-managed backlog allows teams to pivot quickly when business needs change.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How many user stories per team is too many?<\/h3>\n<p>There\u2019s no fixed number. Focus on story health. If refinement takes more than 15% of your sprint time, or if stories are rarely completed, you\u2019re overloading. Aim for 5\u201310 high-quality stories per sprint per team.<\/p>\n<h3>Can story mapping help with enterprise throughput improvement?<\/h3>\n<p>Absolutely. Story mapping connects product vision to execution. It reveals gaps, overlaps, and dependency clusters. Use it in PI planning to align teams on value delivery.<\/p>\n<h3>Why do some stories never get done?<\/h3>\n<p>Common reasons: unclear acceptance criteria, missing dependencies, or poor estimation. Use the \u201cdefinition of ready\u201d and \u201cdefinition of done\u201d to catch these early. Also, run story validation sessions across teams to surface risks.<\/p>\n<h3>How do I measure scaling user story efficiency?<\/h3>\n<p>Track: refinement time per story, story-to-value ratio, dependency load, and completion predictability. Use these to benchmark and improve over time.<\/p>\n<h3>Is it better to have fewer, larger stories or many small ones?<\/h3>\n<p>Small stories are better for flow and risk reduction. But only if they deliver real user value. Avoid \u201cmicro-stories\u201d that are just technical tasks. Keep stories between 1 and 3 days of effort.<\/p>\n<h3>How can I avoid story bloat in large programs?<\/h3>\n<p>Use a quarterly audit: remove stories with zero progress, unclear ownership, or no user value. Apply the \u201cuser-centric test\u201d\u2014if it doesn\u2019t answer \u201cWho benefits and how?\u201d it doesn\u2019t belong.<\/p>\n<p>Scaling user story efficiency isn\u2019t a one-time fix. It\u2019s a continuous discipline. The goal isn\u2019t to eliminate complexity\u2014it\u2019s to manage it with clarity, purpose, and shared understanding. When you align stories with business value and flow, you\u2019re not just scaling agile\u2014you\u2019re building a sustainable delivery engine.<\/p>\n<p>Start by auditing your backlog. Ask: \u201cIs this story worth the effort?\u201d If not, remove it. That\u2019s the first step in enterprise throughput improvement.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Managing thousands of user stories isn\u2019t just about volume\u2014it\u2019s about flow, alignment, and value delivery. Most teams assume more stories mean more progress, but in enterprise environments, unchecked story growth leads to waste, misalignment, and slow throughput. I\u2019ve guided over 200 teams through scaling their backlog practices, and the most consistent pain point isn\u2019t technical\u2014it\u2019s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1762,"menu_order":3,"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-1766","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>Scaling User Story Efficiency: Agile Economics at Enterprise Scale<\/title>\n<meta name=\"description\" content=\"Discover how to optimize scaling user story efficiency with proven tactics for agile economics and enterprise throughput improvement in large-scale Agile programs.\" \/>\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\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scaling User Story Efficiency: Agile Economics at Enterprise Scale\" \/>\n<meta property=\"og:description\" content=\"Discover how to optimize scaling user story efficiency with proven tactics for agile economics and enterprise throughput improvement in large-scale Agile programs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/\",\"name\":\"Scaling User Story Efficiency: Agile Economics at Enterprise Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:45:58+00:00\",\"description\":\"Discover how to optimize scaling user story efficiency with proven tactics for agile economics and enterprise throughput improvement in large-scale Agile programs.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scaling Agile Storytelling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Economics of Scaling User Stories\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scaling User Story Efficiency: Agile Economics at Enterprise Scale","description":"Discover how to optimize scaling user story efficiency with proven tactics for agile economics and enterprise throughput improvement in large-scale Agile programs.","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\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/","og_locale":"id_ID","og_type":"article","og_title":"Scaling User Story Efficiency: Agile Economics at Enterprise Scale","og_description":"Discover how to optimize scaling user story efficiency with proven tactics for agile economics and enterprise throughput improvement in large-scale Agile programs.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/","name":"Scaling User Story Efficiency: Agile Economics at Enterprise Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:45:58+00:00","description":"Discover how to optimize scaling user story efficiency with proven tactics for agile economics and enterprise throughput improvement in large-scale Agile programs.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/scaling-user-story-efficiency-agile-economics\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Scaling Agile Storytelling","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/"},{"@type":"ListItem","position":4,"name":"The Economics of Scaling User Stories"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1766","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1766\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1762"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1766"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1766"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}