/notes/ ·
My four walls and the search for momentum
I am not writing this to give advice, and I am certainly not saying this is the right or most effective way for anyone else to build. It is my experience and the method I ended up using when I had to force my own output.
I locked myself inside twelve square meters. The same four walls, the same routines, week after week. No events, no side projects, no artificial sense of progress from simply moving around. Just ultra-focus in a small room. That isolation was not a choice made out of comfort. It was a setup.
When you have somewhere else to be, you go there. Distribution is hard, so you do design instead. Onboarding is tedious, so you rewrite the landing page for the fourth time. You are still working. You are just working on the part that does not hurt. An easy exit sets your quality ceiling and it sets it low: if quitting is cheap, good enough to feel okay about is where you stop.
So I made leaving expensive. I could not lean on a team or a pipeline to cover a weak product. The product had to be strong enough to take its own space in the market, because that was my only route through the door.
The part I did not expect is that a small room does not run out of material. It runs out of surfaces. For the first weeks it has four landmarks: desk, bed, window, door. The day is a loop between them. Then the restlessness dies down and the loop turns into resolution. You notice that the way you sit at nine in the morning produces different thinking than the way you sit at eleven at night. That a problem you cannot crack at the desk sometimes solves itself standing in the two meters of floor next to it. There are, functionally, six rooms in this room, and you can move between them without opening the door.
The same thing happens to the work. When you cannot go anywhere you cannot go around anything either. A hard problem does not get parked, because there is no lot to park it in. You look at it on Tuesday, again on Wednesday, and by Thursday it looks different. Not because something new came in from outside, but because you finally ran out of shallow ways to look at it. Almost everything in the product I would call actually good came from the third or fourth time I was cornered by the same problem with nowhere to go.
The visible result is boring and it is the whole point. Every part of the product that was not fun to build got built anyway and then got polished. Error states. Empty states. The edge case that hits two percent of users and ruins their entire first impression. The plumbing nobody screenshots. Normally those are the parts you leave at seventy percent and promise yourself you will come back to, and you never do, because the fun work is always right there and nothing forces the choice. I had nothing else to do, so the boring thirty percent got finished. That is most of what people are reacting to when they say something feels solid. Not the clever part, the finished part.
I used to think focus was something you generate. Right playlist, right app, right morning routine, and the state arrives. It does not work like that for me. Focus is not produced, it is the residue of everything else being gone, and it arrived in stages that did not feel like productivity at the time.
First there is the itch. A week or two where your hand keeps reaching for a phone, a walk, a message, anything with a shape different from the problem in front of you. Nothing gets built. You just keep failing to leave. Then the itch runs out of targets and the reaching stops. That is the quiet part and it is uncomfortable in a way I had not felt before: no input coming in and no way to fake motion. And then the work expands to fill the space. Not dramatically. You look up and it has been six hours and you were not fighting anything. The problem got bigger than the room, which is exactly what you needed, because now it is the most interesting thing in your field of view by default. It is not willpower at that point. There is nothing left to resist.
The failure mode is real too. Some days you go down instead of in. Same room, same silence, no work. I do not have a fix for that one. It passes.
The other thing nobody tells you is that the moment something starts working is not the moment it becomes a product. Those are months apart. Working means it does the thing when I run it, in the right order, with the right input, on my machine, with me knowing which button not to press. That is a demo, and a demo is a performance in which I am part of the performance.
It turns into a product somewhere in the boring middle, and the shift is always the same: every place I was quietly holding it up gets replaced by something that holds it up on its own. The step I always did by hand becomes a step it takes by itself. The failure I always noticed and fixed becomes a failure it reports on its own. The instruction I always gave in person becomes something the screen says. You can measure it in how much of you is still in the loop. At the start it is all of you, and the work is removing yourself from it piece by piece until the last piece is gone. That is the actual job and it is most of the ten months. Not the idea, not the first version that worked.
So the door has two locks. It works means someone who has never met me can use it and get value without a call, a demo or an apology, and that is the easy half; plenty of things work once, for one user, with the founder watching. It scales means the thousandth user gets the same result as the first and it does not cost me a day of my life to deliver it. That is the lock that actually opens. A product that only works when you are personally in the loop is not a way out of the room. It is the room, with better furniture. You have swapped a small apartment for a job you cannot quit.
At this stage that is the only metric I have. Not followers, not funding, not hours logged, not how productive the week felt. All of those move without the door moving. A good week and a wasted week look identical from the inside, and the only difference is whether the product got closer to standing on its own. Everything else is weather.
Building alone forces a specific kind of clarity. You cannot afford to wander around asking what happens next or hope direction finds you. You pick your angle, commit to it completely, and build the thing until it stands.
People assume from this that I want to work alone. That is not it. The team just has not been found yet. Alone was the condition I had, not the thing I was after, and I would not recommend anyone choose it on purpose if they have the alternative.
The room was never the point either. It is the ticket in. The target is what happens on the other side of that door. The product out in the world working without me, and then finding my crowd: the people, the team, the momentum where everyone is pushing at full speed.
But you do not get into that room by turning up at it. A seat in any community worth being in is earned by having done things, and the currency is what you built, not what you are planning. Showing up with a pitch gets you a conversation that ends when the coffee does. Showing up with something that works gets you the other kind. That is the order, and I do not think it can be reversed: you do the work first and the room opens after, not before.
I built in isolation so I could earn my place in that room.