Human Intent – Organisational Change in the AI Era: exploring the shift from managing work to governing intent
For most of the last century, organisations have been built around a simple problem:
How do we get work done?
We created departments. We defined roles. We introduced management layers. We built processes to coordinate effort. All of it was designed to solve one constraint: execution is hard, work is slow, coordination is complex, and delivery is expensive.
So we optimised for it.
But something has changed. Not gradually. Structurally.
AI systems, particularly agentic systems, are starting to remove execution as the primary constraint. Not completely. Not perfectly. But enough to matter.
For the first time, organisations are no longer limited by how fast they can build. They are limited by something else entirely:
Do we actually know what we want?
This Changes the Role of Management
If execution is no longer the bottleneck, then the traditional role of management starts to break down.
Because management, as we have known it, is largely about managing execution. Assigning work. Coordinating activity. Managing dependencies. Tracking progress. Resolving delivery issues.
But if execution can increasingly be delegated to machines, then what remains?
What Remains Is Intent
Someone still has to decide what should exist, what success looks like, what trade-offs are acceptable, what constraints must be respected, and what “good” actually means.
That does not go away. It becomes more important.
This Is Not Less Management
It is different management.
Govern Intent. Delegate Execution.
That is the shift.
Management does not disappear. It moves up a level.
From managing tasks, managing people, and managing process – to defining outcomes, setting principles, establishing constraints, and measuring alignment.
This Is Not Just About Software
When we say “build,” most people think of engineering. But in an AI-enabled organisation, every department builds. Just not in the way we have traditionally thought about it.
Operations
Operations does not just run processes anymore.
It can build automated supply chain decisions, dynamic routing and logistics, and real-time capacity planning systems. Instead of managing workflows, it defines delivery outcomes, service levels, and acceptable trade-offs.
And systems execute.
HR
HR does not just manage people and policies.
It can build personalised onboarding journeys, continuous performance feedback systems, and talent matching and development pathways. Instead of administering processes, it defines what great performance looks like, how people should be supported, and what fairness and consistency mean.
And systems enact that intent at scale.
Finance
Finance does not just track and report.
It can build real-time forecasting models, automated investment decision systems, and dynamic cost optimisation mechanisms. Instead of producing reports, it defines financial outcomes, risk tolerance, and investment principles.
And execution follows.
Marketing
Marketing does not just create campaigns.
It can build adaptive content systems, real-time audience targeting, and continuous experimentation engines. Instead of pushing messages, it defines desired customer behaviour, brand principles, and boundaries of acceptable engagement.
And systems optimise toward those outcomes.
Product and Technology
And yes, engineering still builds.
But even here, the shift is the same. From writing code to defining intent clearly enough that code can be generated, adapted, and evolved automatically.
Every Role Becomes Directive
This collapses a distinction that has defined organisations for decades. Technical roles built things. Non-technical roles requested things. Engineers specified. Everyone else consumed.
In a Human Intent world, every role directs execution within its own domain. A finance leader defines financial intent and systems act on it. A marketer defines marketing intent and systems act on it. An HR leader defines talent intent and systems act on it. Engineering is no longer a privileged layer between human need and machine action. It is simply one of many domains where humans now define what should exist and systems deliver it.
The boundary between who builds and who specifies dissolves, because specification becomes the building.
The Real Constraint
Across all of these functions, the pattern is identical.
The constraint is no longer execution. The constraint is clarity of intent.
Poorly defined intent leads to misaligned systems, unintended outcomes, and amplified mistakes. And because execution is faster, those mistakes happen faster too. This is the same principle that underpins intent fidelity in Intent-Driven Development. When intent is unclear, drift is inevitable. When execution is autonomous, drift is amplified.
Intent Has to Change
Intent can no longer be vague, implicit, buried in documents, or spread across PowerPoints, policies, and disconnected systems.
It needs to be structured, shared, measurable, and actionable. Not for humans alone, but for systems that act on it.
This is a shift that goes beyond software development. In Intent-Driven Development, we explored how intent specifications must be clear enough that autonomous systems can execute reliably against them. The same principle applies to every function in the organisation. If an AI system is acting on your behalf, whether it is writing code, managing logistics, or optimising a marketing campaign, it needs to understand your intent with the same rigour.
The Organisational Shift
This leads to a deeper change.
Organisations have traditionally been structured around the flow of work. Tasks move between teams. Outputs move between functions. Work gets handed off, escalated, managed.
But in an AI-enabled world, that model starts to break. Because execution does not need the same coordination.
So the structure shifts toward the flow of intent. Intent is defined at different levels. It is inherited, refined, and promoted. Systems execute against it continuously. Feedback reshapes it in real time.
Those familiar with the Intent Hierarchy will recognise this pattern. The same principles that allow intent to flow between organisation, domain, and project levels in software development apply to the wider organisation. Strategy becomes organisational intent. Departmental goals become domain intent. Operational objectives become project intent. The hierarchy scales.
Human Intent
Which brings us to a simple but important distinction.
Humans have roles. Agents have functions.
Humans define intent, judge outcomes, and resolve ambiguity. Agents execute functions against that intent. The boundary is no longer human work versus machine work. It becomes intent versus execution.
This is what I am calling Human Intent.
Human Intent is the recognition that as AI systems take on more of the execution layer across entire organisations, not just software engineering, the uniquely human contribution becomes the quality of the intent itself. The clarity of purpose. The judgement about trade-offs. The ethical reasoning. The understanding of context that no model yet possesses.
Human Intent is not a framework. It is the era we are entering.
What Comes Next
If intent is what drives everything, then we need to understand it properly. Not as a concept, but as something we can define, structure, and govern.
Because in this new model, the quality of execution is limited by the quality of intent. And that is a very different problem to solve.
This is the first article in the Human Intent series. In the articles that follow, we will explore how organisations must change to operate in this new model, from structure and governance to culture, skills, and the evolving relationship between humans and the systems that act on their behalf.
Frequently Asked Questions
Is Agile dead?
Capital-A Agile, the methodology, the certifications, the ceremonies, the bureaucratic apparatus that grew up around the original Manifesto, is dying. Lowercase-a agile, the underlying spirit of iteration, fast feedback, and responsiveness to change, has never been more alive. The distinction matters because the practices were designed to coordinate human teams doing slow, expensive work. When agentic AI systems can execute in minutes rather than weeks, those coordination mechanisms lose their purpose. But the values that drove Agile in the first place become more important than ever, because they describe how complex systems are built under uncertainty.
What is the difference between capital-A Agile and lowercase-a agile?
Capital-A Agile refers to the methodology, Scrum, SAFe, sprints, standups, story points, backlog grooming, the certification industry, and the entire framework that grew up around the Agile Manifesto. Lowercase-a agile refers to the spirit behind it, being responsive, iterative, and adaptive in the face of uncertainty. The distinction is critical because the methodology and the spirit have very different fates in the AI era. The methodology was built for a world where human teams coordinated slow human execution. The spirit is timeless and applies to any system being built under uncertainty.
What is intent shaping?
Intent shaping is the continuous process of refining human intent in near real-time as AI systems execute against it. Instead of iterating on implementation across two-week sprints, you iterate on intent itself: define what you want, let a system execute, measure the result, refine the intent, and repeat. The loop is the same as Agile’s original cycle of define, build, learn, adjust, but it operates in minutes rather than weeks. Intent shaping is the discipline that replaces sprint planning when execution is delegated to machines. It is core to Intent-Driven Development and to the broader Human Intent shift across organisations.
How does agentic AI change the Agile Manifesto?
The four values of the Agile Manifesto survive the shift to agentic AI, but their practical expression transforms. Individuals and interactions still matter, but the interaction is now between humans defining intent and systems executing against it. Working software still matters, but the specification, the intent, becomes the primary artefact. Responding to change still matters, but the response can be near real-time rather than confined to sprint cycles. Customer collaboration still matters, but the conversation moves upstream from “what should we build” to “what does success look like.” The values live. The practices transform. And the direction of transformation is always the same: upstream, toward intent.
What replaces sprints, standups, and story points in the AI era?
The coordination mechanisms designed for human teams lose their purpose when AI systems handle execution. Sprints exist because human teams need time-boxed cycles; when execution takes minutes, sprints are unnecessary. Standups exist because human coordination needs synchronisation; when there is no human team building the code, there is nothing to synchronise. Story points exist because human effort is variable; when machines execute, effort is not variable in the same way. What replaces them is intent shaping, a continuous loop of defining, executing, measuring, and refining intent in near real-time. The discipline shifts from coordinating execution to governing intent.
Why is natural language so important to this shift?
For most of computing history, the gap between human intent and machine action was a translation problem. Humans had to learn the machine’s language, assembly, then C, then higher-level languages, then frameworks. Every layer of abstraction reduced the gap, but it never closed it. Natural language has collapsed that gap. We can now type or speak our requirements in our native language and have systems act on them directly. This changes the meaning of iteration itself. Agile’s short cycles were partly a response to genuine uncertainty about what users needed, but they were also a response to the fact that you could not specify what you wanted accurately enough upfront. When natural language closes that gap directly, the iteration moves upstream, from refining the implementation to refining the intent itself.
Intent-Driven Development – Humans have Roles, Agents have Functions
For decades, organisations were structured around the work humans had to do manually. But if agents can write code, run tests, deploy systems, and operate platforms, then organisations may no longer be structured around execution at all. Humans define intent. Agents enact it.
Human Intent – Agile is Dead, Long Live agile
For two decades, Agile was the right answer. Sprints, standups, story points – all of it built to coordinate slow human execution. But agentic AI is changing the constraint. The methodology that grew up around the Manifesto is dying. The spirit that drove it has never been more alive. The second article in the Human Intent series explores what survives, what transforms, and why agility finally has space to thrive.
0 Comments