Deadlines on a passion project: how to set them at all

Why a deadline, if nobody's paying

It feels as though a personal project needs no deadline: we're enjoying it, we'll finish when we finish.

In practice "when we finish" means never. Without a date there's no reason to cut anything, no moment to say "enough, let's show it", and the project becomes a permanent building site that quietly fades.

A deadline isn't pressure but a way of finishing.

Setting a realistic one

Count real hours, not calendar days. Two people at six hours a week is twelve hours — about a day and a half of work. Over a month that's six working days, not a month.

Nearly everyone errs here: they plan as though working full time, then work evenings.

Multiply by two. The first estimate is always low. That isn't pessimism but a correction for reality.

Aim for two to four weeks. Not three months. A short horizon holds attention; after three months half the team remains.

Account for life. Holidays, exams, a crunch at work, public holidays. Over a month something happens to someone without fail.

What makes a deadline useful

It must be tied to a result, not a calendar date. Not "we're working until the end of March" but "by the end of March this scenario works end to end".

The difference matters: in the first case it's unclear what counts as success; in the second it's clear, and so is what can be cut to make it.

When you overrun

Three options, and only three:

Cut the scope. Right nine times in ten. Build half of what you planned, but completely, and show it.

Move the date. Once, deliberately, with a fresh honest estimate. Moving it twice means the estimate isn't working at all.

Add time. On a passion project, nearly impossible: people are already giving their free hours.

What you can't do is drag on silently hoping it'll somehow work out. It won't, and the team will be worn out by then.

The rule for cutting

Agree in advance what's essential and what's desirable. One column "no project without this", another "would be nice".

When time gets short, the second column is cut without discussion. Without that split, the moment of shortage begins an argument — and there's no time left to argue.

About the final push

In the last week the temptation appears to add "just this one thing". Don't. That's exactly how projects never end: there's always one more small thing.

Better to finish a trimmed scope on time, show it to people, and decide calmly whether to continue.

What a finished project gives you

At interview the difference between "I was building a project" and "I built a project" is enormous. Everyone says the first; few say the second.

And it isn't about technologies but about being someone who finishes. That's valued above one more entry on a list of things learned.