0.1 · What is a project?

Level 0 · Project management fundamentals

0.1What is a project?

Goal: tell a project apart from ongoing operations, and place the role of the project manager.
Estimated time: 10 min · self-paced reading · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Project = temporary + unique: a start, an end, and a unique deliverable — not a repetitive activity.
  • Operation = repetitive + endless: invoicing, answering support; you don't manage it like a project.
  • Project manager = orchestrator: coordinating resources and constraints, often without hierarchical authority.

Running mini-case — Bilal separates project from routine

Bilal, project manager in a digital service SME of 15 people in Algiers, is swamped with requests: redesign of a client's showcase site, daily support tickets, migration to a new host. Listing everything, he isolates two real projects (site, migration) from recurring support. For each, he writes the unique deliverable and names who orchestrates without commanding.

This same case runs through the course, the diagram, the script and the 48h challenge — and continues in 0.2, 0.3 and 0.4.

1. A temporary, unique effort

A project is not just any activity: it is a temporary effort (start and end) aimed at creating a unique deliverable. Building a website, organizing an event, deploying software are projects.

In contrast, ongoing operations (invoicing, answering support) are repetitive with no defined end.

2. The project manager's job

This distinction founds the project manager's job: bringing this unique effort to success by coordinating resources, within time, cost and quality constraints.

It is a role of orchestration and responsibility — often without direct hierarchical authority over the team, which is exactly what makes it challenging and rewarding.

Common misinterpretation: "All important work is a project, and leading one requires being the best technician." No. A project is recognized by its temporary nature and its unique deliverable, not by its importance. And the project manager is first an orchestrator (planning, coordinating, steering, communicating): they can lead a topic they are not the technical expert in.
Project vs ongoing operation Two natures of work ProjectTemporary, unique deliverable+Ongoing operationRepetitive, endless+Project managerOrchestrates resources and constraints The project manager often acts without hierarchical authority.
Two natures of work
Text version of the diagram (SEO / screen readers / translation): 1) Project: Bilal isolates the client site redesign — start, end, one live site as unique deliverable. 2) Ongoing operation: daily support continues in parallel, repetitive and endless. 3) Project manager: Bilal orchestrates developers and designer without being their hierarchical boss. Lesson: a project is stated through its unique deliverable, and managed differently from an operation.

🔎 Concrete example — 🔎 Concrete example — Project or operation?

The simple test.

Launching a new e-commerce site → PROJECT (start/end, unique deliverable).
Processing orders every day → ONGOING OPERATION (repetitive, endless).
→ the same team can do both; the management differs.

Outcome: knowing what falls under project management.

Reflex: a project is stated through its unique deliverable.

Section vocabulary

Project
Temporary endeavor (start/end) undertaken to create a unique product, service or result.

Simple example: Bilal launches the migration to the new host: start, end, validated switchover.

What it is not: answering support tickets every day (an ongoing operation).

Reflex: state every project through its unique deliverable in one sentence.

Ongoing activity (operation)
Repetitive, continuous work with no defined end (production, support). The opposite of a project.

Simple example: Bilal's SME daily support: tickets, replies, follow-up.

What it is not: the showcase site redesign delivered then put online (that's a project).

Reflex: ask "is there an end and a unique deliverable?" — if not, it's an operation.

Project manager
Responsible for meeting the project's objectives: plans, coordinates, steers and communicates.

Simple example: Bilal assigns tasks between developers and designer and tracks progress.

What it is not: the expert who codes alone without coordinating anyone.

Reflex: orchestrate: who does what, by when, with which trade-off.

Deliverable
Tangible, verifiable outcome produced by the project (a report, software, a building).

Simple example: The redesigned showcase site, tested and put online for Bilal's client.

What it is not: a meeting or an effort with no verifiable outcome.

Reflex: every project must boil down to "what delivered, when".

Stakeholder
Any person or entity concerned by the project (client, team, management, users).

Simple example: The client, the SME owner and the developers around Bilal.

What it is not: a person with no link to nor interest in the project.

Reflex: list stakeholders from the start and what they expect.

In practice — In practice — Telling projects and operations apart

  1. List 5 activities of your organization, then classify each: project (temporary, unique) or ongoing operation (repetitive)?
  2. Pick one project and state its unique deliverable in one sentence ("an e-commerce site delivered and online").
  3. Identify who its project manager is and whom they rely on (do they have hierarchical authority over them?).
  4. Note this project's 3 main stakeholders and what they expect from it.
You clearly tell projects and operations apart, and place the project manager's role: the foundation for the whole project management approach.

Ready-to-say script — stating that this is a project (30s)

"This is a project: one unique deliverable, a start and an end. Our deliverable is the live, validated site. Support continues alongside, but it is not part of the project. I orchestrate it: I assign, I track, I arbitrate."

Say at kickoff: naming the unique deliverable separates the project from routine.

Copy-paste template — project or operation sheet

ACTIVITY: _______________
TYPE (project / operation): _______________
UNIQUE DELIVERABLE (if project, in 1 sentence): _______________
START: _______________ / TARGET END: _______________
PROJECT MANAGER: _______________
3 STAKEHOLDERS: _______________

Small business / tight budget

Bilal does everything himself: noting "project or operation" on one line per activity is enough to stop mixing support and redesign.

Algerian SME

Bilal separates the host migration (a project, with a cutover planned one evening) from daily support, to protect both.

Nonprofit / event

Organizing the annual fair = project (date, deliverable); running the club every week = operation.

Freelancer

Each dated, delivered client order = project; ongoing prospecting and invoicing = operations.

✓ Best practices

  • State every project through its unique deliverable and dates.
  • Spot early that the project manager orchestrates without necessarily commanding.
  • Identify stakeholders from the start.

✗ Common pitfalls

  • Managing a project like an ongoing operation (or vice versa).
  • Believing you must be the technical expert to lead the project.
  • Confusing project management with product management.

Key takeaways

  • A project is temporary (start/end) and produces a unique deliverable.
  • Ongoing operations, in contrast, are repetitive with no defined end.
  • The project manager orchestrates resources, schedule, costs and quality.
  • They often act without hierarchical authority: hence the importance of leadership.

48h Challenge — apply tomorrow

List 5 activities of your organization, classify them as project or operation, and state 1 unique deliverable in one sentence (template above). 20 minutes is enough.

Section exit checklist
  • I can say in one sentence what makes a project (temporary + unique deliverable).
  • I've classified 5 real activities as project or operation.
  • I've stated 1 unique deliverable and named its project manager.
Self-rating 1-5: do I tell project and operation apart without hesitating?do I state a project through its unique deliverable?

Frequently asked questions

Do you need to be a domain expert to be a project manager?

Not necessarily: the project manager is first and foremost an orchestrator (planning, coordination, communication, steering). Domain knowledge helps dialogue with experts and judge feasibility, but their key skills are methodological and human. Many project managers steer topics they are not technical experts in. What matters is asking the right questions, structuring the work, leading a team and arbitrating — not knowing how to do everything yourself.

Are project management and product management the same?

No: the project is temporary and targets a defined deliverable, with an end. The product lives on and evolves continuously (the product manager steers its value and roadmap). The two often intersect — a project may deliver a version of a product — but horizons and responsibilities differ. The project manager answers for meeting objectives within a bounded time; the product manager, for the value created by a product over the long term.

Check your understanding

What characterizes a project?

Additional resources (optional, to go further)

Level 0 examFresh, harder questions to test what you've learned