{"id":8300,"date":"2018-12-25T21:53:39","date_gmt":"2018-12-25T16:23:39","guid":{"rendered":"http:\/\/innoroo.com\/blog\/?p=8300"},"modified":"2019-01-02T09:32:49","modified_gmt":"2019-01-02T04:02:49","slug":"interview-with-andy-carmichael","status":"publish","type":"post","link":"http:\/\/innoroo.com\/blog\/2018\/12\/25\/interview-with-andy-carmichael\/","title":{"rendered":"Interview with Andy Carmichael"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Andy Carmichael is a well-known name in the Agile and Kanban Community, and we are privileged to feature him in this edition. He never fails to amaze us with his humility, intelligence and vision.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In an interview with us, Andy shared his thoughts on questions like: \u201cWhy do organisations fail to achieve business agility?\u201d \u201cWhat\u2019s the difference between growing capability and increasing capacity?\u201d and most importantly, \u201cIs change always an improvement?\u201d He put his emphasis, not on being the right size, but on moving at the right speed, in today\u2019s world of heightened competition and disruption. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">This article is based on our conversation. Let\u2019s read\u2026<\/span><\/p>\n<p><b>Q1. What are the reasons of failure to achieve Business Agility for organisations?<\/b><\/p>\n<p>Andy:\u00a0<span style=\"font-weight: 400;\">It\u2019s an interesting question. There are many more reasons of failure, and many more different ways to fail, than to succeed. The first question I ask organisations though is what they want to achieve. Is business agility one of those things? Because if you are in a very stable situation and you have very stable business, agility isn\u2019t necessarily on the priority list of what must be achieved. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">On the other hand, nearly all organisations \u2013 including those in industries we consider most stable, where nothing seems to have changed in decades \u2013 face the disruption of new ways of doing business, and innovators entering into their markets. It means everybody must think about the need to change\u2026 the need to change fast. Remember: \u201cIt\u2019s not the big fish that eat the small ones, it\u2019s the fast that eat the slow!\u201d If your organisation is slow, there is a good chance that your competitors or new entrants into the market will disrupt it and take market share. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">So the first question is, \u201cIs agility an aim for the organization?\u201d If it isn\u2019t, you won\u2019t achieve it. If you realize that you <\/span><i><span style=\"font-weight: 400;\">do<\/span><\/i><span style=\"font-weight: 400;\"> need to become agile, there are still many reasons why you may fail. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, you need to <\/span><i><span style=\"font-weight: 400;\">plan<\/span><\/i><span style=\"font-weight: 400;\"> to become more agile (more able to respond rapidly to changing market conditions), and you need to <\/span><i><span style=\"font-weight: 400;\">invest<\/span><\/i><span style=\"font-weight: 400;\"> in those plans. If you want to encourage innovation, you need to <\/span><i><span style=\"font-weight: 400;\">communicate<\/span><\/i><span style=\"font-weight: 400;\"> that goal to staff and show how you will reward it. Traditional command and control approaches to managing business, and fixed long-term goals, won\u2019t work, particularly if disruptors are already entering your market and introducing new ways of working more successfully than you are. You have to think about the way the organisation can empowers its staff, and allow them to think differently, to try new things in a safe-to-fail manner. That allows the organisation to discover different ways of working. Agility comes from the chosen strategy of an organisation, and from its leaders\u2019 ability to communicate and encourage staff to implement that strategy.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When people say the word \u201cAgile\u201d, they are often only thinking about it in the context of software development. That software is important to business agility is not in question. Software has \u201ceaten the world,\u201d it is the driver for business transformation, it is the foundation of digital solutions. The way you create software, and the way you plan, manage and finance software development is crucial if you want to achieve business agility. However, I encourage leadership teams to consider first <\/span><i><span style=\"font-weight: 400;\">why<\/span><\/i><span style=\"font-weight: 400;\"> they want to achieve business agility, and what it involves in terms of the changes needed in their organisation. Then they can start planning, not only how it will change software development, but also every other area of the business. Each area, just like the software teams, must invest in new ways of doing business, must try multiple things to see what works; must act before knowing if it <\/span><i><span style=\"font-weight: 400;\">will<\/span><\/i><span style=\"font-weight: 400;\"> work, learning from failures and exploiting successes. Rather than waiting for the fully developed ideas \u2013 the big up-front plans with every component costed and all outcomes forecast, the big implementation and the big-bang delivery \u2013 smaller steps and more learning on the journey is essential. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">These are strategies for moving faster than your competitors and ensuring survival in rapidly moving markets. That\u2019s why business agility is important. It answers the existential question of how we survive in this rapidly changing world, where organisations can quickly discover they are no longer fit for the new competitive landscape. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Back to some of the reasons for failure to achieve business agility:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Not wanting it<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Wanting, but not planning for it<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Planning, but not investing in it<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Not seeing through the changes<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Not dealing with the negative consequences of innovation in the organisation \u2013 not ensuring there is safety in both failed experiments, and successful ones that disrupt existing parts of the business. <\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">One other thing. People think there is some magic method or strategy or formula that makes organisations agile. There are principles to learn, but there is no formula. Applying those principles in the unique context of your business, your market and your people \u2013 and helping your people to innovate \u2013 is where business agility comes from.<\/span><\/p>\n<p><b>Q2. What is your take on developing\/growing capability vs increasing capacity?<\/b><\/p>\n<p>Andy:\u00a0<span style=\"font-weight: 400;\">This is a subtle question, albeit an important one. We often talk in Kanban about the need for balance\u2026 particularly balancing demand against \u201ccapacity\u201d. That\u2019s why we use work-in-progress limits, so that we don\u2019t take on more demand than the capacity of the system can service. But it\u2019s not just capacity (how much we can do), it is more accurately \u201ccapability\u201d (how much we can do of the specific types of work demanded). <\/span><\/p>\n<p><span style=\"font-weight: 400;\">We have demand for work (from customers of our service) and we have capability to provide completed work (provided it matches our skills). These are only in balance if both the amount of work, and the <\/span><i><span style=\"font-weight: 400;\">type<\/span><\/i><span style=\"font-weight: 400;\"> of work is not beyond the \u201ccapability\u201d of the service. If what is demanded is always the same over time, capacity may be all we worry about \u2013 we know we can do that type of work as long as we have enough resources and time. However where the type of work also changes \u2013 and in \u201cknowledge work\u201d it nearly always does \u2013 Kanban services need the flexibility, not just to produce <\/span><i><span style=\"font-weight: 400;\">enough<\/span><\/i><span style=\"font-weight: 400;\"> stuff, but also to produce the <\/span><i><span style=\"font-weight: 400;\">right<\/span><\/i><span style=\"font-weight: 400;\"> stuff for present and future demand.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In building effective Kanban services, we are interested in systems that can effectively deliver what the customers need. It\u2019s all about the flow of work from customer need to needs met. Because the needs vary in the type of work demanded, we need to have flexible <\/span><i><span style=\"font-weight: 400;\">capability<\/span><\/i><span style=\"font-weight: 400;\">, as well as sufficient capacity for that demand. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">So it is right to focus on capability and the development of flexible capability to meet all types of demand. I think it is also true to say that we should <\/span><i><span style=\"font-weight: 400;\">first<\/span><\/i><span style=\"font-weight: 400;\"> pay attention to the capacity of Kanban systems. How many work items or requests for change can we service with the teams that we are have? That\u2019s an aspect to manage, quite apart from the variability that requires different kinds of skills. It helps us to limit work in progress, by counting the number of work items we are dealing with, and limiting that to a number which is in balance with the capacity of team. This is the first step in applying the general practice in Kanban: limit work in progress.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">After that, we can recognise that it\u2019s not just how <\/span><i><span style=\"font-weight: 400;\">many<\/span><\/i><span style=\"font-weight: 400;\"> items that can overload a system, but also the variability in the <\/span><i><span style=\"font-weight: 400;\">types<\/span><\/i><span style=\"font-weight: 400;\"> of demand. So it\u2019s appropriate to look at how we deploy resources to cope with this variability \u2013 not just limiting the capacity on the supply side, but building more flexibility in our Kanban services to match the variability in the type of demand. We need to ensure that we have the <\/span><i><span style=\"font-weight: 400;\">capability<\/span><\/i><span style=\"font-weight: 400;\"> to serve what customers are asking for and will ask for. We should look for where there are gaps in skills \u2013 where we have only one person who can do a particular part of the job for example. That may well end up being the bottleneck in the process, so if we need to grow capability, we must have more flexible staff that can move to that part of the process when needed. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">There\u2019s a final important aspect I want to come back to. When we are applying Kanban in knowledge work, as opposed to applying it in a manufacturing or logistics context, we must realise that it\u2019s in the nature of knowledge work to be variable. There are many more skills, and more variations in those skills, that are needed to fulfil the requirements than in say, traditional manufacturing. We should therefore build teams and services with flexibility and learning at their core. Growing capability is in the end much more important than merely growing capacity.<\/span><\/p>\n<p><b>Q3. Is a change always an improvement?<\/b><\/p>\n<p>Andy:\u00a0<span style=\"font-weight: 400;\">No. Change is not always an improvement. Next question! <\/span><\/p>\n<p><span style=\"font-weight: 400;\">What? You want more than that? <\/span><span style=\"font-weight: 400;\">\ud83d\ude0a<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Perhaps, a bit more then! Remember, change usually breaks things. Gerry Weinberg used to tell a story to demonstrate this. He said that if you change your alarm clock, the chances are that you are going to miss an appointment next week. Simply because you have changed something. Either you don\u2019t understand how to set the new alarm clock, or you leave a button down that should be up, or whatever. If you change something in what you always do, the chances are something will break. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">We should realize that we are in the <\/span><i><span style=\"font-weight: 400;\">job<\/span><\/i><span style=\"font-weight: 400;\"> of change management. Kanban is primarily a method about managing change. But when you change things, you break things. So be sure about what you are trying to change, and most especially why! Is there some source of dissatisfaction in the organization about how you do the work, how are you able to meet customer demands, the quality of work, or the need to learn and innovate? Is there something in current situation that <\/span><i><span style=\"font-weight: 400;\">requires<\/span><\/i><span style=\"font-weight: 400;\"> change? You need to know that, and then work out how to change\u2026 how you overcome that problem. That\u2019s the starting point.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Is change always an improvement? No. Change is almost always <\/span><i><span style=\"font-weight: 400;\">not<\/span><\/i><span style=\"font-weight: 400;\"> an improvement unless you are focused on what you are trying to improve. Improving agility is different from increasing capacity. You can get <\/span><i><span style=\"font-weight: 400;\">more<\/span><\/i><span style=\"font-weight: 400;\"> stuff done by standardising, or using a methodical approach, or mechanically following a process and getting faster at it so you produce more. But if you are seeking business agility, it\u2019s likely you will prioritise getting <\/span><i><span style=\"font-weight: 400;\">different<\/span><\/i><span style=\"font-weight: 400;\"> stuff done, rather than more of the old stuff. If you are going to make a change, make sure you know why you want to change, and focus on that. Look at whether the changes made are moving you towards the goal, and respond accordingly. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">All this relates to the change management principles in Kanban. They explicitly say to \u201cstart with what you are doing now\u201d. Don\u2019t change everybody\u2019s roles, don\u2019t change everybody\u2019s job titles, don\u2019t change the processes even. Start from what you are doing and look at what are you are trying to do. Understand the gap in terms capabilities. Then we can make progress from there. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Secondly, seek agreement. Seek agreement with the people who are going to implement change at every level in the organization. You can then evolve from where you are. Evolution is not necessarily a slow process. Very often a revolutionary approach that sweeps away what\u2019s been there for years, ends up being a longer process, just because of the disruption caused and the resistance to change that\u2019s generated. That can be a very negative experience. Instead seek agreement together as you evolve towards your goals. Apply the principles of evolution: try multiple things to see what works and what doesn\u2019t, and then move towards your goal with that learning. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">The third of Kanban\u2019s three change management principles is \u201cleadership at every level.\u201d It depends on everyone leading in their own capacity, gaining understanding of what\u2019s needed, innovating, and also being able to recover and to use the learning when innovations don\u2019t work. Then building that learning into to what you do next. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Start where you are, agree together to evolve towards the goals, and lead at every level. These are vital principles behind successful change.<\/span><\/p>\n<p><b>Q4. What are the significant benefits of negative feedback loops?<\/b><\/p>\n<p>Andy:\u00a0<span style=\"font-weight: 400;\">Wow! Another quite technical question. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">The thing about feedback loops is they can be negative or positive. That doesn\u2019t mean good or bad. That\u2019s about whether the loops move the system in the same direction as the feedback (positive) or in the opposite direction to the feedback (negative). So a positive feedback loop could be when I praise you for doing something, you do more of it. Then you get more praise and do even more! This is a \u201cvirtuous circle\u201d. I get more and more of what I want, it seems. However positive feedback loops also work as \u201cvicious circles,\u201d if the change is in the opposite direction. I shout at you for not doing something perhaps, you get de-motivated and do even less! Positive feedback loops drive change away from the equilibrium and they are important for that, but they are also dangerous for the same reason.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Negative feedback loops help stabilise systems (they are sometimes called stabilising loops). Negative feedback is fundamental to the control (and evolution) of systems. Take your air-conditioning unit for example. The feedback loop compares the temperature in the room with the requested temperature on the thermostat. If the room is hotter, the system acts in the <\/span><i><span style=\"font-weight: 400;\">opposite<\/span><\/i><span style=\"font-weight: 400;\"> direction to cool the room. Or if the room is colder, the system again acts in the opposite direction to heat the room. This opposing action in the negative feedback loop allows effective control, and that is the key benefit of negative feedback.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Your question though, might imply that because negative feedback loops are beneficial, that\u2019s all we need. In fact there has to be both the kinds of feedback loops in complex systems. Without positive feedback loops, it\u2019s hard to effect change, but without negative feedback loops it\u2019s impossible to control change.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let\u2019s take the idea of putting your foot down in the car making the car go faster. There\u2019s a positive feedback loop between the brain of chauffeur and speed of car here. When the car gets faster, the brain thinks \u201c<\/span><i><span style=\"font-weight: 400;\">This is good, this is exciting \u2013 I will push this accelerator a little bit more. Oh! I am going even faster \u2013 this is good\u201d.<\/span><\/i><span style=\"font-weight: 400;\"> If there is no negative feedback, it\u2019s fairly clear that we are going to crash! Somewhere a negative feedback loop has to kick in \u2013 fear of crashing for example \u2013 that results in the brain sending signals to reduce speed, stabilising the system. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">These are the benefits of the different kinds of feedback loop: to effect change and to control the change. It\u2019s necessary to have both kinds of loop in systems we wish to manage\u2026 Kanban systems and management systems included.<\/span><\/p>\n<p><strong>Q5.\u00a0Is there a role for Kanban outside IT and Software development?<\/strong><\/p>\n<p>Andy:\u00a0<span style=\"font-weight: 400;\">Kanban, its principles and general practices, <\/span><i><span style=\"font-weight: 400;\">are<\/span><\/i><span style=\"font-weight: 400;\"> very much relevant outside IT. If we want to achieve the full benefits of Kanban and Agile, we should look outside the limited scope of just one department or one service. There is work flowing from customer needs to needs met continuously within organisations. The principles and practices we have talked about are certainly applicable to how that \u201cnetwork of services\u201d is controlled and improved, and how work continues to flow, continues to deliver value to customers, and hopefully continuously improves. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you just look at one part, say software development, but ignore what that\u2019s connected to \u2013 how we sell software, how we market software, how we use software within products or services, how we connect to the physical artefacts that we deliver to customers \u2013 we fail to use the full potential of this approach. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Yes. Using the same principles throughout the knowledge work of an organization is very important. It is vital to realise all the potential benefits.<\/span><\/p>\n<p><strong>Q6. One advice for new age Agile\/Kanban Practitioners?<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">Andy:\u00a0<\/span><span style=\"font-weight: 400;\">Learn the principles. Apply them in your context. As I said before, there is no formula!<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" data-attachment-id=\"8306\" data-permalink=\"http:\/\/innoroo.com\/blog\/2018\/12\/25\/interview-with-andy-carmichael\/andy-carmichael-287x300\/\" data-orig-file=\"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-287X300.png?fit=287%2C300\" data-orig-size=\"287,300\" data-comments-opened=\"1\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"Andy Carmichael -287X300\" data-image-description=\"\" data-image-caption=\"\" data-medium-file=\"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-287X300.png?fit=287%2C300\" data-large-file=\"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-287X300.png?fit=287%2C300\" class=\"alignleft size-thumbnail wp-image-8306\" src=\"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-287X300.png?resize=150%2C150\" alt=\"\" width=\"150\" height=\"150\" srcset=\"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-287X300.png?resize=150%2C150 150w, https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-287X300.png?resize=60%2C60 60w\" sizes=\"auto, (max-width: 150px) 100vw, 150px\" \/><span style=\"font-weight: 400;\">Andy Carmichael is a coach, consultant, and business builder who has been at the forefront of process change in software development teams for many years. He\u2019s the principal Kanban trainer and coach for Huge.IO in the UK and Ireland, and he\u2019s an author, speaker and blogger who\u2019s active in getting the lessons of Lean and Agile into the wider business community. He co-authored a guide to Kanban, <\/span><i><span style=\"font-weight: 400;\">Essential Kanban Condensed<\/span><\/i><span style=\"font-weight: 400;\">, with David J Anderson. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">He is active in the Kanban and Agile communities and is a Kanban Coaching Professional and Accredited Kanban Trainer.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Andy Carmichael is a well-known name in the Agile and Kanban Community, and we are privileged to feature him in this edition. He never fails to amaze us with his humility, intelligence and vision. In an interview with us, Andy shared his thoughts on questions like: \u201cWhy do organisations fail to achieve business agility?\u201d \u201cWhat\u2019s [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":8301,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[9],"tags":[17,103,815,65,3,1763,116,110,393,23],"class_list":["post-8300","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interview-series","tag-agile","tag-agile-team","tag-business-agility","tag-continuous-delivery","tag-kanban","tag-kanban-method","tag-leadership","tag-software-development","tag-strategy","tag-thought-of-the-day"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/12\/Andy-Carmichael-Interview-Banner.png?fit=750%2C410","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8Rui8-29S","jetpack-related-posts":[],"_links":{"self":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/8300","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/comments?post=8300"}],"version-history":[{"count":6,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/8300\/revisions"}],"predecessor-version":[{"id":8324,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/8300\/revisions\/8324"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media\/8301"}],"wp:attachment":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media?parent=8300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/categories?post=8300"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/tags?post=8300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}