Becoming a technical founder after a career in engineering
On delegation, focus, bottlenecks, and the uncomfortable shift from engineering depth into founder-shaped thinking.
Becoming a founder didn't feel like starting something new. It felt like slowly realising that the way I had learned to be valuable wasn't going to work anymore.
As an engineer, things were simple. You build. You solve. You go deep. You become the person people rely on when things get difficult.
That identity sticks. Even when you move into leadership, you don't really let go of it. You just express it differently. You review instead of write. You guide instead of implement. But you still know you could do it yourself if needed.
That's the problem.
You become the bottleneck
There's a moment that keeps repeating itself. Something needs to be done.
And the immediate thought is: I could just do this myself, it would be faster, it would at least be more thorough.
And sometimes, that's true. That's what makes it dangerous.
Because if you follow that instinct consistently, something else happens. You don't scale. Everything depends on you. Everything waits for you. Everything improves because of you, and only because of you.
Doing things well yourself stops being a strength. It becomes the constraint.
Delegation is not what I thought it was
I used to think delegation was a practical skill. It isn't. At least not for people who care too much.
It's not about assigning tasks, tracking progress, or checking results. It's about letting go of things you know you could do better, or differently, or faster.
It means accepting that someone else will approach it in their own way, and it might not match your internal standard immediately. That's still okay. That's the part that's hard.
Delegation isn't about trust. It's about accepting imperfection without stepping back in.
You can build forever now
This part changed recently. I feel am constantly writing about this.
Before, you'd stop because you ran out of time. Or energy. Or ideas. Now you stop because you choose to.
With better tools, faster iteration, and almost no friction to prototype, ideas don't stall. Execution isn't the bottleneck. Momentum is easy to maintain, provided you can manage your personal resources.
There is always one more thing to improve. One more feature that makes sense. One more experiment worth running.
As a founder, this is amplified. Because everything feels important. You are building for yourself. And the distance to becoming profitable feels completely in your hands.
The ability to build faster didn't just increase output. It removed the natural stopping points.
And if you're not careful, you just keep going.
Focus becomes exclusion
Focus used to mean going deep. Now it also means not going deep on a lot of things that could work.
That's uncomfortable, because those things don't look like bad ideas. They look like interesting directions, logical extensions, things you should explore at some point.
Saying no to them doesn't feel like discipline. It feels like leaving value on the table.
Focus isn't about intensity anymore. It's about what you're willing to ignore.
Winning is less clear
As an engineer, you get feedback quickly. Things work or they don't. You optimise for correctness, performance, and elegance.
As a founder, that clarity disappears. You can spend days or weeks on something and only later realise it didn't matter, no one wanted it, it was too early, or it solved the wrong problem.
Progress becomes harder to measure.
You stop asking “Is this correct?” and start asking “Was this worth it?”
And you don't always get an immediate answer.
The guilt doesn't go away
One thing I didn't expect: how hard it is to not work.
There is always something to do. Something to finish or start. Something to fix. Something to think through. And when you care about what you're building, stepping away doesn't feel good. It feels like you're leaving something unfinished. Like you're falling behind.
That feeling is familiar. It's the same pattern.
If you don't define what “enough” looks like, you don't stop.
You just pause. And keep thinking.
You don't really transition
I thought this would feel like a clean shift. Engineer → founder.
It doesn't. It feels messy. Some days, I'm so deep in code that I look up and realise the cafe is closing and it's dark outside. Other days, I'm making decisions without enough information, thinking about direction instead of implementation.
And sometimes I'm doing both, and neither as well as I'd like.
You don't become a different person it seems. You just keep switching between versions of yourself.
Closing
Becoming a technical founder didn't make engineering less important. But it made it insufficient on its own.
The instinct to step in, fix things, and improve everything doesn't disappear. But following it blindly stops working.
Sometimes, more often than I would have thought, the best move is not to optimise, not to step in, not to build the next thing. Even when you can.
Let that sink in.