Step 01
Define the project and the deadline
You start by naming the product, choosing a 2 to 5 week window, setting the stake, and writing the version of the product that must exist by the end.
How it works
The product exists to make shipping harder to avoid.
SideProject is not a motivation app. It is a structured commitment flow for developers who need a shorter runway, a clearer MVP, and consequences strong enough to change behavior.
Step 02
Lock the MVP before the build drifts
The planning step forces a narrower launch standard: one-line MVP, must-haves, out-of-scope work, and proof expectations. This is where most procrastination loses oxygen.
Step 03
Work in public enough to stay honest
Weekly check-ins make the commitment visible while there is still time to recover. You record progress, blockers, confidence, and the next concrete step.
Step 04
Finish with proof, not an explanation
At the deadline, the product asks for a live URL, GitHub repo, and a summary of what works now. The system is meant to judge the shipped product, not the effort story around it.
What the system is trying to fix
Most side projects do not die from lack of effort. They die from softness around the finish line.
Scope expands. Deadlines slide. The definition of done stays vague enough that almost-finished work can masquerade as progress. The workflow is built to remove those escape hatches.