The fashion for short cycles comes from software teams, but the idea is older than that, and it belongs on site. Work in a fixed short block, agree at the start what will actually be finished by the end, and then stop and look before starting the next one.
It is the opposite of an open-ended push. A push has no edge, so it never quite ends, and nobody can tell you whether it worked.
Why a fixed short cycle wins
An open-ended push feels productive because everyone is busy. But busy and finished are different things. A fortnight-long push on “the third floor” can end with a hundred people tired and nothing you can point at as complete.
A short cycle forces a different question. Instead of “what are we doing this month”, it asks “what will be measurably finished by Friday”. That question changes what people pick up first.
-
Pick a length and keep it
One or two weeks suits fit-out. Long enough to finish real work, short enough that a bad start is visible before it has eaten the month.
-
Name the finishes, not the effort
Agree at the start which things will be measurably complete by the end. A flat of apartments handed over, a service core second-fixed and tested, a staircase balustrade installed and signed off.
-
Stop and look at the end
At the close of the cycle, walk what was committed. Finished is finished. Not finished is honest data for the next cycle, not a reason to quietly carry it.
The discipline is the stop. Without it, work simply rolls forward and the question of whether anything was actually delivered never gets asked.
What you commit to
A cycle’s commitment is a short list of things that will be done, measurably, by the end. Not started. Not in progress. Done.
| Weak commitment | Real commitment |
|---|---|
| Work on the joinery | Wardrobes to Apartments 4 and 5 fixed and snagged |
| Make progress on MEP first fix | Lighting and power first fix to Floor 3 signed off by the engineer |
| Tidy the marble area | Marble to the reception feature wall fixed, sealed, and protected |
| Sort out the snag list | All Category 1 snags on Block A closed with photos |
The left column describes effort. The right column describes a state you can walk up to and verify. Only the right column lets you walk the site at the end and say, honestly, whether the cycle met its commitment.
Why done has to be agreed once
The single most corrosive argument on a fit-out is not about money. It is two honest people looking at the same wall and disagreeing about whether it is finished.
Done is a state, not a feeling, and it has to be defined once for the whole team rather than re-litigated on every task. Argue the definition once, while everyone is calm and nothing is owed, and write it down. From then on the conversation is short: does this meet the written standard, yes or no.
A good definition of done names the standard, the tolerance, the evidence, and the sign-off. For a partition it might read: built to the approved detail, plumb and true within the specified tolerance, sealed at all penetrations, rubbish cleared, photo taken. Read that line and the argument dissolves — the partition either meets it or it does not.
This is the same lesson as defining done for the whole project. The only difference is scale. A cycle’s commitments inherit the team’s definition of done, so finishing the cycle means the same thing every fortnight.
What this looks like in Taskity
A cycle is a short sprint with a fixed end date and a named list of work committed for that cycle. Each task carries the project’s definition of done, so finishing is judged against one standard rather than argued each time.
Check what you learned
1. A fit-out team agrees at Monday's meeting to "push hard on the third floor this fortnight" with no specific finish. What goes wrong first?
Show the answer
At the end of the fortnight nobody can agree what the push was meant to achieve
"Push hard" is effort, not a commitment. Two weeks later, the team will remember the third floor as close to finished, the foreman as half done, and the QS as barely started — and all three will be honestly describing the same rooms. Without a named, measurable finish the cycle ends in argument, not in anything you can value or hand over. The fix is to name the work that will be measurably complete, not the vigour.
2. Two site engineers disagree about whether a partition is "done". Why is the right fix not to argue this partition to a conclusion?
Show the answer
Because the real gap is a team-wide definition of done that was never written
When done is defined task by task, every closing conversation is a fresh negotiation and morale erodes. The fix is one definition of done, written once for the team: a partition is built to the approved detail, plumb and true within tolerance, sealed at penetrations, and cleared of rubble. With that on the wall, this partition is decided in a minute — and so are the next fifty.
Scored quizzes, progress tracking and certificates live inside Taskity.