{"id":3100,"date":"2024-01-01T01:01:00","date_gmt":"2024-01-01T01:01:00","guid":{"rendered":"https:\/\/www.smharter.com\/blog\/?p=3100"},"modified":"2024-01-04T18:44:14","modified_gmt":"2024-01-04T18:44:14","slug":"when-how-to-move-effectively-tasks-responsibilities-outside-the-team","status":"publish","type":"post","link":"https:\/\/www.smharter.ai\/blog\/2024\/01\/01\/when-how-to-move-effectively-tasks-responsibilities-outside-the-team\/","title":{"rendered":"When\/How to move effectively tasks\/responsibilities outside the team (2-part)"},"content":{"rendered":"\n<pre class=\"wp-block-verse has-text-align-center\"><strong>PART ONE<\/strong><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>This is the rule of thumb<\/strong><\/h1>\n\n\n\n<p>In the context of <em><span style=\"text-decoration: underline;\">knowledge work<\/span><\/em> and <em><span style=\"text-decoration: underline;\">software &amp; digital products development,<\/span><\/em> the rule of thumb is to share all the responsibilities inside a multi-disciplinary team that has all the skills and authority to autonomously do all the work from the concept to when the finished work lands into the hands of the final users, and later for operating, supporting, maintaining and evolving the related product. Therefore, all the responsibilities should remain inside the team.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"430\" src=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-1.png\" alt=\"\" class=\"wp-image-3120\" style=\"width:626px;height:auto\" srcset=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-1.png 1024w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-1-600x252.png 600w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-1-768x323.png 768w\" sizes=\"auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px\" \/><\/figure>\n<\/div>\n\n\n<p>Traditionally, in industrial mass production, the rule of thumb goes toward a different direction, the direction of specialisation, work divisionalisation in separate functions, outsourcing, commoditization, standardisation, and economies of scale.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>When to go beyond the rule of thumb<\/strong><\/h1>\n\n\n\n<p>Even in <em><span style=\"text-decoration: underline;\">knowledge work<\/span><\/em> and <em><span style=\"text-decoration: underline;\">software &amp; digital products development,<\/span><\/em> there can also be situations where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the <span style=\"text-decoration: underline;\"><em>workload<\/em><\/span> exceeds the capacity of the team, as a whole or for a specialistic knowledge\/skillset;<\/li>\n\n\n\n<li>the <span style=\"text-decoration: underline;\"><em>cognitive load<\/em><\/span> exceeds the capacity of the team;<\/li>\n\n\n\n<li>a <span style=\"text-decoration: underline;\"><em>very specialistic knowledge\/skillset<\/em><\/span> is underutilised in the team, nonetheless, it is needed;<\/li>\n\n\n\n<li>some <span style=\"text-decoration: underline;\"><em>services, product areas or components<\/em><\/span> may have reached a level of maturity that would allow them to be delegated to another team and shared across multiple consumers;<\/li>\n\n\n\n<li>any other you can think of?<\/li>\n<\/ul>\n\n\n\n<p>One way to stick to the rule of thumb under these circumstances is to follow an extreme and continuous knowledge &amp; responsibilities sharing. As described in <a href=\"https:\/\/www.smharter.com\/blog\/2022\/11\/21\/transcending-agile-cross-team-collaboration-with-shared-work\/\" data-type=\"link\" data-id=\"https:\/\/www.smharter.com\/blog\/2022\/11\/21\/transcending-agile-cross-team-collaboration-with-shared-work\/\" target=\"_blank\" rel=\"noreferrer noopener\">Transcending Cross-team collaboration with shared work<\/a>.<\/p>\n\n\n\n<p>There are situations tho&#8217; when it may be convenient or easier to go beyond the rule of thumb. See an example inspired by Team Topologies here: <a href=\"https:\/\/www.smharter.com\/blog\/2022\/08\/08\/agile-cross-team-collaboration-how-tos-long\/\" target=\"_blank\" rel=\"noreferrer noopener\">Agile cross-team collaboration How-Tos<\/a>.  <\/p>\n\n\n\n<p>For these situations, we really need to understand when, what, and how to effectively move some tasks and\/or responsibilities outside the team. For example, delegating them to a Subject Matter Expert, an external contractor, an Agency, a global\/shared function, a Team Topologies&#8217; Platform or Complicated subsystem team.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"1218\" height=\"430\" src=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-2.png\" alt=\"\" class=\"wp-image-3121\" style=\"width:774px;height:auto\" srcset=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-2.png 1218w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-2-600x212.png 600w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-2-768x271.png 768w\" sizes=\"auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px\" \/><\/figure>\n<\/div>\n\n\n<h1 class=\"wp-block-heading\"><strong>What does success look like for this<\/strong><\/h1>\n\n\n\n<p>When the work or cognitive load exceed the team capacity or there is a need for a very specialistic knowledge\/skillset, or a service\/product\/component has reached a level of maturity allowing for reuse, the options of moving the related tasks\/responsibilities outside the team should be considered only in ways that make such option beneficial and advantageous compared to the status quo.<\/p>\n\n\n\n<p>Below are some general criteria that can help to find ways to ensure that.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>A) The work and cognitive load should actually be reduced<\/strong><\/h3>\n\n\n\n<p>This means that moving the task\/responsibility outside the team, delegating it, and getting the work done back, should not add more work or cognitive load than doing the work directly inside the team.<br>For each of such tasks\/responsibilities then:<br>&#8211; making an external request for getting the work done should be <span style=\"text-decoration: underline;\">orders<\/span> of magnitude simpler than explaining to others how the work should be done, or just asking to get it done, <br>&#8211; the &#8220;interface&#8221; and &#8220;protocol&#8221; to ask for each task\/responsibility to get done should be simple like it was a black box, therefore should not require knowing or understanding any &#8220;internals&#8221;.<\/p>\n\n\n\n<p>This requires a clear &#8220;separation of concerns&#8221; between tasks and responsibilities and knowledge\/skills remaining inside the team and those moved outside the team.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>B) It should not add hidden costs such as extra-planning and collaboration frictions<\/strong><\/h3>\n\n\n\n<p>Moving a task\/responsibility outside the team should not add dependencies other than to that task\/responsibility, for example, a dependency of the team on:<br>&#8211; an individual or a knowledge that is not more inside the team,<br>&#8211; a technical dependency on source code, infrastructure, tools or other tech moved outside the team,<br>&#8211; any other resource dependency,<br>&#8211; access and\/or authority that has moved outside the team and is not available in the team anymore.<br>Any of these dependencies would require additional collaboration, coordination and planning that go well beyond what is needed for the tasks\/responsibilities moved out, and would typically introduce additional rigidities, complexities and costs that exceed the other expected benefits.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>C) It should not add delays and unpredictability<\/strong><\/h3>\n\n\n\n<p>Those taking care of the tasks\/responsibilities moved outside the team, must have enough capacity to do the required work without adding delays to the team and without becoming a bottleneck.<\/p>\n\n\n\n<p>The &#8220;interface&#8221; and &#8220;protocol&#8221; the team uses to request and obtain the service must remain stable instead of changing over time adding extra work to the team at every request.<\/p>\n\n\n\n<p>The requests must be carried out without the need to change\/modify\/adapt the &#8220;internals&#8221; of the service provided overloading the external person or team (especially when they are serving multiple clients) and adding work also to the team, overall causing further delays and adding more complexity.<\/p>\n\n\n\n<p>When it is feasible, the service itself should be automated allowing for self-procurement therefore avoiding all the potential problems just mentioned. Common examples include cloud environment procurement, code integration, final system testing, and deployment.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity is-style-wide\"\/>\n\n\n\n<p class=\"has-text-align-center\"> (Part 1)<strong><a href=\"https:\/\/www.smharter.com\/blog\/2024\/01\/01\/when-how-to-move-effectively-tasks-responsibilities-outside-the-team\/2\/\"> Part 2 &gt;&gt;<\/a><\/strong><\/p>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity is-style-wide\"\/>\n\n\n\n<!--nextpage-->\n\n\n\n<pre class=\"wp-block-verse has-text-align-center\"><strong>PART TWO<\/strong><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>(Optional) sources of inspiration<\/strong><\/h1>\n\n\n\n<p>Whether the tasks\/responsibilities are to be delegated to a Subject Matter Expert, an external contractor, a global\/shared function, an agency, a Platform team, a Complicated subsystem team, or similar, these models below have inspired me to reflect on ways to identify when the three criteria are met and so the move is going to be really beneficial and advantageous.<br><br>For criteria #A (about the clear separation and simplicity) and #B (about the dependencies), I have found it useful to think about:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>the Encapsulation property of Object Orientation<\/strong> where a clean simple public interface and protocol allow to access the service in a simple way, without the need to know or understand the internal implementation details;<\/li>\n\n\n\n<li><strong>the low coupling property of good Object Oriented design<\/strong> where only dependency between the object and the code using it goes through the public interface and it is limited;<\/li>\n\n\n\n<li><strong>the Domain Driven Design and Event Storming workshop<\/strong> that provide ways to apply the two points above also in complex scenarios. <\/li>\n<\/ul>\n\n\n\n<p>While these thinking tools are specific for code and are naturally useful when moving the ownership of parts of a codebase outside the team, the same concepts can be applied to tasks\/responsibilities, to the way the service is provided through an &#8220;interface&#8221; and a &#8220;protocol&#8221;, and the non-technical dependencies as well.<\/p>\n\n\n\n<p>For criteria #C (about the stable interface and the service provided), I have found it useful to think about:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>the stages of evolution of a product\/service in Wardley Mapping<\/strong>, where the product\/service reaches the required level of stability at the Product + Retail Services stage and the later Commodity + Utility Services stage;<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"784\" height=\"82\" src=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/wardley-map-annimation-copy.png\" alt=\"\" class=\"wp-image-3144\" style=\"width:892px;height:auto\" srcset=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/wardley-map-annimation-copy.png 784w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/wardley-map-annimation-copy-600x63.png 600w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/wardley-map-annimation-copy-768x80.png 768w\" sizes=\"auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px\" \/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>the social learning cycle in Max Boisot&#8217;s I-Space<\/strong> that shows how knowledge (as that related to the tasks\/responsibilities to be moved outside the team) requires going through a process of codification and abstraction before being ready for public diffusion (as moving that knowledge outside the team). Therefore, moving that knowledge outside the team has, as a prerequisite, a certain level of maturity and understanding of the related knowledge.<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"550\" height=\"405\" src=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/5d1ad16a17f3281b.png\" alt=\"\" class=\"wp-image-3145\" style=\"width:564px;height:auto\"\/><\/figure>\n<\/div>\n\n\n<p>Both these models have general validity and can be applied to code whose ownership is to be moved to a Platform or Complicated subsystem team, as well as other tasks\/responsibilities.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>To summarise: The Guidelines<\/strong><\/h1>\n\n\n\n<p>Putting it all together, here are the guidelines that summarise when some tasks\/responsibilities can be effectively moved outside the team to a Subject Matter Expert, an external contractor, an Agency, a global\/shared function, a Team Topologies&#8217; Platform or Complicated subsystem team. When an organisation cannot meet these guidelines, will be better off keeping those tasks\/responsibilities inside the team.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1638\" height=\"430\" src=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-12.png\" alt=\"\" class=\"wp-image-3126\" srcset=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-12.png 1638w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-12-600x158.png 600w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-12-768x202.png 768w, https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/multidisciplinary-team-12-1536x403.png 1536w\" sizes=\"auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px\" \/><\/figure>\n<\/div>\n\n\n<p><strong><mark style=\"background-color:#fcb900\" class=\"has-inline-color\">1) IT MUST LEAD RIGHT AWAY TO A FASTER FLOW.<\/mark><\/strong><br>The moving of tasks\/responsibilities outside the team must increase right away the speed of the flow of work. As a result, the bottleneck currently hindering the flow of work should be mitigated and the overall lead time reduced right away. Frequently used services such as cloud environments procurement, automated testing and deployment, and similar, should be fully automated before moving them outside the team, to allow for self-procurement.<br><br><strong><mark style=\"background-color:#fcb900\" class=\"has-inline-color\">2) THE STEWARDSHIP OF TASKS\/RESPONSIBILITIES MOVED OUTSIDE THE TEAM MUST BE EFFECTIVE.<\/mark><\/strong><\/p>\n\n\n\n<p><strong>2.1) Accessing the moved tasks\/responsibilities must remain simple, practical and convenient<\/strong><br>The individual, function, external agency or internal team taking ownership of the moved tasks\/responsibilities must serve the client team via an &#8220;interface&#8221; and &#8220;protocol&#8221; that shield them from the &#8220;internals&#8221; of the work and that is orders of magnitude simpler than the work to be done. As a result, the cognitive load and workload of the client team must decrease.<br><br><strong>2.2) All technical and non-technical dependencies should be removed before moving the tasks\/responsibilities outside the team<\/strong><br>The client team won&#8217;t have to pay hidden costs in terms of planning constraints and collaboration friction with the new owners of the tasks\/responsibilities, costs inevitably resulting from any existing dependencies other than the public access to the service itself.<\/p>\n\n\n\n<p><strong><mark style=\"background-color:#fcb900\" class=\"has-inline-color\">3) THE MOVE MUST BE DONE GRADUALLY ENSURING AT EACH STEP ALL THE POINTS ABOVE ARE FULLY MET.<\/mark><\/strong><br>The tasks\/responsibilities in order to fully meet the points above and therefore be conveniently moved outside a team, need to reach a level of maturity, stability and a level of codification of their knowledge and understanding that requires a certain amount of time and work.<br>Only a small portion at a time of the tasks\/responsibilities that reached this stage should be moved outside the team. Even such a smaller move should be treated as an experiment where the outcomes should be tested against the points above and fixed or reverted as necessary.<br><strong>The delegation of the following portions of tasks\/responsibilities should follow the adage &#8220;First, make the change easy, then make the easy change&#8221; instead of the adage &#8220;It will get worse before it gets better&#8221;.<\/strong><\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>Conclusions: my personal experience with this<\/strong><\/h1>\n\n\n\n<p>I have seen many delegations of tasks\/responsibilities outside the team introduce long delays, reduce productivity, and make the life of the team much harder. After all, that&#8217;s why the rule of thumb in knowledge work and software development says &#8216;don&#8217;t do it&#8217; and suggests as an alternative the <a href=\"https:\/\/www.smharter.com\/blog\/2022\/11\/21\/transcending-agile-cross-team-collaboration-with-shared-work\/\" data-type=\"link\" data-id=\"https:\/\/www.smharter.com\/blog\/2022\/11\/21\/transcending-agile-cross-team-collaboration-with-shared-work\/\" target=\"_blank\" rel=\"noreferrer noopener\">Shared work<\/a>.<\/p>\n\n\n\n<p>In many cases, I have observed that the expected benefits of moving tasks\/responsibilities outside the team were overestimated because of the widespread beliefs from the industrial mass production era on the economies of scale that do not apply equally to knowledge work and software development. At the same time, the hidden costs were underestimated because only the teams were feeling the pain, that was otherwise ignored by the decision-makers.<\/p>\n\n\n\n<p>In a few other cases, where the potential benefits for the delegation were there, the problem has been a big-bang transition to the new structure, and the lack of experience and skills to approach it gradually in an effective way. The big-bang approach:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li> it is often rushed before the time the tasks\/responsibilities have reached the required maturity stage necessary to be effectively moved outside the team, and before the necessary work to remove the accidental dependencies is completed;<br><\/li>\n\n\n\n<li>when it does not succeed on the 1st try (as most things do) it does not allow us to learn what is not working, why the expected benefits are not there, and which bottleneck is still causing the delays.<\/li>\n<\/ul>\n\n\n\n<p>In some of the cases where it did not work, moving tasks\/responsibilities outside the team was just another silver bullet to avoid facing the really hard problem they had in front of them.<\/p>\n\n\n\n<p>I have also seen cases where it worked well. This brings me back to the reality that every technique has its tread-offs, pros and cons that need to be weighed under the specific context and circumstances that one is facing. These decisions cannot be faced following a trend, an ideology, or an oversimplified vision of the world, instead, they require professionalism, patience and time to explore the context, an open mind and a gradual empirical approach.<\/p>\n\n\n\n<p><strong>This is where I hope the criteria and guidelines that I have shared above might help.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Suggested readings:<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.smharter.com\/blog\/2022\/11\/21\/transcending-agile-cross-team-collaboration-with-shared-work\/\" data-type=\"post\" data-id=\"3016\">Transcending Agile cross-team collaboration with Shared work (3-part)<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.smharter.com\/blog\/2022\/08\/08\/agile-cross-team-collaboration-how-tos-long\/\" data-type=\"post\" data-id=\"2807\">Agile cross-team collaboration HOW-TOs (4-part)<\/a><\/li>\n\n\n\n<li>Feature Teams Primer:&nbsp;<a href=\"https:\/\/featureteams.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/featureteams.org\/<\/a><\/li>\n\n\n\n<li>Feature Teams structure:&nbsp;<a href=\"https:\/\/less.works\/less\/structure\/feature-teams\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/less.works\/less\/structure\/feature-teams&nbsp;<\/a><\/li>\n\n\n\n<li>Feature Team Adoption Map:&nbsp;<a href=\"https:\/\/less.works\/less\/adoption\/feature-team-adoption_map\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/less.works\/less\/adoption\/feature-team-adoption_map<\/a>&nbsp;<\/li>\n\n\n\n<li>Collective code ownership:&nbsp;<a href=\"https:\/\/www.agilealliance.org\/glossary\/collective-ownership\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/www.agilealliance.org\/glossary\/collective-ownership<\/a><\/li>\n\n\n\n<li>Team Topologies:&nbsp;<a href=\"https:\/\/teamtopologies.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/teamtopologies.com\/<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/martinfowler.com\/articles\/talk-about-platforms.html\" target=\"_blank\" rel=\"noreferrer noopener\">What I Talk About When I Talk About Platforms<\/a> (from martinfowler.com)<\/li>\n\n\n\n<li><a href=\"https:\/\/martinfowler.com\/articles\/platform-prerequisites.html\" data-type=\"link\" data-id=\"https:\/\/martinfowler.com\/articles\/platform-prerequisites.html\" target=\"_blank\" rel=\"noreferrer noopener\">Mind the platform execution gap<\/a> (from martinfowler.com)<\/li>\n\n\n\n<li>Wardley Mapping<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity is-style-wide\"\/>\n\n\n\n<p class=\"has-text-align-center\"><strong><a href=\"https:\/\/www.smharter.com\/blog\/2024\/01\/01\/when-how-to-move-effectively-tasks-responsibilities-outside-the-team\/\">&lt;&lt; Part 1<\/a><\/strong>  (Part 2)<\/p>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<div style=\"height:131px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"420\" height=\"318\" src=\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/nourish.png\" alt=\"\" class=\"wp-image-2016\"\/><\/figure>\n\n\n\n<p><\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"text-ads\">\n\t<h3>Elevate the Agility in your organisation.<\/h3>\n\t<p>\n\t<br>\n\tSee how we can help.\n\t<br>\n\tYou, your department, your organisation.\n\t<br><br>\n\t<\/p>\n\n\t<div class=\"local-scroll\">\n\n\t\t<a href=\"\/coaching.html#coaching_as_a_service\" target=\"_blank\" class=\"btn elastic-btn-mod btn-mod btn-dark btn-medium btn-round\" onclick=\"ga('send','event','Blog coaching-org-ads','Click coaching_as_a_service button','Advising, Mentoring, Coaching As A Service');\" rel=\"noopener noreferrer\">Advising, Mentoring, Coaching As A Service<\/a>\n\t<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Whether it is to a Subject Matter Expert, an external contractor, an Agency, a Global\/shared Function, a Team Topologies&#8217; Platform team or a Complicated subsystem team, when and how can some tasks and\/or responsibilities be effectively moved outside the team?<\/p>\n","protected":false},"author":2,"featured_media":3128,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[],"class_list":["post-3100","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-livingcomplexity","category-lean-agile"],"_links":{"self":[{"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/posts\/3100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/comments?post=3100"}],"version-history":[{"count":46,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/posts\/3100\/revisions"}],"predecessor-version":[{"id":3174,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/posts\/3100\/revisions\/3174"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/media\/3128"}],"wp:attachment":[{"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/media?parent=3100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/categories?post=3100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.smharter.ai\/blog\/wp-json\/wp\/v2\/tags?post=3100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}