The Project Lifecycle Is a Loop, Not a Line

The lifecycle is a loop, not a line

Most teams draw the project lifecycle as a five-step waterfall: initiate, plan, execute, monitor, close. The phases are right; the arrows are wrong. In practice the loop runs every week — a stand-up surfaces a missed dependency, planning re-opens, execution shifts, monitoring reports update, and the team closes the increment that was just delivered.

Drawing the lifecycle as a continuous loop has two payoffs. First, it forces the conversation about which loop ran this week — long-cycle for the quarter's strategic goals, short-cycle for sprint-level commits. Second, it makes the bottleneck visible: most teams are dominated by one phase (estimation, monitoring, closure), and the loop frame surfaces it.

How the five phases interleave

Initiation is two questions: who decides, and what do we count as done. If either is unanswered, every later phase pays for it.

Planning is the smallest plan that survives contact. The infinite-canvas idea — every workstream visible, dependencies typed — earns its keep here, because the bad assumption you're going to discover in week three is the one a list view hides.

Execution is where the loop opens out: every team runs its own micro-loop and feeds the macro-loop the deltas.

Monitoring is the loop's heartbeat. Done right, it's a 15-minute weekly that surfaces three things and resets one.

Closure is the discipline most lifecycles skip. The artefact that survives the project — postmortem, runbook, decision log — is the only thing the next cycle inherits.