What If Your Unfinished Project Just Needs to Be Smaller?

The project sitting unfinished on your desk right now might not be too small to ship. It might be too big to finish

That distinction could matter more than you think. Because the instinct when something stalls is to add more. One more module. One more page. One more revision to get it right. But every addition pushes the finish line further away, and the thing keeps growing past the point where it could actually be done.

There's a principle from the 1950s called Parkinson's Law: work expands to fill the time available for its completion. Give yourself a month for a week's worth of work, and it takes a month. Not because you're lazy. Because the brain treats available time as necessary time.

What if perfectionism isn't a personality flaw? What if it's a time management problem?

What You Might Actually Be Waiting For

If something's been sitting unfinished longer than it should, it's worth getting honest about the real reason. In my experience, it's usually one of three things.

Perfection. Good enough keeps moving. Every time you get close, you find another thing that needs to be better.

Completion. The whole thing has to be built before anyone sees it. But it keeps growing as you build it.

Confidence. You're waiting to feel ready. This one's the hardest to name because it disguises itself as the first two.

In my experience, none of those tend to show up before you ship. Perfection follows the work. Completion is just the version you decided to stop adding to. And confidence comes from having shipped and watched it work, not from imagining that it might.

Two Decisions That Could Get a Stuck Project Moving

Here's what's worked for a lot of my coaching clients. Two decisions.

1. What's the minimum version that delivers real value? Not the version you'd be embarrassed by. The version that solves the core problem for the person it's built for. That version is almost always smaller than what you're currently building.
   

2. What's your deadline? A real one. A date you write down and tell someone else so it exists outside your own head.
   

One of my coaching clients had been building a three-day event for months. Months of it sitting there, growing heavier every time she opened the planning document. When she brought it to a call, I asked one question: what if it was one day? She pushed back. Three days is what the topic requires, she said.

The event shipped as one day. It wasn't worse for her audience. It was better, because it happened.

Simple might not be the version you settle for. It could be the strategy. When your event is one focused day, people can see themselves attending. When it's three days of everything you know, it's harder to commit.

The unfinished thing, no matter how comprehensive, has never helped anyone. The finished thing, even the imperfect one, is the only thing that can.

What's the project that's been sitting too long, and what does it look like at half the scope?