Why Goal Execution Is a More Teachable Skill Than Ambition
Ambition is usually treated as the scarce ingredient — the thing some people have and others don't, and the thing a mentor is supposed to instill. In practice, it's the wrong thing to teach, because it's the wrong thing missing. Most people who struggle to make progress on a goal aren't short on ambition. They're short on a workable mechanism for turning a goal into a sequence of actions they can actually evaluate.
That's the premise behind the philanthropic program Julian Pencilliah runs, reaching an estimated 25,000 students per quarter. The curriculum doesn't lead with motivation. It leads with KPI-identification — the practical skill of deciding, before you start, what specific, observable thing will tell you whether an action is working. Without that, "trying harder" and "doing something" become indistinguishable, and progress is impossible to measure until it's too late to correct course.
The second pillar is proactive versus reactive thinking, which sounds like a mindset shift but is really a sequencing discipline: deciding what you control and acting on it before circumstance forces a response. Reactive thinking isn't a character flaw — it's what happens by default when nobody has taught you to look for the decision point before the deadline arrives.
The third is the hardest to teach because it's the least visible: recognizing and moving past self-defeating mentalities. These rarely show up as dramatic self-sabotage. More often they show up as a plan quietly getting smaller and smaller until it's no longer ambitious enough to fail at — which feels safe and accomplishes nothing.
Each participating student receives a free copy of The Jetstream of Success, not as a reward for finishing the program but as a reference for afterward — the habits above only compound if they outlast the classroom. Teaching ambition would have produced a good afternoon. Teaching a mechanism is what's meant to produce a different decade.
People Don't Fail — Strategies Fail
When something goes wrong, the instinct 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. But it's the difference between a hard year that ends a career and one that redirects it.