You're not stuck. You're waiting for a signal that isn't coming.


Flux & Flow

Issue #90

There Is No Finished, Only Release

The project is somewhere in the middle, and somewhere in your mind there’s a finished version of it. You can almost picture it. You’re moving toward that version, putting in the hours, trusting that at some point the work will click into place and tell you it’s done.

That moment keeps not arriving.

The longer that stretch runs, the heavier it gets. After the early energy fades and before anything feels complete, the work starts to cost more than the effort alone explains. A good portion of that weight comes from waiting for a signal the work was never going to send.

Creative work doesn’t arrive at done. It goes out into the world at some point, in some form, because you decide to send it. Release is a decision you make, not a state the work eventually reaches.

When that lands, the middle starts to feel different.

The Distance Problem

There’s a specific point in most creative projects where the gap between where you are and where you imagined done would be starts to feel enormous.

At the start, that distance wasn’t a problem. The energy of beginning carried you through the uncertainty. Open-endedness felt like possibility. Forward motion came without forcing it.

Then the early energy runs out, and what’s left is the actual stretch ahead. You look up and see the gap. Unknown territory, no clear sight line to finished, and the project asking more of you than it’s returning right now.

This is the part of creative work that tends to separate the projects that make it through from the ones that quietly stall.

The Outdated Finish Line

You might know it as the dip. Or the swamp of despair. Whatever the label, the experience is recognizable: somewhere in the middle, the early energy spent, the end not in sight, and every hour forward costing more than it seems to return.

The standard advice is to treat this as a motivation problem. Strengthen your discipline. Put your head down and keep working until you’re through to the other side.

What that framing misses is where much of the weight is actually coming from.

The challenge isn’t simply that the finish line is far away. It’s that the version of finished you’re moving toward was often imagined before the work taught you anything. As the project evolves, that image becomes harder and harder to reach because it no longer reflects the reality of the work itself.

The gap grows when the work is measured against an increasingly outdated vision of where it’s supposed to end up. The version of finished you imagined at the beginning was created before the project taught you anything. As the work evolves, that picture often becomes less accurate, even as you continue using it as the standard you’re trying to reach.

The work changes. The idea of finished often doesn’t.

Release Changes the Shape of the Work

Releasing in smaller forms changes the shape of the problem.

Rather than holding the work for one moment at the end, you let it out in stages. A rough version shared with someone you trust. A section tested before the whole is ready. A prototype that makes one piece of the work concrete enough for someone to respond to.

Each small release does a few things at once.

You get real information about whether you’re heading somewhere worth going, early enough to adjust. The work stays agile, responding to reality rather than the idea of it you formed at the start. Release also exposes the assumptions the project was built on. What seemed obvious in your head becomes visible once another person encounters it.

And each small release creates its own moment of completion. Real contact between the work and the world. A chance for the project to teach you something you couldn’t have learned in isolation.

Momentum returns when the work starts teaching you what it wants to become.

You don’t have to push through the gap intact. You can release your way through it.

One Release This Week

The work you’re holding for done is worth looking at this week.

Not the whole project. Just the idea of finished you’ve been moving toward.

Ask yourself where that endpoint came from, and whether it still reflects the work you’re actually doing. Has the project evolved beyond the version of finished you imagined at the start?

Then look for something small within the project that could go out. A draft shared with one person. A section tested against reality. Anything that creates real contact between the work and the world before the whole thing is ready.

That’s the practice.

One small release from something you’ve been holding.

The gap gets smaller every time the work leaves your head and meets the world.

Until next week, may your releases be more frequent and your finish lines fewer.

Jeff

P.O. Box 050361, Brooklyn, NY 11205
Unsubscribe · Preferences

Flux and Flow by Jeff Tyack

Flux & Flow is a weekly practice for creators to find clarity, make sense of change, and take aligned action without pressure.

Read more from Flux and Flow by Jeff Tyack

Flux & Flow Issue #100 You sit down to keep working on the project you started last week. Everything is already there, exactly where you left it. You look at what’s in front of you and hit the small, familiar problem of not quite remembering where your thinking had gotten to. You open your notes to reconstruct the thread. You look back over what you already built, trying to recover its shape before you can add anything new. A few minutes pass before you’ve actually located yourself inside the...

Flux & Flow Issue #99 There’s a version of your morning that runs without you. The same sequence in the same order. The route to the desk. The order you open things in. The walk you take often enough that you arrive without remembering the middle of it. You’ve done it enough times that it no longer asks much of you. That’s the point of a habit. Other repeated actions interrupt that automatic movement and bring your attention back to where you are. Habits help you continue You repeat an action...

Flux & Flow Issue #98 You have a process. You read the book, took the course, or watched someone explain exactly how they work. You adapted the template, organized the project, and followed the steps. The method is sound. It has worked for other people. It has worked for you. Still, this project sits there. You revise the workflow, adjust the categories, or search for another method instead of moving the work forward. Eventually, you begin wondering whether the real problem is your...