World 1 of Projects, level 1: where it all begins
A project has a goal, an end and a limited set of resources. What that changes in how you manage it — and why almost everything that changes something in a company is a project.
Part 1 of 5 of the series World 1 of Projects.

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).
World 1 of Projects series — level 1 of 5: World 1-1 · World 1-2 · World 1-3 · World 1-4 · World 1-5
Project management tends to be seen as an engineer’s thing: a schedule pinned to the wall, expensive software and someone chasing everybody for dates. People outside the field look at it from a distance and conclude it has nothing to do with them.
Even people outside the field can understand what project management is from one very simple idea: there are people who know how to do the work. And there are people who know how to organise the effort and the resources so that the work gets done. They’re two different things that, combined, raise (a lot) the odds of it working out.
A good project manager can plan a rocket launch or a birthday party. The technique is the same; only the size of the damage changes when it goes wrong.
What makes a piece of work a project?
PMI, the association that publishes the field’s reference guide, defines a project as “a temporary endeavor undertaken to create a unique product, service, or result” [1]. In everyday language, three things:
- It isn’t routine. It has a specific goal that doesn’t repeat itself the same way.
- It has a planned end. It starts, it finishes, and someone can say when it finished.
- It has limited resources. Money, people, machines and time, all counted.
In other words: almost everything is a project. Opening a branch, replacing the billing system, launching a product, moving offices, implementing a management system. Even that “initiative” nobody calls a project, but which has a deadline, a budget and someone who’ll be held to account at the end.
Project or operations: why is mixing them up so expensive?
Between 2005 and 2006, every maintenance shutdown at a Braskem petrochemical plant was mine. All of them, from the small ones to the monstrously large.
The plant, while it runs, is operations: every day the same, the same product, the same team, no end date. The shutdown is something else. The plant switches off, an army of people comes in, scaffolding, materials, support crews, and everything has to be ready within a window of counted days, because every hour of downtime is production that doesn’t come out. It’s a project slotted inside the operation.
One night, in the small hours, the plant had an emergency shutdown. A taxi came to pick me up at home. I had the planning backlog ready, and from one moment to the next we had to put plans into the field for execution. What saved that night was the planning that already existed before the emergency.
This is where you see why the distinction matters. Whoever manages a project as if it were operations loses sight of the end: the work becomes routine, the date slips, and nobody notices because “it’s moving”. Whoever manages operations as if they were a project burns out the team: everything becomes urgent, everything has a deadline, and nothing ever really finishes.
What are the rules of the game?
Every project plays with three forces at the same time:
- Scope: what will be delivered (and what won’t).
- Time: when.
- Resources: how much money, how many people, which machines.
Moving one pulls the others. More scope in the same time needs more resources. Fewer resources stretch the time or shrink the scope. Everything faster, cheaper and with more in it doesn’t exist (and whoever promises it is just selling).
Quality sits in the middle of the three. When one of them is forced without moving the others, quality pays the bill, almost always quietly, and almost always found out late.
We had this recently, at the company. Software to be built in a timeframe everyone knew was short. But the end date was there, all pompous, like a giant concrete wall. It didn’t go well, but we finished. And afterwards we still had a few months of fixing what had been compromised in quality.
Where are most projects already born wrong?
At the starting line. The project begins with a date chosen before anyone knows what’s going to be done. Or with a goal so vague (“improve customer service”) that nobody can say, at the end, whether it got there.
I worked on an industrial project in Brazil that had to hold its inauguration with the works half done. It was election season, and the date wouldn’t move. The plant wasn’t ready. We had to run a pipe from the plant next door so that, when they opened the valve at the ceremony, product would come out.
That’s the price you pay for starting at the end.
The question that saves more projects than any tool is the simplest one: what exactly will exist at the end that doesn’t exist today? If nobody can answer that in one sentence, the project hasn’t started yet.
So, what comes first?
With what comes next in this world, in the order the game teaches it:
- Break the work down until it fits in your hand (World 1-2).
- Build the plan and take a snapshot of it (World 1-3).
- Control what actually happens (World 1-4).
- Choose how to play: predictive, agile or hybrid (World 1-5).
Tools, software and methodology come later.
Although not all work is a project, almost everything that changes something in a company is.
Quick questions
What is a project? A temporary effort to create a unique result. It has a specific goal, a planned end and counted resources: opening a branch, replacing the billing system, launching a product.
What’s the difference between a project and operations? Operations repeat every day and have no end date. A project starts, finishes and leaves behind something that didn’t exist before. A maintenance shutdown is a project inside the operation.
Do I need to be from the field to manage a project? No. You need to separate the people who know how to do the work from the people who organise it, and understand that both are work.
What are the three forces of a project? Scope, time and resources. Moving one pulls the others. When one is forced without moving the others, quality is what pays.
References
- PMI — What is a project? https://www.pmi.org/about/what-is-a-project — accessed 2026-09-25.