Project Manager. Delivery Manager. Product Manager.

Project Manager. Delivery Manager. Product Manager.

Three different job titles, three different disciplines and, in the right organisation, three very different jobs.

But anyone who has worked around transformation, technology or complex change will also know that the lines between them can become surprisingly blurred.

We see this fairly regularly at PM Talent Partners.

A candidate might have spent most of their career as a Project Manager but be doing work that looks increasingly like delivery management. A Delivery Manager may be working alongside a Product Manager and owning considerably more than simply the mechanics of getting work through a team. And occasionally someone with a traditional project background will look at a Product Manager vacancy and realise they already perform a significant proportion of the role.

That doesn’t mean the titles are interchangeable. They aren’t.

But the overlap is worth understanding - particularly in a market like the UAE, where organisations can be at very different stages of maturity and the same title can mean quite different things from one employer to another.

Start with the Project Manager

Of the three, Project Manager is probably the easiest to define in traditional terms. The Association for Project Management describes a project as something with a finite timespan which produces something new or changed. Its definition of the Project Manager is similarly straightforward: the individual responsible for the successful delivery of that project. (APM) That word finite matters.

A Project Manager is normally working towards a defined outcome. There is a beginning, an intended end and a body of work that needs to happen between the two. That usually means responsibility for some combination of planning, budget, resources, risks, issues, dependencies, governance, stakeholders and ultimately making sure the project gets where it needs to go.

APM’s own guidance describes core Project Management activities including building the plan, managing risks and changes, monitoring progress, managing budgets, communicating with stakeholders and eventually closing the project in a controlled way. Of course, very few real jobs fit perfectly inside a textbook definition. A technology Project Manager, a construction Project Manager and somebody delivering organisational change may all use very different tools day to day.

The common thread is ownership of a defined piece of change.

So what is a Delivery Manager?

This is where things become slightly less tidy. Delivery Manager can mean very different things depending on the organisation. In digital and technology environments, however, the role has become increasingly well defined. The UK Government Digital and Data Profession describes a Delivery Manager as being accountable for the delivery of products and services. At practitioner level, that includes building and maintaining effective teams, helping remove obstacles, focusing the team on what matters most and facilitating continuous improvement.

There is an important difference in emphasis here. The Project Manager traditionally manages the project. The Delivery Manager is often much closer to the team and the flow of delivery.

That might mean creating the environment in which engineers, designers, analysts and other specialists can deliver effectively. It can involve removing blockers, managing dependencies, improving ways of working, maintaining momentum and helping a multidisciplinary team navigate complexity.

You can immediately see why the two roles overlap... Both might manage risks. Both might manage dependencies. Both will spend considerable time with stakeholders. Both may plan, forecast, escalate problems and make sure people understand what needs to happen next.

The difference is often where their centre of gravity sits.

For a Project Manager, it is normally the successful delivery of the overall project against its objectives and constraints.

For a Delivery Manager, it is more commonly the effective delivery system around the team or service.

Even that distinction isn’t absolute.

A senior Delivery Manager working across multiple teams can look remarkably similar to a Programme or Senior Project Manager in another organisation.

The UK Government framework itself illustrates this. Its Programme Delivery Manager role includes managing complex products and services delivered across multiple teams, dependencies, planning, risk and broader programme activity.

At that point, job titles only tell you so much.

And then there is Product

Product Management is probably where the clearest distinction exists - even though there is still significant overlap.

The UK Government Digital and Data framework describes a Product Manager as someone who makes sure a product provides value and achieves the right outcomes by balancing user and business needs. That involves framing problems, setting priorities, working with multidisciplinary teams and making decisions about where the team should focus.

That shifts the central question again.

A Project Manager is often asking: How do we successfully deliver this change?

A Delivery Manager might be asking: How do we help this team deliver effectively?

The Product Manager is more likely to be asking: What should we build or improve, for whom, and why?

That distinction is important.

Product Management isn’t simply Project Management performed using Agile terminology. A Product Manager has much greater ownership of value, user need, prioritisation, product strategy and what gets built.

The role also tends not to finish when something is launched. Products can remain in development and continuous improvement for years. The Government framework explicitly describes Product Managers leading products through discovery, development, delivery, continuous improvement and eventually retirement.

That is quite different from the finite nature of a traditional project.

The overlap is still significant

Where this gets interesting is when you compare the capabilities rather than the job titles. The Government Digital and Data framework explicitly identifies Product Managers and Delivery Managers as sharing skills in Agile and Lean practices and lifecycle management. Programme Delivery Managers overlap with Product Managers in those areas too.

In practice, there are considerably more shared behaviours.

• All three roles need to communicate well.
• All three need to influence people who may not report to them.
• All three need to make decisions with incomplete information.
• All three need to understand priorities, risk, dependencies and stakeholders.
• And all three ultimately exist because an organisation is trying to make something happen.

That is why career movement between them is entirely possible.

But transferable skills and identical jobs are not the same thing. A good Project Manager isn’t automatically a good Product Manager because they have worked in an Agile team.

Equally, someone shouldn’t necessarily be discounted from a Delivery Manager role simply because their previous job title said Project Manager.

You have to look at what they actually did.

The title is only the starting point

This is particularly important in recruitment.

Two candidates can both have Project Manager at the top of their CV and have fundamentally different careers.

One might have managed suppliers, procurement, schedules and capital expenditure on a construction programme.

Another may have spent five years embedded in software teams, managing backlogs, dependencies, Agile ceremonies and digital releases.

• They share a job title.
• Their experience is not interchangeable.
• The reverse can also happen.

A Project Manager and Delivery Manager might have different titles but, once you get underneath them, discover that they have been doing remarkably similar work.

This is one of the reasons we spend so much time at PM Talent Partners trying to understand experience beyond the headline on a CV.

For employers, it means being clear about the problem you actually need somebody to solve before deciding what their job title should be.

For candidates, it means describing what you’ve actually delivered rather than relying on your title to explain it for you.

Where PM Talent Partners fits

Our core focus at PM Talent Partners remains Project, Programme and Delivery professionals. We don’t currently position ourselves as a specialist Product Management recruiter.

That distinction is deliberate.

Product is a profession in its own right, with its own disciplines, communities and depth of expertise.

But it would be equally artificial to pretend it sits completely separately from the people we work with.

Modern delivery increasingly brings Project, Programme, Delivery and Product professionals together - particularly around digital transformation and technology.

Understanding the boundaries matters.

Understanding the overlap matters just as much.

For us, the more useful question is rarely:

What is this person’s job title?

It is:

• What have they actually been responsible for?

That normally tells you far more.

If you are looking to change or expand your team and wish to talk with us in full confidence... you can. Email us at info@pmtalentpartners.com, we also have a contact form on our website https://pmtalentpartners.com