The Art of Finishing

This post contains affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you.

Everyone starts things. Few people finish.

I have six published books. Dozens of half-finished projects. Countless ideas that never made it past draft one.

The difference between what I finished and what I abandoned? Not talent. Not motivation.

Systems for finishing.

Here's how to become someone who actually completes what they start.

Why Finishing Is Hard

Starting is exciting. New project energy. Unlimited potential. No mistakes yet.

Finishing is grinding. The novelty is gone. The flaws are visible. The work is tedious.

The Three Finish-Killers

1. The Shiny Object

A new idea shows up. It's more exciting than the current project. You switch.

Six months later, you've started five things and finished zero.

2. The Messy Middle

The beginning was fun. The end will feel great. But the middle is hard, boring, and slow.

Most people quit in the messy middle.

3. Perfectionism

You can't finish because it's not good enough. So you tweak forever.

"Done" never arrives because "perfect" never arrives.

The Finishing Mindset

Before tactics, you need the right mindset:

1. Done > Perfect

A finished mediocre project is more valuable than a perfect unfinished one.

Why? Because finished projects:

• Teach you what works and what doesn't
• Can be improved in version 2
• Actually exist in the world

Perfect projects that never ship teach you nothing.

2. Finishing Is a Skill

Some people aren't "naturally good at finishing." They just practiced it more.

Every project you complete makes the next one easier.

3. Momentum Compounds

Finishing one thing creates momentum for the next.

Not finishing creates a pattern of abandonment that's hard to break.

The Finishing Framework

Phase 1: Define "Done"

You can't finish if you don't know what finished looks like.

Bad goal: "Write a book"

Good goal: "Write a 50,000-word manuscript with 12 chapters, edited twice, and formatted for publication"

Why specificity matters:

• You know when you're done
• You can track progress
• You can't move the goalpost

The "Done" Checklist:

For every project, write down:

1. What does finished look like?
2. What are the specific deliverables?
3. What's the deadline?
4. What quality level is "good enough"?

Phase 2: Break It into Milestones

Big projects are overwhelming. Milestones make them manageable.

Example: Writing a book

• Milestone 1: Outline (12 chapters defined)
• Milestone 2: First draft (50,000 words written)
• Milestone 3: First edit (structural revisions)
• Milestone 4: Second edit (line edits)
• Milestone 5: Formatting & cover
• Milestone 6: Published

Why milestones work:

• Each milestone is a small win
• Progress is visible
• You can celebrate along the way

Phase 3: Time-Box the Work

Open-ended projects never finish. Deadlines force completion.

My rule: Every milestone gets a deadline.

• Outline: 1 week
• First draft: 12 weeks (1 chapter/week)
• First edit: 2 weeks
• Second edit: 1 week
• Formatting: 1 week

What if I miss a deadline?

Set a new one immediately. Don't let it drift into "whenever."

Phase 4: Work Daily (Even When Unmotivated)

Motivation comes and goes. Systems persist.

The daily minimum:

Pick a ridiculously small daily action:

• Write 200 words
• Code for 15 minutes
• Edit 2 pages

On bad days, do the minimum. On good days, keep going.

Why small daily actions work:

• Momentum builds
• You never lose more than one day
• Showing up becomes automatic

I wrote six books with this method. 500 words/day. Every day. No exceptions.

Phase 5: Protect Against Shiny Objects

New ideas will show up. They always do.

The "Idea Parking Lot":

Keep a document for new ideas. Write them down. Then ignore them until your current project is done.

Why this works:

• You don't lose the idea
• You don't abandon the current project
• Most "great" ideas look mediocre three months later

The rule: One active project at a time. Everything else waits.

Phase 6: Kill Perfectionism Early

Perfectionism disguises itself as quality. It's actually fear.

How to spot perfectionism:

• You're tweaking details that nobody will notice
• You're revising the same section for the 10th time
• You're afraid to show anyone the work
• You keep adding "one more thing"

The cure:

Set a quality threshold upfront: "Good enough is X."

For a first book: "Clear, useful, and readable" is good enough.

For a blog post: "One good idea, explained clearly" is good enough.

Once you hit "good enough," ship it.

Phase 7: The Final Push

The last 10% is the hardest. This is where most projects die.

Why the final stretch is brutal:

• The exciting part is done
• What's left is tedious (editing, formatting, admin)
• You're tired of the project

How to power through:

1. Timebox it: "I will finish this by Friday, no matter what."
2. Eliminate distractions: Turn off everything. This is the only thing that matters this week.
3. Make it non-negotiable: Tell someone you'll finish by X date. Public accountability helps.
4. Remember why you started: Reconnect with the original motivation.

The Finishing Strategies That Work

Strategy 1: The Sprint Finish

What it is: Dedicate a short, intense period to finishing.

Example: "This weekend, I'm finishing the book. No social plans. No distractions. Just work."

When to use it: When you're 80%+ done and need one final push.

Strategy 2: The Accountability Partner

What it is: Tell someone you'll finish by a specific date. Check in weekly.

Why it works: You don't want to disappoint them (or yourself).

When to use it: When you've been stuck in the messy middle for months.

Strategy 3: The "Ship Ugly" Method

What it is: Ship version 1.0 even if it's not pretty. Improve based on feedback.

Why it works: Done beats perfect. You can always improve v2.

When to use it: When perfectionism is stopping you from finishing.

Strategy 4: The Finish Line Ritual

What it is: Create a ritual for finishing projects.

My ritual:

1. Final review (1 hour max)
2. Hit "publish" or "submit"
3. Close the project file
4. Archive all notes
5. Celebrate (dinner out, day off, whatever feels good)

Why it works: Rituals create closure. They mark the transition from "working" to "done."

Real Examples from My Life

Finished: The Lean Startup Blueprint

System I used:

• Defined "done": 50,000 words, 12 chapters, two edits
• Set milestone deadlines: outline (1 week), draft (12 weeks), edit (3 weeks)
• Wrote 500 words/day minimum, no exceptions
• Parked new book ideas in a separate document
• Final sprint: dedicated one full weekend to formatting and publishing

Result: Finished in 4 months. Published. Helping readers.

Abandoned: A SaaS Product

Why I didn't finish:

• No clear "done" definition (kept adding features)
• No milestones (just "build until it's ready")
• No daily minimum (worked in irregular bursts)
• Got distracted by new ideas every month

Result: 6 months of work. Nothing shipped. Total waste.

Lesson: Systems matter more than enthusiasm.

Finished: This Website

System I used:

• Defined MVP: homepage, books page, blog, contact form
• Set deadline: launch in 1 week
• Timeboxed each page: 2 hours max
• Shipped "good enough" (not perfect)
• Improved based on feedback after launch

Result: Live in 7 days. Iterating publicly.

The Finish Rate Metric

Track your finish rate: Projects finished / Projects started

My early years: 3 finished / 20 started = 15% finish rate

After implementing systems: 12 finished / 15 started = 80% finish rate

Goal: 70%+ finish rate

(You'll abandon some projects strategically. That's fine. But most should finish.)

When NOT to Finish

Not every project deserves to be finished:

• The goal changed: You no longer want the outcome
• The market doesn't exist: You validated and found no demand
• The approach is fundamentally flawed: No amount of finishing will fix it
• Better opportunities emerged: Finishing this means missing that

Strategic quitting is smart. Chronic non-finishing is a problem.

The 30-Day Finishing Challenge

Pick one unfinished project. Commit to finishing it in 30 days.

Steps:

1. Day 1: Define "done" and break into milestones
2. Days 2-28: Work on it daily (even 15 minutes counts)
3. Day 29: Final push (spend the whole day if needed)
4. Day 30: Ship it, celebrate, move on

Rules:

• No starting new projects during the 30 days
• No perfectionism—ship "good enough"
• If you miss a day, double your effort the next day

The Bottom Line

Starting is exciting. Finishing is rare.

Most people fail to finish because they lack systems, not talent.

To finish more:

1. Define "done" upfront
2. Break it into milestones
3. Set deadlines for each milestone
4. Work daily (even small amounts)
5. Protect against shiny objects
6. Ship "good enough" (perfectionism kills projects)
7. Push through the final 10%

Finishing is a skill. The more you practice, the easier it gets.

Start fewer things. Finish more of them.