David Senra

Second, constant forcing functions, both real and manufactured.

I think this part is underrated.

Some were genuinely existential, like the 2008 cash crisis when SpaceX had funds for exactly one more Falcon 1 attempt.

Others, Elon created himself.

Aggressive public timelines that even he knew were ambitious.

Internal do or die milestones that felt real even when they weren't legally binding.

The forcing function prevents drift.

You can't endlessly study when a deadline, real or perceived, is bearing down.

Even an arbitrary deadline is better than no deadline because it forces decisions.

Third, direct technical engagement that bypasses organizational filters.

Andrej Karpathy, who worked for Elon at Tesla, notes that Elon spends about 50% of his time talking directly to engineers, not to VPs summarizing engineering work.

This sounds obvious, but it's unusual in the corporate world.

The CEO has to trust the CTO, who works through layers of managers to enact a vision.

Each layer is a hop where information is lost.

It's like a game of telephone.

By the time the technical reality reaches the CEO, it has been polished, caveated, and de-risked.

It is a summary of a summary with the inconvenient details removed.

SpaceX collapses the chain.

The CEO, CTO, VP, engineer layers become a single conversation.

By talking directly to the engineers, Elon removes the signal loss.