Verstreuen [ver-ˈstrɔɪ̯-ən]

verb (German)

1. to scatter; to spread widely.

2. (versehentlich) to spill, often by accident.

Verstreuen is my weekly ritual of revisiting notes to find the ideas worth carrying into the next week.

_{Forwarded this email? Subscribe here for more}

🗃️ This Week’s Highlights

This week's notes come from 12 new additions to the Zettelkasten - here’s the three that stood out most to share with you:

🟨 Where Does the Value Go When the Work Becomes Obsolete?

🟦 Why Good Routines Can Still Make You Fragile

🟥 Why Square One Is Never Really Zero

There is a specific kind of frustration that shows up when the ground shifts beneath work you were finally starting to trust.

You build the system. Refine the process. Finally start to see things working.
Then the requirements change.

The thing you optimized for is no longer the thing being asked of you. The plan that was supposed to get you across the finish line has to be redrawn. The architecture you trusted suddenly needs to be rethought.

And the thought creeps in: Was all of that for nothing?

I felt this recently on a project I had been working on for months. There was uncertainty from the beginning - around access, timing, ownership, and where everything was ultimately going to land. But the one constant was the architecture I had drawn up in the first few weeks.

That was the thing I could hold onto and build from.

Even when the rest of the project felt unclear, the structure gave me something stable. I had spent months shaping decisions around it, refining the approach, and slowly turning ambiguity into something workable.

Then the lead partner decided we were moving to a new solution.
And suddenly, everything we had built got thrown into the air.

I remember sitting with it for a while, trying to figure out if I was frustrated or just tired.
Both, probably.

It is a strange kind of loss because nothing dramatic happens. Nobody takes anything from you. The work doesn’t explode. The alignment just changes, and you are left with a portfolio of work that is now askew.

This feeling, not failure, not wasted effort, just obsolescence. Work that was right until it wasn’t.

And the natural assumption is that the loss is in the artifact. That the compounding you had put into what you had built is now lost - but what I realized is that compounding is never only in the artifact the same learnings transfer to the builder.

The artifact died but the operator improved. The system may not survive - the person who built it does.

Every serious attempt leaves something behind in you: better judgment, sharper taste, more patience, more confidence in your ability to start again.

A workflow only functions inside the environment it was built for. Judgment travels. Resilience travels. The ability to reorient travels.

That's a different kind of compounding.
The work expires. You don't.

📎 Takeaway:
Progress is not preserved only in what you build. It is preserved in who you become by building it.

—🗃️—

There is a unsettling discomfort that comes from realizing a system only worked because life was predictable.

The routine was good. The workflow was clean. The plan made sense.
Then the environment changed.

Schedules shift. Energy changes. The assumptions that made the system work stopped being true.

And suddenly, the thing that used to make you feel disciplined starts making you feel broken.

I have felt this most clearly with my routines lately as work has picked up and consumed my free time. When life is stable, it is easy to believe you have finally “figured it out.” You know when you write. When you work out. When you read. When you think. The days have a shape, and the shape makes you feel in control.

But then travel, responsibilities, workload pickup. Projects start demanding more than you have to give and the routine that felt so solid starts falling apart.

At first, it feels like a discipline problem.
Why can’t I just stick to the plan?

But often the issue isn’t discipline it’s that the system was overfit to a version of life that no longer exists.

That is the hidden cost of being optimized.

A routine that only works when your schedule is perfect is not really a routine. It is a dependency.

This is why adaptive challenges are uncomfortable. They do not just ask for a better tactic. They ask you to change your relationship to the work itself.

The instinct is to fix the system. Better calendar, tighter blocks, cleaner process. But sometimes the system does not need a patch. Sometimes the old assumptions just no longer fit the life you are actually living.

A routine that only works when nothing changes is not really a routine. It is a best case scenario.

The goal is not rigidity that holds until it snaps. It is structure loose enough to absorb the disruption - and pull you back after it.

A good system is not the one you never break. It is the one you can always return to.

📎 Takeaway:
A system that only works when nothing changes is not a system. It is a dependency.

—🗃️—

There is a moment after a plan changes, a routine breaks, or work becomes obsolete, where the problem is no longer logistical. It is emotional.

You can redraw the architecture, rebuild the calendar, make a new plan. But before any of that happens, you still have to sit with the feeling of being back at square one.

And square one has a way of making progress feel hollow. It makes you question whether you were ever as far along as you thought. Whether the confidence you felt was real or just borrowed from conditions that happened to be stable in the moment.

I felt this acutely during my college capstone project.

My team had spent a week working every day after class to gather data. We were tired, but there was momentum. We finally got to the analysis, expecting to see the effect we had been chasing.

And there was nothing. Not even remotely statistically significant.

I remember everyone leaving that day, disheartened. When the room emptied, I just laid on the floor.

No plan. No next step. Just the feeling that all of it had led us back to the beginning.

Starting over isn't just frustrating because there's more work to do. It's frustrating because it threatens the story you were telling yourself about where you were.

Sometimes the highest-leverage move isn't changing the circumstance. It's changing what you make it mean.

I eventually got up and started writing on the whiteboard. I felt behind. I felt responsible. I felt the pressure of a deadline that didn't care how disappointed we were.

But the longer I stood there, the more obvious something became: we were not actually back where we started.

We had data. We had sharper judgment. The first plan had failed, but the work hadn't disappeared.

A new angle emerged. We got the team back on board and presented something at the senior design expo that we were proud of.

Square one is rarely as empty as it feels.

The room may look familiar, but you're not entering it empty-handed. You bring back the reps, the judgment, the pattern recognition - and the confidence that comes from having been here before and made it through.

📎 Takeaway:
Square one is not proof that you failed. It is where the next version begins.

—🗃️—

Closing Thoughts

Across these three reflections, a common thread emerges: the real measure of progress isn’t found in unchanging systems or flawless plans. It’s found in our ability to adapt, to grow through disruption, and to embrace the journey of returning to square one.

Square one isn’t a setback. It’s a recurring home base for anyone who’s committed to continuous growth. And each time we return to it, we’re not the same person who started. We’re more equipped, more aware, and more ready for the next adventure.

Embrace the journey. Square one is where the next chapter of growth begins.

🟨🟦🟥 Join the Workframe Community

Be apart of a close community of readers and people who want to explore reflect and share their ideas in a community of like minded people.

→ Come hang out!

Until next week
-GH

Thanks for reading Verstreuen! 👋