When I moved to Rotterdam last year, I started three new things in four months.
A new research project.
A new side concept I never shipped.
A new approach to content I mapped out in a notebook and never opened again.
Each one felt like momentum. Each one was actually a reset.
This is what happens without a system: you don’t stop working.
You just keep starting.
And every time you start something new, you pay the full initiation cost: The energy of figuring out what it is, what it’s for, who it’s for, and how it works.
You pay that cost in full. Every time.
And every time you do, you’re back at zero.
The worst part? It feels productive.
Starting things feels like progress. The notebook full of new ideas feels like momentum. But it’s a treadmill, a lot of movement, no distance covered.
The opposite of this isn’t discipline.
It’s not willpower or a stricter schedule, either.
It’s a system. It’s a base.
A system gives you something to return to instead of something new to begin.
When I did post a diagram during those quiet months, it barely cost me anything. I already knew the format. I already knew what made it work, how to structure the concept, what to label, where the hook goes, and what gets bookmarked versus what gets scrolled past.
The diagram got better every time I made one.
That compounded quietly, even when I wasn’t paying attention to it.
The new things I started? Gone.
No base, no compounding, no return.
Here’s what I think is actually happening when we fall into this pattern.
We live in a culture that rewards building.
Shipping.
Iterating fast.
Moving on.
And those things are not wrong: but they are incomplete.
Because you can build forever without ever asking whether what you’re building adds up to anything.
Most people never stop to answer two questions:
What am I actually trying to create?
How do all these pieces fit together as a whole?
Without those answers, every new thing you build is just another thing. It doesn’t compound. It doesn’t reinforce the last thing. It doesn’t move you closer to anything in particular. It just sits next to everything else.
The most useful thing I did when coming back to databites.tech wasn’t making a new diagram. It was stepping back and mapping what databites.tech actually is: what the three arms are, how the weekly flywheel works, what the offer looks like, what the five-year shape of it is.
Treating it as a project with a structure, not just a stream of outputs.
That’s the work that doesn’t feel like work. The planning, the architecture, the articulation of where you’re going and how the pieces connect. And it’s exactly the work most people skip because it’s slower and less visible than shipping something new.
Build less. Design more. Then build with direction.
For me, that answer was obvious once I stopped ignoring it. That’s what databites.tech is built on now: one format, kept and compounded, not replaced.
— Josep
Are you still here? 🧐
👉🏻 I want this newsletter to be useful, so please let me know your feedback!
Before you go, tap the 💚 and the restack buttons at the bottom of this email to show your support—it really helps and means a lot!
What would change if you spent one week planning instead of building? Hit reply.👇🏻