Projects involve people, and every person has a role. Understanding who does what — and who has authority over what — prevents the confusion that derails teams. Four roles appear on almost every project, regardless of size or methodology.
The project sponsor
The sponsor is the senior leader who owns the business case for the project. They provide funding, remove organisational blockers, and are accountable to the business for the project's outcomes. Crucially, the sponsor is the person who can say yes to scope changes, additional budget, or early termination.
A strong sponsor is engaged but not in the weeds. They attend steering committee meetings, read status reports, and make decisions when escalated issues land on their desk. A weak or absent sponsor is one of the most reliable predictors of project failure — without executive air cover, a PM has limited ability to resolve cross-departmental conflict or protect the project from competing priorities.
Your job as PM is to keep the sponsor informed without overwhelming them. One-page status reports, a clear escalation path, and a brief standing meeting are usually enough. Don't make them dig for information, and don't surprise them.
The project manager
The project manager is responsible for planning and delivering the project. They don't do all the work themselves — they coordinate the people and resources that do. The PM owns the schedule, manages risk, communicates with stakeholders, and is accountable for day-to-day delivery.
A common misconception is that the PM's job is to tell people what to do. In practice, most PMs have no direct authority over the team members assigned to their project. Those people report to their functional managers — the PM earns their cooperation through credibility, clarity, and good communication.
The skills that matter most aren't technical. They're organisational: knowing what questions to ask, spotting when something is behind before it becomes a crisis, and creating the conditions for the team to do their best work.
The project team and stakeholders
The project team is the group that does the work. They may be employees, contractors, or vendor resources, and they're often borrowed from functional departments rather than dedicated to the project full-time. Managing a team that doesn't fully report to you is one of the defining challenges of project management.
Stakeholders are anyone with an interest in the project — they can affect it or be affected by it. They include end users, department heads, regulators, customers, and sometimes the general public. Not all stakeholders are supportive, and not all of them are visible at the start.
A key early task is stakeholder identification — actively seeking out everyone who has a stake, not just the obvious ones. An overlooked stakeholder who surfaces late can derail a project that was otherwise on track. You'll go deep on this in the Working with Stakeholders course.
Summary & next steps
Four roles form the core of almost every project: the sponsor (owns the outcome and the budget), the project manager (owns the plan and the day-to-day delivery), the team (does the work), and stakeholders (are affected by or can affect the project). Knowing who sits in each role, and managing each relationship appropriately, is foundational PM practice.
Next you'll put this into practice by looking at the project charter — the document that formally authorises a project and captures everything the sponsor and PM need to align on before work begins.