Every project starts with a deceptively simple question: what actually makes something a project? Understanding the answer separates work that needs formal management from work that doesn't — and that distinction is where your career as a PM begins.
Projects vs ongoing operations
A project is a temporary endeavour undertaken to create a unique product, service, or result. Those two words — temporary and unique — are what set projects apart from the operational work that keeps a business running day to day.
Operations are repetitive. A call centre handles tickets using the same process every day. A payroll team runs the same cycle every fortnight. There's no defined end date and no unique outcome — just consistent delivery of a known result.
A project, by contrast, has a clear start, a clear finish, and a specific outcome that hasn't existed before. Building a new customer portal is a project. Running the portal once it's live is an operation. Rolling out a new invoicing system is a project. Processing invoices every month is an operation.
The practical test: ask yourself whether the work has a finish line and a unique output. If both answers are yes, you're looking at a project — and it benefits from structured management.
The triple constraint
Every project lives inside three competing forces: scope (what you're building), time (when it must be done), and cost (what resources you have). This is known as the triple constraint, and it's the first mental model every PM internalises.
The key insight is that the three constraints are connected. If a stakeholder asks you to add more scope, something has to give — either the deadline moves, the budget increases, or you reduce scope elsewhere. Nothing is free.
In practice, one constraint is usually fixed. A regulatory deadline is immovable, so scope and cost must flex around it. A fixed budget means scope must be managed tightly as time pressure builds. Knowing which constraint is locked in any given project tells you immediately where to focus your attention.
A common beginner mistake is agreeing to hold all three constant simultaneously. Your job as a PM is to make the trade-offs explicit — surface them early, present the options, and let the right decision-maker choose.
Why 'temporary' matters more than you think
The temporary nature of a project has practical consequences that most beginners overlook. Because projects end, the team assembled for them is also temporary. People come from different departments, bring different priorities, and will return to their home teams when the project closes.
This means the social contract of a project team is different from a permanent team. You can't rely on long-established trust and shared history. You need to build alignment quickly, establish clear roles early, and create a working rhythm that doesn't depend on people already knowing each other.
It also means urgency is built-in. An operational team can defer a problem until next month. A project team with a fixed end date cannot. Every week that passes without progress is a week that can't be recovered. Good PMs feel this time pressure and use it to keep energy and focus high.
Summary & next steps
A project is temporary and unique — those two characteristics define it and explain why it needs deliberate management. The triple constraint of scope, time, and cost is the fundamental tension every PM navigates, and one constraint is almost always fixed.
In the next lesson you'll walk through the full PM lifecycle — the five phases that take a project from authorisation to close — and see how each phase builds on the last.