<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Agentic Engineering on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/agentic-engineering/</link>
		<description>Recent content in Agentic Engineering 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/agentic-engineering/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Telling People What to Do Is Not Leadership. It’s a Failure of System Design</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/</link>
				<pubDate>Mon, 04 Aug 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/</guid>
				<description>Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work.</description>
			</item>
			<item>
				<title>Are We Still Pretending Coding Was the Bottleneck?</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</link>
				<pubDate>Mon, 01 Sep 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/</guid>
				<description>AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output.</description>
			</item>
			<item>
				<title>Rethinking Dev-Test-Staging-Production Pipelines for Safety</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</link>
				<pubDate>Fri, 21 Feb 2025 16:30:30 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/</guid>
				<description>Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency.</description>
			</item>
			<item>
				<title>How Lack of Agency is Killing Your DevOps Initiatives</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</link>
				<pubDate>Mon, 16 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/</guid>
				<description>DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues.</description>
			</item>
			<item>
				<title>The Missing Lever in Agile Transformations</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-missing-lever-in-agile-transformations/</link>
				<pubDate>Mon, 02 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-missing-lever-in-agile-transformations/</guid>
				<description>Agile transformations often fail because they focus on following ceremonies instead of building real agency in people and systems. True agility comes from empowering individuals and teams to make decisions and adapt, supported by evidence-based management to measure outcomes and guide change. To succeed, shift your transformation efforts from compliance to fostering agency and use data to drive continuous improvement.</description>
			</item>
			<item>
				<title>You want speed, adaptability, resilience</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</link>
				<pubDate>Sun, 11 May 2025 15:30:29 +0100</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/you-want-speed-adaptability-resilience/</guid>
				<description>Investing in Agile, Scrum, Kanban, and DevOps will not deliver real speed, adaptability, or resilience unless your teams have the agency to truly own their work and outcomes. Without empowering people to take responsibility, you risk superficial processes and disengaged teams. To achieve genuine agility, ensure your system supports team and individual ownership, not just frameworks.</description>
			</item>
			<item>
				<title>How I Used Generative AI to Transform Site Tagging and Categories</title>
				<link>https://engineering-leadership.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/</link>
				<pubDate>Thu, 15 May 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/</guid>
				<description>Migrating a large, legacy blog to Hugo enabled the use of generative AI for automated tagging and categorisation, significantly improving content discoverability and editorial consistency while reducing manual effort. The system combines AI-driven suggestions with human oversight, using multi-factor scoring, penalty logic, and transparent reasoning to ensure quality and accountability. Development managers considering similar automation should maintain human control over final decisions and leverage AI to streamline, not replace, editorial processes.</description>
			</item>
			<item>
				<title>Human and AI Agency in Adaptive Systems: Strategy Before Optimisation</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/human-and-ai-agency-in-adaptive-systems-strategy-before-optimisation/</link>
				<pubDate>Mon, 30 Jun 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/human-and-ai-agency-in-adaptive-systems-strategy-before-optimisation/</guid>
				<description>Human decision-making is essential for setting strategy, purpose, and adapting to change, while AI should be used for tactical optimisation within clear human-defined boundaries. Over-relying on AI for adaptation leads to fragile systems, loss of accountability, and strategic obsolescence. Development managers should ensure humans remain responsible for strategic direction and adaptation, using AI only to optimise within those parameters.</description>
			</item>
			<item>
				<title>Agentic Engineering</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agentic-engineering/</link>
				<pubDate>Tue, 22 Jul 2025 15:58:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agentic-engineering/</guid>
				<description>Agentic Engineering is the deliberate design and practice of software development that maximises the agency of both humans and intelligent systems. It integrates engineering excellence, DevOps ethos, and ethical autonomy to create environments where decisions are decentralised, feedback is fast, and value delivery is continuous. It&amp;rsquo;s characterised by Developer Agency, Systemic Observability, DevOps-Infused Craft, Ethical AI Integration, and Feedback-Driven Adaptation. Agentic Engineering is not a job title, role, or method, it&amp;rsquo;s a philosophy of engineering in which the ability to act with clarity, intent, and impact is engineered into the way we build, learn, and evolve.</description>
			</item>
			<item>
				<title>Agentic Agility</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agentic-agility/</link>
				<pubDate>Mon, 07 Apr 2025 12:39:49 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agentic-agility/</guid>
				<description>Agentic Agility is the capacity, human or AI, to take intentional, adaptive action within socio-technical environments to improve outcomes and align with evolving goals. It is grounded in agency: the power to act with autonomy, accountability, and purpose. Without agency, Agile devolves into hollow rituals; with it, people and systems can deliberately shape value delivery. Agentic Agility manifests through human judgement and learning or AI-driven optimisation within constraints, enabling continuous evolution of both what is delivered and how it is delivered. It is the critical lever that sustains agility as a living, resilient capability rather than a hollow label.</description>
			</item>
			<item>
				<title>Collective Intelligence</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/collective-intelligence/</link>
				<pubDate>Thu, 23 Jan 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/collective-intelligence/</guid>
				<description>Collective Intelligence represents the enhanced problem-solving and innovation capabilities that emerge when humans with agency effectively collaborate with AI agents as team members. This concept goes beyond traditional human collaboration to encompass human-AI partnerships where both parties contribute complementary strengths, human creativity, judgment, and contextual understanding combined with AI processing power, pattern recognition, and consistent execution. Unlike passive tool usage, Collective Intelligence requires humans to have genuine agency and AI systems to operate with designed autonomy within appropriate constraints. The resulting synergy enables teams to navigate complex socio-technical environments, make more informed decisions, and deliver superior outcomes that neither humans nor AI could achieve independently. This form of agentic agility is essential for modern product development, where the volume and complexity of information, rapid change cycles, and need for continuous adaptation exceed purely human cognitive capabilities. By cultivating Collective Intelligence, organisations can harness the full potential of human-AI collaboration, transforming how value is created and delivered in digital product development.</description>
			</item>
			<item>
				<title>Agentic Software Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/agentic-software-delivery/</link>
				<pubDate>Tue, 21 Jan 2025 10:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/agentic-software-delivery/</guid>
				<description>Agentic Software Delivery is a strategy for continuously achieving business outcomes through the deliberate integration of autonomous AI agents, human expertise, and organisational context. It is not about automation for automation&amp;rsquo;s sake, but about enabling teams to move faster and smarter by embedding proactive, context-aware intelligence into their systems of work. The term &amp;lsquo;agentic&amp;rsquo; implies more than assistance, it implies agency. These agents operate autonomously within defined boundaries, learning from data, adapting to patterns, and making context-informed decisions. They contribute meaningfully to outcomes across discovery, development, delivery, and operations. This approach relies on the synergy between domain experts and AI agents, requiring lean, empirical systems of work, strong product strategy, and modern engineering practices such as CI/CD, observability, infrastructure as code, and automated testing.</description>
			</item>
	</channel>
</rss>
