Everyone in this industry already runs projects. You did one last month. The word just sounds like something that belongs to people in offices with charts.
So let us start from what you actually know.
Three things that make it a project
A job is a project when it has all three of these. Take one away and it becomes something else — usually something that drifts.
-
It ends
There is a point where you stop and hand over. “Maintaining the building” is not a project. “Fitting out the ground floor by 14 March” is.
-
It is new enough to need thinking about
You have done fit-outs before, but you have not done this one. If the work is identical every time and needs no decisions, it is a routine, not a project.
-
Someone can tell when it is finished
Not “when it looks good” — when a specific, agreed thing is true.
That third one is where most fit-out jobs quietly go wrong, so it is worth sitting with for a moment.
”Done” has to be something you can point at
Here are two versions of the same instruction.
| What the client said | What you can actually finish |
|---|---|
| Make the reception look premium | Walnut veneer to the rear wall, stone counter installed and sealed, lighting at 300 lux, snag list cleared |
| Sort out the lighting | All 42 fittings installed, tested, and commissioned to the approved layout |
| Finish the joinery soon | Joinery complete and signed off by the client’s rep before the 8th |
The left column feels friendlier. The right column is the one that lets you go home.
Why the definition matters more than the plan
You can have a beautiful programme and still lose a job. What you cannot do is recover from nobody agreeing what finished means, because there is no version of “more effort” that fixes it. You will simply keep working and the client will keep finding things.
This is the whole reason the rest of this track exists. Everything that follows — breaking work down, sequencing it, pricing it, inspecting it — assumes you have first agreed on what you are being asked to deliver.
What this looks like in Taskity
You will meet this idea again as a real field. Every project you create has a description and a target date, and every task has a definition of done. Those boxes are not admin — they are the thing this lesson is about, in a form the whole team can see.
Check what you learned
1. A client asks you to "make the reception look premium." Why is that not yet a project?
Show the answer
Because there is no way to tell when it is finished
A project needs a finish line you can point at. "Premium" is a feeling — two people will disagree about whether you got there. "Walnut veneer to the rear wall, stone counter, lighting at 300 lux" is something you can stand in front of and agree is done. Budget and signatures matter, but without a definition of done you cannot even tell whether you have delivered.
2. Which of these is the clearest sign that "the fit-out of Villa 3" has become too big to manage as one lump?
Show the answer
Nobody can tell you what percentage is complete without guessing
Duration and headcount are not the test — plenty of long jobs stay perfectly legible. The test is whether progress is *measurable*. The moment the honest answer to "how far along are we?" becomes a shrug or a number someone invented, the work needs breaking down. That is what the next few lessons are about.
Scored quizzes, progress tracking and certificates live inside Taskity.