I could make a good plan. Following it was another story.
First, I went looking
I wasn't coming from a productivity app I wanted to replace. I just knew I needed something. I searched for a tool that made sense for me, or someone with big ambitions who struggles to follow through. I couldn't find what I had in mind.
Planning came easily to me. I could keep refining a plan until it looked just right. But the execution didn't match. I thought that if I could make doing the work more systematic, instead of leaving it to intention, it would be worth building. So I started Dobahn.
What changed surprised me
I expected to get much better at execution. It improved to some extent, but not dramatically. The bigger change was that I started planning more realistically.
Dobahn puts what I planned beside what actually happened. Seeing those together helped me adjust what I expected of a day. The gap narrowed, not just because I did more, but because my plans got closer to reality.
What I expected to happen
What actually happened
I expected execution to catch up with the plan. Instead, planning became more realistic, while execution improved a little. And once a day actually went as planned, I followed through.
Building it has its own irony
There's an awkward part to this story: building a system meant to help with productivity can itself become a way to procrastinate. That has been part of it for me, too.
I've spent longer on Dobahn than I expected, and there is still a lot I want to finish. I have second thoughts sometimes. I'm still learning when to keep refining a plan, and when to get on with the work.
So this isn't advice from someone who has productivity figured out. It's a system I'm still building around something that has genuinely helped me: seeing the difference between what I intended and what I did.
The setup grew with the lesson
Once that difference became useful, I also needed a better way to hold the work around it. I needed to keep the larger areas of my life visible, organize projects inside them, turn projects into tasks, decide what could fit into a day, and record the focused sessions that actually happened. Each layer gave the next one enough context to be useful.
That is how Dobahn became more than a response to putting work off. It became a connected setup for moving from domains to projects, projects to tasks, tasks to focused work, and focused work back to a more honest plan. The planned-versus-actual calendar is what keeps that loop together.
If that sounds familiar
If making the plan comes more easily than doing the work, that's where Dobahn started, too. Take a look at how it works. And if something feels missing, I'd like to hear it.