{"id":1320,"date":"2026-02-25T10:39:43","date_gmt":"2026-02-25T10:39:43","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/"},"modified":"2026-02-25T10:39:43","modified_gmt":"2026-02-25T10:39:43","slug":"pmbok-change-control-flexibility-governance","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/","title":{"rendered":"How to Control Change Without Bureaucracy"},"content":{"rendered":"<p>Projects that spiral out of control often begin not with scope creep, but with poor change control. I\u2019ve seen teams spend weeks building features only to be told \u201cnot needed\u201d by the client in a post-mortem. The root isn\u2019t poor communication\u2014it\u2019s the absence of a structured yet lightweight change management process. This happens when teams confuse documentation with discipline. <\/p>\n<p>My experience shows that the real issue isn\u2019t complexity\u2014it\u2019s inconsistency. Some teams follow a rigid, paper-heavy process. Others let change happen ad hoc, leading to misaligned priorities and rework. The truth lies in the middle: a disciplined but adaptive model rooted in PMBOK change control. <\/p>\n<p>Here, you\u2019ll learn how to implement integration management PMBOK not as a bureaucratic hurdle, but as a strategic advantage. You\u2019ll discover the exact steps for a real-world change request process PMBOK that\u2019s both compliant and agile. You\u2019ll build confidence in decision-making and avoid the cost of uncontrolled change.<\/p>\n<h2>Why Change Control Fails (And How to Fix It)<\/h2>\n<p>Change management isn\u2019t about stopping change. It\u2019s about managing it responsibly. The most common failure I\u2019ve observed is treating change control as a gatekeeping ritual instead of a decision-making engine. <\/p>\n<p>When change requests pile up without triage, teams drown in work that doesn\u2019t deliver value. Worse, stakeholders begin to distrust the process. This erodes accountability and slows execution. The fix isn\u2019t more forms\u2014it\u2019s better structure.<\/p>\n<p>Integration management PMBOK is the backbone of this structure. It ensures that every change is evaluated against project objectives, resources, and risks. It\u2019s not about restricting innovation. It\u2019s about ensuring every change contributes to the project\u2019s success.<\/p>\n<h3>The Real Cost of Uncontrolled Change<\/h3>\n<p>Unmanaged changes lead to: <\/p>\n<ul>\n<li>Scope creep<\/li>\n<li>Missed deadlines<\/li>\n<li>Budget overruns<\/li>\n<li>Team burnout<\/li>\n<li>Stakeholder dissatisfaction<\/li>\n<\/ul>\n<p>These aren\u2019t side effects\u2014they\u2019re symptoms of a broken process. A structured change request process PMBOK isn\u2019t a burden. It\u2019s the difference between chaos and clarity.<\/p>\n<h2>Building a Lightweight PMBOK Change Control Process<\/h2>\n<p>Every change starts with a request. But how you handle that request determines the outcome. Here\u2019s a proven step-by-step flow based on PMBOK integration management, adapted for real-world speed and transparency.<\/p>\n<h3>Step 1: Capture the Change Request<\/h3>\n<p>Every request must be documented, even informally. Use a simple template: <\/p>\n<ul>\n<li><strong>Request ID:<\/strong> Unique identifier (e.g., CR-001)<\/li>\n<li><strong>Requestor:<\/strong> Name and role<\/li>\n<li><strong>Proposed Change:<\/strong> One-sentence summary<\/li>\n<li><strong>Justification:<\/strong> Why it\u2019s needed (business, technical, regulatory)<\/li>\n<li><strong>Impact:<\/strong> Effect on scope, timeline, budget, quality<\/li>\n<\/ul>\n<p>Do not collect this in a spreadsheet or email thread. Use a shared digital log\u2014like a simple table or a project management tool. This ensures visibility and prevents loss.<\/p>\n<h3>Step 2: Conduct a Preliminary Impact Assessment<\/h3>\n<p>Before involving the full team, answer three quick questions: <\/p>\n<ol>\n<li>Does this affect the project\u2019s key deliverables?<\/li>\n<li>Will it impact the approved schedule or budget?<\/li>\n<li>Does it introduce new risks?<\/li>\n<\/ol>\n<p>If all answers are \u201cno,\u201d the change may be approved without a formal review. If any are \u201cyes,\u201d escalate to the Change Control Board (CCB).<\/p>\n<h3>Step 3: Review by the Change Control Board (CCB)<\/h3>\n<p>The CCB is not a bureaucracy. It\u2019s a decision-making group. Include: <\/p>\n<ul>\n<li>Project Manager<\/li>\n<li>Key Stakeholder (e.g., product owner)<\/li>\n<li>Team Lead or Technical Architect<\/li>\n<li>Finance or Resource Manager (if needed)<\/li>\n<\/ul>\n<p>Meet quickly\u201415 to 30 minutes. Use the change request form and a simple impact matrix.<\/p>\n<h3>Step 4: Document the Decision<\/h3>\n<p>Every decision must be recorded. Use this format: <\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Field<\/th>\n<th>Content<\/th>\n<\/tr>\n<tr>\n<td>Change Request ID<\/td>\n<td>CR-001<\/td>\n<\/tr>\n<tr>\n<td>Decision<\/td>\n<td>Approved with minor adjustments<\/td>\n<\/tr>\n<tr>\n<td>Reason<\/td>\n<td>Improves user experience and aligns with business goals<\/td>\n<\/tr>\n<tr>\n<td>Approved By<\/td>\n<td>Project Manager, Product Owner<\/td>\n<\/tr>\n<tr>\n<td>Date<\/td>\n<td>2025-04-05<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Store all decisions in a shared log. This creates a historical record and enables audit readiness.<\/p>\n<h2>Integration Management PMBOK: The Invisible Thread<\/h2>\n<p>Change control isn\u2019t an isolated process. It\u2019s part of integration management PMBOK\u2014the glue that holds project elements together. <\/p>\n<p>Every change must be evaluated in the context of: <\/p>\n<ul>\n<li>Project scope<\/li>\n<li>Work breakdown structure (WBS)<\/li>\n<li>Resource allocation<\/li>\n<li>Risk register<\/li>\n<li>Communication plan<\/li>\n<\/ul>\n<p>When you approve a change, update all related artifacts. If you don\u2019t, you risk creating conflicting versions of the truth.<\/p>\n<p>Here\u2019s what happens when integration is ignored: <\/p>\n<ul>\n<li>A change alters the user interface but no one updates the test plan.<\/li>\n<li>The timeline is extended, but the budget isn\u2019t adjusted.<\/li>\n<li>New features are added without updating acceptance criteria.<\/li>\n<\/ul>\n<p>These gaps lead to rework, delays, and stakeholder complaints. Integration management PMBOK prevents this by ensuring alignment across all project components.<\/p>\n<h2>Real-World Example: A Marketing Campaign Update<\/h2>\n<p>Consider a digital marketing campaign. Midway, the client requests to add a new ad format\u2014interactive video. <\/p>\n<p>First, capture the request: <\/p>\n<pre><code>CR-003\nRequestor: Client Marketing Lead\nProposed Change: Add interactive video ads to the campaign\nJustification: Higher engagement in previous campaigns; aligns with target audience behavior\nImpact: +2 days to production, +$3K budget, minor risk to launch date<\/code><\/pre>\n<p>Assessment: Yes, impacts timeline and budget. Escalate to CCB.<\/p>\n<p>CCB review: Approved. But only if the team delivers a prototype by Friday. <\/p>\n<p>Update: <\/p>\n<ul>\n<li>Project schedule: Add 2 days to production phase<\/li>\n<li>Resource plan: Assign a video developer<\/li>\n<li>Risk register: Add \u201cdelay in video rendering\u201d with mitigation plan<\/li>\n<li>Test plan: Add validation for interactive elements<\/li>\n<\/ul>\n<p>Done. The change is approved, documented, and integrated\u2014not just rubber-stamped.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<h3>1. Over-Documenting<\/h3>\n<p>Don\u2019t require 20-page change forms. Keep it focused. One page is enough for most projects.<\/p>\n<h3>2. Delaying Decisions<\/h3>\n<p>Set a 48-hour response window for all change requests. If no decision, it\u2019s automatically rejected. This forces accountability.<\/p>\n<h3>3. Ignoring the &#8222;No Change&#8221; Decision<\/h3>\n<p>Not every request needs approval. Saying \u201cno\u201d with a clear reason builds trust. Never leave a request unresponded.<\/p>\n<h3>4. Skipping Post-Approval Updates<\/h3>\n<p>Approved change? Update the baseline. If not, you\u2019re managing a ghost project. The real project is the one with updated artifacts.<\/p>\n<h2>FAQs<\/h2>\n<h3>What is PMBOK change control?<\/h3>\n<p>PMBOK change control is a process within integration management PMBOK that ensures all changes to the project are formally evaluated, approved, and documented. It prevents uncontrolled scope creep while maintaining flexibility.<\/p>\n<h3>How do I start a change request process PMBOK?<\/h3>\n<p>Begin with a shared change log. Create a simple template with requestor, description, justification, and impact. Use a CCB for review\u2014keep meetings short and focused. Always update project baselines after approval.<\/p>\n<h3>Can I skip change control for small changes?<\/h3>\n<p>No. Even minor changes should be documented. Small changes accumulate quickly. Without a log, you lose visibility into project evolution and risk unintended scope creep.<\/p>\n<h3>Who should be on the Change Control Board (CCB)?<\/h3>\n<p>Include the project manager, key stakeholders (e.g., product owner), technical lead, and a resource or finance rep. The CCB should be small\u20143 to 5 members\u2014so decisions are fast and actionable.<\/p>\n<h3>How does integration management PMBOK support change control?<\/h3>\n<p>Integration management PMBOK ensures that every change is evaluated across all project components: scope, schedule, budget, resources, risks, and communications. It prevents siloed decisions and maintains project alignment.<\/p>\n<h3>What if stakeholders demand urgent changes?<\/h3>\n<p>Respond with urgency but structure. Approve the change, but document it. Require a post-implementation review to assess impact. Use this to refine your process and communicate trade-offs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Projects that spiral out of control often begin not with scope creep, but with poor change control. I\u2019ve seen teams spend weeks building features only to be told \u201cnot needed\u201d by the client in a post-mortem. The root isn\u2019t poor communication\u2014it\u2019s the absence of a structured yet lightweight change management process. This happens when teams [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1313,"menu_order":6,"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-1320","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>PMBOK Change Control: Master Flexibility with Governance<\/title>\n<meta name=\"description\" content=\"Learn how to control change without bureaucracy using PMBOK change control. Balance flexibility with governance through integration management PMBOK and a streamlined change request process PMBOK.\" \/>\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\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PMBOK Change Control: Master Flexibility with Governance\" \/>\n<meta property=\"og:description\" content=\"Learn how to control change without bureaucracy using PMBOK change control. Balance flexibility with governance through integration management PMBOK and a streamlined change request process PMBOK.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/\",\"name\":\"PMBOK Change Control: Master Flexibility with Governance\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:39:43+00:00\",\"description\":\"Learn how to control change without bureaucracy using PMBOK change control. Balance flexibility with governance through integration management PMBOK and a streamlined change request process PMBOK.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PMBOK Essentials for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Core PMBOK Practices Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"How to Control Change Without Bureaucracy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"PMBOK Change Control: Master Flexibility with Governance","description":"Learn how to control change without bureaucracy using PMBOK change control. Balance flexibility with governance through integration management PMBOK and a streamlined change request process PMBOK.","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\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/","og_locale":"pl_PL","og_type":"article","og_title":"PMBOK Change Control: Master Flexibility with Governance","og_description":"Learn how to control change without bureaucracy using PMBOK change control. Balance flexibility with governance through integration management PMBOK and a streamlined change request process PMBOK.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/","name":"PMBOK Change Control: Master Flexibility with Governance","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:39:43+00:00","description":"Learn how to control change without bureaucracy using PMBOK change control. Balance flexibility with governance through integration management PMBOK and a streamlined change request process PMBOK.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-change-control-flexibility-governance\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"PMBOK Essentials for Beginners","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Core PMBOK Practices Explained","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/"},{"@type":"ListItem","position":4,"name":"How to Control Change Without Bureaucracy"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1320\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1313"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1320"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}