Blog · Tactics
How to actually finish a project
Motivation is unreliable. These 7 operational tactics will get you to the finish line even when motivation fails. Daily commits, public ship dates, the 10% in 10 days rule, the 5-person review, and more.
Published July 13, 2026 · ~4 min read
The motivation trap
Most advice about "how to finish a project" centers on motivation. Find your why. Visualize the outcome. Use a reward system. The problem: motivation is a feeling, and feelings are unreliable. The professionals — the writers, the founders, the artists with decades of output — don't rely on motivation. They rely on tactics. These 7 tactics are the ones that work when motivation fails.
The 7 tactics
Tactic 1: The smallest possible daily commitment
200 words. 30 minutes of code. 1 sketch. The number is small enough that "I don't have time" is never an excuse. The number is large enough that the project moves. Adjust the number until daily is possible. The system is the daily; the parameter is the volume.
Tactic 2: The public ship date
Pick a date. Tell 5 people. Ship on the date, regardless of readiness. The date is a forcing function. The public announcement is social pressure. Most finished projects were finished because of a date, not because of motivation.
Tactic 3: The 10% in 10 days rule
The last 10% of any project can usually be done in 10 days of focused work. The time it took to get to 90% is not the time it takes to finish. The finish-line is closer than it feels. The 10% in 10 days rule is a reminder that the finish is a sprint, not a marathon.
Tactic 4: The 5-person review
Before shipping, show the work to 5 people you trust. Their reactions will reveal what really matters and what's just polish. The 5-person review also serves as a pre-shipping stress test — if 5 people can use it, the public can use it.
Tactic 5: The 1-week cooldown
After you think the project is done, walk away for 1 week. When you come back, you'll see the work with fresh eyes. The 1-week break also tells you which projects you actually want to ship (vs. which projects you've outgrown).
Tactic 6: The "no backward edits" rule
Don't edit anything you've already written/coded/painted until you've completed the next 10%. The polish phase is the end, not the middle. Backward edits are the most common reason projects die at 90% — the creator polishes chapter 1 when they should be writing chapter 12.
Tactic 7: The public log
Tweet the daily progress. Post the daily log. The public log creates accountability that motivation can't. The log also serves as a forcing function — skipping a day is visible. Skipping 3 days in a row is publicly embarrassing. The log is the simplest accountability system.
Frequently asked questions
What's the difference between motivation and tactics?
Motivation is a feeling. Tactics are operational systems. The professionals rely on tactics.
What if I can't make daily progress?
Reduce the commitment until daily is possible. 200 words. 30 minutes. 1 sketch.
Does this work for all project types?
Yes. The tactics are operational, not domain-specific.
Related reading
Get rescued projects in your inbox
A short Monday-morning note on the projects abandoned last week and who adopted them. No spam, unsubscribe anytime.
Related reading on BreakPoint
The concepts, guides, and reports behind this post.