Engineering, Leadership, Reality

Long-form writing on systems, people, and the predictable chaos they create.

startupsleadershipgovernanceengineeringexecutionincentivesproductteams

The Board Is Not Your Enemy, Unless You Make It One

Boards don't become adversarial by default. They become adversarial when founders avoid structure and force governance to emerge through intervention instead of design.

When Structure Fails, Conflict Fills the Gap

Most conflicts between technical leadership and business development aren't personality clashes. They're structural failures caused by unclear authority, blurred domains, and leaders who won't respect boundaries.

It's more important to have a motivated employee than a perfect product.

If you want ownership, you have to give people the authority to make decisions; even when you think they might choose wrong.

The Myth of 'Build It and They Will Come'

A startup without hustle defaults to building in the dark, convinced features replace customers. They don’t.

ESOPs Are Not Remuneration

ESOPs get sold as part of your compensation, but structurally they're not pay. They're discretionary, illiquid side-bets that shift risk onto employees without giving them real value or power.

Why Founders Struggle With Letting Go

Founders often believe their personal involvement is what keeps the company alive. That may be true early on, but it becomes the bottleneck that stops the organisation from maturing. Letting go isn’t emotional; it’s structural.

The Cost of Technical Debt Isn’t Technical

Technical debt shows up in code, but its real impact is on how people work, think, and interact. The cost is paid in trust, morale, and predictability long before anyone starts refactoring.

Startups Don’t Fail from Lack of Vision; They Fail from Lack of Structure

Most startups don’t die because they lack big ideas. They die because they never build the structure needed to turn those ideas into reality.