From 266df8f2097816508c3a8bc4e5819dc030581a08 Mon Sep 17 00:00:00 2001
From: "Martin Hinshelwood nkdAgility.com" <martin@nkdagility.com>
Date: Thu, 30 Jan 2025 11:02:23 +0000
Subject: [PATCH 1/4] =?UTF-8?q?=E2=9C=A8=20(blog.html):=20conditionally=20?=
 =?UTF-8?q?load=20Elevenlabs=20AudioNative=20Player=20for=20recent=20posts?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The Elevenlabs AudioNative Player is now only included for blog posts published within the last 5 years. This change optimizes the page load time for older posts by not loading unnecessary scripts and widgets, enhancing the user experience for readers accessing archived content.
---
 site/layouts/resources/blog.html | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/site/layouts/resources/blog.html b/site/layouts/resources/blog.html
index 30d6cb188b..9bb17005a7 100644
--- a/site/layouts/resources/blog.html
+++ b/site/layouts/resources/blog.html
@@ -16,10 +16,15 @@ <h2 class="mb-4 nkda-heading-secondary">{{- .Params.subtitle | markdownify }}</h
 {{- end }}
 
 {{- define "main" }}
-  <section class="container my-5" style="max-width: 700px !important">
-    <div id="elevenlabs-audionative-widget" data-height="90" data-width="100%" data-frameborder="no" data-scrolling="no" data-publicuserid="71edc96043fbd75e5e1bd94d997b31cfa7932b5e94d7296094d7bc2906e081ab" data-playerurl="https://elevenlabs.io/player/index.html">Loading the <a href="https://elevenlabs.io/text-to-speech" target="_blank" rel="noopener">Elevenlabs Text to Speech</a> AudioNative Player...</div>
-    <script src="https://elevenlabs.io/player/audioNativeHelper.js" type="text/javascript"></script>
-  </section>
+
+  {{ if (gt .PublishDate (now.AddDate -5 0 0)) }}
+    <section class="container my-5" style="max-width: 700px !important">
+      <div id="elevenlabs-audionative-widget" data-height="90" data-width="100%" data-frameborder="no" data-scrolling="no" data-publicuserid="71edc96043fbd75e5e1bd94d997b31cfa7932b5e94d7296094d7bc2906e081ab" data-playerurl="https://elevenlabs.io/player/index.html">Loading the <a href="https://elevenlabs.io/text-to-speech" target="_blank" rel="noopener">Elevenlabs Text to Speech</a> AudioNative Player...</div>
+      <script src="https://elevenlabs.io/player/audioNativeHelper.js" type="text/javascript"></script>
+    </section>
+  {{ end }}
+
+
   <section class="container my-5 content" style="max-width: 700px !important">
     {{- .Content }}
   </section>

From baa2706bdd6a875e6c67840ae187da047b635701 Mon Sep 17 00:00:00 2001
From: "Martin Hinshelwood nkdAgility.com" <martin@nkdagility.com>
Date: Thu, 30 Jan 2025 11:13:12 +0000
Subject: [PATCH 2/4] =?UTF-8?q?=E2=9C=A8=20(blog):=20add=20AudioNative=20s?=
 =?UTF-8?q?upport=20to=20blog=20posts=20for=20enhanced=20accessibility?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Add the `AudioNative` parameter to blog posts to enable audio
rendering. This change enhances accessibility by providing an audio
version of the content, making it more inclusive for users who prefer
or require audio content. The layout logic is updated to conditionally
render the audio player based on the `AudioNative` flag and the
environment, ensuring that audio is only rendered in production.
---
 .../index.md                                  |  1 +
 .../index.md                                  | 21 ++++++++++---------
 .../index.md                                  | 17 ++++++++-------
 site/layouts/resources/blog.html              | 12 ++++++++---
 4 files changed, 30 insertions(+), 21 deletions(-)

diff --git a/site/content/resources/blog/2021/2021-03-15-hiring-a-professional-scrum-master/index.md b/site/content/resources/blog/2021/2021-03-15-hiring-a-professional-scrum-master/index.md
index 240b93ebbe..f3be391f48 100644
--- a/site/content/resources/blog/2021/2021-03-15-hiring-a-professional-scrum-master/index.md
+++ b/site/content/resources/blog/2021/2021-03-15-hiring-a-professional-scrum-master/index.md
@@ -2,6 +2,7 @@
 title: Hiring a Professional Scrum Master
 description: Discover essential insights for hiring a Scrum Master. Learn key skills, certifications, and role expectations to find the perfect fit for your team.
 date: 2021-03-15
+AudioNative: true
 creator: Martin Hinshelwood
 layout: blog
 resourceTypes: blog
diff --git a/site/content/resources/blog/2023/2023-08-24-sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/index.md b/site/content/resources/blog/2023/2023-08-24-sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/index.md
index 5e0b280ef7..2ea5c71670 100644
--- a/site/content/resources/blog/2023/2023-08-24-sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/index.md
+++ b/site/content/resources/blog/2023/2023-08-24-sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/index.md
@@ -1,26 +1,27 @@
 ---
-title: 'Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness'
+title: "Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness"
 description: Master the art of crafting a lean Product Backlog that balances current needs and future readiness, ensuring clarity and value for your team and stakeholders.
 date: 2023-08-24
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49523"
 layout: blog
 resourceTypes: blog
 slug: sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness
 aliases:
-- /blog/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness
-- /sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness
-- /sculpting-the-product-backlog--a-delicate-balance-between-lean-inventory-and-future-readiness
-- /blog/sculpting-the-product-backlog--a-delicate-balance-between-lean-inventory-and-future-readiness
+  - /blog/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness
+  - /sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness
+  - /sculpting-the-product-backlog--a-delicate-balance-between-lean-inventory-and-future-readiness
+  - /blog/sculpting-the-product-backlog--a-delicate-balance-between-lean-inventory-and-future-readiness
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- measure-and-learn
-- people-and-process
+  - measure-and-learn
+  - people-and-process
 preview: image-1.jpg
-
 ---
+
 In the realm of product development, crafting an efficient Product Backlog is an endeavour akin to sculpting a masterpiece. Just as sculptors chisel away the excess marble to reveal the form within, product managers must carefully mould their backlog, ensuring it's a lean inventory that reflects the unrealized value of the product. The Product Backlog must encapsulate our current aspirations for the product while being transparent and understandable to all stakeholders. It’s a living artefact that dynamically evolves with the product. However, we must also resist the temptation to create an overwhelming catalogue that loses its sharpness and becomes a weight dangling around the team's neck.
 
 ## TLDR;
diff --git a/site/content/resources/blog/2023/2023-12-14-the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar/index.md b/site/content/resources/blog/2023/2023-12-14-the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar/index.md
index 43c553a853..10bfe29449 100644
--- a/site/content/resources/blog/2023/2023-12-14-the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar/index.md
+++ b/site/content/resources/blog/2023/2023-12-14-the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar/index.md
@@ -2,24 +2,25 @@
 title: "The Evolution of Agile Learning: Insights from Scrum.org's Webinar"
 description: Discover the future of Agile training with immersive learning insights from Scrum.org's webinar. Enhance your skills and drive real change in your organization!
 date: 2023-12-14
+AudioNative: true
 creator: Martin Hinshelwood
 id: "50979"
 layout: blog
 resourceTypes: blog
 slug: the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar
 aliases:
-- /blog/the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar
-- /the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar
-- /the-evolution-of-agile-learning--insights-from-scrum-org's-webinar
-- /blog/the-evolution-of-agile-learning--insights-from-scrum-org's-webinar
+  - /blog/the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar
+  - /the-evolution-of-agile-learning-insights-from-scrum-orgs-webinar
+  - /the-evolution-of-agile-learning--insights-from-scrum-org's-webinar
+  - /blog/the-evolution-of-agile-learning--insights-from-scrum-org's-webinar
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-TheEvolutionofAgileLearning-1-1-16-16.jpg
-
 ---
+
 This week, I participated in a [Scrum.org](http://scrum.org/) Webinar hosted by Sabrina Love (Scrum.org Product Owner) as well as my colleagues, [Joanna Płaskonka, Ph.D.](https://www.linkedin.com/article/edit/7140678898370928640/?author=urn%3Ali%3Afsd_profile%3AACoAAAAUzPABQyVbo7yoAY7fK8HpaEwXfTa5iCY#) and [Alex Ballarin](https://www.linkedin.com/article/edit/7140678898370928640/?author=urn%3Ali%3Afsd_profile%3AACoAAAAUzPABQyVbo7yoAY7fK8HpaEwXfTa5iCY#) to discuss the state of learning and how immersive learning is the future of training.
 
 You can watch the video below to hear what we say, but it's also worth framing the problem and the need for change here. I welcome all feedback!
diff --git a/site/layouts/resources/blog.html b/site/layouts/resources/blog.html
index 9bb17005a7..631b117303 100644
--- a/site/layouts/resources/blog.html
+++ b/site/layouts/resources/blog.html
@@ -17,10 +17,16 @@ <h2 class="mb-4 nkda-heading-secondary">{{- .Params.subtitle | markdownify }}</h
 
 {{- define "main" }}
 
-  {{ if (gt .PublishDate (now.AddDate -5 0 0)) }}
+  {{ if or (gt .PublishDate (now.AddDate -1 0 0)) (.Params.AudioNative) }}
     <section class="container my-5" style="max-width: 700px !important">
-      <div id="elevenlabs-audionative-widget" data-height="90" data-width="100%" data-frameborder="no" data-scrolling="no" data-publicuserid="71edc96043fbd75e5e1bd94d997b31cfa7932b5e94d7296094d7bc2906e081ab" data-playerurl="https://elevenlabs.io/player/index.html">Loading the <a href="https://elevenlabs.io/text-to-speech" target="_blank" rel="noopener">Elevenlabs Text to Speech</a> AudioNative Player...</div>
-      <script src="https://elevenlabs.io/player/audioNativeHelper.js" type="text/javascript"></script>
+      {{- if ne hugo.Environment "production" }}
+        <div>RENDER AUDIO NATIVE from Eleven Labs (Production only)</div>
+        <div>PublishDate: {{ .PublishDate }} | {{ (gt .PublishDate (now.AddDate -1 0 0)) }}</div>
+        <div>AudioNative: {{ .Params.AudioNative }}</div>
+      {{- else -}}
+        <div id="elevenlabs-audionative-widget" data-height="90" data-width="100%" data-frameborder="no" data-scrolling="no" data-publicuserid="71edc96043fbd75e5e1bd94d997b31cfa7932b5e94d7296094d7bc2906e081ab" data-playerurl="https://elevenlabs.io/player/index.html">Loading the <a href="https://elevenlabs.io/text-to-speech" target="_blank" rel="noopener">Elevenlabs Text to Speech</a> AudioNative Player...</div>
+        <script src="https://elevenlabs.io/player/audioNativeHelper.js" type="text/javascript"></script>
+      {{- end -}}
     </section>
   {{ end }}
 

From 81f35da386496750a4b7c14725aa14e4b8afd492 Mon Sep 17 00:00:00 2001
From: "Martin Hinshelwood nkdAgility.com" <martin@nkdagility.com>
Date: Thu, 30 Jan 2025 11:16:53 +0000
Subject: [PATCH 3/4] =?UTF-8?q?=F0=9F=93=9D=20(blog.html):=20remove=20outd?=
 =?UTF-8?q?ated=20publish=20date=20condition=20for=20audio=20rendering?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The condition checking if the publish date is within the last year is removed. The audio rendering logic now solely relies on the presence of the AudioNative parameter. This change simplifies the logic and ensures that audio rendering is not inadvertently skipped due to date constraints, aligning with the current content strategy.
---
 site/layouts/resources/blog.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/layouts/resources/blog.html b/site/layouts/resources/blog.html
index 631b117303..24820d61ba 100644
--- a/site/layouts/resources/blog.html
+++ b/site/layouts/resources/blog.html
@@ -17,11 +17,11 @@ <h2 class="mb-4 nkda-heading-secondary">{{- .Params.subtitle | markdownify }}</h
 
 {{- define "main" }}
 
-  {{ if or (gt .PublishDate (now.AddDate -1 0 0)) (.Params.AudioNative) }}
+  <!-- Change this date as needed -->
+  {{ if .Params.AudioNative }}
     <section class="container my-5" style="max-width: 700px !important">
       {{- if ne hugo.Environment "production" }}
         <div>RENDER AUDIO NATIVE from Eleven Labs (Production only)</div>
-        <div>PublishDate: {{ .PublishDate }} | {{ (gt .PublishDate (now.AddDate -1 0 0)) }}</div>
         <div>AudioNative: {{ .Params.AudioNative }}</div>
       {{- else -}}
         <div id="elevenlabs-audionative-widget" data-height="90" data-width="100%" data-frameborder="no" data-scrolling="no" data-publicuserid="71edc96043fbd75e5e1bd94d997b31cfa7932b5e94d7296094d7bc2906e081ab" data-playerurl="https://elevenlabs.io/player/index.html">Loading the <a href="https://elevenlabs.io/text-to-speech" target="_blank" rel="noopener">Elevenlabs Text to Speech</a> AudioNative Player...</div>

From 7646602dc03629926197ce0fbc5fad1e8b500093 Mon Sep 17 00:00:00 2001
From: "Martin Hinshelwood nkdAgility.com" <martin@nkdagility.com>
Date: Thu, 30 Jan 2025 11:21:07 +0000
Subject: [PATCH 4/4] =?UTF-8?q?=F0=9F=93=9D=20(blog):=20add=20AudioNative?=
 =?UTF-8?q?=20flag=20to=20blog=20posts=20for=20enhanced=20accessibility?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The addition of the `AudioNative: true` flag to the blog posts enables audio versions of the content, making it more accessible to users who prefer listening over reading. This change supports inclusivity and caters to a wider audience, including those with visual impairments or those who consume content on-the-go.
---
 .../index.md                                  | 27 ++++++-----
 .../index.md                                  | 23 ++++-----
 .../index.md                                  | 23 ++++-----
 .../index.md                                  | 15 +++---
 .../index.md                                  | 29 ++++++------
 .../index.md                                  | 21 +++++----
 .../index.md                                  | 19 ++++----
 .../index.md                                  | 21 +++++----
 .../index.md                                  | 17 +++----
 .../index.md                                  | 23 ++++-----
 .../index.md                                  | 13 ++---
 .../index.md                                  | 23 ++++-----
 .../index.md                                  | 15 +++---
 .../index.md                                  | 47 ++++++++++---------
 .../index.md                                  | 19 ++++----
 .../index.md                                  | 17 +++----
 .../index.md                                  | 17 +++----
 .../index.md                                  | 21 +++++----
 .../index.md                                  | 15 +++---
 .../index.md                                  | 15 +++---
 .../index.md                                  | 21 +++++----
 .../index.md                                  | 15 +++---
 .../index.md                                  | 19 ++++----
 .../index.md                                  | 25 +++++-----
 .../index.md                                  | 25 +++++-----
 .../index.md                                  | 19 ++++----
 .../index.md                                  | 13 ++---
 .../index.md                                  | 19 ++++----
 .../index.md                                  | 21 +++++----
 .../index.md                                  | 17 +++----
 .../index.md                                  | 21 +++++----
 .../index.md                                  |  9 ++--
 .../index.md                                  | 13 ++---
 .../index.md                                  | 17 +++----
 .../index.md                                  | 25 ++++++----
 .../index.md                                  | 19 ++++----
 .../index.md                                  |  1 +
 .../index.md                                  |  1 +
 .../index.md                                  |  1 +
 39 files changed, 383 insertions(+), 338 deletions(-)

diff --git a/site/content/resources/blog/2020/2020-12-14-getting-started-definition-done-dod/index.md b/site/content/resources/blog/2020/2020-12-14-getting-started-definition-done-dod/index.md
index 8d5bacdd4f..323773d93e 100644
--- a/site/content/resources/blog/2020/2020-12-14-getting-started-definition-done-dod/index.md
+++ b/site/content/resources/blog/2020/2020-12-14-getting-started-definition-done-dod/index.md
@@ -2,29 +2,30 @@
 title: Getting started with a Definition of Done (DoD)
 description: Learn how to establish a robust Definition of Done (DoD) for your Scrum team to ensure quality and transparency in software delivery. Start improving today!
 date: 2020-12-14
+AudioNative: true
 creator: Martin Hinshelwood
 id: "38238"
 layout: blog
 resourceTypes: blog
 slug: getting-started-definition-done-dod
 aliases:
-- /blog/getting-started-definition-done-dod
-- /getting-started-definition-done-dod
-- /getting-started-with-a-definition-of-done-(dod)
-- /blog/getting-started-with-a-definition-of-done-(dod)
+  - /blog/getting-started-definition-done-dod
+  - /getting-started-definition-done-dod
+  - /getting-started-with-a-definition-of-done-(dod)
+  - /blog/getting-started-with-a-definition-of-done-(dod)
 tags:
-- agile
-- definition-of-done
-- engineering-excellence
-- homepage
-- scrum
-- scrumble
+  - agile
+  - definition-of-done
+  - engineering-excellence
+  - homepage
+  - scrum
+  - scrumble
 categories:
-- agility
-- devops
+  - agility
+  - devops
 preview: naked-Agility-Scrum-Framework-Definition-of-Done-2-1.jpg
-
 ---
+
 In my last post about [Professional software teams creating working software](https://nkdagility.com/blog/professional-scrum-teams-build-software-works/) [David Corbin](https://www.scrum.org/david-corbin) made a good point. How do you determining what "Free from fault or defect" means? Since that is different for each Product and may change over time you need to focus on Quality and reflecting that quality in a Definition of Done (DoD).
 
 [Updated to reflect the 2020 Scrum Guide!](https://nkdagility.com/blog/update-scrum-guide-25th-anniversary-scrum-framework/)
diff --git a/site/content/resources/blog/2020/2020-12-17-backlog-not-refined-wrong/index.md b/site/content/resources/blog/2020/2020-12-17-backlog-not-refined-wrong/index.md
index 375eae0b73..8f6ca44543 100644
--- a/site/content/resources/blog/2020/2020-12-17-backlog-not-refined-wrong/index.md
+++ b/site/content/resources/blog/2020/2020-12-17-backlog-not-refined-wrong/index.md
@@ -2,27 +2,28 @@
 title: If your backlog is not refined then you are doing it wrong
 description: Ensure your Scrum team's success by refining your Product Backlog. Discover effective strategies to enhance clarity and quality in Sprint Planning.
 date: 2020-12-17
+AudioNative: true
 creator: Martin Hinshelwood
 id: "38243"
 layout: blog
 resourceTypes: blog
 slug: backlog-not-refined-wrong
 aliases:
-- /blog/backlog-not-refined-wrong
-- /backlog-not-refined-wrong
-- /if-your-backlog-is-not-refined-then-you-are-doing-it-wrong
-- /blog/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong
+  - /blog/backlog-not-refined-wrong
+  - /backlog-not-refined-wrong
+  - /if-your-backlog-is-not-refined-then-you-are-doing-it-wrong
+  - /blog/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong
 tags:
-- product-backlog
-- product-discovery
-- refinement
+  - product-backlog
+  - product-discovery
+  - refinement
 categories:
-- agility
-- discovery-ideation
-- people-and-process
+  - agility
+  - discovery-ideation
+  - people-and-process
 preview: naked-Agility-Scrum-Framework-Product-Backlog-2-1.jpg
-
 ---
+
 Most [Scrum Teams](/the-2020-scrum-guide/#scrum-team) that I encounter don’t do refinement of their [Product Backlog](/the-2020-scrum-guide/#product-backlog) and try to work on things that they don’t understand correctly. However, if you get to the Sprint Planning event and your backlog is not ready, then you are doing it wrong. If what you build is not of good quality then you should [read about Defenition of Done](/blog/getting-started-definition-done-dod/).
 
 [Updated to reflect the 2020 Scrum Guide!](https://nkdagility.com/the-2020-scrum-guide/)
diff --git a/site/content/resources/blog/2020/2020-12-21-product-goal-is-an-intermediate-strategic-goal/index.md b/site/content/resources/blog/2020/2020-12-21-product-goal-is-an-intermediate-strategic-goal/index.md
index ae95a184d1..9adbe18cad 100644
--- a/site/content/resources/blog/2020/2020-12-21-product-goal-is-an-intermediate-strategic-goal/index.md
+++ b/site/content/resources/blog/2020/2020-12-21-product-goal-is-an-intermediate-strategic-goal/index.md
@@ -2,27 +2,28 @@
 title: Product Goal is an Intermediate Strategic Goal
 description: Discover how to set effective product goals as intermediate strategic goals to enhance agility and drive successful outcomes in your organization.
 date: 2020-12-21
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45309"
 layout: blog
 resourceTypes: blog
 slug: product-goal-is-an-intermediate-strategic-goal
 aliases:
-- /blog/product-goal-is-an-intermediate-strategic-goal
-- /product-goal-is-an-intermediate-strategic-goal
+  - /blog/product-goal-is-an-intermediate-strategic-goal
+  - /product-goal-is-an-intermediate-strategic-goal
 tags:
-- ebm
-- evidence-based-management
-- intermediate-goal
-- intermediate-strategic-goal
-- product-discovery
-- product-goal
+  - ebm
+  - evidence-based-management
+  - intermediate-goal
+  - intermediate-strategic-goal
+  - product-discovery
+  - product-goal
 categories:
-- discovery-ideation
-- measure-and-learn
+  - discovery-ideation
+  - measure-and-learn
 preview: naked-agility-hypothesis-driven-1-1.jpg
-
 ---
+
 The [Evidence-Based Management Guide](https://nkdagility.com/the-evidence-based-management-guide-measuring-value-to-enable-improvement-and-agility/) describes not only a [Strategic Goal](https://nkdagility.com/blog/product-goal-is-an-intermediate-strategic-goal/) but also an [Intermediate Strategic Goal](https://nkdagility.com/blog/product-goal-is-an-intermediate-strategic-goal/) that is needed to evaluate and adapt your progress towards your intended visions of your product.
 
 <figure>
diff --git a/site/content/resources/blog/2020/2020-12-28-there-is-no-place-like-production/index.md b/site/content/resources/blog/2020/2020-12-28-there-is-no-place-like-production/index.md
index d6e45afc9b..57f983fbad 100644
--- a/site/content/resources/blog/2020/2020-12-28-there-is-no-place-like-production/index.md
+++ b/site/content/resources/blog/2020/2020-12-28-there-is-no-place-like-production/index.md
@@ -2,23 +2,24 @@
 title: There is no place like production
 description: Discover why real user feedback in production is essential for delivering value. Learn to validate assumptions and enhance product success effectively.
 date: 2020-12-28
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45324"
 layout: blog
 resourceTypes: blog
 slug: there-is-no-place-like-production
 aliases:
-- /blog/there-is-no-place-like-production
-- /there-is-no-place-like-production
+  - /blog/there-is-no-place-like-production
+  - /there-is-no-place-like-production
 tags:
-- hypothesis-driven-development
-- product-discovery
-- product-owner
+  - hypothesis-driven-development
+  - product-discovery
+  - product-owner
 categories:
-- discovery-ideation
+  - discovery-ideation
 preview: wizard-of-oz-ruby-slippers-2018-billboard-1548-2-2.jpg
-
 ---
+
 Value is such a subjective thing that we will often be wrong, and there is no way around that wrongness. In order to minimise the wrongness and maximise the amount of value that we deliver we need to have a clear understanding of what our users need, how they are using the product, and validate our new value as soon as we can. Without validation we only have assumptions and assumptions can be dangerous.
 
 As a start we can collect some qualitative data to validate some of our assumptions:
diff --git a/site/content/resources/blog/2020/2020-12-30-evidence-based-management-gathering-metrics/index.md b/site/content/resources/blog/2020/2020-12-30-evidence-based-management-gathering-metrics/index.md
index b556aadb0c..495039d801 100644
--- a/site/content/resources/blog/2020/2020-12-30-evidence-based-management-gathering-metrics/index.md
+++ b/site/content/resources/blog/2020/2020-12-30-evidence-based-management-gathering-metrics/index.md
@@ -1,30 +1,31 @@
 ---
-title: 'Evidence-based Management: Gathering the metrics'
+title: "Evidence-based Management: Gathering the metrics"
 description: Discover how to effectively gather metrics for Evidence-based Management in software organizations to enhance value delivery and drive agile success.
 date: 2020-12-30
+AudioNative: true
 creator: Martin Hinshelwood
 id: "10528"
 layout: blog
 resourceTypes: blog
 slug: evidence-based-management-gathering-metrics
 aliases:
-- /blog/evidence-based-management-gathering-metrics
-- /evidence-based-management-gathering-metrics
-- /evidence-based-management--gathering-the-metrics
-- /blog/evidence-based-management--gathering-the-metrics
+  - /blog/evidence-based-management-gathering-metrics
+  - /evidence-based-management-gathering-metrics
+  - /evidence-based-management--gathering-the-metrics
+  - /blog/evidence-based-management--gathering-the-metrics
 tags:
-- ebmgt
-- evidence
-- evidence-based-management
-- featured
-- leadership-track
-- merics
+  - ebmgt
+  - evidence
+  - evidence-based-management
+  - featured
+  - leadership-track
+  - merics
 categories:
-- measure-and-learn
-- people-and-process
+  - measure-and-learn
+  - people-and-process
 preview: naked-agility-evidence-based-management-1-1.jpg
-
 ---
+
 Gathering the metrics for Evidence-based Management in software organisations can be a strenuous task and I have a number of customers that are fretting on what to collect and from where. Here I try to create an understanding of the 'what' that we need to collect.
 
 [Updated to reflect the 2020 Scrum Guide!](https://nkdagility.com/the-2020-scrum-guide/)
diff --git a/site/content/resources/blog/2021/2021-01-04-story-points-velocity-are-a-sign-of-an-unsuccessful-team/index.md b/site/content/resources/blog/2021/2021-01-04-story-points-velocity-are-a-sign-of-an-unsuccessful-team/index.md
index fa69c890a6..433185635e 100644
--- a/site/content/resources/blog/2021/2021-01-04-story-points-velocity-are-a-sign-of-an-unsuccessful-team/index.md
+++ b/site/content/resources/blog/2021/2021-01-04-story-points-velocity-are-a-sign-of-an-unsuccessful-team/index.md
@@ -2,26 +2,27 @@
 title: Story Points & Velocity are a sign of an unsuccessful team
 description: Discover why relying on Story Points and Velocity may hinder your Scrum team's success. Learn to embrace true agility and enhance your team's adaptability.
 date: 2021-01-04
+AudioNative: true
 creator: Martin Hinshelwood
 id: "44532"
 layout: blog
 resourceTypes: blog
 slug: story-points-velocity-are-a-sign-of-an-unsuccessful-team
 aliases:
-- /blog/story-points-velocity-are-a-sign-of-an-unsuccessful-team
-- /story-points-velocity-are-a-sign-of-an-unsuccessful-team
-- /story-points-&-velocity-are-a-sign-of-an-unsuccessful-team
-- /blog/story-points-&-velocity-are-a-sign-of-an-unsuccessful-team
+  - /blog/story-points-velocity-are-a-sign-of-an-unsuccessful-team
+  - /story-points-velocity-are-a-sign-of-an-unsuccessful-team
+  - /story-points-&-velocity-are-a-sign-of-an-unsuccessful-team
+  - /blog/story-points-&-velocity-are-a-sign-of-an-unsuccessful-team
 tags:
-- daily-scrum
-- featured
-- leadership-track
+  - daily-scrum
+  - featured
+  - leadership-track
 categories:
-- agility
-- measure-and-learn
+  - agility
+  - measure-and-learn
 preview: image-9-14-14.png
-
 ---
+
 Story Points and velocity have been used for many years in the Scrum community and have been engrained so much in the way that things are done that most folks believe that they are part of Scrum. The accepted wisdom is that Scrum Teams are supposed to use User Stories, Story Points, and Velocity to measure their work.
 
 **Accepted wisdom is wrong!**
diff --git a/site/content/resources/blog/2021/2021-01-11-sprint-goal-is-an-immediate-tactical-goal/index.md b/site/content/resources/blog/2021/2021-01-11-sprint-goal-is-an-immediate-tactical-goal/index.md
index 23f76f3877..7ae0ad77bc 100644
--- a/site/content/resources/blog/2021/2021-01-11-sprint-goal-is-an-immediate-tactical-goal/index.md
+++ b/site/content/resources/blog/2021/2021-01-11-sprint-goal-is-an-immediate-tactical-goal/index.md
@@ -2,25 +2,26 @@
 title: Sprint Goal is an Immediate Tactical Goal
 description: Discover how to define effective Sprint Goals as tactical steps towards your Product Goal, enhancing value delivery and user engagement in Agile projects.
 date: 2021-01-11
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45310"
 layout: blog
 resourceTypes: blog
 slug: sprint-goal-is-an-immediate-tactical-goal
 aliases:
-- /blog/sprint-goal-is-an-immediate-tactical-goal
-- /sprint-goal-is-an-immediate-tactical-goal
+  - /blog/sprint-goal-is-an-immediate-tactical-goal
+  - /sprint-goal-is-an-immediate-tactical-goal
 tags:
-- intermediate-tactical-goal
-- leadership-track
-- product-owner
-- sprint-goal
+  - intermediate-tactical-goal
+  - leadership-track
+  - product-owner
+  - sprint-goal
 categories:
-- discovery-ideation
-- measure-and-learn
+  - discovery-ideation
+  - measure-and-learn
 preview: naked-agility-hypothesis-driven-2-2.jpg
-
 ---
+
 In the [The Evidence-Based Management Guide](https://nkdagility.com/the-evidence-based-management-guide-measuring-value-to-enable-improvement-and-agility/) we talk about the [Intermediate Strategic Goal](https://nkdagility.com/blog/product-goal-is-an-intermediate-strategic-goal/) and I likened that to the [Product Goal](https://nkdagility.com/the-2020-scrum-guide/#commitment-product-goal) in the [2020 Scrum Guide](https://nkdagility.com/the-2020-scrum-guide). If we also think of each Sprint as a tactical move towards fulfilling that [Product Goal](https://nkdagility.com/the-2020-scrum-guide/#commitment-product-goal) then the [Sprint Goal](https://nkdagility.com/the-2020-scrum-guide/#commitment-sprint-goal) becomes an Intermediate Tactical Goal that moves us towards our current Intermediate Strategic Goal.
 
 ## Sprint Goal is an Immediate Tactical Goal
diff --git a/site/content/resources/blog/2021/2021-01-18-what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/index.md b/site/content/resources/blog/2021/2021-01-18-what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/index.md
index 561d98945c..60eda4c589 100644
--- a/site/content/resources/blog/2021/2021-01-18-what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/index.md
+++ b/site/content/resources/blog/2021/2021-01-18-what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg/index.md
@@ -2,26 +2,27 @@
 title: What is Taylorism, and why Waterfall is just the tip of the iceberg!
 description: Explore the roots of Taylorism and its impact on modern project management. Discover why traditional methods may hinder innovation and employee engagement.
 date: 2021-01-18
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45392"
 layout: blog
 resourceTypes: blog
 slug: what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg
 aliases:
-- /blog/what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg
-- /what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg
-- /what-is-taylorism,-and-why-waterfall-is-just-the-tip-of-the-iceberg-
-- /blog/what-is-taylorism,-and-why-waterfall-is-just-the-tip-of-the-iceberg-
+  - /blog/what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg
+  - /what-is-taylorism-and-why-waterfall-is-just-the-tip-of-the-iceberg
+  - /what-is-taylorism,-and-why-waterfall-is-just-the-tip-of-the-iceberg-
+  - /blog/what-is-taylorism,-and-why-waterfall-is-just-the-tip-of-the-iceberg-
 tags:
-- featured
-- taylorism
-- traditional-project-management
-- waterfall
+  - featured
+  - taylorism
+  - traditional-project-management
+  - waterfall
 categories:
-- people-and-process
+  - people-and-process
 preview: naked-agility-with-martin-hinshelwood-iceberg-11-10.jpg
-
 ---
+
 For many people the traditional project management methodologies (see PMI / PRINCE2) are the root of the problems that birthed Waterfall. I assert that this is the tip of the iceberg. These methodologies are just a symptom of a greater problem that has its roots in the changes made during the industrial revolution. These changes, while they generated great amounts of wealth and many jobs around the world,  dehumanised work and destroyed the essence of value and discovery that brought humanity to where it is now. It created processes that turned people into little more than sophisticated robots and enshrined that thinking into the very core of how we do things.
 
 **These practices, which spread like cancer, have been seeded around the world by the Master of Business Administration (MBA). These practices have been calcified in the malignant bureaucracy that can be likened to an iceberg that may very well sink your company.**
diff --git a/site/content/resources/blog/2021/2021-01-19-professional-kanban-trainer-for-applying-professional-kanban/index.md b/site/content/resources/blog/2021/2021-01-19-professional-kanban-trainer-for-applying-professional-kanban/index.md
index 89ad8ebcee..d533311244 100644
--- a/site/content/resources/blog/2021/2021-01-19-professional-kanban-trainer-for-applying-professional-kanban/index.md
+++ b/site/content/resources/blog/2021/2021-01-19-professional-kanban-trainer-for-applying-professional-kanban/index.md
@@ -2,24 +2,25 @@
 title: Professional Kanban Trainer for Applying Professional Kanban
 description: Become a certified Professional Kanban Trainer with expert guidance from Martin Hinshelwood. Learn to optimize value flow and enhance your Scrum practices!
 date: 2021-01-19
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45694"
 layout: blog
 resourceTypes: blog
 slug: professional-kanban-trainer-for-applying-professional-kanban
 aliases:
-- /blog/professional-kanban-trainer-for-applying-professional-kanban
-- /professional-kanban-trainer-for-applying-professional-kanban
+  - /blog/professional-kanban-trainer-for-applying-professional-kanban
+  - /professional-kanban-trainer-for-applying-professional-kanban
 tags:
-- kanban
-- kanban-theory
-- professional-kanban
-- professional-scrum-with-kanban
+  - kanban
+  - kanban-theory
+  - professional-kanban
+  - professional-scrum-with-kanban
 categories:
-- news-and-reviews
+  - news-and-reviews
 preview: applying-professional-kanban-background-logo-2-2.jpg
-
 ---
+
 The [Scrum Guide](https://nkdagility.com/the-2020-scrum-guide/) only contains the minimum necessary to create an e**mpirical process control system for managing risk**. The new [Kanban Guide](https://nkdagility.com/the-kanban-guide/) reflects the minimum that you need to do to create a **strategy for optimizing the flow of value through a visual, pull-based system**.
 
 ![](images/applying-professional-kanban-background-logo-1280x611-1-1.jpg)
diff --git a/site/content/resources/blog/2021/2021-01-25-all-technical-debt-is-a-risk-to-the-product-and-to-your-business/index.md b/site/content/resources/blog/2021/2021-01-25-all-technical-debt-is-a-risk-to-the-product-and-to-your-business/index.md
index da212293a5..aedeef5ff2 100644
--- a/site/content/resources/blog/2021/2021-01-25-all-technical-debt-is-a-risk-to-the-product-and-to-your-business/index.md
+++ b/site/content/resources/blog/2021/2021-01-25-all-technical-debt-is-a-risk-to-the-product-and-to-your-business/index.md
@@ -2,27 +2,28 @@
 title: All technical debt is a risk to the product and to your business.
 description: Discover how technical debt poses risks to your product and business. Learn strategies to manage it effectively and ensure quality delivery. Read more!
 date: 2021-01-25
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45521"
 layout: blog
 resourceTypes: blog
 slug: all-technical-debt-is-a-risk-to-the-product-and-to-your-business
 aliases:
-- /blog/all-technical-debt-is-a-risk-to-the-product-and-to-your-business
-- /all-technical-debt-is-a-risk-to-the-product-and-to-your-business
-- /all-technical-debt-is-a-risk-to-the-product-and-to-your-business-
-- /blog/all-technical-debt-is-a-risk-to-the-product-and-to-your-business-
+  - /blog/all-technical-debt-is-a-risk-to-the-product-and-to-your-business
+  - /all-technical-debt-is-a-risk-to-the-product-and-to-your-business
+  - /all-technical-debt-is-a-risk-to-the-product-and-to-your-business-
+  - /blog/all-technical-debt-is-a-risk-to-the-product-and-to-your-business-
 tags:
-- continuous-quality
-- definition-of-done
-- featured
-- predictable-quality
+  - continuous-quality
+  - definition-of-done
+  - featured
+  - predictable-quality
 categories:
-- code-and-complexity
-- transparency-commitment
+  - code-and-complexity
+  - transparency-commitment
 preview: All-technical-debt-is-risk-to-the-product-and-to-your-business-2-2.jpg
-
 ---
+
 If you were buying a car, or a TV, you as the purchaser would do your best to understand the product that you are buying, the quality tradeoffs, and the capabilities.
 
 <figure>
diff --git a/site/content/resources/blog/2021/2021-02-04-become-the-leader-that-you-were-meant-to-to-be/index.md b/site/content/resources/blog/2021/2021-02-04-become-the-leader-that-you-were-meant-to-to-be/index.md
index bbfb0f70e6..8162c91d93 100644
--- a/site/content/resources/blog/2021/2021-02-04-become-the-leader-that-you-were-meant-to-to-be/index.md
+++ b/site/content/resources/blog/2021/2021-02-04-become-the-leader-that-you-were-meant-to-to-be/index.md
@@ -2,22 +2,23 @@
 title: Become the leader that you were meant to to be
 description: Unlock your leadership potential! Discover how to inspire and lead effectively in modern organizations. Become the leader you were meant to be!
 date: 2021-02-04
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45806"
 layout: blog
 resourceTypes: blog
 slug: become-the-leader-that-you-were-meant-to-to-be
 aliases:
-- /blog/become-the-leader-that-you-were-meant-to-to-be
-- /become-the-leader-that-you-were-meant-to-to-be
+  - /blog/become-the-leader-that-you-were-meant-to-to-be
+  - /become-the-leader-that-you-were-meant-to-to-be
 tags:
-- featured
-- leadership-track
+  - featured
+  - leadership-track
 categories:
-- news-and-reviews
+  - news-and-reviews
 preview: image-2-2.png
-
 ---
+
 Leadership is not about control, but about inspiring those around you.
 
 ## Managers transition to Leaders
diff --git a/site/content/resources/blog/2021/2021-03-01-scrum-is-made-up-of-influencers-entrepreneurs-and-makers/index.md b/site/content/resources/blog/2021/2021-03-01-scrum-is-made-up-of-influencers-entrepreneurs-and-makers/index.md
index b3ffefcf7b..f880827f0e 100644
--- a/site/content/resources/blog/2021/2021-03-01-scrum-is-made-up-of-influencers-entrepreneurs-and-makers/index.md
+++ b/site/content/resources/blog/2021/2021-03-01-scrum-is-made-up-of-influencers-entrepreneurs-and-makers/index.md
@@ -2,27 +2,28 @@
 title: Scrum is made up of Influencers, Entrepreneurs, and Makers
 description: Explore how Scrum thrives on the synergy of Influencers, Entrepreneurs, and Makers. Discover key roles and training for maximizing product value!
 date: 2021-03-01
+AudioNative: true
 creator: Martin Hinshelwood
 id: "45946"
 layout: blog
 resourceTypes: blog
 slug: scrum-is-made-up-of-influencers-entrepreneurs-and-makers
 aliases:
-- /blog/scrum-is-made-up-of-influencers-entrepreneurs-and-makers
-- /scrum-is-made-up-of-influencers-entrepreneurs-and-makers
-- /scrum-is-made-up-of-influencers,-entrepreneurs,-and-makers
-- /blog/scrum-is-made-up-of-influencers,-entrepreneurs,-and-makers
+  - /blog/scrum-is-made-up-of-influencers-entrepreneurs-and-makers
+  - /scrum-is-made-up-of-influencers-entrepreneurs-and-makers
+  - /scrum-is-made-up-of-influencers,-entrepreneurs,-and-makers
+  - /blog/scrum-is-made-up-of-influencers,-entrepreneurs,-and-makers
 tags:
-- entrepreneurs
-- leadership
-- leadership-track
-- technical-track
-- value-track
+  - entrepreneurs
+  - leadership
+  - leadership-track
+  - technical-track
+  - value-track
 categories:
-- news-and-reviews
+  - news-and-reviews
 preview: image-4-5-5.png
-
 ---
+
 In the empirical world, we have 3 key skill areas of accountability that are needed to effectively deliver products of the highest possible value! We need Influencers that can provide leadership and create environments within which groups of people can organise the work. I consider this the Leadership Track where you have Scrum Masters, Coaches, and CEO. We need Entrepreneurs who can have a vision and project knowledge and understanding of that vision to the people that need to make that vision happen. This is the Value Track and may be made up of Product Owners, Analysts, and Subject Matter Experts. Last we have the Makers who are the ones who do the work that brings the product to life. They are on the Technical Track and focus on turning the vision into a reality. They have many skills and may have coders, testers, and other experts...
 
 ![](images/image-4-1280x720-4-4.png)
diff --git a/site/content/resources/blog/2021/2021-04-19-stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/index.md b/site/content/resources/blog/2021/2021-04-19-stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/index.md
index 52cad0f03d..c661833218 100644
--- a/site/content/resources/blog/2021/2021-04-19-stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/index.md
+++ b/site/content/resources/blog/2021/2021-04-19-stop-normalizing-unprofessional-behaviour-in-the-name-of-agility/index.md
@@ -2,23 +2,24 @@
 title: Stop normalizing unprofessional behaviour in the name of agility
 description: Discover why unprofessional behavior undermines agility in Scrum. Learn to uphold professionalism for true agile success and better team dynamics.
 date: 2021-04-19
+AudioNative: true
 creator: Martin Hinshelwood
 id: "46108"
 layout: blog
 resourceTypes: blog
 slug: stop-normalizing-unprofessional-behaviour-in-the-name-of-agility
 aliases:
-- /blog/stop-normalizing-unprofessional-behaviour-in-the-name-of-agility
-- /stop-normalizing-unprofessional-behaviour-in-the-name-of-agility
+  - /blog/stop-normalizing-unprofessional-behaviour-in-the-name-of-agility
+  - /stop-normalizing-unprofessional-behaviour-in-the-name-of-agility
 tags:
-- professional-scrum
-- professionalism
+  - professional-scrum
+  - professionalism
 categories:
-- people-and-process
-- transparency-commitment
+  - people-and-process
+  - transparency-commitment
 preview: naked-agility-technically-agile-1280×720-19-1-1.jpg
-
 ---
+
 In Scrum Events across the world, I hear repeated the phrase "that's how agile works" when describing behaviours that are both unprofessional and the very opposite of an agile mindset. These behaviours will inhibit agility and are a result of a lack of understanding of the underlying principles.
 
 We need to stop normalising unprofessional behaviour and call it out whenever we hear it.
diff --git a/site/content/resources/blog/2021/2021-05-17-hiring-a-professional-product-owner/index.md b/site/content/resources/blog/2021/2021-05-17-hiring-a-professional-product-owner/index.md
index 11d3b4cea6..223e8b62e0 100644
--- a/site/content/resources/blog/2021/2021-05-17-hiring-a-professional-product-owner/index.md
+++ b/site/content/resources/blog/2021/2021-05-17-hiring-a-professional-product-owner/index.md
@@ -2,40 +2,41 @@
 title: Hiring a Professional Product Owner
 description: Discover the essential qualities of a Professional Product Owner. Learn how to maximize product value and enhance team collaboration for success.
 date: 2021-05-17
+AudioNative: true
 creator: Martin Hinshelwood
 contributors:
-- name: Fredrik Wendt
-  external: https://www.scrum.org/fredrik-wendt
-- name: Ralph Jocham
-  external: https://www.scrum.org/ralph-jocham
-- name: Andy Hiles
-  external: https://www.scrum.org/andy-hiles
-- name: Maarten Dalmijn
-  external: https://www.linkedin.com/in/maarten-dalmijn/
-- name: Jim Sammons
-  external: https://www.scrum.org/jim-sammons
-- name: Victoria Pent
-  external: https://www.linkedin.com/in/victoria-pent-627a6b61/
-- name: James Powis
-  external: https://www.linkedin.com/in/james-powis-agile-product-owner/
+  - name: Fredrik Wendt
+    external: https://www.scrum.org/fredrik-wendt
+  - name: Ralph Jocham
+    external: https://www.scrum.org/ralph-jocham
+  - name: Andy Hiles
+    external: https://www.scrum.org/andy-hiles
+  - name: Maarten Dalmijn
+    external: https://www.linkedin.com/in/maarten-dalmijn/
+  - name: Jim Sammons
+    external: https://www.scrum.org/jim-sammons
+  - name: Victoria Pent
+    external: https://www.linkedin.com/in/victoria-pent-627a6b61/
+  - name: James Powis
+    external: https://www.linkedin.com/in/james-powis-agile-product-owner/
 id: "46138"
 layout: blog
 resourceTypes: blog
 slug: hiring-a-professional-product-owner
 aliases:
-- /blog/hiring-a-professional-product-owner
-- /hiring-a-professional-product-owner
+  - /blog/hiring-a-professional-product-owner
+  - /hiring-a-professional-product-owner
 tags:
-- featured
-- product-discovery
-- product-owner
+  - featured
+  - product-discovery
+  - product-owner
 categories:
-- discovery-ideation
-- news-and-reviews
-- people-and-process
+  - discovery-ideation
+  - news-and-reviews
+  - people-and-process
 preview: image-3-3.png
-
 ---
+
 One of my customers is asking me about the accountabilities of a Product Owner and how they break down. While I had seen many things around the Scrum Master for my post on [Hiring a Professional Scrum Master](https://nkdagility.com/blog/hiring-a-professional-scrum-master/), this was a little bit more of a discovery session, which is why I asked some of my trusted colleagues at Scrum.org to help out.
 
 This represents my best efforts to pull together a specification of the Product Owner accountability from the Scrum Guide, agile practitioners, and a little bit of experience.
diff --git a/site/content/resources/blog/2023/2023-06-21-embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/index.md b/site/content/resources/blog/2023/2023-06-21-embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/index.md
index 813844daec..b0e3a6213e 100644
--- a/site/content/resources/blog/2023/2023-06-21-embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/index.md
+++ b/site/content/resources/blog/2023/2023-06-21-embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success/index.md
@@ -1,25 +1,26 @@
 ---
-title: 'Embrace Uniqueness: Why Creating Your Own Scaling Practices Leads to Business Success'
+title: "Embrace Uniqueness: Why Creating Your Own Scaling Practices Leads to Business Success"
 description: Discover how creating unique scaling practices can drive your business success. Embrace your distinctiveness and foster agility for sustainable growth.
 date: 2023-06-21
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49480"
 layout: blog
 resourceTypes: blog
 slug: embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success
 aliases:
-- /blog/embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success
-- /embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success
-- /embrace-uniqueness--why-creating-your-own-scaling-practices-leads-to-business-success
-- /blog/embrace-uniqueness--why-creating-your-own-scaling-practices-leads-to-business-success
+  - /blog/embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success
+  - /embrace-uniqueness-why-creating-your-own-scaling-practices-leads-to-business-success
+  - /embrace-uniqueness--why-creating-your-own-scaling-practices-leads-to-business-success
+  - /blog/embrace-uniqueness--why-creating-your-own-scaling-practices-leads-to-business-success
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- agility
+  - agility
 preview: naked-agility-technically-agile-Blog-EmbraceUniqueness-1-1-1.jpg
-
 ---
+
 Business Leaders face a key challenge when scaling their organisations effectively while maintaining the distinctiveness that made us successful in the first place. Many frameworks and methodologies, such as Scaled Agile Framework (SAFe) or the Spotify Model, promise a structured approach to scaling, but do they genuinely fit our unique needs? In this post, I aim to highlight the importance of creating our own scaling practices, highlighting that successful commercial software organizations have thrived by embracing their distinctiveness rather than adopting standardized approaches.
 
 Unique DNA of Success: Every successful organisation has its DNA, a unique combination of values, culture, and practices contributing to its achievements. These characteristics differentiate us from our competitors and have played a significant role in our success thus far. Implementing someone else's scaling practices, like SAFe or the Spotify Model, may seem tempting, but it risks diluting our distinctive DNA and eroding the competitive edge we've worked so hard to build.
diff --git a/site/content/resources/blog/2023/2023-06-29-alpha-to-beta-the-urgent-call-for-agile-organisational-transformation/index.md b/site/content/resources/blog/2023/2023-06-29-alpha-to-beta-the-urgent-call-for-agile-organisational-transformation/index.md
index 04805f4ef7..18567333df 100644
--- a/site/content/resources/blog/2023/2023-06-29-alpha-to-beta-the-urgent-call-for-agile-organisational-transformation/index.md
+++ b/site/content/resources/blog/2023/2023-06-29-alpha-to-beta-the-urgent-call-for-agile-organisational-transformation/index.md
@@ -2,24 +2,25 @@
 title: The Urgent Call for Agile Organisational Transformation
 description: Explore the urgent need for agile transformation in organizations. Discover how to break free from outdated hierarchies and thrive in dynamic markets.
 date: 2023-06-29
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49485"
 layout: blog
 resourceTypes: blog
 slug: alpha-to-beta-the-urgent-call-for-agile-organisational-transformation
 aliases:
-- /blog/alpha-to-beta-the-urgent-call-for-agile-organisational-transformation
-- /alpha-to-beta-the-urgent-call-for-agile-organisational-transformation
-- /the-urgent-call-for-agile-organisational-transformation
-- /blog/the-urgent-call-for-agile-organisational-transformation
+  - /blog/alpha-to-beta-the-urgent-call-for-agile-organisational-transformation
+  - /alpha-to-beta-the-urgent-call-for-agile-organisational-transformation
+  - /the-urgent-call-for-agile-organisational-transformation
+  - /blog/the-urgent-call-for-agile-organisational-transformation
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- organisational-change
+  - organisational-change
 preview: 1686217267121-1-1-1.jpg
-
 ---
+
 As we progress deeper into the dynamic landscape of the 21st century, our long-established organisations, born of the Industrial Age and infused with a DNA of strict command and control, stand on shaky ground. These organisations strut with command-and-control bravado, erecting clear hierarchies in their stable inert markets where bureaucracy reigns supreme. However, they are feeling the tremors of a rapidly evolving, technologically charged dynamic markets and are plagued by sluggish responses and missed opportunities, which are their Achilles heel in these new fast-paced markets. Not since the 1970s has the classic hierarchical model, rooted in the stagnant waters of stable markets, been a viable proposition for companies seeking to thrive in an era of unprecedented change and unpredictability. Clearly, we cannot continue to coat deep-seated hierarchical practices with a thin veneer of modern innovation and expect sustainable transformation.
 
 I see countless individuals trapped in the bureaucratic maze of classic hierarchical organisational structures, their creative potential stifled, their drive for innovation subdued. The belief is that switching to a more modern network model could liberate them from this stifling environment, fuelling both individual and organisational growth.
diff --git a/site/content/resources/blog/2023/2023-07-06-a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets/index.md b/site/content/resources/blog/2023/2023-07-06-a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets/index.md
index bde7d37c14..1ae374e4bb 100644
--- a/site/content/resources/blog/2023/2023-07-06-a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets/index.md
+++ b/site/content/resources/blog/2023/2023-07-06-a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets/index.md
@@ -2,24 +2,25 @@
 title: "A Titanic Misfit: The Alpha Organization's Wasteful Endeavor in Red Markets"
 description: Explore how Alpha organizations waste resources in fast-paced red markets and discover the agile Beta model as the key to thriving in today's economy.
 date: 2023-07-06
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49490"
 layout: blog
 resourceTypes: blog
 slug: a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets
 aliases:
-- /blog/a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets
-- /a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets
-- /a-titanic-misfit--the-alpha-organization's-wasteful-endeavor-in-red-markets
-- /blog/a-titanic-misfit--the-alpha-organization's-wasteful-endeavor-in-red-markets
+  - /blog/a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets
+  - /a-titanic-misfit-the-alpha-organizations-wasteful-endeavor-in-red-markets
+  - /a-titanic-misfit--the-alpha-organization's-wasteful-endeavor-in-red-markets
+  - /blog/a-titanic-misfit--the-alpha-organization's-wasteful-endeavor-in-red-markets
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- organisational-change
+  - organisational-change
 preview: image-1.jpg
-
 ---
+
 Under the ruthless canopy of the red market, I find myself staring at the bloated behemoth of an Alpha organisation, huffing and puffing in a vain attempt to keep up with the frenzied pace of the modern world. The Alpha model, once a paragon of order and efficiency in the leisurely blue market era, has now morphed into a lumbering dinosaur, with its hierarchical structures and rigid command and control systems looking out of place in the high-speed, unpredictable red markets.
 
 > Alpha Organizations: Born in the Industrial Age, they are hierarchical and less adaptable.
diff --git a/site/content/resources/blog/2023/2023-07-13-risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/index.md b/site/content/resources/blog/2023/2023-07-13-risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/index.md
index 4db8e1bd4a..20d3d11dfa 100644
--- a/site/content/resources/blog/2023/2023-07-13-risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/index.md
+++ b/site/content/resources/blog/2023/2023-07-13-risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/index.md
@@ -1,26 +1,27 @@
 ---
-title: 'Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management'
+title: "Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management"
 description: Explore how Agile's focus on usable products enhances risk mitigation compared to traditional documentation methods in project management. Adapt and thrive!
 date: 2023-07-13
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49495"
 layout: blog
 resourceTypes: blog
 slug: risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management
 aliases:
-- /blog/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management
-- /risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management
-- /risk-mitigation--agile-usable-products-vs-documentation-in-traditional-project-management
-- /blog/risk-mitigation--agile-usable-products-vs-documentation-in-traditional-project-management
+  - /blog/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management
+  - /risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management
+  - /risk-mitigation--agile-usable-products-vs-documentation-in-traditional-project-management
+  - /blog/risk-mitigation--agile-usable-products-vs-documentation-in-traditional-project-management
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- discovery-ideation
-- transparency-commitment
+  - discovery-ideation
+  - transparency-commitment
 preview: image-1.jpg
-
 ---
+
 As the software development landscape evolves, evaluating the time-tested traditional project management strategies alongside the burgeoning agile methodologies is essential. The central tenet I would like to explore today is comparing using usable working products as a risk mitigation strategy in Agile with the elaborate documentation characteristic of traditional project management.
 
 ### TL;DR:
diff --git a/site/content/resources/blog/2023/2023-07-20-how-usable-working-products-are-your-ultimate-weapon-against-risks/index.md b/site/content/resources/blog/2023/2023-07-20-how-usable-working-products-are-your-ultimate-weapon-against-risks/index.md
index 8e37bd9687..72fb21bd58 100644
--- a/site/content/resources/blog/2023/2023-07-20-how-usable-working-products-are-your-ultimate-weapon-against-risks/index.md
+++ b/site/content/resources/blog/2023/2023-07-20-how-usable-working-products-are-your-ultimate-weapon-against-risks/index.md
@@ -2,23 +2,24 @@
 title: How Usable Working Products Are Your Ultimate Weapon Against Risks
 description: Discover how delivering usable working products can mitigate risks in Agile practices. Embrace feedback loops and automation for true agility!
 date: 2023-07-20
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49501"
 layout: blog
 resourceTypes: blog
 slug: how-usable-working-products-are-your-ultimate-weapon-against-risks
 aliases:
-- /blog/how-usable-working-products-are-your-ultimate-weapon-against-risks
-- /how-usable-working-products-are-your-ultimate-weapon-against-risks
+  - /blog/how-usable-working-products-are-your-ultimate-weapon-against-risks
+  - /how-usable-working-products-are-your-ultimate-weapon-against-risks
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- measure-and-learn
-- transparency-commitment
+  - measure-and-learn
+  - transparency-commitment
 preview: image-1.jpg
-
 ---
+
 It baffles me how some agile teams, who claim to be the pioneers of modernity, are living in archaic times where usable working products are as rare as unicorns! Just a heads-up, my dear agile practitioners: the linchpin of Agile is a Usable Working Product. Yes, you read it right!
 
 **TL;DR;**
diff --git a/site/content/resources/blog/2023/2023-07-27-storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/index.md b/site/content/resources/blog/2023/2023-07-27-storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/index.md
index 4c46a23dd6..e1f7e99009 100644
--- a/site/content/resources/blog/2023/2023-07-27-storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/index.md
+++ b/site/content/resources/blog/2023/2023-07-27-storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/index.md
@@ -2,23 +2,24 @@
 title: Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations
 description: Explore the critical consequences of neglecting usable products in Agile iterations. Learn how to maintain trust, adaptability, and team morale for success.
 date: 2023-07-27
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49502"
 layout: blog
 resourceTypes: blog
 slug: storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations
 aliases:
-- /blog/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations
-- /storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations
+  - /blog/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations
+  - /storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- discovery-ideation
-- transparency-commitment
+  - discovery-ideation
+  - transparency-commitment
 preview: image-1.jpg
-
 ---
+
 In light of the importance professional teams place on delivering usable, working products, I find myself compelled to address the woes that befall teams that need to adhere to this crucial tenet. We understand the need for working products; now, let us dissect the perils of straying from this righteous path.
 
 ### TL;DR;
diff --git a/site/content/resources/blog/2023/2023-08-03-from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/index.md b/site/content/resources/blog/2023/2023-08-03-from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/index.md
index 50d63ec36d..9d44835a71 100644
--- a/site/content/resources/blog/2023/2023-08-03-from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/index.md
+++ b/site/content/resources/blog/2023/2023-08-03-from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments/index.md
@@ -2,26 +2,27 @@
 title: From Unused Gym Memberships to Agile Implementation The Parallels of Misapplied Investments
 description: Explore the parallels between unused gym memberships and agile implementation. Discover how commitment and consistent effort drive true transformation in both realms.
 date: 2023-08-03
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49507"
 layout: blog
 resourceTypes: blog
 slug: from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments
 aliases:
-- /blog/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments
-- /from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments
+  - /blog/from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments
+  - /from-unused-gym-memberships-to-agile-implementation-the-parallels-of-misapplied-investments
 tags:
-- agile
-- agile-transformation
-- continuous-improvement
-- featured
-- homepage
+  - agile
+  - agile-transformation
+  - continuous-improvement
+  - featured
+  - homepage
 categories:
-- people-and-process
-- transparency-commitment
+  - people-and-process
+  - transparency-commitment
 preview: naked-agility-technically-agile-gym-membership-Agile-1-1.jpg
-
 ---
+
 In software development, an increasingly prevalent phenomenon is the adoption of agile methodologies, akin to individuals embarking on fitness journeys through gym memberships. However, a striking parallel between the two realms can be drawn – the misuse and under-utilization of the tools at disposal. The essence of this analogy reflects a more fundamental notion: the gap between intention and implementation.
 
 Buying a gym membership is often the first step in the fitness world. It symbolises the recognition of the necessity to adopt a healthier lifestyle. However, obtaining a membership doesn’t miraculously bestow the benefits of a toned physique or improved cardiovascular health. The gym membership must be coupled with consistent visits, well-planned workout regimes, and monitored nutrition. This membership often lies dormant, with the individual not reaping any potential benefits.
diff --git a/site/content/resources/blog/2023/2023-08-10-navigating-the-future-with-a-fine-tuned-product-backlog/index.md b/site/content/resources/blog/2023/2023-08-10-navigating-the-future-with-a-fine-tuned-product-backlog/index.md
index b2e58eedc1..9be66907a3 100644
--- a/site/content/resources/blog/2023/2023-08-10-navigating-the-future-with-a-fine-tuned-product-backlog/index.md
+++ b/site/content/resources/blog/2023/2023-08-10-navigating-the-future-with-a-fine-tuned-product-backlog/index.md
@@ -2,23 +2,24 @@
 title: Navigating the Future with a Fine-Tuned Product Backlog
 description: Discover how a well-ordered Product Backlog can guide your Agile projects to success. Learn essential strategies for effective backlog management today!
 date: 2023-08-10
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49510"
 layout: blog
 resourceTypes: blog
 slug: navigating-the-future-with-a-fine-tuned-product-backlog
 aliases:
-- /blog/navigating-the-future-with-a-fine-tuned-product-backlog
-- /navigating-the-future-with-a-fine-tuned-product-backlog
+  - /blog/navigating-the-future-with-a-fine-tuned-product-backlog
+  - /navigating-the-future-with-a-fine-tuned-product-backlog
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- measure-and-learn
-- people-and-process
+  - measure-and-learn
+  - people-and-process
 preview: naked-agility-technically-NavigatingtheFuturewithaFine-TunedProductBacklog-1-1.jpg
-
 ---
+
 As a seasoned Agile consultant, I find myself amidst conversations about the mechanics of a successful Agile project. Today, I focus on an essential yet often underappreciated aspect - the Product Backlog. A well-ordered Product Backlog that is comprehensible to all stakeholders is a critical beacon that illuminates the path to a transparent future.
 
 At the foundational level, the Product Backlog is simply a list of items required for a product, encompassing features, enhancements, and fixes. These items, sometimes called ‘User Stories’, are critical to understanding what needs to be built. The Product Backlog must be seen as a living document, which evolves as the market conditions, customer needs, and product goals change.
diff --git a/site/content/resources/blog/2023/2023-08-17-rethinking-product-backlog-navigating-through-the-weeds-of-complexity/index.md b/site/content/resources/blog/2023/2023-08-17-rethinking-product-backlog-navigating-through-the-weeds-of-complexity/index.md
index cbe63d6ae1..b0ec11ceb6 100644
--- a/site/content/resources/blog/2023/2023-08-17-rethinking-product-backlog-navigating-through-the-weeds-of-complexity/index.md
+++ b/site/content/resources/blog/2023/2023-08-17-rethinking-product-backlog-navigating-through-the-weeds-of-complexity/index.md
@@ -1,25 +1,26 @@
 ---
-title: 'Rethinking Product Backlog: Navigating Through the Weeds of Complexity'
+title: "Rethinking Product Backlog: Navigating Through the Weeds of Complexity"
 description: Explore innovative strategies for managing your Product Backlog in complex environments. Discover how to enhance agility and foster team autonomy today!
 date: 2023-08-17
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49515"
 layout: blog
 resourceTypes: blog
 slug: rethinking-product-backlog-navigating-through-the-weeds-of-complexity
 aliases:
-- /blog/rethinking-product-backlog-navigating-through-the-weeds-of-complexity
-- /rethinking-product-backlog-navigating-through-the-weeds-of-complexity
-- /rethinking-product-backlog--navigating-through-the-weeds-of-complexity
-- /blog/rethinking-product-backlog--navigating-through-the-weeds-of-complexity
+  - /blog/rethinking-product-backlog-navigating-through-the-weeds-of-complexity
+  - /rethinking-product-backlog-navigating-through-the-weeds-of-complexity
+  - /rethinking-product-backlog--navigating-through-the-weeds-of-complexity
+  - /blog/rethinking-product-backlog--navigating-through-the-weeds-of-complexity
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- measure-and-learn
+  - measure-and-learn
 preview: image-1.jpg
-
 ---
+
 The Product Backlog is a critical asset in Agile product development; it represents a dynamic lean inventory of everything the product needs. For those of us navigating the multifaceted landscape of product development, there is often an impulse to seek an ideal structure for the Product Backlog. The familiar hierarchy of Initiative->Epic->Feature->User Story->Task/Bug is a common schema. However, before embracing this structure as a silver bullet, it’s imperative to critically evaluate the implications of imposing a hierarchy on the Product Backlog and to recognize the nuanced dynamics of working in complex environments. In this article, I will examine the delicate interplay between Product Backlog management and the intrinsic nature of complex systems.
 
 ### TLDR;
diff --git a/site/content/resources/blog/2023/2023-08-31-rethinking-user-stories-a-call-for-clarity-in-product-backlog-management/index.md b/site/content/resources/blog/2023/2023-08-31-rethinking-user-stories-a-call-for-clarity-in-product-backlog-management/index.md
index 82e8bd305f..4b35ac39e8 100644
--- a/site/content/resources/blog/2023/2023-08-31-rethinking-user-stories-a-call-for-clarity-in-product-backlog-management/index.md
+++ b/site/content/resources/blog/2023/2023-08-31-rethinking-user-stories-a-call-for-clarity-in-product-backlog-management/index.md
@@ -2,28 +2,29 @@
 title: "Rethinking 'User Stories': A Call for Clarity in Product Backlog Management"
 description: Discover why 'User Stories' may hinder product development and learn to embrace 'Product Backlog Items' for clearer, more effective communication.
 date: 2023-08-31
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49726"
 layout: blog
 resourceTypes: blog
 slug: rethinking-user-stories-a-call-for-clarity-in-product-backlog-management
 aliases:
-- /blog/rethinking-user-stories-a-call-for-clarity-in-product-backlog-management
-- /rethinking-user-stories-a-call-for-clarity-in-product-backlog-management
-- /rethinking-'user-stories'--a-call-for-clarity-in-product-backlog-management
-- /blog/rethinking-'user-stories'--a-call-for-clarity-in-product-backlog-management
+  - /blog/rethinking-user-stories-a-call-for-clarity-in-product-backlog-management
+  - /rethinking-user-stories-a-call-for-clarity-in-product-backlog-management
+  - /rethinking-'user-stories'--a-call-for-clarity-in-product-backlog-management
+  - /blog/rethinking-'user-stories'--a-call-for-clarity-in-product-backlog-management
 tags:
-- featured
-- homepage
-- product-backlog-item
-- product-backlog-management
-- user-stories
+  - featured
+  - homepage
+  - product-backlog-item
+  - product-backlog-management
+  - user-stories
 categories:
-- agility
-- discovery-ideation
+  - agility
+  - discovery-ideation
 preview: naked-agility-technically-rethinkinguserstories-1-1-1.jpg
-
 ---
+
 As someone who has spent a fair amount of time in the trenches of product development, I've realised that the language we use to describe our work can profoundly shape our approach to it. One term that I believe has been misused and misunderstood to the point of causing more harm than good is "User Stories".
 
 ### TLDR;
diff --git a/site/content/resources/blog/2023/2023-09-07-the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/index.md b/site/content/resources/blog/2023/2023-09-07-the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/index.md
index 1e3bf6d69f..867d9f98c4 100644
--- a/site/content/resources/blog/2023/2023-09-07-the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/index.md
+++ b/site/content/resources/blog/2023/2023-09-07-the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility/index.md
@@ -1,28 +1,29 @@
 ---
-title: 'The Race for Market Responsiveness: A Fresh Perspective on Organisational Agility'
+title: "The Race for Market Responsiveness: A Fresh Perspective on Organisational Agility"
 description: Discover how to enhance your organization's agility and market responsiveness. Learn to pivot swiftly and seize opportunities faster than competitors.
 date: 2023-09-07
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49732"
 layout: blog
 resourceTypes: blog
 slug: the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility
 aliases:
-- /blog/the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility
-- /the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility
-- /the-race-for-market-responsiveness--a-fresh-perspective-on-organisational-agility
-- /blog/the-race-for-market-responsiveness--a-fresh-perspective-on-organisational-agility
+  - /blog/the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility
+  - /the-race-for-market-responsiveness-a-fresh-perspective-on-organisational-agility
+  - /the-race-for-market-responsiveness--a-fresh-perspective-on-organisational-agility
+  - /blog/the-race-for-market-responsiveness--a-fresh-perspective-on-organisational-agility
 tags:
-- betacodex
-- featured
-- homepage
-- organisational-physics
-- organisational-transformational-mastery
+  - betacodex
+  - featured
+  - homepage
+  - organisational-physics
+  - organisational-transformational-mastery
 categories:
-- agility
+  - agility
 preview: naked-agility-technically-survivalisoptional-1-1.jpg
-
 ---
+
 As I sit here, sipping my morning cup of tea, I ponder the current state of organisational agility. I've been in this game long enough to have seen the rise and fall of various methodologies, each promising to be the silver bullet that will solve all of an organisation's woes. I was initially an ALM consultant, then DevOps. But, as I've often found, the reality is far from the promise.
 
 ### TLDR;
diff --git a/site/content/resources/blog/2023/2023-09-14-decoding-scrum-team-work-balancing-sprint-and-refinement-work/index.md b/site/content/resources/blog/2023/2023-09-14-decoding-scrum-team-work-balancing-sprint-and-refinement-work/index.md
index de3e73b9d7..e3d12a74b7 100644
--- a/site/content/resources/blog/2023/2023-09-14-decoding-scrum-team-work-balancing-sprint-and-refinement-work/index.md
+++ b/site/content/resources/blog/2023/2023-09-14-decoding-scrum-team-work-balancing-sprint-and-refinement-work/index.md
@@ -1,25 +1,26 @@
 ---
-title: 'Decoding Scrum Team Work: Balancing Sprint and Refinement Work'
+title: "Decoding Scrum Team Work: Balancing Sprint and Refinement Work"
 description: Master the balance between Sprint and Refinement work in Scrum. Discover strategies to enhance team efficiency and achieve your product goals effectively.
 date: 2023-09-14
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49783"
 layout: blog
 resourceTypes: blog
 slug: decoding-scrum-team-work-balancing-sprint-and-refinement-work
 aliases:
-- /blog/decoding-scrum-team-work-balancing-sprint-and-refinement-work
-- /decoding-scrum-team-work-balancing-sprint-and-refinement-work
-- /decoding-scrum-team-work--balancing-sprint-and-refinement-work
-- /blog/decoding-scrum-team-work--balancing-sprint-and-refinement-work
+  - /blog/decoding-scrum-team-work-balancing-sprint-and-refinement-work
+  - /decoding-scrum-team-work-balancing-sprint-and-refinement-work
+  - /decoding-scrum-team-work--balancing-sprint-and-refinement-work
+  - /blog/decoding-scrum-team-work--balancing-sprint-and-refinement-work
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-SprintRefignementBallance-6-6.jpg
-
 ---
+
 **Software Development** is not just a systematic process but a dynamic interplay of critical work that shapes the progress of your product. A **Scrum** team's work can be classified into **Sprint** work and **Refinement**. To steer your **Scrum Team** towards success, it's essential to understand, manage, and balance these two types of work. This article dives deep into the heart of Scrum team operations, offering clear-cut strategies and innovative visualisation techniques to help you understand and manage your Sprint work and Refinement processes effectively. Decode the intricacies of Scrum teamwork and unlock the path to achieving your product goals with increased efficiency.
 
 ## TLDR;
diff --git a/site/content/resources/blog/2023/2023-09-21-deciphering-the-enigma-of-story-points-across-teams/index.md b/site/content/resources/blog/2023/2023-09-21-deciphering-the-enigma-of-story-points-across-teams/index.md
index 38b0307433..4597553eae 100644
--- a/site/content/resources/blog/2023/2023-09-21-deciphering-the-enigma-of-story-points-across-teams/index.md
+++ b/site/content/resources/blog/2023/2023-09-21-deciphering-the-enigma-of-story-points-across-teams/index.md
@@ -2,22 +2,23 @@
 title: Deciphering the Enigma of Story Points Across Teams
 description: Explore how to effectively use Story Points in agile teams. Discover better metrics for performance and value delivery to enhance your team's success.
 date: 2023-09-21
+AudioNative: true
 creator: Martin Hinshelwood
 id: "49888"
 layout: blog
 resourceTypes: blog
 slug: deciphering-the-enigma-of-story-points-across-teams
 aliases:
-- /blog/deciphering-the-enigma-of-story-points-across-teams
-- /deciphering-the-enigma-of-story-points-across-teams
+  - /blog/deciphering-the-enigma-of-story-points-across-teams
+  - /deciphering-the-enigma-of-story-points-across-teams
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- agility
+  - agility
 preview: naked-agility-technically-flow-not-velocity-5-5.jpg
-
 ---
+
 Over the past decade, a recurring query has been echoing in my ears: "How can we normalise Story Points across teams so that we can look across and maybe compare teams?" It's high time we address this.
 
 ### TLDR;
diff --git a/site/content/resources/blog/2023/2023-09-27-the-definition-of-done-ensuring-quality-without-compromising-value/index.md b/site/content/resources/blog/2023/2023-09-27-the-definition-of-done-ensuring-quality-without-compromising-value/index.md
index e193841d8f..ffae438258 100644
--- a/site/content/resources/blog/2023/2023-09-27-the-definition-of-done-ensuring-quality-without-compromising-value/index.md
+++ b/site/content/resources/blog/2023/2023-09-27-the-definition-of-done-ensuring-quality-without-compromising-value/index.md
@@ -1,25 +1,26 @@
 ---
-title: 'The Definition of Done: Ensuring Quality without Compromising Value'
+title: "The Definition of Done: Ensuring Quality without Compromising Value"
 description: Discover the importance of the Definition of Done in agile practices. Ensure quality and transparency in your projects with insights from NKDAgility. Learn more!
 date: 2023-09-27
+AudioNative: true
 creator: Martin Hinshelwood
 id: "50083"
 layout: blog
 resourceTypes: blog
 slug: the-definition-of-done-ensuring-quality-without-compromising-value
 aliases:
-- /blog/the-definition-of-done-ensuring-quality-without-compromising-value
-- /the-definition-of-done-ensuring-quality-without-compromising-value
-- /the-definition-of-done--ensuring-quality-without-compromising-value
-- /blog/the-definition-of-done--ensuring-quality-without-compromising-value
+  - /blog/the-definition-of-done-ensuring-quality-without-compromising-value
+  - /the-definition-of-done-ensuring-quality-without-compromising-value
+  - /the-definition-of-done--ensuring-quality-without-compromising-value
+  - /blog/the-definition-of-done--ensuring-quality-without-compromising-value
 tags:
-- featured
-- homepage
+  - featured
+  - homepage
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-DOD-Not-AC-3-1-1-1.jpg
-
 ---
+
 The Definition of Done (DoD) is a sacrosanct measure of quality, ensuring that every piece of work meets the standards necessary for release. On the other hand, acceptance criteria focus on the work's content. Merging the two can risk the integrity of a working, usable product. This article delves into the nuances of maintaining the sanctity of the DoD while ensuring the delivery of valuable increments.
 
 ### Why having Acceptance Criteria on the Definition of Done risks the sanctity of the working usable product
diff --git a/site/content/resources/blog/2023/2023-09-29-how-to-set-and-achieve-effective-sprint-goals/index.md b/site/content/resources/blog/2023/2023-09-29-how-to-set-and-achieve-effective-sprint-goals/index.md
index 0c1c33e97c..da34b6e9c1 100644
--- a/site/content/resources/blog/2023/2023-09-29-how-to-set-and-achieve-effective-sprint-goals/index.md
+++ b/site/content/resources/blog/2023/2023-09-29-how-to-set-and-achieve-effective-sprint-goals/index.md
@@ -2,27 +2,28 @@
 title: How to Set and Achieve Effective Sprint Goals
 description: Unlock the power of effective Sprint Goals in Scrum! Learn to craft clear, actionable objectives that drive team success and stakeholder trust. Start now!
 date: 2023-09-29
+AudioNative: true
 creator: Martin Hinshelwood
 contributors:
-- name: Ralph Jocham
-  external: https://www.scrum.org/ralph-jocham
+  - name: Ralph Jocham
+    external: https://www.scrum.org/ralph-jocham
 id: "50115"
 layout: blog
 resourceTypes: blog
 slug: how-to-set-and-achieve-effective-sprint-goals
 aliases:
-- /blog/how-to-set-and-achieve-effective-sprint-goals
-- /how-to-set-and-achieve-effective-sprint-goals
+  - /blog/how-to-set-and-achieve-effective-sprint-goals
+  - /how-to-set-and-achieve-effective-sprint-goals
 tags:
-- featured
-- homepage
-- scrum
-- sprint-goal
+  - featured
+  - homepage
+  - scrum
+  - sprint-goal
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-SetEffectiveSprintGoals-1-1.jpg
-
 ---
+
 Many teams grapple with the intricacies of Scrum, and one of the most pivotal components is the Sprint Goal. It's not just a fleeting thought or a mere list of tasks; it's a commitment, a promise, and a clear direction.
 
 ## TLDR;
diff --git a/site/content/resources/blog/2023/2023-10-17-the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/index.md b/site/content/resources/blog/2023/2023-10-17-the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/index.md
index ad77d72a0c..d21a3148e1 100644
--- a/site/content/resources/blog/2023/2023-10-17-the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/index.md
+++ b/site/content/resources/blog/2023/2023-10-17-the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development/index.md
@@ -1,24 +1,25 @@
 ---
-title: 'The 7 Deadly Sins of Agile: A Grecian Odyssey through Modern Software Development'
+title: "The 7 Deadly Sins of Agile: A Grecian Odyssey through Modern Software Development"
 description: Explore the 7 Deadly Sins of Agile through ancient Greek wisdom. Learn to navigate modern software challenges and foster a culture of growth and collaboration.
 date: 2023-10-17
+AudioNative: true
 creator: Martin Hinshelwood
 id: "50309"
 layout: blog
 resourceTypes: blog
 slug: the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development
 aliases:
-- /blog/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development
-- /the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development
-- /the-7-deadly-sins-of-agile--a-grecian-odyssey-through-modern-software-development
-- /blog/the-7-deadly-sins-of-agile--a-grecian-odyssey-through-modern-software-development
+  - /blog/the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development
+  - /the-7-deadly-sins-of-agile-a-grecian-odyssey-through-modern-software-development
+  - /the-7-deadly-sins-of-agile--a-grecian-odyssey-through-modern-software-development
+  - /blog/the-7-deadly-sins-of-agile--a-grecian-odyssey-through-modern-software-development
 tags:
-- homepage
+  - homepage
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-7DeadlySins-16-15.jpg
-
 ---
+
 In the rich tapestry of ancient Greek philosophy, the concept of the seven deadly sins stands out as a profound exploration of human nature and morality. Deeply rooted in Greek thought, these sins were not seen as fleeting transgressions. Instead, they were formidable obstacles, barriers between individuals and a virtuous, fulfilling life.
 
 ![](images/NKDAgility-technically-7DeadlySins-jpg-15-16.webp)
diff --git a/site/content/resources/blog/2024/2024-02-13-blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/index.md b/site/content/resources/blog/2024/2024-02-13-blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/index.md
index df5cab8f73..f893834b3f 100644
--- a/site/content/resources/blog/2024/2024-02-13-blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/index.md
+++ b/site/content/resources/blog/2024/2024-02-13-blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/index.md
@@ -2,27 +2,28 @@
 title: Blocked Columns on Kanban Boards Obfuscate Workflow and Undermine Effectiveness
 description: Discover how blocked columns on Kanban boards hinder workflow efficiency. Learn effective strategies to enhance transparency and accountability in your team.
 date: 2024-02-13
+AudioNative: true
 creator: Martin Hinshelwood
 contributors:
-- name: Will Seele
-  external: https://www.linkedin.com/in/wjseele/
+  - name: Will Seele
+    external: https://www.linkedin.com/in/wjseele/
 id: "51208"
 layout: blog
 resourceTypes: blog
 slug: blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness
 aliases:
-- /blog/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness
-- /blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness
+  - /blog/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness
+  - /blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness
 tags:
-- homepage
+  - homepage
 categories:
-- agility
-- kanban
-- measure-and-learn
-- tools-and-techniques
+  - agility
+  - kanban
+  - measure-and-learn
+  - tools-and-techniques
 preview: NKDAgility-technically-BlockedColumns-7-7.jpg
-
 ---
+
 The Boards in Azure DevOps are a powerful tool that your teams can leverage to enable transparent visualization of the current state of value delivery.
 
 However, the inclusion of Blocked columns can stealthily erode the very foundations of efficiency these boards are meant to uphold. By obfuscating the state of work-in-progress and breeding a culture of hands-off responsibility, Blocked columns can become the silent saboteurs in your workflow.
diff --git a/site/content/resources/blog/2024/2024-03-21-pragmatism-crushes-dogma-in-the-wild/index.md b/site/content/resources/blog/2024/2024-03-21-pragmatism-crushes-dogma-in-the-wild/index.md
index 6b9ff89642..9d430c8750 100644
--- a/site/content/resources/blog/2024/2024-03-21-pragmatism-crushes-dogma-in-the-wild/index.md
+++ b/site/content/resources/blog/2024/2024-03-21-pragmatism-crushes-dogma-in-the-wild/index.md
@@ -2,19 +2,20 @@
 title: Pragmatism crushes Dogma in the wild
 description: Discover how pragmatism triumphs over dogma in Scrum through real-world challenges in Minecraft, fostering adaptability and resilience in product development.
 date: 2024-03-21
+AudioNative: true
 creator: Martin Hinshelwood
 id: "51362"
 layout: blog
 resourceTypes: blog
 slug: pragmatism-crushes-dogma-in-the-wild
 aliases:
-- /blog/pragmatism-crushes-dogma-in-the-wild
-- /pragmatism-crushes-dogma-in-the-wild
+  - /blog/pragmatism-crushes-dogma-in-the-wild
+  - /pragmatism-crushes-dogma-in-the-wild
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-PragamtismCrushesDogma-1-1.jpg
-
 ---
+
 In my journey of delivering an immersive [Product Development Mentor Program](https://nkdagility.com/global-consultancy-services/product-development-mentoring-program/) over the last eight weeks, a compelling narrative unfolded that beautifully illustrates the essence and true strength of Scrum. This story, rooted in the practical application of Scrum through Minecraft, unveils the depth of adaptability and resilience that Scrum can foster within a team.
 
 The program structured around a series of sprints in Minecraft, aimed to mirror the real-world complexities and dynamism present in product development projects. Starting from the initial chaos of Sprint 1, where participants grappled with the inherent complexity of a new project, the program progressively unfolded to reveal the power of Scrum. By Sprint 2, the fruits of understanding empiricism and embracing a philosophy of flexibility were evident. The teams learned to navigate and adapt to complexities with much less stress and frustration.
diff --git a/site/content/resources/blog/2024/2024-04-17-you-cant-stop-the-signal-but-you-can-ignore-it/index.md b/site/content/resources/blog/2024/2024-04-17-you-cant-stop-the-signal-but-you-can-ignore-it/index.md
index 88fe48511d..b91d9962ea 100644
--- a/site/content/resources/blog/2024/2024-04-17-you-cant-stop-the-signal-but-you-can-ignore-it/index.md
+++ b/site/content/resources/blog/2024/2024-04-17-you-cant-stop-the-signal-but-you-can-ignore-it/index.md
@@ -2,21 +2,22 @@
 title: You can't stop the signal! But you can ignore it!
 description: Explore how Agile and Scrum illuminate challenges in teams and organizations, fostering a culture of continuous improvement and responsiveness to critical signals.
 date: 2024-04-17
+AudioNative: true
 creator: Martin Hinshelwood
 id: "51389"
 layout: blog
 resourceTypes: blog
 slug: you-cant-stop-the-signal-but-you-can-ignore-it
 aliases:
-- /blog/you-cant-stop-the-signal-but-you-can-ignore-it
-- /you-cant-stop-the-signal-but-you-can-ignore-it
-- /you-can't-stop-the-signal--but-you-can-ignore-it-
-- /blog/you-can't-stop-the-signal--but-you-can-ignore-it-
+  - /blog/you-cant-stop-the-signal-but-you-can-ignore-it
+  - /you-cant-stop-the-signal-but-you-can-ignore-it
+  - /you-can't-stop-the-signal--but-you-can-ignore-it-
+  - /blog/you-can't-stop-the-signal--but-you-can-ignore-it-
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-YouCantStopTheSignal-1-1.jpg
-
 ---
+
 In organizational development and team dynamics, Agile (as the Agile Manifesto delineates) and Scrum (as the Scrum Guide outlines) guide teams not by solving their problems but by illuminating the issues that demand attention. These frameworks aim to identify and spotlight the challenges within a team or organization's processes, effectively saying, "This is wrong, go fix it!" when a team struggles to produce a working product due to various obstacles. These are clear signals!
 
 Yet, teams often overlook these clear signals. This raises the question: Why does such a disconnect exist between receiving these critical signals and acting on them? What barriers within teams and organizations prevent them from hearing and responding to these alerts?
diff --git a/site/content/resources/blog/2024/2024-09-05-the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know/index.md b/site/content/resources/blog/2024/2024-09-05-the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know/index.md
index 051e0aca0d..117381cd7a 100644
--- a/site/content/resources/blog/2024/2024-09-05-the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know/index.md
+++ b/site/content/resources/blog/2024/2024-09-05-the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know/index.md
@@ -2,24 +2,25 @@
 title: Why Most Scrum Masters Are Failing and What They Should Know
 description: Discover why many Scrum Masters fail and learn essential skills for success. Elevate your Agile practices and ensure your team's effectiveness today!
 date: 2024-09-05
+AudioNative: true
 creator: Martin Hinshelwood
 id: "51730"
 layout: blog
 resourceTypes: blog
 slug: the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know
 aliases:
-- /blog/the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know
-- /blog/why-most-scrum-masters-are-failing-and-what-they-should-know/
-- /the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know
-- /why-most-scrum-masters-are-failing-and-what-they-should-know
-- /blog/why-most-scrum-masters-are-failing-and-what-they-should-know
+  - /blog/the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know
+  - /blog/why-most-scrum-masters-are-failing-and-what-they-should-know/
+  - /the-incompetent-scrum-master-why-most-are-failing-and-what-they-should-know
+  - /why-most-scrum-masters-are-failing-and-what-they-should-know
+  - /blog/why-most-scrum-masters-are-failing-and-what-they-should-know
 tags:
-- Scrum Masters
+  - Scrum Masters
 categories:
-- agility
+  - agility
 preview: NKDAgility-technically-whymostscrummastersarefailing-2-2.jpg
-
 ---
+
 As a DevOps consultant, Agile consultant, and trainer, I’ve worked with hundreds of companies to improve their software product development. It’s astonishing how many Scrum Masters lack even a basic understanding of Scrum, let alone the expertise required to support the teams they work with.
 
 A significant portion of Scrum Masters (about 61%\*) have either never read the Scrum Guide, lack technical proficiency relevant to their teams, or have only a superficial grasp of how to apply Scrum principles.
diff --git a/site/content/resources/blog/2025/2025-01-03-definition-of-done-objective-vs-subjective/index.md b/site/content/resources/blog/2025/2025-01-03-definition-of-done-objective-vs-subjective/index.md
index 4de7affb72..5f044a6b81 100644
--- a/site/content/resources/blog/2025/2025-01-03-definition-of-done-objective-vs-subjective/index.md
+++ b/site/content/resources/blog/2025/2025-01-03-definition-of-done-objective-vs-subjective/index.md
@@ -2,38 +2,43 @@
 title: Definition of Done - Objective vs Subjective
 description: Learn the critical distinction between subjective goals and the objective Definition of Done (DoD) in Scrum. This guide dives into why a measurable, automated DoD is essential for consistent quality, stakeholder trust, and professional-grade product delivery.
 date: 2025-01-03
+AudioNative: true
 creator: Martin Hinshelwood
 layout: blog
 resourceTypes: blog
 slug: definition-of-done-objective-vs-subjective
 aliases:
 tags:
-- Definition of Done
+  - Definition of Done
 categories:
-- Scrum
-- Product Delivery
+  - Scrum
+  - Product Delivery
 preview: 2025-01-03-definition-of-done-objective-vs-subjective.jpg
 ---
 
 In countless teams, there’s a recurring mix-up between “what” we’re building, “how” it aligns with business objectives, and the objective quality criteria by which it should be measured. The result? Chaos masquerading as agility. To clear the air: in Scrum, the “what” and “how” are driven by Product and Sprint Goals. These provide directional clarity but remain inherently subjective—a north star guiding your path, not a litmus test of quality.
 
 Contrast this with the Definition of Done (DoD). The DoD is your team’s objective compass—a binary, quantifiable checklist that ensures every Increment meets professional-grade quality. It’s non-negotiable and should be firmly rooted in your product’s brand, user expectations, and technical robustness.
+
 #### TL;DR:
 
 Don’t confuse subjective goals with objective quality. In Scrum, the Definition of Done (DoD) is a crucial, measurable bar of quality, not a negotiable outcome. Keep it clear, objective, and automated wherever possible to ensure that every Increment meets professional standards.
+
 ### Product and Sprint Goals: Subjective by Design
 
-Goals in Scrum are aspirational, meant to challenge teams and align efforts towards strategic outcomes. The Product Goal represents a long-term objective, while the Sprint Goal offers a short-term milestone. Together, they guide the team like a compass through the wilderness., helping maintain direction even through surprise obstacles and side quests.  However, achieving these goals isn’t always guaranteed. Progress is iterative, incremental, and constantly adapting to new insights - a bit like chasing a moving target.
+Goals in Scrum are aspirational, meant to challenge teams and align efforts towards strategic outcomes. The Product Goal represents a long-term objective, while the Sprint Goal offers a short-term milestone. Together, they guide the team like a compass through the wilderness., helping maintain direction even through surprise obstacles and side quests. However, achieving these goals isn’t always guaranteed. Progress is iterative, incremental, and constantly adapting to new insights - a bit like chasing a moving target.
+
 ### Definition of Done: The Objective Measure
 
 Unlike goals, the Definition of Done is a steadfast benchmark for quality. It defines the bare minimum for an Increment to be considered complete. Without it, teams risk releasing poorly constructed, subpar products that erode user trust and damage the brand. A solid DoD ensures consistent quality across all deliverables, instilling confidence in both internal teams and end users.
+
 ### Establishing a Solid Definition of Done
 
 There is a key message in the Scrum Guide that is often overlooked that plays a critical role in establishing the DoD.
 
 > If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. - Scrum Guide 2020
 
-For me this suggests that there should be some kind of Organizational or Product DoD. I think of this as comming from the business. This is driven by the business and should reflect the businesses intent for quality in the product. That might be the minimum level of quality required by the business to protect their brand, their customers, and their employees. 
+For me this suggests that there should be some kind of Organizational or Product DoD. I think of this as comming from the business. This is driven by the business and should reflect the businesses intent for quality in the product. That might be the minimum level of quality required by the business to protect their brand, their customers, and their employees.
 
 An example of a Organizational or Product DoD for a team working on a cloud product might be:
 
@@ -41,13 +46,14 @@ An example of a Organizational or Product DoD for a team working on a cloud prod
 
 This sets a clear bar for delivery while supporting empirical learning and iterative improvement. It stays clear of the technical detail and jargon of an individual teams DoD and focuses on its objective and purpose for the product. It implies much, from ideation to delivery while minimizing imposition on the teams. It creates alignment of intent while maintaining autonomy of implementation. It recognizes that every team needs a unique DoD that is relevant for their context.
 
-Each team working on a product would then be responsible for creating a DoD that is appropriate for their context within that product. 
+Each team working on a product would then be responsible for creating a DoD that is appropriate for their context within that product.
 
 This is the seed that will grow into each teams unique quality bar that reflects this DoD. A robust reflection should be:
 
 1. **Objective and Measurable**: Avoid vague criteria and instead focus on things that you can measure.
 2. **Comprehensive**: What are all the things that need to be true for a production deployment of your product to be deployed to production?
-4. **Living Document**: The teams DoD as needed to reflect evolving standards, technologies, and stakeholder expectations of the product as it grows.
+3. **Living Document**: The teams DoD as needed to reflect evolving standards, technologies, and stakeholder expectations of the product as it grows.
+
 ### Common Pitfalls
 
 Despite its critical importance, the DoD is often misunderstood, undervalued, or even undermined. Teams frequently:
@@ -55,11 +61,12 @@ Despite its critical importance, the DoD is often misunderstood, undervalued, or
 - **Blur Subjective and Objective**: Adding criteria like “approved by the Product Owner”, which shifts focus from quality to stakeholder satisfaction. Any "approved by ... person or department" should be strictly avoided.
 - **Overlook Automation**: Relying on manual checks leads to inconsistencies and slower feedback loops.
 - **Treat the DoD as a Maximum**: Viewing it as a ceiling instead of a floor hampers innovation and improvement.
+
 ### Practices for Defining Done
 
 To maintain focus on quality, consider the following practices:
 
-1. **Automate Everything:** Automated tests and CI/CD pipelines should validate DoD compliance as part of the development process. If you have things that cant be automated right now, plan the work to change the product to enable those activities to be automated.  
+1. **Automate Everything:** Automated tests and CI/CD pipelines should validate DoD compliance as part of the development process. If you have things that cant be automated right now, plan the work to change the product to enable those activities to be automated.
 2. **Review Regularly**: Incorporate DoD reviews in retrospectives to ensure its relevance and alignment with current product and organizational needs. Keep a list of "things that need to be true to deploy to production that we cant do yet", and regularly move these to Done.
 3. **Train Teams**: Ensure every team member understands the DoD and its importance in delivering professional-grade Increments.
 4. **Separate Quality from Approval**: Keep subjective approval processes distinct from the DoD to avoid undermining its objectivity.
@@ -70,4 +77,4 @@ In Scrum, the Definition of Done is your minimum bar for quality. It’s the saf
 
 **What’s Your Take?**
 
-We’d love to hear your thoughts! How does your team define and enforce the Definition of Done? Have you faced challenges distinguishing subjective goals from objective quality measures? Share your experiences and insights in the comments below! 
\ No newline at end of file
+We’d love to hear your thoughts! How does your team define and enforce the Definition of Done? Have you faced challenges distinguishing subjective goals from objective quality measures? Share your experiences and insights in the comments below!
diff --git a/site/content/resources/blog/2025/2025-01-11-why-handoffs-are-killing-your-agility/index.md b/site/content/resources/blog/2025/2025-01-11-why-handoffs-are-killing-your-agility/index.md
index eeaae44139..c1cee53f0a 100644
--- a/site/content/resources/blog/2025/2025-01-11-why-handoffs-are-killing-your-agility/index.md
+++ b/site/content/resources/blog/2025/2025-01-11-why-handoffs-are-killing-your-agility/index.md
@@ -2,20 +2,21 @@
 title: Why Handoffs Are Killing Your Agility
 description: Explore the detrimental impact of handoffs in software development and discover strategies to eliminate them for better agility.
 date: 2025-01-13
+AudioNative: true
 creator: Martin Hinshelwood
 layout: blog
 resourceTypes: blog
 slug: why-handoffs-are-killing-your-agility
 aliases:
 tags:
-- handoffs
-- lean
-- devops
-- agile
-- cross-functional-teams
+  - handoffs
+  - lean
+  - devops
+  - agile
+  - cross-functional-teams
 categories:
-- agility
-- people-and-process
+  - agility
+  - people-and-process
 preview: 2025-01-11-why-handoffs-are-killing-your-agility.jpg
 ---
 
@@ -62,7 +63,8 @@ Eliminating handoffs requires a mix of modern engineering practices and a commit
 To achieve true agility, a focus on eliminating handoffs is necessary by implementing cross-functional teams and optimising flow. Here's how:
 
 1. **Create Cross-Functional Teams** - Bring together individuals with all the skills needed to deliver end-to-end value. A cross-functional team might include developers, testers, designers, and operations personnel working collaboratively towards a shared goal. No sub-teams. No silos.
-> **Pro Tip:** Co-locate teams in timezones and use collaboration tools like Microsoft Teams or Slack to ensure seamless communication.
+
+   > **Pro Tip:** Co-locate teams in timezones and use collaboration tools like Microsoft Teams or Slack to ensure seamless communication.
 
 2. **Adopt Continuous Delivery Practices** - Automation is a cornerstone of Continuous Delivery (CD). By integrating automated testing, deployment, and monitoring into your pipeline, you ensure quality at every step while reducing manual intervention. Moving towards "testing in production" becomes a natural evolution of this strategy, allowing teams to gather real-world feedback quickly and address issues proactively.
 
@@ -91,5 +93,4 @@ Remember: every handoff is an opportunity for waste. Eliminate them, and watch y
 5. The Agile Manifesto - [AgileManifesto.org](https://agilemanifesto.org/)
 6. Don Reinertsen, _Principles of Product Development Flow_
 
-
 **What challenges has your team faced in eliminating handoffs?** _Share your experiences and thoughts in the comments below._ Let’s start a conversation about how we can all build better, faster, and more collaborative teams!
diff --git a/site/content/resources/blog/2025/2025-01-30-the-scrum-master-is-accountable-for-delivery/index.md b/site/content/resources/blog/2025/2025-01-30-the-scrum-master-is-accountable-for-delivery/index.md
index ae10203a0f..121c586053 100644
--- a/site/content/resources/blog/2025/2025-01-30-the-scrum-master-is-accountable-for-delivery/index.md
+++ b/site/content/resources/blog/2025/2025-01-30-the-scrum-master-is-accountable-for-delivery/index.md
@@ -2,6 +2,7 @@
 title: The Scrum Master is accountable for Delivery
 description: The Scrum Master is accountable for delivery, ensuring every Scrum Team produces a usable increment every sprint while fostering effectiveness and value delivery.
 date: 2025-01-30
+AudioNative: true
 creator: Martin Hinshelwood
 contributors:
   - name: Ryan Ripley
diff --git a/site/content/resources/blog/2025/2025-02-03-delivery-as-the-ultimate-measure-of-progress/index.md b/site/content/resources/blog/2025/2025-02-03-delivery-as-the-ultimate-measure-of-progress/index.md
index 7e79f259b9..0460285096 100644
--- a/site/content/resources/blog/2025/2025-02-03-delivery-as-the-ultimate-measure-of-progress/index.md
+++ b/site/content/resources/blog/2025/2025-02-03-delivery-as-the-ultimate-measure-of-progress/index.md
@@ -2,6 +2,7 @@
 title: Delivery is the only Measure of Progress in Scrum
 description: Delivery, not just a Done Increment, is the real measure of progress in Scrum. In 2025, if you're not delivering every Sprint, you're not truly Agile.
 date: 2025-02-03T09:00:00
+AudioNative: true
 creator: Martin Hinshelwood
 contributors:
   - name: Ana Kotevska
diff --git a/site/content/resources/blog/2025/2025-02-10-without-delivery-there-is-no-value/index.md b/site/content/resources/blog/2025/2025-02-10-without-delivery-there-is-no-value/index.md
index 7ec77284ee..05ed729560 100644
--- a/site/content/resources/blog/2025/2025-02-10-without-delivery-there-is-no-value/index.md
+++ b/site/content/resources/blog/2025/2025-02-10-without-delivery-there-is-no-value/index.md
@@ -2,6 +2,7 @@
 title: "Without Delivery, There Is No Value"
 description: "Everything before delivery is an assumption, and all non-delivered product represents a cost of delay. Learn why frequent delivery is critical to maximising value."
 date: 2025-02-10T09:00:00
+AudioNative: true
 creator: Martin Hinshelwood
 layout: blog
 resourceTypes: blog