fudgy brownies, earthshine, and the cost of completion

A few weeks ago, I was on a lunch walk in the middle of a big project when a roadrunner shot across the front yard before darting into the street. Then it took off at full speed past the house.

It was one of those rare things you get to see in person. And after the joy and awe of the moment wore off, I moved on.
Back to finishing my project, supporting clients, and the day-to-day of life. 

Then Friday happened.
The project was done, and instead of feeling relieved, I felt... strange.

A little flat, foggy, and a bit untethered. 

Almost immediately, my brain handed me that roadrunner image. Reminding me of all the Looney Tunes I watched as a kid, where Wile E. Coyote chased the Road Runner off the cliff.

And that split second of awareness that comes just as you realize you’ve been moving on momentum for so long that you didn't notice the ground is gone—until you look down.

That’s what finishing something big can feel like sometimes.

The deadline passes.
The deliverable gets sent.
The sprint ends.
The project is done. 

Instead of relief or celebration, you just feel off.

The hard thing is technically over, so it can be surprisingly easy to make that feeling mean something about you.

That you should be happier.
That you’re ungrateful.
That maybe the thing didn’t matter as much as you thought. 

When it's actually a normal, human response to the chemicals in your brain dropping after doing the thing. Sometimes called the "letdown effect" or "post-achievement depression."

Because productivity culture is deeply invested in the chase sequence.

It loves the countdown and the heroic montage where everyone is exhausted but determined. And then the joy of achievement means everyone emerges glowing, accomplished, and immediately ready for the next episode. 

Completely glossing over the landing.

Almost no one talks about what happens after the milestone.
After the calendar clears.
After the structure that held your attention for days or weeks (sometimes months or years) suddenly disappears. 

For weeks leading up to finishing this project friends have been asking if I'm excited for the achievement.

And my response was always along the lines of:

 👁️👄👁️

Because I couldn't even think past tomorrow, let alone get excited at being done.
So they got excited enough for the both of us.
And tried to remember in that moment, that the drop was coming.

That a weird quiet was going to roll in.

So that instead of treating it like:

An error message.
Something to override.
Or something to fix by quickly chasing after the next thing.

I could keep an eye on it, because the flatness after a big push is not necessarily a sign that anything has gone wrong. 

Sometimes it’s just honest data.
A human experience to account for instead of combat against. 

Something important required a lot from you and your system organized around that requirement. Now the external demand is gone, but your internal pace hasn’t caught up yet.

That doesn’t mean you’re lazy or the goal was wrong.
It doesn’t even mean you need to become less (or more) ambitious. 

It just means completion has a cost. And most of us were handed systems that know how to get us to the finish line, but not how to hold us once we cross it. 

No landing pad.
No transition.
No space to actually arrive before the next ask appears.

That’s the part I keep coming back to.

Sustainable systems don’t only account for effort. They account for aftermath. For the disorienting little moment where part of you is still running, even though the chase scene is over.

Not because there’s one correct way to land.
Not because every ending needs a ritual and a color-coded recovery plan.
But because honest systems tell the truth about the full arc. 

The build. The push. The finish.
And the very human experience of figuring out how to be on the other side of it. 

If your systems only know how to support part of the arc, it's going to be hard for them to be sustainable long term.

Because the landing shouldn't be an afterthought—it's part of the process too.