{"id":2267,"date":"2018-05-21T15:28:00","date_gmt":"2018-05-21T12:28:00","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=2267"},"modified":"2018-05-21T15:28:02","modified_gmt":"2018-05-21T12:28:02","slug":"organizational-evolutionary-design","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/","title":{"rendered":"Organizational Evolutionary Design"},"content":{"rendered":"

What is Organizational Evolutionary Design?<\/h1>\n

Evolutionary Design\u00a0is the practice of growing a system in a natural way, by adding the minimum amount of code to satisfy the business needs in an iterative and incremental approach.\u00a0When done right, the code structure changes continuously to optimize for change, thus allowing a constant speed of development for longer periods of time.<\/p><\/blockquote>\n

 <\/p>\n

In a dynamic world we need to adapt our tools and techniques to be resilient to change. Evolutionary Design is one of these techniques that helps us grow a system well by understanding its current characteristics.<\/p>\n

Please see more of my ideas on the topic of Evolutionary Design here<\/a>. During this article I will explain that there\u00a0 is an obvious parallel between Software Evolutionary Design and Organizational Evolutionary Design.<\/p>\n

 <\/p>\n

\"Organizational<\/a><\/p>\n

<\/p>\n

Evolutionary Design<\/h2>\n

In my experience as a programmer, trainer, technical coach and then organizational coach I observed a correlation between various systems around me. Especially when working with various teams to transition from one way of working to another, I facilitate the restructuring of the links between these systems.<\/p>\n

Situation:<\/strong>\u00a0A medium sized organization that has the Development Lead, Testing Lead and Operations Manager as roles. Their problem is they deliver a feature in 6 months on average. Their CEO wants them to deliver faster, because the clients are waiting too much and they could lose business.<\/p>\n

Situation: Evolutionary Approach<\/h4>\n

When restructuring such an organization I take a systemic approach: I want to understand the relationships between these departments and what blocks them from faster delivery. I talk with the people, look at their delivery cycle, understand their technical practices, discover their business model, etc. The result of this assessment is a change roadmap created specially for their organization. We discuss this roadmap together, I make sure everyone understands it and we adjust it where needed. I make the roadmap public and keep it up to date. It looks like a board with next actions, current actions, and what is done.<\/p>\n

In this situation it is virtually impossible to know how much time it will take to get to a normalization. I can use my experience and have an educated guess, but the error is quite high, as it’s just a guess and not an estimation.<\/p>\n

Normalizing Growth<\/strong><\/p>\n

I adjust this roadmap daily, depending on the problems that arise and the feedback from the organization. The purpose is to have the organization increase their performance step by step, in their own time, with their own strengths, weaknesses and resources. I am just a facilitator of improvement, of\u00a0 normalizing growth from their initial level to an improved level. We measure at each step how well we are and if the organization decides they are good enough, I leave and leave them independent.<\/p>\n

I call this process Normalizing Growth<\/strong>. Normalizing Growth<\/strong> is the process of observing the natural traits of a system and adjusting its growth patterns so it can become a sustainable self-reliant ecosystem. Think about when you were a kid and started to be independent; you could go to school or friends alone, without adult supervision.<\/p>\n

Optimizing Growth<\/strong><\/p>\n

After a while the organization calls me back because they know they can perform better. I analyze again their current system, talk with people, and we discuss about their expected outcome. In this moment they want to optimize their processes in a specific direction. When you optimize any system you need to compromise. An organization cannot be 100% of time working for clients and still be a learning organization. So you need to reduce the time for some areas and increase it for some others. My help in this situation is to find the right compromise, given their business strategy.<\/p>\n

We create again a roadmap to change certain areas. Usually during this stage people are more autonomous, some levels of management disappear and specialists become internal coaches or mentors. This is the first step to transform into a learning organization. Usually I leave the organization after a while and they are more effective, but also more dynamic.<\/p>\n

The second step in evolving an organization is Optimizing Growth<\/strong>. Optimizing Growth<\/strong> is finding the good compromise for using the time and effort in the right directions so the organization can grow naturally on its strategic direction. Management is transformed to observation, coaching and leadership.<\/p>\n

Maximizing Growth<\/strong><\/p>\n

Not many organizations reach this phase. Most of them would’t have better business if they would move from Optimizing Growth. This next step is useful for organizations in a very dynamic business, small organizations that want to have great business in their market. Typically these organizations have good or great profits with few people.<\/p>\n

For example one organization has 15 people and a direct profit of 13 million \u20ac per year. In the same city there is another organization that has 350 people and has a direct profit of 14 million \u20ac per year. The first one would be willing to maximize growth. The latter would maybe need to first Optimize Growth, and it would then be enough.<\/p>\n

Maximizing Growth<\/strong> means having a systemic approach to all the activities. All the people from the organization know the business direction, take active actions to improve their activities with respect to business metrics they all analyze quite often. The organization is comprised of people sharing the same business goal, but independent from each other from the management point of view. They don’t have managers, but they manage their work.<\/p>\n

Situation: Big-Bang Approach<\/h4>\n

When restructuring an organization in a Big-Bang approach you analyze -> estimate -> plan -> execute.\u00a0But the problem is that there are so many variables and the people in the organization might mimic the change. So often I see people pretending they acquired the new skills, but they work in the same old ways. So it’s like changing bits and pieces, but leaving everything the same.<\/p>\n

In this situation you can estimate how much time it takes for an organization to reach a certain goal. It doesn’t mean the approach is necessarily better for the organization. It’s like applying a plan blindly just because you created it in the first place.\u00a0This situation is very good for managers, because they are in a safe space and can plan budgets and justify their work.<\/p>\n

Normalizing Growth<\/h4>\n

This type of normalization comes natural, with applying a model. You can call it in any way, most of them have acronyms and are presented as the best for everyone. Many people come in the organization and teach the new model. Often people agree, sometimes they disagree with the new model. Anyway it is a strategic decision and it needs to keep going until the plan is executed and the transition is made.<\/p>\n

Optimizing Growth<\/h4>\n

Only a few organizations can reach this stage when applying Big-Bang approach. Most often it happens the model the chose for growth fits like a glove and then it’s just a natural phase to continue and optimize growth. This is a happy situation, because unfortunately not often a model fits very well an organization.<\/p>\n

Maximizing Growth<\/h4>\n

I think you can forget about maximizing growth when directed, managed change is implemented. Reaching this phase needs systemic thinking and any growth model would need to be substantially adjusted.<\/p>\n

 <\/p>\n

Conclusion<\/h2>\n

When you want your organization to perform, think about the whole ecosystem and adjust it accordingly. Without external help it is quite difficult to have a fresh picture and try new things, but not impossible.<\/p>\n

My recommendation is to always keep trying maximizing growth. The enemy of maximizing business growth is maximizing the number of people and transforming a small organization into a big organization based on internal politics and not on business metrics.<\/p>\n<\/a><\/table>","protected":false},"excerpt":{"rendered":"

What is Organizational Evolutionary Design? Evolutionary Design\u00a0is the practice of growing a system in a natural way, by adding the minimum amount of code to satisfy the business needs in… <\/p>\n","protected":false},"author":3,"featured_media":2283,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[169],"tags":[253,311,108,326,193,328,216,327,325,322,312,308],"yoast_head":"\nOrganizational Evolutionary Design - Adrian Bolboaca<\/title>\n<meta name=\"description\" content=\"Organizational Evolutionary Design is the practice of transforming an organization in an organic way, with a loose initial plan that changes depending on factors observed after starting the transformation. Same ideas from Software Evolutionary Design apply to Organizational Design as well.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Organizational Evolutionary Design - Adrian Bolboaca\" \/>\n<meta property=\"og:description\" content=\"Organizational Evolutionary Design is the practice of transforming an organization in an organic way, with a loose initial plan that changes depending on factors observed after starting the transformation. Same ideas from Software Evolutionary Design apply to Organizational Design as well.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\" \/>\n<meta property=\"og:site_name\" content=\"Adrian Bolboaca\" \/>\n<meta property=\"article:published_time\" content=\"2018-05-21T12:28:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-05-21T12:28:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2018\/05\/organizational-evolutionary-design-image-blog-adrianbolboaca-ro.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1031\" \/>\n\t<meta property=\"og:image:height\" content=\"686\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Adrian Bolboaca\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Adrian Bolboaca\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\"},\"author\":{\"name\":\"Adrian Bolboaca\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\"},\"headline\":\"Organizational Evolutionary Design\",\"datePublished\":\"2018-05-21T12:28:00+00:00\",\"dateModified\":\"2018-05-21T12:28:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\"},\"wordCount\":1284,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\"},\"keywords\":[\"Agile\",\"Coaching\",\"Design\",\"Digital\",\"Evolutionary\",\"Leadership\",\"Lean\",\"Management\",\"Organizational\",\"Organizational Design\",\"Training\",\"Transformation\"],\"articleSection\":[\"Evolutionary Design\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\",\"url\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\",\"name\":\"Organizational Evolutionary Design - Adrian Bolboaca\",\"isPartOf\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#website\"},\"datePublished\":\"2018-05-21T12:28:00+00:00\",\"dateModified\":\"2018-05-21T12:28:02+00:00\",\"description\":\"Organizational Evolutionary Design is the practice of transforming an organization in an organic way, with a loose initial plan that changes depending on factors observed after starting the transformation. Same ideas from Software Evolutionary Design apply to Organizational Design as well.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.adrianbolboaca.ro\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Organizational Evolutionary Design\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#website\",\"url\":\"https:\/\/blog.adrianbolboaca.ro\/\",\"name\":\"Adrian Bolboaca\",\"description\":\"Programmer, Trainer, Coach\",\"publisher\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.adrianbolboaca.ro\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\",\"name\":\"Adrian Bolboaca\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg\",\"contentUrl\":\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg\",\"width\":300,\"height\":400,\"caption\":\"Adrian Bolboaca\"},\"logo\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/\"},\"description\":\"Adrian was involved in developing software for domains like energy, ecommerce, banking, customs and ERP\/CRM. He has been working with companies from Netherlands, Romania, Italy, France and Germany, and he is knowledgeable in software technical domains like: clean code, unit testing, test driven development, simple design, emergent design, working effectively with legacy code. As a continuous learner and challenger of existing ideas and concepts, Adrian is a supporter of movements that give new ideas on how to continuously improve software and that embrace the values of software quality and efficiency. He facilitated many code retreats in Romania, Belgium, France, Germany, Netherlands, Finland, Bulgaria and has a keen interest in serious games and using gamestorming for continuous improvement. He is fluent in Romanian, English and French, but when it comes to programming languages he supports language agnosticism, since he strongly believes that a programming language is only a tool towards higher level software concepts. As a constant participant to conferences and workshops, he is recognized for challenging ideas and getting people out of their comfort zone, not out of disrespect or lack of reverence for his peers, but out of his desire to show people that there are always things to learn. \u201cI try to be a continuous learner and a continuous teacher, because I think good software comes from the skills of the people that are involved in the process, on each and every level. Whenever I write code I focus on reducing domain complexity to obtain maintainable software. I love to develop software that helps companies to improve their business, to implement solutions that improve their internal processes and to motivate teams to use their capabilities to yet another level.\u201d Adrian works as a technical and organizational trainer and coach at Mozaic Works.\",\"sameAs\":[\"http:\/\/blog.adrianbolboaca.ro\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Organizational Evolutionary Design - Adrian Bolboaca","description":"Organizational Evolutionary Design is the practice of transforming an organization in an organic way, with a loose initial plan that changes depending on factors observed after starting the transformation. Same ideas from Software Evolutionary Design apply to Organizational Design as well.","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:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/","og_locale":"en_US","og_type":"article","og_title":"Organizational Evolutionary Design - Adrian Bolboaca","og_description":"Organizational Evolutionary Design is the practice of transforming an organization in an organic way, with a loose initial plan that changes depending on factors observed after starting the transformation. Same ideas from Software Evolutionary Design apply to Organizational Design as well.","og_url":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/","og_site_name":"Adrian Bolboaca","article_published_time":"2018-05-21T12:28:00+00:00","article_modified_time":"2018-05-21T12:28:02+00:00","og_image":[{"width":1031,"height":686,"url":"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2018\/05\/organizational-evolutionary-design-image-blog-adrianbolboaca-ro.png","type":"image\/png"}],"author":"Adrian Bolboaca","twitter_misc":{"Written by":"Adrian Bolboaca","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#article","isPartOf":{"@id":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/"},"author":{"name":"Adrian Bolboaca","@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76"},"headline":"Organizational Evolutionary Design","datePublished":"2018-05-21T12:28:00+00:00","dateModified":"2018-05-21T12:28:02+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/"},"wordCount":1284,"commentCount":0,"publisher":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76"},"keywords":["Agile","Coaching","Design","Digital","Evolutionary","Leadership","Lean","Management","Organizational","Organizational Design","Training","Transformation"],"articleSection":["Evolutionary Design"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/","url":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/","name":"Organizational Evolutionary Design - Adrian Bolboaca","isPartOf":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#website"},"datePublished":"2018-05-21T12:28:00+00:00","dateModified":"2018-05-21T12:28:02+00:00","description":"Organizational Evolutionary Design is the practice of transforming an organization in an organic way, with a loose initial plan that changes depending on factors observed after starting the transformation. Same ideas from Software Evolutionary Design apply to Organizational Design as well.","breadcrumb":{"@id":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.adrianbolboaca.ro\/2018\/05\/organizational-evolutionary-design\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.adrianbolboaca.ro\/"},{"@type":"ListItem","position":2,"name":"Organizational Evolutionary Design"}]},{"@type":"WebSite","@id":"https:\/\/blog.adrianbolboaca.ro\/#website","url":"https:\/\/blog.adrianbolboaca.ro\/","name":"Adrian Bolboaca","description":"Programmer, Trainer, Coach","publisher":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.adrianbolboaca.ro\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76","name":"Adrian Bolboaca","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/","url":"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg","contentUrl":"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg","width":300,"height":400,"caption":"Adrian Bolboaca"},"logo":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/"},"description":"Adrian was involved in developing software for domains like energy, ecommerce, banking, customs and ERP\/CRM. He has been working with companies from Netherlands, Romania, Italy, France and Germany, and he is knowledgeable in software technical domains like: clean code, unit testing, test driven development, simple design, emergent design, working effectively with legacy code. As a continuous learner and challenger of existing ideas and concepts, Adrian is a supporter of movements that give new ideas on how to continuously improve software and that embrace the values of software quality and efficiency. He facilitated many code retreats in Romania, Belgium, France, Germany, Netherlands, Finland, Bulgaria and has a keen interest in serious games and using gamestorming for continuous improvement. He is fluent in Romanian, English and French, but when it comes to programming languages he supports language agnosticism, since he strongly believes that a programming language is only a tool towards higher level software concepts. As a constant participant to conferences and workshops, he is recognized for challenging ideas and getting people out of their comfort zone, not out of disrespect or lack of reverence for his peers, but out of his desire to show people that there are always things to learn. \u201cI try to be a continuous learner and a continuous teacher, because I think good software comes from the skills of the people that are involved in the process, on each and every level. Whenever I write code I focus on reducing domain complexity to obtain maintainable software. I love to develop software that helps companies to improve their business, to implement solutions that improve their internal processes and to motivate teams to use their capabilities to yet another level.\u201d Adrian works as a technical and organizational trainer and coach at Mozaic Works.","sameAs":["http:\/\/blog.adrianbolboaca.ro"]}]}},"_links":{"self":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/posts\/2267"}],"collection":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/comments?post=2267"}],"version-history":[{"count":0,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/posts\/2267\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/media\/2283"}],"wp:attachment":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/media?parent=2267"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/categories?post=2267"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/tags?post=2267"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}