{"id":783,"date":"2026-02-25T10:24:33","date_gmt":"2026-02-25T10:24:33","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/"},"modified":"2026-02-25T10:24:33","modified_gmt":"2026-02-25T10:24:33","slug":"crc-for-business-modeling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/","title":{"rendered":"Adapting CRC Concepts to Business or UX Modeling"},"content":{"rendered":"<p>Too many teams start business process modeling with swimlanes and flowcharts, treating roles and systems as static boxes to be connected. It\u2019s a common trap: these diagrams look structured but often miss the real issue \u2014 who is *responsible* for what, and what do they *do* when they collaborate? That\u2019s where CRC for business modeling shifts the focus from \u201cwhat happens\u201d to \u201cwho does what.\u201d<\/p>\n<p>After years of facilitating design sessions across software, finance, and healthcare teams, I\u2019ve seen the same pattern: confusion arises not from complexity, but from vague responsibility assignment. CRC cards, even in non-software contexts, offer a lightweight yet powerful way to clarify who owns what \u2014 not just in code, but in real business processes and user experiences.<\/p>\n<p>This chapter will show you how to apply CRC thinking outside of code. You\u2019ll learn how to translate business roles into classes, define actionable responsibilities, and identify critical handoffs between departments or UX states \u2014 all while keeping the model simple, collaborative, and grounded in real decision-making.<\/p>\n<h2>Why CRC Works Beyond Code<\/h2>\n<p>Traditional business modeling often focuses on *what* happens: \u201cThe invoice is reviewed,\u201d \u201cThe form is submitted.\u201d But what if we asked: \u201cWho is responsible for reviewing the invoice?\u201d and \u201cWhat does that person actually *do*?\u201d That shift \u2014 from process steps to responsible agents \u2014 is where CRC shines.<\/p>\n<p>When you use CRC for business modeling, you&#8217;re not just diagramming workflows. You&#8217;re modeling responsibility allocation, handoffs, and decision points. This is especially powerful in cross-functional teams where boundaries blur and ownership is ambiguous.<\/p>\n<p>Consider a loan approval process. A flowchart might show: \u201cApplication \u2192 Review \u2192 Approval \u2192 Disbursement.\u201d But with CRC, you define actual roles: <strong>Loan Officer<\/strong>, <strong>Underwriter<\/strong>, <strong>Compliance Analyst<\/strong>. Each becomes a class with clear responsibilities.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>Loan Officer<\/strong>: Collects applicant documents. Explains loan terms. Submits application.<\/li>\n<li><strong>Underwriter<\/strong>: Assesses creditworthiness. Verifies income. Makes approval recommendation.<\/li>\n<li><strong>Compliance Analyst<\/strong>: Checks regulatory requirements. Flags high-risk cases. Signs off on compliance.<\/li>\n<\/ul>\n<p>Now the workflow isn\u2019t just a sequence \u2014 it\u2019s a chain of responsibilities with defined handoffs.<\/p>\n<h3>From Flowchart to Responsibility Map<\/h3>\n<p>Here\u2019s how to convert a standard process diagram into a CRC-based model:<\/p>\n<ol>\n<li><strong>Identify real-world agents<\/strong>: Replace abstract process steps with actual people, roles, or systems.<\/li>\n<li><strong>Define responsibilities<\/strong>: Use active verbs. Avoid \u201chandles,\u201d \u201cmanages,\u201d or \u201cinvolves.\u201d Instead, say \u201cevaluates credit history\u201d or \u201cconfirms identity.\u201d<\/li>\n<li><strong>Map collaboration<\/strong>: Show what each agent *does* and what they *need* from others.<\/li>\n<li><strong>Validate handoffs<\/strong>: At each boundary, ask: \u201cWhat does the next agent receive? Is it clear, unambiguous, and complete?\u201d<\/li>\n<\/ol>\n<p>This approach surfaces gaps and overlaps that flowcharts often hide. For instance, if both the Loan Officer and Underwriter are responsible for \u201cchecking employment,\u201d it\u2019s a red flag \u2014 who owns it? CRC forces clarity.<\/p>\n<h2>Applying CRC UX: Designing User-Centered Flow<\/h2>\n<p>UX designers increasingly use CRC for business modeling to align user journeys with operational realities. When a user completes a form, the backend may need to trigger multiple actions \u2014 but the user only sees one step.<\/p>\n<p>Here\u2019s where CRC UX helps: model not just the user action, but the *system\u2019s responsibility* behind it.<\/p>\n<p>Take a customer onboarding flow:<\/p>\n<h3>Example: Onboarding Process CRC Model<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Class<\/th>\n<th>Responsibility<\/th>\n<th>Collaboration<\/th>\n<\/tr>\n<tr>\n<td>User<\/td>\n<td>Provides personal and financial details.<\/td>\n<td>Interacts with onboarding form.<\/td>\n<\/tr>\n<tr>\n<td>Onboarding Form<\/td>\n<td>Validates input format. Stores data temporarily.<\/td>\n<td>Relays to Identity Verification.<\/td>\n<\/tr>\n<tr>\n<td>Identity Verification<\/td>\n<td>Checks ID documents. Confirms identity via third party.<\/td>\n<td>Notifies Compliance and Onboarding Workflow.<\/td>\n<\/tr>\n<tr>\n<td>Compliance System<\/td>\n<td>Checks AML\/KYC rules. Flags suspicious patterns.<\/td>\n<td>Signals back to Onboarding Workflow.<\/td>\n<\/tr>\n<tr>\n<td>Onboarding Workflow<\/td>\n<td>Coordinates steps. Notifies user of status.<\/td>\n<td>Depends on all above.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This model does more than document steps \u2014 it reveals who determines success, what decisions are made where, and where delays are likely. It\u2019s a blueprint for UX, operations, and compliance.<\/p>\n<h3>Why CRC UX Reduces Misalignment<\/h3>\n<p>Too often, UX designers assume the backend will \u201cjust handle it.\u201d But when responsibilities are not defined, handoffs become ambiguous \u2014 leading to delays, errors, or frustration.<\/p>\n<p>Using CRC UX ensures that every interaction has a clear owner. A user sees \u201cDocument verified\u201d \u2014 but who verified it? What criteria? CRC makes the invisible visible.<\/p>\n<p>It also helps teams identify where automation can replace manual steps. If a system is responsible for \u201cchecking credit history,\u201d and the input is always the same, perhaps that step can be automated \u2014 but only if the responsibility is clear.<\/p>\n<h2>Non-Software CRC: Real-World Applications<\/h2>\n<p>CRC isn\u2019t just for software teams. I\u2019ve used non-software CRC in healthcare, insurance, and even nonprofit operations. The principles remain the same \u2014 classes, responsibilities, collaborations \u2014 but the context changes.<\/p>\n<h3>Example: Hospital Patient Admission Process<\/h3>\n<p>Instead of a flowchart showing \u201cAdmission \u2192 Registration \u2192 Room Assignment,\u201d map it with CRC:<\/p>\n<ul>\n<li><strong>Receptionist<\/strong>: Gathers patient info. Logs admission. Contacts nurse.<\/li>\n<li><strong>Nurse<\/strong>: Confirms medical history. Prepares patient for exam. Assigns room.<\/li>\n<li><strong>Admitting Physician<\/strong>: Reviews case. Orders tests. Approves admission.<\/li>\n<li><strong>Admission Coordinator<\/strong>: Manages bed availability. Updates system. Notifies department.<\/li>\n<\/ul>\n<p>Now, when a patient arrives and the nurse says, \u201cWe need the doctor,\u201d you can ask: \u201cWho is responsible for confirming the physician is on duty?\u201d This prevents delays.<\/p>\n<p>These models don\u2019t replace process flowcharts \u2014 they complement them. You can use CRC to annotate and validate the flow.<\/p>\n<h2>Business Responsibility Mapping: A Step-by-Step Approach<\/h2>\n<p>Here\u2019s a proven way to apply CRC for business modeling:<\/p>\n<ol>\n<li><strong>Identify key stakeholders<\/strong>: Who is involved in the process? Name real roles, not labels like \u201cSystem A\u201d or \u201cTeam B.\u201d<\/li>\n<li><strong>Define one clear responsibility per role<\/strong>: Use a verb + object. \u201cVerifies identity\u201d not \u201cManages verification.\u201d<\/li>\n<li><strong>Map handoffs<\/strong>: What information or artifact does each agent receive? Is it complete? Is it timely?<\/li>\n<li><strong>Check for redundancy or gaps<\/strong>: Does one role do too much? Is there an unassigned step?<\/li>\n<li><strong>Revisit in iteration<\/strong>: After implementation, review whether the model still holds. Update as needed.<\/li>\n<\/ol>\n<p>When done well, business responsibility mapping with CRC becomes a living document \u2014 a shared mental model that evolves with the process.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even simple models can go off track. Here are the most common mistakes in non-software CRC and how to fix them:<\/p>\n<ul>\n<li><strong>Too many responsibilities per class<\/strong>: A single agent shouldn\u2019t be responsible for \u201cmanaging,\u201d \u201creviewing,\u201d and \u201capproving.\u201d Split them.<\/li>\n<li><strong>Vague responsibilities<\/strong>: \u201cHandles documents\u201d is too broad. Be specific: \u201cSends documents to compliance for review.\u201d<\/li>\n<li><strong>Ignoring handoffs<\/strong>: If the nurse receives data but doesn&#8217;t know what to do with it, the model is incomplete.<\/li>\n<li><strong>Misaligned ownership<\/strong>: If the system says \u201capprove\u201d but no one is accountable, the process breaks.<\/li>\n<\/ul>\n<p>Always ask: \u201cIf this responsibility fails, who is accountable?\u201d If no one, then the model is incomplete.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know which roles to include in a business CRC model?<\/h3>\n<p>Include every party that performs a distinct action. Start with the people or systems directly involved in key steps. If one person handles \u201cdata entry,\u201d but another \u201creviews it,\u201d they are two classes. Avoid grouping roles that perform different functions.<\/p>\n<h3>Can CRC UX help with user research or personas?<\/h3>\n<p>Yes \u2014 but not directly. CRC doesn&#8217;t replace personas, but it complements them. Use personas to understand *who* the user is, and CRC to define *what they do* and *who they depend on*. Together, they create a clearer picture of user-centered workflows.<\/p>\n<h3>What if multiple teams own a responsibility?<\/h3>\n<p>This is a red flag. CRC helps identify shared responsibilities \u2014 but it should be explicit. If two teams share a duty, define how they coordinate: \u201cTeam A initiates, Team B confirms.\u201d This clarifies ownership and prevents gaps.<\/p>\n<h3>How do I keep CRC models from becoming outdated?<\/h3>\n<p>Treat CRC models as living artifacts. Review them after major process changes or audits. Update only when the responsibility or handoff changes. Use versioning or labels like \u201cQ3 2024\u201d to track updates.<\/p>\n<h3>Is CRC UX the same as user journey mapping?<\/h3>\n<p>No. User journey maps focus on emotions, touchpoints, and experiences. CRC UX focuses on *responsibilities* and *handoffs*. You can use both together: the journey map shows the user\u2019s path, and CRC UX explains what actually happens behind the scenes.<\/p>\n<h3>Can I use CRC for non-technical teams without training?<\/h3>\n<p>Yes \u2014 but with caution. Start simple: use sticky notes, write one responsibility per card, and ask \u201cWho does this?\u201d in a group setting. Avoid jargon. The goal is clarity, not perfection. With practice, teams learn to think in responsibilities naturally.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many teams start business process modeling with swimlanes and flowcharts, treating roles and systems as static boxes to be connected. It\u2019s a common trap: these diagrams look structured but often miss the real issue \u2014 who is *responsible* for what, and what do they *do* when they collaborate? That\u2019s where CRC for business modeling [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":782,"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-783","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>CRC for Business Modeling: Design with Purpose<\/title>\n<meta name=\"description\" content=\"Use CRC for business modeling to map responsibilities, clarify handoffs, and improve process design. Learn how non-software CRC modeling enhances UX and team alignment with real-world examples.\" \/>\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\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC for Business Modeling: Design with Purpose\" \/>\n<meta property=\"og:description\" content=\"Use CRC for business modeling to map responsibilities, clarify handoffs, and improve process design. Learn how non-software CRC modeling enhances UX and team alignment with real-world examples.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/\" \/>\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=\"7 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\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/\",\"name\":\"CRC for Business Modeling: Design with Purpose\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:24:33+00:00\",\"description\":\"Use CRC for business modeling to map responsibilities, clarify handoffs, and improve process design. Learn how non-software CRC modeling enhances UX and team alignment with real-world examples.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CRC Cards Explained: A Beginner\u2019s Modeling Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Applying CRC Thinking Beyond Software\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Adapting CRC Concepts to Business or UX Modeling\"}]},{\"@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":"CRC for Business Modeling: Design with Purpose","description":"Use CRC for business modeling to map responsibilities, clarify handoffs, and improve process design. Learn how non-software CRC modeling enhances UX and team alignment with real-world examples.","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\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/","og_locale":"id_ID","og_type":"article","og_title":"CRC for Business Modeling: Design with Purpose","og_description":"Use CRC for business modeling to map responsibilities, clarify handoffs, and improve process design. Learn how non-software CRC modeling enhances UX and team alignment with real-world examples.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"7 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/","name":"CRC for Business Modeling: Design with Purpose","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:24:33+00:00","description":"Use CRC for business modeling to map responsibilities, clarify handoffs, and improve process design. Learn how non-software CRC modeling enhances UX and team alignment with real-world examples.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-for-business-modeling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"CRC Cards Explained: A Beginner\u2019s Modeling Guide","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/"},{"@type":"ListItem","position":3,"name":"Applying CRC Thinking Beyond Software","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/crc-cards-explained\/crc-beyond-coding\/"},{"@type":"ListItem","position":4,"name":"Adapting CRC Concepts to Business or UX Modeling"}]},{"@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\/783","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\/783\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/782"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=783"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}