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 32 new additions to the Zettelkasten - here’s the three that stood out most to share with you:

🟨 Stop optimizing your constraints. Start becoming them.

🟦 Balance isn't a state you find. It's a practice you never stop doing.

🟥 A very productive way to miss the point

A few nights ago, I almost killed the newsletter. It was late, the doc was blank, I was tired, and one thought kept surfacing: I don't have to do this.

It felt like a reasonable excuse to let things drift for a week. But the longer I sat with it, the clearer the real problem became. It wasn't that I had too little time. It was that I kept operating like someone with more time than I actually had. A very different diagnosis.

Most productivity advice treats constraints as the enemy. Not enough time? Optimize. Not enough money? Raise more. Not enough help? Delegate, automate, eliminate. The goal is always to remove friction so you can finally become who you wanted to be.

I think that's backward.

Consider Muji: a company whose entire identity is a constraint made visible. No logos, no names, no decoration. They turned that limit into the most recognizable design language in retail. The constraint wasn't an obstacle to their identity. It was the identity.

Your constraint isn't just an obstacle to who you are. Often, it's the thing that authors you.

If you don't have unlimited time, you become someone who builds systems so time stops being the bottleneck. If you don't have unlimited energy, you become someone who designs rituals instead of relying on motivation. If you don't have unlimited attention, you become someone who curates aggressively, because not everything can come with you.

The constraint doesn't disappear. It becomes a design input.

This is what I keep returning to with Verstreuen, and now with doneOS. The newsletter was never going to survive on vibes. It needed a system, a way to turn scattered notes into a weekly artifact without requiring me to become a different person with different weeks.

That's the gift of a constraint: it forces you to design instead of drift. A wish for "more time" doesn't compound. An identity built around a system that solves real constraints does.

So the question isn't "How do I get rid of this limitation?" The better question is: What kind of person is this constraint asking me to become?

Because sometimes the thing you keep trying to delete is the most honest fingerprint of the work you're actually here to do.

 📎 Takeaway: Your real identity isn't what you'd do with no limits - it's what your limits made you do instead.

—🗃️—

I was sitting on a park bench the other day and realized something probably quite obvious about riding a bike that had never actually occurred to me before.

You are never actually balanced. You are constantly falling - slightly right, slightly left - and "balance" is just what it looks like from the outside when the corrections are fast enough. At slow speeds you feel every adjustment. At speed you stop noticing them entirely - which isn't stability, it's just correction happening faster than your awareness can track.

Stability isn't a state you find. It's a practice you never stop doing, whether you feel it or not.

A few issues ago I wrote about explore vs exploit - the idea that most progress lives in the push and pull between discovering new paths and optimizing the ones you're already on. As I was thinking about applying this to systems design, I found a word that Dee Hock - the man who built Visa - coined to describe this exact idea. The place between chaos and order where emergence seems to happen: chaord. A forest, a city, even jazz are chaordic systems.

A purely exploitative system is pure order: optimizing the same narrow map, extracting every last drop from a path you've stopped questioning. A purely exploratory system is pure chaos: interesting fragments pile up, nothing coheres, nothing compounds. Emergence requires moving between the two. Not balance. Switching. Constant correction, like the bike.

Most advice tells you to find the balance. That's the fortune cookie version - it tells you nothing about which way to lean.

For people who build systems, who have a process for their processes, the silent killer is almost always over-order. Structure accumulates, the creative engine quietly stalls, and it's hard to diagnose because it feels like discipline. For people who resist systems entirely, the problem runs the other way - exploration without exploitation never lands, and interesting ideas pile up without ever becoming anything.

Both are ways of avoiding the edge. Both feel justified from the inside.

That switching is where emergence lives. And a bike stays upright for the same reason a good system stays alive - not because it found a stable position, but because it never stopped responding to what's actually happening. Lock the handlebars and you fall. Stop switching between explore and exploit and the system calcifies or scatters. The correction is the stability.

Emergence means the system surprises its own designer. By definition. Instructions you imposed can never surprise you - you wrote them, you already know what they do. Chaos can startle you, but it can't build anything. Surprise only comes from the tension.

So the diagnostic is simple:
does it still surprise me?

A Zettelkasten that's stopped surprising you has become a filing cabinet. A newsletter that's stopped surprising you has become a content calendar. A company that's stopped surprising its founder is dying - possibly while the metrics look fine, especially while the metrics look fine, because clean metrics are exactly what over-order feels like from the inside.

Figure out which way you're falling. Correct. Repeat. 

 📎 Takeaway: The test of a living system isn't whether it runs smoothly - it's whether it still surprises you.

—🗃️—

As someone who reads honestly too many productivity books, I definitely idealize the goal more than I should.

I set goals. A lot of them. And then I set goals about my goals.

For a long time I thought this was a discipline problem. Too many objectives, not enough focus, bad prioritization. The standard productivity diagnosis. But the more I sat with it, the more I think the diagnosis is wrong - or at least, it's aimed at the wrong level.

The problem isn't the goals. It's what the goals are standing in for.

Modern life has hollowed out containers of meaning - religion, family, community, nation, meaningful work, self-sufficiency - and left a vacuum where they used to be. And so we fill that space with surrogate activities, artificial goals. Things that feel like they matter, that produce the sensation of progress and purpose, without being connected to anything.

The gym PR. The follower count. The streak. The quarterly OKR.
Not worthless - but not that real either.

Game designers understand this failure mode better than most - because they see it kill products.

A game with too many objectives isn't ambitious, it's broken. When everything is tracked, nothing feels meaningful. The player loses the thread of what they're actually playing for. Good game design doesn't solve this by improving the objectives - it solves it by forcing a harder question: what is the one thing this game is actually about? Everything else gets cut, or moved to the background. The score only means something if it's measuring the right thing.

The fix isn't better goals. It's recognizing which parts of life actually need them.

Connecting this to the ideas of explore vs exploit, goals are exploit mode - they extract value from a direction you've already chosen. But the parts of life that generate meaning - relationships, creativity, identity, the unplanned evening that becomes the thing you remember - are chaordic by nature and require some freedom from goals to explore. When you apply goal mechanics to these activities, you don't get meaning. You get a very efficient way of missing the point.

So the question isn't whether your goals are aligned with your values. It's whether your goals are actually your goals - or whether they're the placeholder you built when the real thing got harder to find.

Because a life full of surrogate activities isn't an ambitious life.
It's just a very productive way to avoid building a meaningful one.

 📎 Takeaway: Goals are exploit mode applied to a life. Some parts of life only work in explore mode - and those are usually the parts where meaning actually lives.

—🗃️—

Closing Thoughts

There's a pattern underneath all three of these notes that I didn't see until I put them next to each other.

Every piece is about a version of control that backfires.

Fight your constraint and it stays a constraint. Accept it as a design input and it becomes an identity. Lock the handlebars and you fall - the stability was never in the position, it was in the correction. Fill every open space with a goal and you optimize your way past the things that actually matter.

In each case, the tighter the grip, the faster you lose the thing you were holding.

Structure isn't the point. Structure is what makes the unplanned possible.
And the unplanned, it keeps turning out, is where the good stuff was.

Hit reply and tell me which of the three landed - or which one you think I've got wrong.

Until next week
-GH

Thanks for reading Verstreuen! 👋