David Senra
👤 SpeakerAppearances Over Time
Podcast Appearances
Running an organization that constantly questions requirements, deletes parts, and accepts visible failures requires something that can't be built through iteration.
An engineering process that treats failure as data only works if the engineers themselves believe it.
A system that pushes to the edge of what's possible only survives if the people doing the pushing can handle the intensity.
The practices described here are the mechanism, but they're powered by something else entirely.
And that goes to his next subheading, which is the people.
And so Max writes, back to my original point, the practices I've described so far aren't secret.
The standard answer is organizational inertia, bureaucracy, risk aversion, et cetera.
And yet there's truth to all of these, but it's not the whole story.
The answer is that strategy doesn't exist in isolation.
The same playbook in a different environment would produce different results or nothing at all.
You can't copy strategy without transplanting the conditions that make them work.
A fail-fast culture needs people willing to fail visibly.
A first principles approach requires people willing to question experts.
Skip-level truth-seeking requires people willing to deliver bad news directly to the CEO.
The variable I've been circling around is people, not in the bland HR sense of our people are our greatest asset.
Who shows up, what they believe, and what behaviors they're willing to accept from each other.
It built a system that attracts, retains, and amplifies a particular kind of engineer while filtering out everyone else.