<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Technical Debt on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/technical-debt/</link>
		<description>Recent content in Technical Debt on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/tags/technical-debt/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/</link>
				<pubDate>Mon, 26 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/</guid>
				<description>Technical debt slows teams down and hurts morale, but stopping all work to fix it is unrealistic. The most effective approach is to make technical debt visible, prioritize high-impact improvements, and embed continuous improvement into daily workflows. Development managers should focus on changing team practices and decision-making so that managing technical debt becomes a natural, ongoing part of delivering value.</description>
			</item>
			<item>
				<title>Release planning and predictable delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/release-planning-and-predictable-delivery/</link>
				<pubDate>Tue, 24 Nov 2020 13:00:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/release-planning-and-predictable-delivery/</guid>
				<description>Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability.</description>
			</item>
			<item>
				<title>Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</link>
				<pubDate>Wed, 21 May 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/</guid>
				<description>Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence.</description>
			</item>
			<item>
				<title>There no such thing as &#34;good&#34; technical debt</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/</link>
				<pubDate>Sat, 19 Apr 2025 15:30:34 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/</guid>
				<description>Technical debt is always harmful and should not be considered acceptable; it slows onboarding, increases errors, and creates inefficiency. It accumulates quickly and can suddenly halt delivery, as seen in Microsoft&amp;rsquo;s experience before they overhauled their processes and addressed their debt. Development managers should prioritize identifying and reducing technical debt now rather than accepting it as normal.</description>
			</item>
			<item>
				<title>Engineering can fix technical debt, but leadership has to invest in it</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</link>
				<pubDate>Mon, 03 Mar 2025 16:30:35 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/</guid>
				<description>Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements.</description>
			</item>
			<item>
				<title>Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/</link>
				<pubDate>Thu, 19 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/</guid>
				<description>Technical debt is the cost of future rework from prioritising speed over good design, and it is distinct from poor quality, which often causes bigger productivity losses. Long release cycles and mislabeling poor quality as technical debt can lead to unsustainable practices and higher costs. Development managers should set clear quality standards, encourage regular refactoring, and adopt continuous improvement to reduce technical debt, improve efficiency, and deliver better products.</description>
			</item>
			<item>
				<title>The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</link>
				<pubDate>Wed, 21 Aug 2024 07:00:19 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/</guid>
				<description>DevOps transformation delivers major benefits when organizations address technical debt, simplify systems, and empower teams to take ownership of change. Key outcomes include faster delivery, lower costs, and happier, more effective teams, but success requires upskilling and active participation rather than outsourcing the work. Development managers should prioritize regular refactoring and foster a culture of continuous improvement to achieve lasting results.</description>
			</item>
			<item>
				<title>The Power of Technical Excellence in Agile Development</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</link>
				<pubDate>Thu, 27 Jun 2024 06:45:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/</guid>
				<description>Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive.</description>
			</item>
			<item>
				<title>Technical debt isn’t just messy code</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/</link>
				<pubDate>Thu, 13 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/</guid>
				<description>Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines.</description>
			</item>
			<item>
				<title>Transforming Chaos into Clarity: How Optimising Systems Fuels Engineering Excellence</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/</link>
				<pubDate>Mon, 16 Dec 2024 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/</guid>
				<description>Unmanaged chaos in software delivery leads to poor quality, technical debt, and wasted resources. Optimising systems and processes, as shown by Microsoft’s transformation of their DevOps team, enables faster delivery, higher productivity, and better products by reducing technical debt and improving testing practices. Development managers should prioritise system optimisation and technical leadership to empower teams and drive sustainable engineering excellence.</description>
			</item>
			<item>
				<title>Scaling Smart: How to Tackle Technical Debt for Sustainable Growth</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/</link>
				<pubDate>Tue, 25 Feb 2025 06:00:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/</guid>
				<description>Unchecked technical debt slows development, increases bugs, and reduces team productivity, making scaling risky and inefficient. Addressing weak points through sustainable architecture, automated testing, and continuous integration enables faster feedback, more reliable releases, and confident growth. Development managers should prioritize managing technical debt and automation to support sustainable scaling and maintain innovation.</description>
			</item>
			<item>
				<title>Technical debt cripples business agility and slows engineers down</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/</link>
				<pubDate>Tue, 06 May 2025 15:30:42 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/</guid>
				<description>Technical debt severely limits business agility and slows down engineering teams, making it harder to respond to market opportunities and innovate. This is a real risk seen in major companies and happens when technical debt is ignored. To stay competitive, focus on shortening feedback loops, automating processes, increasing transparency, and actively managing technical debt rather than accepting it.</description>
			</item>
			<item>
				<title>The Hidden Costs of Supporting Multiple Versions in Production</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/</link>
				<pubDate>Thu, 06 Feb 2025 16:30:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/</guid>
				<description>Supporting multiple versions in production drains engineering resources through increased context-switching, merge conflicts, and bug risks. Back-porting fixes and maintaining separate branches for each customer make things worse, leading to instability and technical debt. To avoid these problems, teams should simplify and standardise their branching strategy.</description>
			</item>
			<item>
				<title>The Hidden Costs of Poor Quality Code, and How to Turn It Into a Superpower</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</link>
				<pubDate>Tue, 19 Nov 2024 09:58:28 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/</guid>
				<description>Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success.</description>
			</item>
			<item>
				<title>Mastering Technical Debt: Strategies to Transform Challenges into Opportunities for Your Development Team</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/</link>
				<pubDate>Thu, 28 Nov 2024 06:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/</guid>
				<description>Technical debt results from choosing quick fixes over robust solutions, leading to future costs and risks that can hinder your team&amp;rsquo;s productivity. Proactively paying down technical debt, as shown by the Azure DevOps team&amp;rsquo;s shift to agile practices, can dramatically increase feature delivery and product quality. Make refactoring, short feedback loops, and a focus on quality part of your regular process to unlock long-term gains and sustainable success.</description>
			</item>
			<item>
				<title>Avoid the pick-n-mix branching anti-pattern</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/</link>
				<pubDate>Mon, 14 Jul 2014 15:35:35 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/</guid>
				<description>Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability.</description>
			</item>
			<item>
				<title>The Insufficiency of Scrum is a fallacy</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</link>
				<pubDate>Sat, 23 Mar 2013 17:37:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/</guid>
				<description>Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes.</description>
			</item>
			<item>
				<title>Stop Writing Business Logic in Stored Procedures</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/</link>
				<pubDate>Mon, 23 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/</guid>
				<description>Stop adding business logic to stored procedures and refactor existing logic into application code as you make changes, rather than rewriting everything at once. Keeping business logic in stored procedures makes testing, deployment, version control, scalability, and maintainability much harder, increasing technical debt and risk. Adopt a gradual, pay-as-you-go approach to modernize your codebase, improve engineering practices, and enable faster, more reliable delivery.</description>
			</item>
			<item>
				<title>Understand the true risk of technical debt in your business</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/</link>
				<pubDate>Thu, 24 Apr 2025 15:30:48 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/</guid>
				<description>Technical debt is pure risk with no upside, leading to lost time, reduced agility, and missed opportunities. Microsoft’s experience shows that unchecked technical debt can severely slow delivery, but addressing it directly restores speed and flexibility. Development managers should treat technical debt as a critical business issue and take proactive steps to reduce it.</description>
			</item>
			<item>
				<title>Technical Debt Management for Long-Term Quality</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/</link>
				<pubDate>Thu, 21 Nov 2024 07:00:11 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/</guid>
				<description>Technical debt results from choosing quick fixes over long-term solutions and can be both intentional and unintentional, eventually limiting your team&amp;rsquo;s ability to deliver value. The Azure DevOps team dramatically increased their feature delivery by prioritizing and paying down technical debt, showing that addressing it leads to faster delivery and higher product quality. Development managers should actively identify and pay back technical debt to maximize long-term productivity and value.</description>
			</item>
			<item>
				<title>Would your CFO approve misrepresenting corporate assets?</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/</link>
				<pubDate>Mon, 21 Apr 2025 15:30:34 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/</guid>
				<description>Ignoring technical debt is like misrepresenting the value of your software assets, which can lead to future losses and operational risks. Most businesses fail to track this risk, even though technical debt reduces asset value and increases costs. Development managers should ensure technical debt is monitored and addressed to protect the true value of software investments.</description>
			</item>
			<item>
				<title>All technical debt is a risk to the product and to your business</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/</link>
				<pubDate>Mon, 25 Jan 2021 14:55:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/</guid>
				<description>Technical debt is a significant risk to your product and business, as it undermines quality, slows delivery, and can accumulate unnoticed until it becomes a major problem. The Microsoft Team Foundation Server example shows that ignoring technical debt leads to reduced productivity and competitiveness, while addressing it through transparency and shorter feedback cycles enables faster, higher-quality delivery. Development managers should prioritize eliminating technical debt and fostering a culture of quality to protect business value and avoid long-term risks.</description>
			</item>
			<item>
				<title>Team Foundation Server 2013 is production ready</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-2013-is-production-ready/</link>
				<pubDate>Tue, 23 Jul 2013 09:44:42 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/team-foundation-server-2013-is-production-ready/</guid>
				<description>Team Foundation Server 2013 is stable for production use, addressing past update issues with improved agility, technical debt management, and enhanced ALM features.</description>
			</item>
			<item>
				<title>Transforming Technical Debt: Unlocking Opportunities for Innovation and Value</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/</link>
				<pubDate>Wed, 20 Nov 2024 16:53:31 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/</guid>
				<description>Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to accumulate slows delivery, increases maintenance costs, and lowers team morale, while proactively addressing it empowers teams, improves agility, and enhances value delivery. Make technical debt management a regular part of your workflow and educate stakeholders to unlock your team&amp;rsquo;s full potential.</description>
			</item>
			<item>
				<title>Technical Debt</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/technical-debt/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/technical-debt/</guid>
				<description>Technical debt is the concept that encapsulates the hidden costs associated with opting for quick, suboptimal solutions in software development rather than investing time in more effective, long-term strategies. It often emerges from factors such as hurried development processes, insufficient documentation, or reliance on outdated technologies. Recognising and managing technical debt is essential for teams striving to deliver consistent and sustainable value, as its accumulation can impede innovation and responsiveness to market changes, ultimately compromising product quality and delivery timelines. Addressing technical debt requires a commitment to refactoring, enhancing code quality, and adopting superior tools and practices, which not only boosts team efficiency but also cultivates a culture of continuous improvement. By systematically tackling technical debt, organisations can sustain a healthy development pace, ensuring competitiveness and responsiveness to customer demands. This strategic focus on technical debt is crucial for fostering organisational agility, as it directly impacts the ability to innovate and adapt in a fast-evolving landscape.</description>
			</item>
	</channel>
</rss>
