The Question That Changes Every Project

There's a question I ask at the start of every project I work on, and it's one of the simplest but most powerful tools I have.

What does done look like?

Not "what are we working on" or "what's the goal." Those are important, but they're not specific enough to keep a project from spiraling. I'm asking: What does it look like when this project is finished? How will we know we're done? What will exist that doesn't exist now? What decisions need to be made before we can close this out?

Most projects stall because there's no clear finish line.

People keep working. Owners keep tweaking. Teams keep adding just one more thing. And nothing ever actually closes because no one defined what "complete" meant in the first place.

I see this happen in all kinds of ways.

A website redesign that's been "almost done" for six months because the owner keeps finding new pages to add or copy to refine. A process documentation project that never gets implemented because it doesn't feel comprehensive enough yet. A product launch that keeps getting delayed because there's always one more feature that would make it better.

The work isn't bad. The problem is that there's no agreement on when to stop.

Without a clear definition of done, projects drift. Scope creeps. Timelines stretch. Decision fatigue sets in because every choice feels like it could be revisited later. And the team, or the person leading the work, starts to lose momentum because there's no sense of progress or completion.

Here's what I've learned: defining "done" upfront, before the work even starts, changes everything.

1. It eliminates scope creep because you know exactly what's in and what's out.

2. It reduces decision fatigue because you're not constantly second-guessing whether something is good enough.

3. It creates accountability because everyone knows what they're working toward.

4. And it gives you permission to actually finish and move on instead of endlessly refining.

So how do you define done?

Start by asking yourself these questions at the beginning of your next project:

• What will exist when this is finished?

Be specific. Not "a better onboarding process" but "a documented onboarding checklist, a welcome email template, and a 30-day check-in form." Not "an updated website" but "five new service pages, an updated About page, and a contact form that routes to the right inbox."

The more concrete you can be about what will exist, the easier it is to know when you've arrived.

• What decisions need to be made before we can close this?

Projects often stall because there's an unmade decision lurking in the background. Which software are we using? Who's responsible for maintenance? What's our budget cap? What's the approval process?

Identify those decisions upfront and make them early. Don't let them become roadblocks later.

• What are we explicitly not doing?

This is just as important as defining what you are doing. What's out of scope? What are we saving for version two? What ideas are we acknowledging but choosing not to pursue right now?

When you name what's not included, you protect the project from growing beyond what's realistic or necessary.

• How will we know it's good enough to ship?

Not perfect. Good enough. What's the standard you're holding this to? Does it need to be polished and client-ready, or does it need to be functional and improvable over time?

Knowing your quality bar upfront prevents you from holding something hostage to perfection when good enough would actually serve you better.

• What happens after this is done?

Sometimes projects don't close because there's no plan for what comes next. If you launch this, who maintains it? If you document this process, who owns keeping it updated? If you build this system, when do you revisit it?

Knowing the handoff or the next step makes it easier to actually finish.

The question "what does done look like" isn't just about clarity. It's about momentum.

When you know where you're going, you stop second-guessing every decision along the way. You stop adding scope. You stop tweaking endlessly. You finish, you ship, and you move on to the next thing. And that rhythm of completion, of actually closing projects instead of leaving them perpetually open, changes how your business operates.

So before you start your next project, take five minutes and answer the question: What does done look like? Write it down. Share it with anyone else involved. Refer back to it when you're tempted to add just one more thing.

That clarity will carry you all the way to the finish line.

Warmly,

Jazmin

P.S. If you're stuck in the middle of a project that feels like it will never end, or if you're trying to launch something but can't figure out what "done" actually means, a clarity session can help you define the finish line and build a realistic plan to get there. Learn more here.