What Is Project Management? Roles, the Project Life Cycle, and Why Projects Need One
Where projects end and operations begin, what a project manager is accountable for, and the four phases every project moves through.
Beginner
TopNotchNote
Notes that matter
what makes something a "project"
A project is a temporary effort with a defined start and end that produces a specific outcome — a new warehouse layout, a rebuilt checkout flow, a relocated office. It is different from operations, the ongoing, repeating work that keeps a business running day to day (processing orders, staffing a help desk, running payroll).
The line matters because the two need different management styles. Operations is optimized for repeatability: the same steps, done well, forever. A project is optimized for change: a one-time push toward a goal that, once reached, ends the project.
A useful test: if the work has a finish line after which the team disbands or moves to the next thing, it is a project. If the work simply continues as long as the business exists, it is operations.
what a project manager actually does
The project manager (PM) is accountable for the plan, not necessarily for doing the technical work themselves. A PM organizes the schedule, tracks the budget, removes blockers, and keeps every stakeholder—sponsor, team, customer—aligned on the same goal.
Three overlapping skill areas show up in almost every PM job description:
| Skill area | Looks like |
|---|---|
| Technical project management | Building schedules, tracking budgets, managing risk logs, running a WBS |
| Leadership | Motivating a team with no direct authority over their performance review, resolving conflict, coaching |
| Strategic / business sense | Connecting the project's outcome to the company's actual goals, knowing when to say no to scope |
the project life cycle: four phases
Every project, regardless of industry or methodology, moves through the same four broad phases. Frameworks like Waterfall and Agile disagree about how rigidly to separate them — not about whether they exist. See PM Methodologies Compared for that contrast.
- Initiating — confirm the project is worth doing, get formal approval, write the charter.
- Planning — define scope, build the schedule and budget, identify risks, decide how the team will communicate.
- Executing — do the work, track progress, manage changes as they come up.
- Closing — confirm the deliverable meets the goal, hand it off, capture lessons learned.
a short example
A regional grocery chain decides to replace the handheld scanners its stockers use in 12 stores. Someone has to confirm the budget is approved (initiating), work out delivery dates and training schedules store by store (planning), coordinate the actual rollout while fielding complaints about a firmware bug (executing), and finally confirm every store is live and write up what went wrong with the firmware for next time (closing). None of that happens by accident — it happens because a project manager owns the plan end to end.
practical notes
Small projects still benefit from a lightweight version of these phases — skipping "planning" entirely is usually where missed deadlines start, even on a two-week effort.
A PM without formal authority over the team (common in matrix organizations, see Organizational Structures & the PMO) relies on influence, clear documentation, and stakeholder buy-in rather than the ability to assign performance ratings.