The popular conception is somewhere between "person who maintains the spreadsheet" and "person who schedules the meetings." Both are wrong, and the misunderstanding is why so many projects fail with a project manager assigned to them.
Here's a working definition: project management is the discipline of converting a goal into a delivered outcome under constraints.
That's it. Goal in, outcome out. Time, budget, scope, and quality are the constraints. Everything project managers do — scoping, planning, scheduling, reporting, escalating, governing — is in service of that conversion.
What this means in practice is that a project manager's job is to remove the things that prevent delivery, not to create the artifacts that document delivery. The Gantt chart is not the work. The status report is not the work. The work is making sure that, by Friday, the thing that needed to happen has happened — and if it hasn't, you know why and what's being done about it.
A few things that often get confused with project management but aren't:
Scribing meetings is not project management. Note-taking is a useful skill. It's not the discipline. A PM who only documents what was said in the room and never drives what happens next is doing administrative work, not project work.
Maintaining the schedule is not project management. The schedule is a tool. It's a representation of when work is supposed to happen. Updating it to reflect reality is bookkeeping. Project management is what you do because the schedule says something is slipping — not the act of marking the slip.
Status reports are not project management. A status report is the output of the management work, not the work itself. If your PM's job ends when the report is sent, your PM is a reporter.
Being the most senior person in the room is not project management. Project authority comes from the role, not the seniority. A junior PM with clear charter and a sponsor who backs her can run a better project than a director who's running it by tenure.
So what is it?
Project management is making sure the right people are making the right decisions at the right time, with the right information. It's identifying risk early enough to do something about it. It's holding scope when scope creep would be easier. It's getting a clear "yes" or "no" out of a sponsor who wants to give you a "let's revisit." It's protecting the team's focus from the politics that surround the project. It's running the boring meeting where the integration architecture gets resolved so the build team isn't waiting on an answer for three weeks.
It's unglamorous, durable, and almost entirely about people. The technical artifacts — plans, charts, reports — are the residue of the real work, not the work itself.
The teams that hire project managers expecting "someone to keep us organized" usually end up with administrative support and no real delivery muscle. The teams that hire project managers expecting "someone to make the project actually ship" usually end up with both.
The difference is in the brief. Hire for delivery, get delivery. Hire for documentation, get documentation.
If you're trying to figure out whether you need a project manager or a project coordinator, the answer is in the outcomes you need. Book a scoping call.
