{"id":7861,"date":"2026-07-23T10:41:34","date_gmt":"2026-07-23T08:41:34","guid":{"rendered":"https:\/\/getnave.com\/blog\/?p=7861"},"modified":"2026-07-28T19:46:17","modified_gmt":"2026-07-28T17:46:17","slug":"blocked-tasks","status":"publish","type":"post","link":"https:\/\/getnave.com\/blog\/blocked-tasks\/","title":{"rendered":"How to Handle Blocked Tasks Without Losing Predictability"},"content":{"rendered":"
<\/div>\n

Every delivery team eventually runs into the same situation. A piece of work is progressing well until it suddenly stops. Maybe you’re waiting on another team. Maybe a customer needs to make a decision. Maybe an external supplier hasn’t delivered what you need.<\/p>\n

The team is ready to continue. The work isn’t.<\/p>\n

At that point every team has to answer a simple question. What do we do with the blocked task?<\/p>\n

Back in my early years as a delivery manager, I thought I had found the perfect answer. We created a blocked column. Whenever a task couldn’t move forward, we moved it there. The rest of the board stayed clean, everyone could keep pulling new work, and blocked items were easy to spot.<\/p>\n

It seemed like a sensible policy. It turned out to be one of the biggest mistakes we made.<\/p>\n

Why Moving Blocked Work Breaks Your Workflow<\/h2>\n

The problems didn’t appear overnight. At first everything looked better. The active columns kept moving, fewer cards appeared stuck, and the board looked healthier than before.<\/p>\n

Then the side effects started showing up.<\/p>\n

The first thing we lost was our focus on finishing work. Once moving blocked tasks aside became normal, starting new work became easier than completing what we’d already committed to. Every blocked task created permission to begin something else.<\/p>\n

Then our measurements stopped reflecting reality. A task would start, disappear into the blocked column for two weeks, and eventually come back into the workflow. We could no longer measure how long work actually took from start to finish. Every forecast we built inherited the same distortion. Eventually we started missing our delivery commitments.<\/p>\n

The final consequence wasn’t visible on any chart. It showed up in the team.<\/p>\n

Starting. Stopping. Restarting. Switching context. Trying to remember where we had left off. Anyone who has experienced it knows how exhausting that cycle becomes.<\/p>\n

At first these problems looked unrelated. Eventually we realized they all had the same cause.<\/p>\n

The Problem Wasn’t the Blocked Work. It Was Our Definition of Work in Progress<\/h2>\n

Our blocked column had no WIP limit. In other words, we’d created an “in progress” state where work no longer counted as work in progress.<\/p>\n

We weren’t reducing our WIP. We were moving work somewhere WIP no longer counted.<\/p>\n

Something else happened too. Once a task entered that column, it somehow felt like it wasn’t our responsibility anymore. Nobody consciously decided that. The design of the board made it feel that way.<\/p>\n

That’s when I realized we’d been solving the wrong problem. The problem wasn’t where blocked work should sit. The problem was how we thought about blocked work in the first place.<\/p>\n

Blocked Work Is Still Work in Progress<\/h2>\n

I still hear the same question today. “If the work is blocked anyway, why should it continue occupying a WIP slot? Why not let the team start something else?”<\/p>\n

Because blocked work is still work in progress.<\/p>\n

It still consumes delivery capacity. Your customer is still waiting. Your commitment still exists.<\/p>\n

Starting another task doesn’t create more capacity. It simply hides the commitment you’ve already made while creating another one.<\/p>\n

That’s why we changed our policy completely. When work blocks, it stays exactly where it stopped. We flag it. We record why it blocked. We note who is responsible for removing the obstacle. We write down when it became blocked. Then we talk about that blocker every day.<\/p>\n

Sometimes the fastest way to unblock the work is to lend someone to the team causing the dependency. Sometimes it requires escalating the issue outside the team. Either way, the blocked work stays visible because the commitment never disappeared.<\/p>\n

Use Your Blockers as Improvement Data<\/h2>\n

Those blocker records become far more valuable than most teams expect. Once a month, total the blocked days for each blocker. Very quickly you’ll discover that a small number of causes are responsible for most of your delivery delays.<\/p>\n

Now your improvement work has direction. Instead of asking, “How do we improve?” you can ask, “Which blocker is costing us the most delivery time?” That’s a much easier question to answer.<\/p>\n

If you’re using Nave, the Cycle Time Breakdown chart performs this blocker clustering analysis automatically, helping you identify which blockers have the greatest impact on your delivery times so you know where improvement will have the biggest effect first.<\/p>\n

\"Cycle<\/a>
\nAgile teams across the globe use the Cycle Time Breakdown chart by Nave to identify the blockers that slow them down the most.<\/em><\/p>\n

What I’d Do Differently Today<\/h2>\n

Looking back, I don’t think creating a blocked column was the mistake. The mistake was believing blocked work had somehow stopped being our work.<\/p>\n

It hadn’t. The customer was still waiting. The commitment was still there. The capacity was still occupied.<\/p>\n

Once we started treating blocked work as work in progress instead of work set aside, something changed. The conversations changed. The priorities changed. The improvements changed.<\/p>\n

We stopped asking how to keep the board looking clean. We started asking how to remove the obstacle preventing value from reaching the customer.<\/p>\n

<\/div>\n

That’s when flow improved. That’s when our forecasts became trustworthy again. And that’s when the blocked column stopped making sense.<\/p>\n

I’ll see you next week, same time and place for more managerial goodness. Bye for now.<\/p>\n

<\/div>\n
<\/div>","protected":false},"excerpt":{"rendered":"

Every delivery team eventually runs into the same situation. A piece of work is progressing well until it suddenly stops. Maybe you’re waiting on another team. Maybe a customer needs to make a decision. Maybe an external supplier hasn’t delivered what you need. The team is ready to continue. The work isn’t. At that point […]<\/p>\n","protected":false},"author":1,"featured_media":7868,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"yasr_overall_rating":0,"yasr_post_is_review":"","yasr_auto_insert_disabled":"","yasr_review_type":"","footnotes":""},"categories":[69,7],"tags":[1900,1901,1902,1904,1905,1813,1903,1800,1880],"class_list":["post-7861","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-process-improvement","category-project-management","tag-blocked-tasks","tag-blocked-work","tag-blocker-management","tag-board-policies","tag-continuous-improvement","tag-cycle-time","tag-delivery-forecasting","tag-flow-metrics","tag-wip-limits"],"acf":[],"yoast_head":"\nHow to Handle Blocked Tasks (Without Breaking Your Delivery Forecasts)<\/title>\n<meta name=\"description\" content=\"Most teams move blocked work out of the way. It feels like the right thing to do until your forecasts stop matching reality. Here's a better approach.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/getnave.com\/blog\/blocked-tasks\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Handle Blocked Tasks (Without Breaking Your Delivery Forecasts)\" \/>\n<meta property=\"og:description\" content=\"Most teams move blocked work out of the way. It feels like the right thing to do until your forecasts stop matching reality. Here's a better approach.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/getnave.com\/blog\/blocked-tasks\/\" \/>\n<meta property=\"og:site_name\" content=\"Nave Blog: Expert tips and guidelines for agile teams\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/getnave\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/NaveHQ\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-23T08:41:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-28T17:46:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Sonya Siderova\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@https:\/\/twitter.com\/NaveHQ\" \/>\n<meta name=\"twitter:site\" content=\"@getnave\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Sonya Siderova\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/\"},\"author\":{\"name\":\"Sonya Siderova\",\"@id\":\"https:\/\/getnave.com\/blog\/#\/schema\/person\/d758aa37dbe33f3696219f81bc52a5ea\"},\"headline\":\"How to Handle Blocked Tasks Without Losing Predictability\",\"datePublished\":\"2026-07-23T08:41:34+00:00\",\"dateModified\":\"2026-07-28T17:46:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/\"},\"wordCount\":887,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/getnave.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg\",\"keywords\":[\"blocked tasks\",\"blocked work\",\"blocker management\",\"board policies\",\"continuous improvement\",\"cycle time\",\"delivery forecasting\",\"flow metrics\",\"WIP limits\"],\"articleSection\":[\"Process Improvement\",\"Project Management\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/getnave.com\/blog\/blocked-tasks\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/\",\"url\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/\",\"name\":\"How to Handle Blocked Tasks (Without Breaking Your Delivery Forecasts)\",\"isPartOf\":{\"@id\":\"https:\/\/getnave.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg\",\"datePublished\":\"2026-07-23T08:41:34+00:00\",\"dateModified\":\"2026-07-28T17:46:17+00:00\",\"description\":\"Most teams move blocked work out of the way. It feels like the right thing to do until your forecasts stop matching reality. Here's a better approach.\",\"breadcrumb\":{\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/getnave.com\/blog\/blocked-tasks\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage\",\"url\":\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg\",\"contentUrl\":\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg\",\"width\":1536,\"height\":1024,\"caption\":\"How to Handle Blocked Tasks Without Losing Predictability | Illustration\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/getnave.com\/blog\/blocked-tasks\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/getnave.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Handle Blocked Tasks Without Losing Predictability\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/getnave.com\/blog\/#website\",\"url\":\"https:\/\/getnave.com\/blog\/\",\"name\":\"Nave Blog: Expert tips and guidelines for agile teams\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/getnave.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/getnave.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/getnave.com\/blog\/#organization\",\"name\":\"Nave\",\"url\":\"https:\/\/getnave.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/getnave.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/2018\/01\/nave-1.png\",\"contentUrl\":\"https:\/\/getnave.com\/blog\/wp-content\/uploads\/2018\/01\/nave-1.png\",\"width\":70,\"height\":18,\"caption\":\"Nave\"},\"image\":{\"@id\":\"https:\/\/getnave.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/getnave\",\"https:\/\/x.com\/getnave\",\"https:\/\/www.linkedin.com\/company\/6387485\/\",\"https:\/\/www.youtube.com\/channel\/UC-2BKBUVu5WPvVZD6te2aAA\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/getnave.com\/blog\/#\/schema\/person\/d758aa37dbe33f3696219f81bc52a5ea\",\"name\":\"Sonya Siderova\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/getnave.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d2c83a7d50c14385ac672f9a09bd32a51fd484d74f283e8c40f4e52a02c820db?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d2c83a7d50c14385ac672f9a09bd32a51fd484d74f283e8c40f4e52a02c820db?s=96&d=identicon&r=g\",\"caption\":\"Sonya Siderova\"},\"sameAs\":[\"https:\/\/getnave.com\",\"https:\/\/www.facebook.com\/NaveHQ\",\"https:\/\/www.linkedin.com\/company\/NaveHQ\",\"https:\/\/x.com\/https:\/\/twitter.com\/NaveHQ\"]},false]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Handle Blocked Tasks (Without Breaking Your Delivery Forecasts)","description":"Most teams move blocked work out of the way. It feels like the right thing to do until your forecasts stop matching reality. Here's a better approach.","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:\/\/getnave.com\/blog\/blocked-tasks\/","og_locale":"en_GB","og_type":"article","og_title":"How to Handle Blocked Tasks (Without Breaking Your Delivery Forecasts)","og_description":"Most teams move blocked work out of the way. It feels like the right thing to do until your forecasts stop matching reality. Here's a better approach.","og_url":"https:\/\/getnave.com\/blog\/blocked-tasks\/","og_site_name":"Nave Blog: Expert tips and guidelines for agile teams","article_publisher":"https:\/\/www.facebook.com\/getnave","article_author":"https:\/\/www.facebook.com\/NaveHQ","article_published_time":"2026-07-23T08:41:34+00:00","article_modified_time":"2026-07-28T17:46:17+00:00","og_image":[{"width":1536,"height":1024,"url":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg","type":"image\/jpeg"}],"author":"Sonya Siderova","twitter_card":"summary_large_image","twitter_creator":"@https:\/\/twitter.com\/NaveHQ","twitter_site":"@getnave","twitter_misc":{"Written by":"Sonya Siderova","Estimated reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#article","isPartOf":{"@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/"},"author":{"name":"Sonya Siderova","@id":"https:\/\/getnave.com\/blog\/#\/schema\/person\/d758aa37dbe33f3696219f81bc52a5ea"},"headline":"How to Handle Blocked Tasks Without Losing Predictability","datePublished":"2026-07-23T08:41:34+00:00","dateModified":"2026-07-28T17:46:17+00:00","mainEntityOfPage":{"@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/"},"wordCount":887,"commentCount":0,"publisher":{"@id":"https:\/\/getnave.com\/blog\/#organization"},"image":{"@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage"},"thumbnailUrl":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg","keywords":["blocked tasks","blocked work","blocker management","board policies","continuous improvement","cycle time","delivery forecasting","flow metrics","WIP limits"],"articleSection":["Process Improvement","Project Management"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/getnave.com\/blog\/blocked-tasks\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/","url":"https:\/\/getnave.com\/blog\/blocked-tasks\/","name":"How to Handle Blocked Tasks (Without Breaking Your Delivery Forecasts)","isPartOf":{"@id":"https:\/\/getnave.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage"},"image":{"@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage"},"thumbnailUrl":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg","datePublished":"2026-07-23T08:41:34+00:00","dateModified":"2026-07-28T17:46:17+00:00","description":"Most teams move blocked work out of the way. It feels like the right thing to do until your forecasts stop matching reality. Here's a better approach.","breadcrumb":{"@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/getnave.com\/blog\/blocked-tasks\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#primaryimage","url":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg","contentUrl":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/blocked-tasks-illustation.jpg","width":1536,"height":1024,"caption":"How to Handle Blocked Tasks Without Losing Predictability | Illustration"},{"@type":"BreadcrumbList","@id":"https:\/\/getnave.com\/blog\/blocked-tasks\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/getnave.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Handle Blocked Tasks Without Losing Predictability"}]},{"@type":"WebSite","@id":"https:\/\/getnave.com\/blog\/#website","url":"https:\/\/getnave.com\/blog\/","name":"Nave Blog: Expert tips and guidelines for agile teams","description":"","publisher":{"@id":"https:\/\/getnave.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/getnave.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/getnave.com\/blog\/#organization","name":"Nave","url":"https:\/\/getnave.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/getnave.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/2018\/01\/nave-1.png","contentUrl":"https:\/\/getnave.com\/blog\/wp-content\/uploads\/2018\/01\/nave-1.png","width":70,"height":18,"caption":"Nave"},"image":{"@id":"https:\/\/getnave.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/getnave","https:\/\/x.com\/getnave","https:\/\/www.linkedin.com\/company\/6387485\/","https:\/\/www.youtube.com\/channel\/UC-2BKBUVu5WPvVZD6te2aAA"]},{"@type":"Person","@id":"https:\/\/getnave.com\/blog\/#\/schema\/person\/d758aa37dbe33f3696219f81bc52a5ea","name":"Sonya Siderova","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/getnave.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d2c83a7d50c14385ac672f9a09bd32a51fd484d74f283e8c40f4e52a02c820db?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d2c83a7d50c14385ac672f9a09bd32a51fd484d74f283e8c40f4e52a02c820db?s=96&d=identicon&r=g","caption":"Sonya Siderova"},"sameAs":["https:\/\/getnave.com","https:\/\/www.facebook.com\/NaveHQ","https:\/\/www.linkedin.com\/company\/NaveHQ","https:\/\/x.com\/https:\/\/twitter.com\/NaveHQ"]},false]}},"yasr_visitor_votes":{"stars_attributes":{"read_only":false,"span_bottom":false},"number_of_votes":5,"sum_votes":25},"_links":{"self":[{"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/posts\/7861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/comments?post=7861"}],"version-history":[{"count":0,"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/posts\/7861\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/media\/7868"}],"wp:attachment":[{"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/media?parent=7861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/categories?post=7861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/getnave.com\/blog\/wp-json\/wp\/v2\/tags?post=7861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}