Close to the Work

One reason labels like founder have always felt incomplete to me is that they often imply distance from the work. Strategy, positioning, delegation, high-level direction. I understand the need for those things, but I have never wanted them to become the whole shape of how I operate. I want to stay close to the work itself.

Why distance does not appeal to me

Some people want altitude as quickly as possible. They want to move up and away from execution. They want to talk about the system without staying near the actual points where the system either holds or fails. That has never felt right to me.

Part of it is temperamental. I trust judgment more when it has stayed in contact with reality. Another part is that I genuinely like the overlap where design, tech, strategy, and execution are still touching each other. That is where things feel alive. That is where trade-offs are visible. That is where you learn fastest.

What closeness gives me

Staying close to the work keeps me honest. It prevents me from hiding inside abstraction. It keeps my standards tied to actual outputs rather than polished language about outputs. It also sharpens taste. When you stay near the thing, you notice more. You see which details actually matter and which ones only sound intelligent from a distance.

This is one of the reasons builder fits more naturally than founder as a self-description. Builder implies contact. Founder can sometimes imply separation.

Why this matters for Duodode

With Duodode, I do not want to become the kind of person who only talks about offers, direction, positioning, and leverage while forgetting how the actual work feels when it is being made. I want the strategy to stay connected to the making. I want business sense and execution sense to inform each other instead of drifting apart.

That does not mean refusing scale. It means building scale on top of real contact rather than using scale as an excuse to detach too early.

Closeness as a learning advantage

Another reason I value this is that staying close to the work accelerates learning. If I remain near the execution layer, I see the friction directly. I see what skills are missing, where the system is weak, and what would actually move the outcome forward. Distance can protect ego. Closeness improves judgment.

That improvement matters more to me than the prestige of looking purely strategic.

The balance I want

I am not arguing for permanent smallness or refusing delegation forever. The point is not to romanticize doing everything by hand. The point is to preserve the relationship with reality that made the work worth scaling in the first place.

If I ever lose that, I start sounding more like a narrator of work than a maker of it. I do not want that version of myself.

Related

Being a Builder · Execution-First Mindset · Responsibility for Outcomes · Duodode · Designer vs Builder