People Don't Fail — Strategies Fail
In 1997, early in his career as a qualified civil engineer, Julian Pencilliah went through a crisis that would reshape how he thought about risk, planning, and what failure actually means. The instinct in a moment like that is to treat it as a verdict on yourself — proof that you aren't cut out for whatever you were attempting. That instinct is almost always wrong, and it is also almost always unhelpful.
The more useful frame, and the one that eventually pointed toward a career in venture capital rather than engineering, is this: people don't fail — strategies fail. A plan can be built on an assumption that turns out to be false, a timeline that was always too optimistic, or a structure that couldn't absorb the shock it eventually met. None of that is a statement about the person who built the plan. It's a statement about the plan.
This distinction matters because it changes what you do next. If you believe you failed, the only available response is to doubt yourself more carefully next time — which tends to produce caution, not better judgment. If you believe the strategy failed, the response is diagnostic: which assumption broke, and what would have had to be true for the plan to hold? That question is answerable. "Am I good enough" is not.
It's also the reason a background in engineering translates more directly into venture capital than people usually expect. Engineering trains you to treat a failure as a structural question first — where was the load miscalculated, where was the tolerance too tight — before it's ever treated as a personal one. Carrying that habit into capital allocation means a bad outcome gets interrogated for what it teaches about the next structure, rather than filed away as a reason to take fewer risks altogether.
One should always mitigate the risk of a decision before the decision is made, not after it's gone wrong. That isn't a guarantee against hard years — 1997 still happened. But it's the difference between a hard year that ends a career and one that redirects it.
Becoming a Student of Your Own History
Most people treat their own past as a story that's already finished — something to explain or defend, rather than something to actually study. I've found the more useful habit is the opposite: to become a student of your own history, the same way you'd study a market, a competitor, or a case at business school.
That means going back to a decision — a deal taken, a partnership formed, a year that didn't go the way it was supposed to — and asking the question most people skip: what was the actual mechanism? Not the flattering version, and not the self-punishing version either. Just the mechanism. What information did I have at the time. What did I get right for the wrong reasons. What did I get wrong that I could have caught. Sophistication, in the way I use the word, isn't about sounding polished. It's the discipline of separating what worked from what merely happened to work — because those two things get filed under the same memory if you're not careful, and only one of them is repeatable.
This is harder than it sounds, because hindsight is generous in exactly the wrong direction. It smooths outcomes into narratives, and narratives are comfortable. A case study isn't comfortable. It's specific, it's a little clinical, and it usually surfaces at least one thing you'd genuinely do differently. That discomfort is the point — it's where the actual lesson lives, not in the retelling.
I'd rather build forward from an honest audit of my own decisions than from a curated highlight reel of them. Every stage of building Quantum Capital Fund — the ones that compounded and the ones that cost time — is raw material for the next decision, provided I'm willing to look at it plainly. That's the whole practice: not reliving the past, but debriefing it, the way any serious operator debriefs a quarter, a launch, or a fund.
It's a small shift in posture, but it changes what you're actually optimizing for. You stop trying to be right about yesterday and start trying to be accurate about it — which, it turns out, is the far more useful thing to be.