What a project is

People call almost any work "a project," which is why so much project management is confused from the start. A project is a specific kind of work, and managing it well begins with recognising what makes it different from the ordinary running of things — because the two need completely different handling.

The definition

A project is a temporary effort to create a specific, unique result — with a defined beginning and end.

Every word does work:

• Temporary — it ends. A project has a finish line, unlike ongoing operations that just continue.
• Specific, unique result — it produces something particular that didn't exist before: an event, a product, a building, a launch. Not the same output repeated.
• Beginning and end — it's bounded in time, which is why it needs planning, scheduling, and a defined "done."

Projects vs operations — and why the distinction matters

The crucial contrast is with operations — the ongoing, repetitive work that keeps a business running. Making the same product day after day, serving customers, doing the monthly accounts: that's operations, not projects. It's continuous, repetitive, and it doesn't "finish."

They need opposite management:

• Operations are managed for efficiency and consistency — do the same thing well, repeatedly, smoothly. You optimise a steady process.
• Projects are managed for delivery of a unique result within constraints — plan, coordinate, and steer a one-time effort to a defined end, on time and on budget.

Treating a project like operations (no plan, no end, just "keep working") means it drifts forever with no finish. Treating operations like a project (constant re-planning of routine work) means needless overhead. Knowing which one you have tells you how to manage it. Most management confusion comes from applying the wrong mode.

Why "project thinking" helps

When you recognise something as a project, project thinking kicks in and serves you well: define the specific result, set a clear beginning and end, plan the path, manage the constraints, and drive to completion. This is exactly what one-time efforts need and rarely get. A wedding, a product launch, a house build, a software release, a move — all projects, all better for being managed as projects rather than as vague ongoing effort that somehow never quite finishes.

The worked example

A treats a one-time effort — launching a new service — as ongoing work. No defined end, no plan, no clear "done." So it drifts: work continues indefinitely, scope creeps because nothing bounds it, and months later it's still "in progress" with no finish in sight. He managed a project as operations, and operations don't finish — so neither did his project.

B recognises the launch as a project: a specific result (the service live and available), a defined start and end, a plan, managed constraints. So it has a shape and a finish line she can drive toward. It completes, on a timeline, because she managed it as the bounded, unique effort it was. Same work; project thinking gave it an end.

The mistake

Not distinguishing projects from operations, and so managing one-time efforts as if they were ongoing work (which drifts endlessly) or ongoing work as if it were a project (needless overhead). Recognise a project by its signature — temporary, unique result, defined beginning and end — and manage it as a project: plan it, bound it, and drive it to a defined done. The whole discipline of project management exists for this specific kind of work; step one is knowing when you have it.

---

Your turn

1. List your current work. Label each item PROJECT (temporary, unique result, has an end) or OPERATIONS (ongoing, repetitive).
2. Find something you're treating as ongoing that's actually a project. Give it a defined result and an end date.
3. For that project, write its 'done' — the specific result that means it's finished. Drift comes from having no 'done'.

Key points

• A project is a temporary effort creating a specific, unique result — with a start and an end.
• Operations are ongoing and repetitive; projects are bounded and one-time.
• They need opposite management: efficiency/consistency vs delivery-within-constraints.
• Managing a project like operations makes it drift forever with no finish.