What Is Project Management and How Do You Actually Run a Project?
Project management is the discipline of planning, executing, and closing a temporary effort that produces a specific outcome—distinct from ongoing operations, which repeat indefinitely. You "run" a project by moving it through five phases (initiation, planning, execution, monitoring, closure), maintaining four core artifacts (scope, schedule, budget, risk register), and choosing a methodology (waterfall, agile, or hybrid) that matches how much uncertainty you face. This guide explains each piece and where projects typically break.
Project vs. operations: the line that matters
A project has a defined start and end, a unique deliverable, and a temporary team. Operations are continuous and repeatable—processing payroll, running a support desk, maintaining a production line.
The distinction changes how you manage:
| Dimension | Project | Operations |
|---|---|---|
| Duration | Temporary, ends at delivery | Ongoing |
| Output | Unique deliverable | Consistent, repeatable service |
| Success measure | Delivered on scope, time, budget | Stable throughput and quality |
| Team | Assembled, then disbanded | Stable, role-based |
| Change | Expected and managed | Minimized |
If the work never "finishes," you are managing operations and should use process-improvement methods instead of project controls.
The five phases, and what each produces
Initiation
Define why the project exists and who owns it. Outputs: a project charter (problem, goal, sponsor, high-level constraints) and a stakeholder list. Without a named sponsor with authority to remove blockers, projects stall at the first conflict.
Planning
Turn the goal into a workable plan. Outputs: scope statement, work breakdown structure (WBS), schedule, budget, resource plan, and risk register. Planning is where scope creep is prevented—or invited—by how precisely you define what is out of scope.
Execution
The team does the work. Your job shifts to coordination: assigning tasks, unblocking people, and keeping communication flowing. Most of the project manager's time is spent here.
Monitoring and controlling
Runs alongside execution. You compare actual progress against the plan and correct course. Outputs: status reports, change requests, updated risk register. This is not a separate phase in time—it is a parallel activity.
Closure
Deliver, get formal acceptance, release the team, and capture lessons learned. Skipping closure means the next project repeats the same mistakes.
The four artifacts that hold a project together
- Scope — what is included and explicitly excluded. The WBS decomposes scope into deliverable-sized chunks.
- Schedule — tasks, dependencies, durations, and milestones. Critical-path tasks have zero slack; delay them and the whole project slips.
- Budget — estimated cost by category, with contingency for known risks.
- Risk register — each risk with likelihood, impact, owner, and a response (avoid, mitigate, transfer, accept).
A change to any one of these usually affects the others. That relationship is the "triple constraint": scope, time, and cost trade off against each other, with quality as the outcome.
Waterfall, agile, or hybrid: pick by uncertainty
| Methodology | Best when | Weakness |
|---|---|---|
| Waterfall | Requirements are stable and known; regulatory or contractual gates | Poor at absorbing change late |
| Agile | Requirements will evolve; frequent feedback is available | Harder to forecast fixed cost/date |
| Hybrid | Some phases are fixed (compliance), others exploratory | Requires discipline to avoid the worst of both |
Choose waterfall when change is expensive and requirements are clear. Choose agile when you can deliver in increments and learn as you go. Choose hybrid when a fixed milestone (e.g., a compliance review) must coexist with iterative build work.
Documenting current state and keeping people aligned
Before you can plan change, you need a shared picture of how things work today. Teams often map the current state—processes, systems, dependencies—so that everyone, including new contributors, works from the same reference. Lucid positions its capabilities around documenting the current state of a business and keeping people and AI agents aligned as work moves forward, which fits the "shared reference" problem that derails projects when it is missing.
Practically, alignment requires:
- One source of truth for status, not five.
- A visible owner for every open risk and decision.
- A cadence (daily standup, weekly review) that matches the project's pace.
Where projects actually fail
- No sponsor authority — decisions stall; escalate early or the project drifts.
- Vague scope — "improve the portal" becomes infinite. Write exclusions.
- Optimistic estimates — no contingency, no buffer on critical-path tasks.
- Silent risks — a register nobody updates is decoration.
- No closure — lessons lost, team not released, benefits never measured.
Troubleshoot by returning to the artifact that is weakest: if dates keep slipping, re-examine dependencies and estimates; if scope keeps growing, reassert the change-control process; if the team is confused, the problem is usually communication cadence, not effort.
Getting started
Pick your methodology based on uncertainty, write a one-page charter, build a WBS before a schedule, and keep a live risk register. If you need a shared place to document current state and keep contributors aligned, Lucid offers a free sign-up and published pricing for its charting plans—check the current terms on its pricing page before committing a team.