How to finish a side project
Reduce the scope, protect the time and produce a first version you can show.
Choose one finish
Write a result that somebody else could recognise. “Work on my invention” is an activity. “Demonstrate a prototype that performs the core action” is a finish. Keep this first result small enough to attempt with the time and resources you actually have.
Make the boundary explicit
List what the first version must do, then list what can wait. A company might begin with a tested offer and one deliverable. A creative project might begin with one finished piece. Resist adding features whenever the work becomes uncomfortable.
Give the next move a time
Choose an action that produces evidence: build, test, practise, ask or publish. Put a realistic block in your calendar. Write what you expect to exist at the end. If the action depends on someone else, make contacting them the first move.
Review what happened
At the end of the week, compare the intended result with the evidence. If you did not get there, identify the specific obstruction. Reduce scope, resolve a dependency, seek relevant expertise or deliberately change the goal. Repeating the same plan without changing the conditions is rarely useful.
Try it this week
Finish: a demonstration of the core idea. Boundary: one scenario, no polished branding. Next move: a 45-minute test build on Tuesday. Evidence: a short demonstration and three observations. Review: Friday, then decide whether to improve, test with someone or stop.
Bring the next question.
Use the guide on your own, bring the results into Weekly Counsel, or make room for a focused discussion with Finish Sprint.