About
About Intent-Driven Development
Intent-Driven Development grew from the intersection of three threads: consulting on how organisations build technology, coaching leaders on how they make decisions, and a conviction that clarity of intent determines the quality of outcomes.
Created by Richard Stockley
Richard Stockley is a fractional IT architect, executive coach and mentor with almost thirty years of global experience across software engineering, IT architecture and delivery leadership. His career spans investment banking, government, healthcare, retail, motorsport and international NGOs, with particular depth in distributed systems, microservices and mission-critical architectures, and he has been delivering AI projects since 2019.
He is a Fellow of the British Computer Society (FBCS), an EMCC-accredited coach and mentor, and holds an MSc in Advanced Computer Science from the University of Manchester.
Across that work one pattern has held constant. The projects that succeed are those in which the people involved are clear about what they are trying to achieve before they start building, and the projects that fail are those in which someone starts coding before anyone has articulated what the system is for, who it serves and how they will know it works. Agentic AI has not changed that pattern, but it has changed the consequence: unclear intent now produces the wrong thing faster than ever. IDD is a practical response to that shift, drawn from what was happening in his consulting work rather than devised in isolation.
Contributors
The concept and name of intent shaping came from Calum Gunn. The founding articles were also shaped by the readers, practitioners and colleagues who responded to each one as it was published, and whose questions set the direction of the next.
Related work
A number of practitioners and organisations are exploring related ideas, and their work reinforces the direction of travel towards intent-first delivery. They differ mainly in scope.
- John Ferguson Smart used the phrase "intent-driven development" in 2019 to describe announcing your intent before you act, a practice close to Behaviour-Driven Development and focused on the individual developer.
- Keyhole Software describes intent-driven development as a modern SDLC for AI-accelerated teams, concentrating on aligning product and engineering on intent before building.
- Adaptive Intent-Driven Development (AIDD), explored by Binoy Ayyagari, looks at AI-first development with multi-agent collaboration.
- Exadra37's AI Intent Driven Development is a practical collection of guidelines for AI coding agents, structured around why, what and how documents.
- Spec-driven development tools and writing, including intent-driven.dev, focus on specification-first workflows for coding agents. The relationship is set out in IDD and spec-driven development.
What distinguishes IDD is its breadth: a connected model spanning specification, governance, measurement and organisational design.
Beyond software
The principle behind IDD, Govern Intent. Delegate Execution., does not stop at the codebase. The Human Intent series on richardstockley.com takes the same argument to the whole organisation, asking what happens to structures, roles and leadership when work is no longer the unit being organised.
Get in touch
For speaking, workshops or help applying IDD in your organisation, send Richard a message, or find him on LinkedIn. Worked examples and case studies from practitioners applying IDD are especially welcome.