There are eight core roles in project management – from the project lead and the team to the sponsor, stakeholders and quality assurance. Who holds which role should be settled before kick-off, not after. Because the most annoying "I thought you were doing that?" isn't a people problem, it's an organisation problem. And some of these roles are changing right now because of AI.
You know how it goes.
A project kicks off, everyone's motivated, and two weeks later half the team is asking: "Who was actually in charge of that?" Clear roles aren't bureaucratic box-ticking. They're the difference between a team that gets into the work and one that wears itself out arguing over who owns what.
The good news: frustration on projects rarely comes from the wrong people. It comes from unclear processes – opaque workflows, duplicated work, nobody holding the reins. And that's exactly what you can fix.
What is a role in project management?
A role is a functional job within a specific project – for example "project lead" or "quality assurance". A position is your fixed job title in your contract, like "senior designer".
The difference matters in practice: you can be a team member on project A and take the project lead on project B. It's not the title on the business card that counts, but who wears which hat on this project.
Why clear roles make your team more relaxed
In many agencies the lines are blurry: sometimes management runs the project, sometimes senior designers take the lead. That's completely fine – as long as the expectations are clear. Well-defined roles give you:
- Less duplicated work: nobody builds something a colleague finished long ago.
- Faster decisions: it's clear who has the final say on budget or design.
- Fewer conflicts: "I thought you were doing that" becomes a thing of the past.
To keep this alive day to day, you need a tool that makes responsibilities visible. In awork you set a project lead for each project – one click on a task shows who's holding the ball right now. Transparency without a status meeting.
The 8 most important roles in project management
Depending on project size and method (classic waterfall or agile with Scrum), the labels vary. For agency teams, these eight functions have proven especially relevant.
Role: Project lead (PM)
Responsible for: steering the project
In the agency often: the interface between creative and client
Focus: planning, budget, timing, reporting
Role: Project team
Responsible for: hands-on delivery
In the agency often: designers, developers, copywriters
Focus: delivering work packages
Role: Sponsor (client)
Responsible for: strategic sign-off
In the agency often: the client or internal C-level
Focus: direction & funding
Role: Stakeholder
Responsible for: an interest in the outcome
In the agency often: end users, departments, freelancers
Focus: getting them involved early
Role: Product owner
Responsible for: the "what"
In the agency often: the client or a strategist
Focus: backlog & prioritisation
Role: Scrum master
Responsible for: the agile process
In the agency often: experienced PMs or coaches
Focus: clearing obstacles
Role: Resource management
Responsible for: utilisation across the whole agency
In the agency often: team leads or PMs
Focus: capacity & billability
Role: Quality assurance (QA)
Responsible for: the result
In the agency often: art director, senior copy, testers
Focus: standards & branding
1. Project lead / project manager (PM)
The PM is the role in charge. Being responsible here doesn't mean doing everything yourself – it means steering: planning resources, keeping an eye on budgets, maintaining the schedule, communicating with everyone involved. In agencies, the PM is the central interface between creative and client.
2. Project team (the people who deliver)
The heart of every project. This is where the specialists sit – in the creative industry that's designers, developers, copywriters or strategists. They turn the defined work packages into actual output. Important for planning: this is where it's decided whether capacity is distributed realistically, or whether a few people end up permanently overbooked.
3. Sponsor (client)
Often underrated, always decisive. The sponsor initiates the project, funds it and signs it off at a strategic level. In agencies that's usually the client themselves or an internal partner at C-level. When push comes to shove, the sponsor makes the big directional calls.
4. Stakeholder
A stakeholder is anyone with an interest in how the project turns out: end users, other departments, freelancers, suppliers or even the public. Good project management involves the key stakeholders early – that's what prevents nasty surprises just before go-live.
5. Product owner (PO)
Indispensable in digital projects and software development. The product owner represents the interests of the users and decides on the "what": they prioritise the backlog and sign off the team's results. In agencies this role is often taken on by the client or a dedicated strategist.
6. Scrum master
Working agile? Then you need a scrum master. This isn't a boss but a servant leader: they make sure the team can work undisturbed, clear obstacles (impediments) out of the way and keep an eye on the agile process.
7. Resource management
In larger agencies, this is the key role for utilisation. While the PM looks after a single project, resource management keeps an overview of all the agency's resources. It decides who has time for which project and when – and stops teams from snatching capacity from one another. This role is tied directly to profitability and billability: staff costs are fixed, so what matters is how much capacity lands on billable projects.
8. Quality assurance (art director / QA)
Is the result actually good enough? In software development that's down to testers, in creative agencies often art directors or senior copywriters. They're the quality gate: they make sure standards and branding are right before anything goes out to the client.
Distributing roles in agencies: who does what?
Rigid job titles are often a hindrance in agencies. Roles here are assigned dynamically:
- Account managers often take on the sponsor role (as the client's advocate) or act as strategic advisors, while PMs handle the operational delivery.
- Creative directors frequently act as quality assurance and subject-matter leads.
- Team leads or PMs handle the broad resource planning, while the project lead does the fine-grained planning.
What matters isn't what's in the email signature, but that for every project it's clear who's wearing which hats.
AI in project management: which roles will it take over?
The most interesting shift of the next few years isn't about who sits on the team, but what the roles do. AI is increasingly taking over the operational grind – the work that classically costs the PM and capacity planning hours. What remains is leadership.
In concrete terms, AI already takes over or supports these role tasks today:
- Resource & capacity management: AI suggests who can take on a project – based on real availability, skills and calendars, not gut feeling. If someone drops out at short notice, it checks open tasks and proposes a redistribution. "Marc's off sick, the deadline stands" turns into a few minutes of AI workflow instead of a crisis meeting.
- PM reporting & status: AI fills status reports, project documentation and custom report templates based on the project history – instead of building slides by hand.
- Planning & scheduling: from a briefing or an email, a structured project plan emerges with phases, tasks and realistic time budgets – derived from comparable past projects.
- Risk flags: AI flags bottlenecks, overbookings and slipping deadlines early, rather than letting them surface only at go-live.
What stays human?
Strategy, leadership, team management and creative judgement. A sponsor decides on the direction, an art director on quality, a PM on the relationship with the client. AI suggests, the human decides. Project management therefore shifts away from operational admin towards leadership, supported by powerful assistance systems.
Pros and risks of AI in project management
Pros
- Operational grind (reporting, scheduling, estimates) falls away → more time for creative work
- Planning based on real data instead of gut feeling (utilisation, skills, calendars)
- Reacting in minutes instead of hours (emergency staffing, replanning)
- Knowledge from past projects becomes usable (realistic budgets)
Limits & risks
- AI without context is just guessing. Generic tools like a standard chatbot don't know your project data
- No substitute for leadership, client relationships and creative judgement
- Data protection has to be solid: briefings and client data are sensitive
- Responsibility stays with the human – AI doesn't make the final call
Why context beats the model
The most common reason AI disappoints in agencies: it doesn't fail because of the model, but because of missing context. As long as project data, time tracking and availability sit in different tools, AI can't give you reliable recommendations.
That's exactly where the difference lies: other AI tools guess, awork AI knows – because it works natively with plans, times, skills, calendars and utilisation, not as a generic chatbot. On top of that comes responsibly built AI: no training on your client data, hosted on ISO 27001-certified servers in the EU, and switchable off by admins. For agencies in the DACH region, that's a decisive advantage over external tools where it's unclear where client data ends up.
FAQ: common questions about project roles
What's the difference between a role and a position?A position (e.g. "senior designer") is the fixed job title in your contract. A role (e.g. "sub-project lead") is a functional job within a specific project. You can be a team member on project A and the project lead on project B.
Does every role need its own person?No. On smaller projects one person often takes on several roles (e.g. the PM is also responsible for risk management). All that matters is that no role's tasks get forgotten. The exception is roles with a conflict of interest – developers shouldn't sign off their own code.
What roles are there in Scrum?Scrum has three clear roles: product owner (defines the "what"), scrum master (looks after the process) and development team (does the work). There's no classic project lead in the old sense here.
Which project management roles does AI take over?Mainly operational tasks: resource planning, scheduling, status reports, risk flags and creating project plans from briefings. Strategy, leadership and team management stay with the human.
Who's responsible when AI takes over tasks?Responsibility always stays with the human. AI delivers suggestions based on data – the decision and sign-off rest with the relevant role, such as the project lead or quality assurance.
Conclusion: clarity creates freedom
Whether you go strictly by the book or for a relaxed mix of methods: settle the roles before the starting gun fires. That gives your team the confidence to focus on the actual work, instead of debating who's responsible for what. And the more operational tasks AI takes over, the more this clarity matters – because it decides who ends up leading.
Ready to organise your team better? Try awork and see how easy resource planning and task allocation can be.
[.b-button-primary]Test awork for free[.b-button-primary]
