<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Lead Time on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/lead-time/</link>
		<description>Recent content in Lead Time 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/lead-time/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Rethinking Capacity Planning</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/rethinking-capacity-planning/</link>
				<pubDate>Mon, 21 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/rethinking-capacity-planning/</guid>
				<description>Capacity planning should focus on optimising system flow and predictability, not tracking individual hours or task assignments. Shifting from micromanagement to managing work as a system at portfolio, category, and team levels helps prevent overload, improves value delivery, and enables reliable forecasting. Development managers should prioritise system-level metrics, enforce work-in-progress limits, and empower teams to pull well-prepared work, creating sustainable and predictable delivery.</description>
			</item>
			<item>
				<title>Why Measuring Individual Cycle Time Fails to Help Teams</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</link>
				<pubDate>Sat, 15 Mar 2025 16:30:02 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/</guid>
				<description>Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals.</description>
			</item>
			<item>
				<title>Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics</title>
				<link>https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</link>
				<pubDate>Mon, 25 Aug 2025 06:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/</guid>
				<description>Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible.</description>
			</item>
			<item>
				<title>Why Tracking Individual Cycle Time Distorts Team Behaviour</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</link>
				<pubDate>Wed, 12 Mar 2025 16:30:03 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/</guid>
				<description>Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead.</description>
			</item>
			<item>
				<title>Lead Time</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/lead-time/</link>
				<pubDate>Fri, 11 Apr 2025 06:00:00 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/lead-time/</guid>
				<description>Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments.</description>
			</item>
	</channel>
</rss>
