When AI Delivery Refuses to Behave Like a Normal Project

1. Insight

AI initiatives are increasingly being delivered through established project management structures.

However, many project managers are finding that AI projects do not behave in the same way as traditional digital or business change projects.

A typical AI development is not waterfall and not even agile in the way many project managers are used to. It is often more fluid, experimental and iterative, with requirements, solutions and delivery paths becoming clearer as work progresses.

Requirements may not be fully defined at the outset. Solutions may not be fully understood before delivery begins. Understanding often develops as work progresses.

At the same time, project managers are still expected to:

• define scope

• build delivery plans

• manage timelines and resources

• provide confidence to stakeholders

This creates a tension.

In practice, the problem is that AI delivery often refuses to behave like a normal project. The work may still need structure, plans and assurance, but the conditions are more fluid than many project managers are used to, with understanding emerging progressively rather than being fixed upfront.

Experienced project managers are being asked to deliver outcomes in situations where both requirements and solutions remain fluid.

This is not a failure of project management discipline.

It is a natural response to working in a delivery environment where certainty emerges progressively rather than being established upfront.

That is why AI projects can feel so different in practice. The challenge is not lack of discipline, but the need to apply discipline in a delivery environment that does not behave in a familiar way.

2. Why This Matters

AI delivery often operates under conditions that are less stable than traditional project environments.

This means AI projects can resist the normal assumptions of project delivery. Scope may be harder to stabilise early, feasibility may need to be proven during delivery and the route to a workable solution may only become clear through iteration.

Project managers may find that:

• requirements evolve as understanding improves

• feasibility needs to be proven during delivery

• solutions are shaped through iteration rather than defined upfront

• stakeholder expectations change as the opportunity becomes clearer

Without recognising this, there is a risk of:

• attempting to lock down scope too early

• interpreting iteration as loss of control

• applying delivery approaches that do not match the nature of the work

• underestimating the differences between types of AI implementation

In this context, maintaining delivery confidence becomes more challenging — even for experienced project managers.

This can make AI projects feel less predictable, even when they are being managed well.

3. What This Means in Practice

AI project delivery requires a shift in how control is established and maintained because the work does not always behave like a normal project.

The challenge is not to abandon project management discipline.

It is to apply it in a way that accommodates:

• evolving understanding of requirements

• emerging solution design

• iterative delivery approaches

• varying delivery modes with different risk profiles

In practice, this often means the project cannot be managed as a simple sequence of defined tasks moving toward a stable end-state. Instead, the project manager may need to manage evolving scope, emerging learning and shifting stakeholder understanding at the same time.

Without this adjustment, projects can become:

• difficult to plan and re-plan

• subject to ongoing scope tension

• misaligned with stakeholder expectations

• hard to baseline and control in the way stakeholders may expect

• technically delivered but not successfully adopted or used

In practice, this can create a delivery environment where multiple dimensions are evolving at once. Scope may still be forming, solution options may still be emerging, and stakeholder expectations may still be adjusting as understanding develops. The role of the project manager becomes less about executing a fixed plan and more about maintaining alignment, clarity and momentum as that understanding evolves.

4. How AI Project Management Maintains Delivery Confidence

There are four practical steps that project managers can take to maintain delivery confidence and control.

4.1 Build Orientation in AI Capabilities

Project managers do not need deep technical expertise.

However, they do need enough understanding to:

• recognise different types of AI capability

• understand how they are typically applied

• assess relative complexity and risk

This enables more effective:

• planning

• stakeholder engagement

• expectation management

Explore this further in the Insight here: The Orr Consulting AI Universe — The Current AI Landscape.

4.2 Recognise Different Modes of AI Delivery

AI projects are not delivered in a single, uniform way.

In practice, project managers will encounter different delivery modes, including:

• custom AI development (build)

• configuration of AI-enabled vendor solutions (configure)

• adoption of generative AI tools (use)

Each mode has:

• different levels of uncertainty

• different timescales

• different technical and delivery risks

Understanding these distinctions is critical to:

• selecting appropriate delivery approaches

• setting realistic expectations

• managing delivery effectively

  
  

Explore this further in the Insight here: AI Project Management — Adapting Project Delivery for AI.

4.3 Adapt to Iterative Delivery Cycles

AI delivery often involves iterative cycles of:

• Discover

• Design

• Deliver

These cycles:

• refine requirements

• test feasibility

• improve solutions progressively

This does not replace project management discipline.

It changes how planning and control are applied.

Project managers should expect:

• plans to evolve

• scope to be refined

• learning to be built into delivery

  
  

In AI delivery, iteration is not simply a response to change. It is often the primary way the team discovers what will actually work.

This also means that decision points, control mechanisms and delivery assurance may need to be applied differently from more traditional project work.

Explore this further in the Insight here:AI Project Management — Adapting Project Delivery for AI.

4.4 Prioritise the Human Side of Delivery

Even where AI solutions are technically successful, value depends on:

• stakeholder understanding

• trust in outputs

• effective adoption and use

Project managers should ensure that:

• changes are clearly communicated

• confidence in AI-supported decisions is built

• users are supported in adopting new ways of working

• changes to roles, decisions and ways of working are actively managed

Without this, projects may be delivered but fail to realise their intended benefits.

Explore this further in the Insight here: AI Benefits Realisation — Ensuring AI Delivery Translates into Measurable Value

5. Risks of Not Adapting to AI Delivery

If AI delivery is approached using only traditional project assumptions, common patterns can emerge:

• unstable plans as requirements continue to evolve

• tension between fixed scope and emerging understanding

• misalignment between delivery outputs and stakeholder expectations

• underestimation of differences between AI delivery types

• solutions delivered but not adopted, trusted or used effectively

These challenges are often not caused by poor project management.

They arise from applying familiar approaches in unfamiliar conditions.

In other words, the problem is not simply that AI projects are difficult. It is that they often refuse to behave in the more predictable way that traditional project structures expect.

6. Benefits of Adapting to AI Delivery

When project managers adapt their approach to AI delivery, the impact is significant:

• more realistic and adaptable delivery plans

• better alignment between expectations and delivery

• improved management of uncertainty and iteration

• stronger stakeholder confidence

• increased likelihood of successful adoption and value realisation

Projects become more resilient, better understood and more likely to succeed in practice.

7. Final Thoughts

AI is becoming part of the project delivery landscape, but it does not always arrive in a form that behaves like normal project work. Requirements may move, solutions may emerge through iteration and delivery confidence may need to be maintained in conditions of greater fluidity than many project managers are used to.

Experienced project managers already have many of the skills required. The challenge is ensuring those skills are applied in a way that reflects how AI delivery actually behaves in practice.

The objective is not to replace project management discipline.

It is to apply it in a way that reflects how AI solutions are developed, tested and adopted.

By building orientation, recognising delivery modes, adapting to iterative cycles and prioritising the human side, project managers can maintain delivery confidence while working with fluid requirements and evolving solutions.

This Insight is part of the Orr Consulting AI Insights Library — structured thinking for AI transformation leaders and decision makers.

8. Call to Action

If AI delivery in your organisation is starting to feel harder to control than more traditional project work, the next step is not to force a conventional model onto it, but to strengthen the structure, planning and assurance around how AI projects actually behave.

If this Insight reflects your organisation’s experience, we would welcome a conversation.

Discuss your next AI steps

Subscribe to Orr Consulting to receive occasional emails with practical AI Insights and updates.

Subscribe to Orr Consulting