Most businesses don’t fail because of “competition” or “bad ideas.”
They fail because of unmanaged risk.
I know, because I spent years flying Navy helicopters where risk was the difference between life and death.
Here’s why I started Pre-Mortem Labs 🧵
I’ve been off X for a bit — finishing Aviation Safety School.
The timing has been good. Stepping back always reminds me why I started building Pre-Mortem Labs in the first place.
The entire course revolves around one idea: small risks compound. The sooner you identify them, the cheaper they are to fix.
That mindset applies in the cockpit and in business. Whether it’s a checklist or a company, prevention always beats reaction.
Back to building.
The deeper I dig into the historical side of Christianity, the more tension I feel between evidence and faith.
The evidence gives the story weight — names, dates, archaeology — but it doesn’t remove the need to believe.
At some point, the search stops being about proving something and starts being about trust.
I’m still reading, still wrestling, but the more I learn, the harder it is to call it blind faith anymore.
While refining the Pre-Mortem Labs framework, I keep circling one silent risk: relying on handshakes and memory instead of documentation.
Verbal agreements feel efficient in the moment — they save time, skip email chains, and keep things “moving.”
But when expectations blur or leadership changes, those shortcuts turn into finger-pointing and lost trust.
Documentation isn’t bureaucracy. It’s clarity. It’s proof.
I’m building systems that make recording decisions effortless, so good intentions don’t become expensive misunderstandings.
How do you balance speed with documentation in your work?
Building systems to prevent failure keeps exposing how easily “flexibility” turns into scope creep.
It starts with good intentions — small tweaks, quick add-ons, “just one more thing.��
Before you notice, structure starts bending under the weight of small compromises.
I’m working on ways to flag those shifts early so the framework stays flexible without losing focus.
How do you keep projects adaptable without letting them drift?