{"id":683,"date":"2026-02-25T10:22:46","date_gmt":"2026-02-25T10:22:46","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/"},"modified":"2026-02-25T10:22:46","modified_gmt":"2026-02-25T10:22:46","slug":"user-story-without-business-value","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/","title":{"rendered":"No Link to Business Value"},"content":{"rendered":"<p>At the heart of every effective user story is a single truth: it must deliver value. I\u2019ve seen teams spend hours refining a story that technically checks all boxes\u2014clear role, defined action, testable acceptance criteria\u2014but still fail to resonate with the product\u2019s real purpose. The moment you start writing stories that only describe functionality, not benefit, you\u2019re already off track.<\/p>\n<p>Every time a story is written without a clear connection to business or user value, you risk building something that no one actually needs. This is not a minor oversight\u2014it\u2019s a strategic misalignment that compounds over sprints. The real danger? The team finishes the work, delivers the feature, and the product owner realizes it doesn\u2019t move the needle.<\/p>\n<p>What you\u2019ll learn here isn\u2019t just about rewriting a sentence. You\u2019ll learn how to test each story for value, how to pivot from \u201cwhat\u201d to \u201cwhy,\u201d and how to embed value reasoning into your team\u2019s daily rhythm. This is practical guidance from over two decades of working with product teams across startups, enterprises, and government digital transformations.<\/p>\n<h2>Why Business Value Is the Heart of Every Story<\/h2>\n<p>Agile isn\u2019t about speed. It\u2019s about delivering what matters. A story without business value becomes a technical chore masked as a user need. It may be technically correct, testable, and well-formed\u2014but it doesn\u2019t serve the user, nor does it contribute to a business objective.<\/p>\n<p>I once worked with a fintech team building a dashboard. The story read: \u201cAs a user, I want to see transaction history in a table.\u201d That\u2019s a valid action\u2014but it\u2019s not a story. It\u2019s a UI task. The real value? \u201cSo that I can track my spending and identify unusual activity.\u201d That\u2019s where the benefit lives.<\/p>\n<p>Without that \u201cso that\u201d clause tied to a real user or business outcome, you\u2019re not writing a story\u2014you\u2019re writing a specification.<\/p>\n<h3>The Hidden Cost of Functionality-Only Stories<\/h3>\n<p>Stories without business value lead to:<\/p>\n<ul>\n<li>Wasted sprint capacity on features no one uses.<\/li>\n<li>Missed opportunities for innovation because teams focus on output, not impact.<\/li>\n<li>Backlog bloat\u2014stories that never get prioritized because they don\u2019t solve a problem.<\/li>\n<li>Product owner frustration, as they can\u2019t justify effort to stakeholders.<\/li>\n<\/ul>\n<p>Here\u2019s a real example from a healthcare platform: \u201cAs a doctor, I want to save patient notes in a database.\u201d The team built it. It worked. But after launch, 87% of doctors never used it. Why? Because the real need wasn\u2019t saving data\u2014it was accessing it quickly during appointments, or getting alerts for critical updates. That\u2019s where value was.<\/p>\n<h2>How to Fix a Story Without Business Value<\/h2>\n<p>Reframing a story to include business value isn\u2019t about adding words. It\u2019s about shifting your mindset from \u201ctask\u201d to \u201cpurpose.\u201d Use this simple but powerful framework:<\/p>\n<ol>\n<li><strong>Start with the user.<\/strong> Who is this for? Be specific\u2014\u201ca nurse in an ICU,\u201d not \u201ca healthcare worker.\u201d<\/li>\n<li><strong>Clarify the action.<\/strong> What should they be able to do? Be precise.<\/li>\n<li><strong>State the value.<\/strong> Why does this matter? Link it to a measurable outcome.<\/li>\n<\/ol>\n<p>Let\u2019s walk through a before-and-after example:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Before (Functionality-Only)<\/th>\n<th>After (Value-Oriented)<\/th>\n<\/tr>\n<tr>\n<td>As a customer, I want to filter search results by price.<\/td>\n<td>As a customer, I want to filter search results by price so I can find products I can actually afford.<\/td>\n<\/tr>\n<tr>\n<td>As an admin, I want to export user data to CSV.<\/td>\n<td>As an admin, I want to export user data to CSV so I can analyze retention trends monthly.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Notice the difference? The second version doesn\u2019t just say what happens\u2014it explains why it matters. It\u2019s not just about the feature. It\u2019s about the outcome.<\/p>\n<h3>Ask: \u201cWhat Changes When This Story Is Done?\u201d<\/h3>\n<p>Use this question during refinement: \u201cIf this story is delivered, what changes for the user or business?\u201d If the answer is vague\u2014\u201cIt improves the system,\u201d \u201cIt makes it faster\u201d\u2014you\u2019re still stuck in functionality mode.<\/p>\n<p>Push further: \u201cWhat\u2019s the measurable impact?\u201d \u201cHow does this affect revenue, retention, or efficiency?\u201d If you can\u2019t answer, you\u2019re not writing a value-oriented story.<\/p>\n<h2>Practical Techniques for Value-Driven Story Writing<\/h2>\n<p>Here are three techniques I use with teams to embed business value from the start:<\/p>\n<h3>1. The \u201cSo That\u201d Clause Drill<\/h3>\n<p>During backlog refinement, every story must include a \u201cso that\u201d clause. If it\u2019s missing, pause. Ask: \u201cWhat\u2019s the purpose?\u201d If the answer is \u201cto improve the UI\u201d or \u201cto make it easier to use,\u201d dig deeper: \u201cEasier for whom? And easier at what cost?\u201d<\/p>\n<p>Replace vague \u201cimprovements\u201d with outcomes: \u201cso that users can complete checkout in under 30 seconds.\u201d That\u2019s measurable. That\u2019s valuable.<\/p>\n<h3>2. The Value Hypothesis Template<\/h3>\n<p>Use this template during story creation:<\/p>\n<pre><code>As a [user type],\nI want [action or feature],\nso that [specific business or user benefit].\n(And if successful, we expect [measurable outcome].)<\/code><\/pre>\n<p>For example:<\/p>\n<pre><code>As a customer who shops weekly,\nI want to receive a weekly summary of my purchases,\nso that I can spot spending patterns and adjust my budget.\n(And if successful, we expect a 15% increase in budget feature usage.)<\/code><\/pre>\n<p>This format forces clarity and accountability. It turns stories into experiments with testable outcomes.<\/p>\n<h3>3. Prioritize by Value, Not Ease<\/h3>\n<p>I\u2019ve seen teams prioritize stories based on \u201ceasiest to build\u201d or \u201cquick win.\u201d But that\u2019s backwards. The most impactful stories aren\u2019t always the simplest. The real value lies in solving high-impact problems.<\/p>\n<p>Use this simple scoring model to filter stories:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Factor<\/th>\n<th>Weight<\/th>\n<th>Scoring (1\u20135)<\/th>\n<\/tr>\n<tr>\n<td>Business impact (revenue, retention, user satisfaction)<\/td>\n<td>40%<\/td>\n<td>5<\/td>\n<\/tr>\n<tr>\n<td>User effort reduction<\/td>\n<td>30%<\/td>\n<td>4<\/td>\n<\/tr>\n<tr>\n<td>Technical complexity<\/td>\n<td>20%<\/td>\n<td>3<\/td>\n<\/tr>\n<tr>\n<td>Alignment with roadmap<\/td>\n<td>10%<\/td>\n<td>4<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Score each story. The higher the total, the more likely it delivers real value. This isn\u2019t just theory\u2014this is how teams I\u2019ve mentored have reduced backlog waste by up to 40%.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with intent, teams fall into traps. Here\u2019s what to watch for:<\/p>\n<ul>\n<li><strong>Confusing \u201cfeature\u201d with \u201cbenefit.\u201d<\/strong> \u201cI want a search bar\u201d \u2260 \u201cI want to find products fast.\u201d One is input, the other is outcome.<\/li>\n<li><strong>Using abstract value statements.<\/strong> \u201cSo that the business can grow\u201d is too vague. Tie value to a goal: \u201cso that we can increase customer retention by 10% in Q3.\u201d<\/li>\n<li><strong>Letting stakeholders define value.<\/strong> Product owners must drive value, not just accept requests. If a stakeholder says \u201cI want a new button,\u201d ask: \u201cWhat problem does it solve?\u201d<\/li>\n<li><strong>Assuming value is self-evident.<\/strong> Just because a feature seems useful doesn\u2019t mean it is. Test it with users. Validate the assumption.<\/li>\n<\/ul>\n<h2>Building a Culture of Value-Oriented Story Writing<\/h2>\n<p>Value isn\u2019t a one-off fix. It\u2019s a team habit.<\/p>\n<p>Start every sprint planning with a \u201cvalue check\u201d: \u201cWhat\u2019s the top benefit this story delivers?\u201d Tie acceptance criteria directly to that outcome. If a story passes acceptance testing but doesn\u2019t move the needle\u2014flag it. Review it in the retrospective.<\/p>\n<p>Make \u201cvalue\u201d part of your Definition of Ready. A story isn\u2019t ready until someone can explain its business or user impact. This isn\u2019t bureaucracy\u2014it\u2019s discipline.<\/p>\n<p>And if a story can\u2019t be justified by value? It shouldn\u2019t be built. Period.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Why does my team keep writing stories without business value?<\/h3>\n<p>Because they\u2019re trained to think in features, not outcomes. The team may have no explicit practice for verifying value. Introduce the \u201cso that\u201d rule and a simple value checklist during refinement. It takes 2\u20133 sprints to stick.<\/p>\n<h3>Can a technical story have business value?<\/h3>\n<p>Yes\u2014but only if it enables a user-facing outcome. For example: \u201cAs a developer, I want to improve API response time so that users don\u2019t experience delays during peak hours.\u201d That\u2019s valid because it links technical work to user experience.<\/p>\n<h3>How do I convince the product owner to focus on value?<\/h3>\n<p>Use data. Show them how stories without value get deprioritized or abandoned. Then run a small experiment: pick one story, reframe it with a clear benefit, and measure if it gets faster approval or higher priority.<\/p>\n<h3>What if the business doesn\u2019t define value clearly?<\/h3>\n<p>That\u2019s your job. Ask: \u201cWhat\u2019s the goal of this feature?\u201d \u201cWho benefits?\u201d \u201cHow will we know it worked?\u201d If the answer is \u201cwe\u2019ll see,\u201d push back. Value must be measurable, even if it\u2019s qualitative\u2014e.g., \u201cusers feel more in control.\u201d<\/p>\n<h3>How do I handle stories that seem valuable but are actually redundant?<\/h3>\n<p>Use story mapping to visualize the user journey. If two stories solve the same problem in different ways, merge them. Ask: \u201cWhich one delivers the better outcome?\u201d If both are needed, break them into phases: \u201cPhase 1: deliver core benefit, Phase 2: enhance based on feedback.\u201d<\/p>\n<h3>Can value be negative?<\/h3>\n<p>Yes. \u201cSo that users don\u2019t get distracted by too many options\u201d is a valid value\u2014reducing cognitive load. But it must still be tied to a measurable outcome: \u201cso that 80% of users complete the form in under 2 minutes.\u201d<\/p>\n<p><strong>Remember:<\/strong> A story is not a task. It\u2019s a conversation about value. If you can\u2019t explain why it matters, it shouldn\u2019t be built.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At the heart of every effective user story is a single truth: it must deliver value. I\u2019ve seen teams spend hours refining a story that technically checks all boxes\u2014clear role, defined action, testable acceptance criteria\u2014but still fail to resonate with the product\u2019s real purpose. The moment you start writing stories that only describe functionality, not [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":682,"menu_order":0,"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-683","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>User Story Without Business Value<\/title>\n<meta name=\"description\" content=\"Fix the #1 mistake in user story writing: lack of business value. Learn how to write value-oriented stories that deliver real impact and align with agile goals.\" \/>\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\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Without Business Value\" \/>\n<meta property=\"og:description\" content=\"Fix the #1 mistake in user story writing: lack of business value. Learn how to write value-oriented stories that deliver real impact and align with agile goals.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/\" \/>\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=\"8 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\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/\",\"name\":\"User Story Without Business Value\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:22:46+00:00\",\"description\":\"Fix the #1 mistake in user story writing: lack of business value. Learn how to write value-oriented stories that deliver real impact and align with agile goals.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Strategic and Conceptual Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"No Link to Business Value\"}]},{\"@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":"User Story Without Business Value","description":"Fix the #1 mistake in user story writing: lack of business value. Learn how to write value-oriented stories that deliver real impact and align with agile goals.","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\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/","og_locale":"id_ID","og_type":"article","og_title":"User Story Without Business Value","og_description":"Fix the #1 mistake in user story writing: lack of business value. Learn how to write value-oriented stories that deliver real impact and align with agile goals.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"8 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/","name":"User Story Without Business Value","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:22:46+00:00","description":"Fix the #1 mistake in user story writing: lack of business value. Learn how to write value-oriented stories that deliver real impact and align with agile goals.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-story-without-business-value\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Strategic and Conceptual Errors","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/"},{"@type":"ListItem","position":4,"name":"No Link to Business Value"}]},{"@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\/683","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\/683\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/682"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=683"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}