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

🟨 Why your transition doc won’t save them

🟦 The bathroom break productivity hack I didn’t expect

🟥 The fastest way to get smart people unstuck

I’m in the middle of handing off a project before PTO, and I’m watching something interesting happen in real time.

The person taking over is smart, capable, and fully briefed. Still, they’re stressed. Not because the project is too hard, but because leadership creates a kind of uncertainty no transition doc can convey.

I forgot I had to learn to stop treating uncertainty like a threat and start reading the soft edges as flexibility. I had to learn how to stop requiring every step to be defined before moving. I had to start trusting that if something changed, I could adjust.

But that shift doesn’t happen overnight.

And you can’t hand it to someone in a doc.

It’s made me realize that we use one word - uncertainty - to describe something that is really more of a spectrum.

On one end is pure uncertainty: where my colleague is right now. The terrain is unreadable. Every unknown feels equally significant. Every loose edge looks like a possible failure point.

I can share notes, context, risks, history, patterns, and decisions. I can explain what usually matters and what probably won’t. I can point to the places where the project tends to flex.

But there is a limit to how much certainty can be transferred.

Some of it has to be earned by experiance.

On the other end is too much certainty, which sounds like a good thing until you feel it. Too much certainty is when the future is so defined that there is no room left for alternative surprise. No discovery. Nothing unresolved enough to pull you forward.

That is not mastery.
That is a project that stopped teaching you anything.

Most of us think we want certainty.
But what I think we actually want is the confidence to not need it in the first place.

Eisenhower said it well: “Plans are worthless, but planning is essential.” Planning matters because it builds the mental model that lets you navigate when the plan breaks.

That’s the real lesson in this handoff. The briefs matter. The notes matter. The context matters. But the real handoff is not the information. It is the confidence to operate between certainty and uncertainty.

And that is the one thing I can’t fully give them.
The best I can do is stop pretending the map I have is one they can simply inherit.
They have to draw their own.

 📎 Takeaway: You can transfer notes, context, and the shape of the terrain. But certainty cannot be handed over whole. Judgment has to be built in experience.

—🗃️—

I started up a coding agent today then got up to use the bathroom, and had a weird realization halfway through: I was still making progress.

Not metaphorically. Literally.

The agent was still working. Code still getting written. Work moving forward - without me sitting there pretending my attention made it faster.

It feels small, but it’s been a real shift.

Most of my work used to punish stepping away. If you weren’t typing, deciding, replying, reviewing, or nudging something forward, the work stopped.

Now more of the work has momentum.

You can write the prompt, kick off the agent, start the upload, run the script, send the draft, trigger the research - then leave.

Coffee. Laundry. Walk. Bathroom. Another task.

The strange part is that this creates little pockets of time that are technically free, but still productive. Not because your break became optimized but because something else is carrying the thread while you’re gone.

And this changes the skill required to self-manage.

The people who get the most done won’t just be the people who work hardest. They’ll be the people who know what to put in motion before their attention moves somewhere else.

What can run without me?
What needs my judgment?
What should already be in motion before I focus somewhere else?

That’s the new rhythm.

Start the thing that can move on its own. Go do the thing only you can do. Come back when there’s a decision to make.

The skill is no longer doing every step yourself. It is knowing which loops can run without you and which ones still require judgment.

The bathroom break didn’t become productive.
It just stopped being a place where progress had to pause.

 📎 Takeaway: Work that runs without you is not laziness. It is leverage. The new skill is orchestration: knowing what to start, what to leave running, and where your judgment is actually needed.

—🗃️—

At the beginning of the year, I was on a different project.

It had all the usual pieces: documents in different places, people who understood different corners, decisions that made sense individually but not always together, and a few recurring problems everyone could feel but nobody had really drawn.

We kept talking around the system.
So one day I opened a blank page and started mapping it.
Not carefully. Not officially. Not with perfect context.

Just my best read of how the pieces connected, drawn quickly enough that I could share it before I talked myself out of it.

It wasn’t elegant. It was definitely not complete. Everyone agreed it had flaws.
But almost immediately, the conversation changed.
People stopped trying to explain the whole project from scratch and started pointing.

This part is wrong.
That should be split into two things.
This connects over here too.
We already solved something like this on another project.
That pattern won’t work here, but this piece might.

Nobody treated the map like the answer. They treated it like a working surface.

Something to react to, correct, borrow against, and improve.

Before the map, the project lived in everyone’s head slightly differently. After the map, we had one imperfect thing in front of us that could absorb everyone’s ideas.

That’s when I started to understand innovation differently.

It rarely feels like invention while it is happening. More often, you see a shape from somewhere else. You remember a pattern from a different project. You borrow a piece that almost fits and adapt it until it does.

The breakthrough usually isn’t a lightning bolt.
It’s someone noticing, “Wait, this looks kind of like that.”

But that only happens once there is something to look at.

A blank page asks too much. A rough surface asks just enough.
It gives people a place to begin and creates the conditions for everyone else to make it better.

You don’t need a perfect map.
You need one good enough that people can finally point at it and say, “Start here.”

 📎 Takeaway: Progress rarely starts with the perfect idea. It starts with a rough artifact that gives people something to react to, borrow from, and improve.

—🗃️—

Closing Thoughts

I’m heading into the next week with an agent still running, a colleague inheriting a project, and a few imperfect maps left behind.

The pattern is obvious now: the map was never the work.

The work is knowing when the map is good enough to move, when the agent is good enough to run, and when the person taking over has enough context to begin drawing their own version.

You can transfer notes, context and ideas
but judgment has to be built in experience.

That's what you can't transfer, shortcut, or wait till you are ready to start.
You build it by going anyway and building the map on the way.

🟨🟦🟥 Join the Workframe Community

Be part 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! 👋