I grew up in construction. Long before I studied risk formally, I learned from job sites that projects are built through judgment—by people making decisions with imperfect information, changing conditions and consequences that are rarely confined to a single cost or schedule number.
What changed for me later was learning that uncertainty did not have to remain something people simply described as “high,” “medium” or “low.” It could be examined systematically. Assumptions could be made explicit. Different outcomes could be represented as ranges rather than single forecasts. Alternatives could be compared. And as new information arrived, the analysis—and therefore the decision—could change.
That idea has stayed with me throughout my career: a project plan should not become more certain merely because it has been approved. Construction continuously produces new information. Good project decision-making requires us to observe that information, test what it means, and update our view when the evidence changes.
Operating on real projects added an equally important lesson. Analysis earns its place only when it can improve the decision. A model that does not help determine contingency, identify what deserves further investigation, distinguish among alternatives, show when a forecast is no longer credible, or indicate when intervention may be warranted is analytical activity—not decision support.
That is why I created TRAVO.
The practice begins with the decision rather than the software. We ask what must be decided, what is known, what remains uncertain, what alternatives are available, and what evidence could materially change the answer. Risk analysis makes the uncertainty visible. Decision analysis makes the alternatives explicit. The objective is to identify the course that best serves the decision-maker’s objectives under the conditions actually facing the project.
I believe independent analysis also carries a responsibility. The analytical answer should be traceable to evidence, assumptions should be visible, limitations should be stated, and the person responsible for the work should stand behind it. TRAVO owns that rigor. The decision remains with the decision-maker.
That is the practice I wanted to build: one in which uncertainty is not hidden behind a single forecast, analysis is not performed for its own sake, and better information leads to better decisions.
— Dr. Karim S. KaramPrincipal, TRAVO
