Primary metric is streak weeks, not raw completion rate.
ScenarioSide ProjectSustained Execution
Side Project Flow
A minimal operating pattern for sustaining side projects alongside full-time work.
Governing Message
Side projects sustain better when folder boundaries are clear and slots are locked.
How This Scenario Is Different
Execution starts with folder boundary between work and side project.
Priority is 60-120 minute wins, not huge milestones.
Gap recovery is treated as an explicit 30-min restart routine.
Sustained Execution Scenes
Cards make common side-project drop-off points visible at a glance.
Reserve fixed slots
Without 2-3 fixed weekly slots, side projects disappear quickly.
Separate folders first
Split work and side-project folders to reduce context-switch cost and priority confusion.
Protect streak weeks
Track streak weeks over raw completion rate to reduce drop-offs.
Execution Flow
Slot lock -> small wins -> restart rule works better than heavy planning.
- STEP 1
Lock 2-3 weekly slots first
Reserve side-project slots before your main job calendar fills up.
- STEP 2
Separate side-project folder + split goals
After separating folders, split goals into 60-120 minute tasks to reduce context switch and drop-off.
- STEP 3
Use 30-min restart task after gaps
After a missed week, restart with one 30-minute task, not a full replanning session.
Common Failure Points
Running one giant task
Lack of small wins drains momentum quickly.
Long pause after one missed week
Treating a gap as failure raises restart cost.
Mixing work and side-project in one folder
Priority clarity drops and side-project slots get pushed out easily.
Recovery Rules
Cut task size in half
Smaller units increase completion frequency and restore momentum.
30-minute restart rule
After a gap week, finish one 30-minute task to recover flow.
Re-align by folder boundary
Separate work and side-project folders, then lock side-project slots first.