Standards & Operating Philosophy

How I lead, decide, and hold a standard.

Three convictions, formed over a decade of pricing risk, managing capital, running teams and portfolios, and building the models and processes decision-makers actually rely on.

01

Systems outlast any single decision.

A well-built model answers one question. A well-built process answers that question every time it comes up again, without me in the room. Over a decade, I've built the scorecards, controls, and reporting rhythms that let a team make good decisions repeatably, not just once. The individual number matters less to me than the system that keeps producing good ones.

02

Risk is information, wherever it shows up.

From pricing insurance risk in Nairobi to stress-testing a resort's construction budget before the first shovel broke ground, I have spent over a decade treating uncertainty as a signal to decode, not a threat to manage around. Operational risk, market risk, execution risk: it's the same instinct applied to different terrain, and the downside case is always where the real strategy reveals itself.

03

Precision is respect, at every level of an organization.

Whether I'm presenting to an eight-member investment committee, briefing a board on governance exposure, or walking a junior analyst through where their model broke, the people in the room deserve the same standard. Getting the assumption right matters. Getting the process right matters. I hold the line on the details that determine whether a decision can be trusted, not just the analysis behind it.

HOW THIS SHOWS UP IN PRACTICE

Standards I hold across every engagement.

Downside cases are mandatory

Every plan I deliver, financial or operational, includes a stress case built with the same rigor as the base case, not a caveat added after the fact.

Assumptions are stated plainly

Whether behind a valuation or a process redesign, the reasoning sits in plain view, open to challenge, never buried where no one thinks to look.

Results are attribution-checked

A performance claim, financial or operational, gets decomposed to its actual drivers, so a result can be explained, not just reported.

The audience shapes the delivery

A board gets a different document than an investment committee, which gets a different document than a first-time entrepreneur, same standard, different translation.

None of this is theoretical for me. It's the difference between a decision that survives being challenged in a room full of skeptics and one that doesn't. If you're bringing me in, that's what you're actually getting: someone who has already stress-tested the plan, the process, and the number before you have to defend any of them.