Discussion about this post

User's avatar
ShowMeTheValue's avatar

Reading the first paragraph, you could have been talking directly about me 🤣

But as I used to build and run models in my engineering past, I know exactly what you mean. The model is ultimately just a bunch of equations, intentionally intended to aggregate, approximate and simplify reality by stripping out "unnecessary" detail. What is "unnecessary" is often down to the subjective assessment of the modeller.

The model can't, by itself, know whether the output is sensible. Most of my time as a modeller was spent trying to work out why the model wouldn't run or converge cleanly, or where runtime was being lost, or checking how the model's controllers had matched target without violating my imposed constraints. Only then would I look at the actual outputs and try to draw inferences, and that was often the quickest and easiest part of the job.

With financial models, I try to take the same approach: Are there any strange and difficult-to-justify implications of your model, like inconsistencies between revenue, market share and size of total addressable market? If you constrain total market size and market share, what kind of revenue growth does that imply?

Do you have any anomalies in the returns on capital implied by your modelled results by trying to match revenue, earnings and operating profits? Are your implied tax rates reasonable? Can you tally your modelled earnings and cash flow with your balance sheet? Are you even looking?

If you are running your model without even looking at at these factors, you aren't checking your model is producing viable results. But that doesn't mean your model is wrong.

As George Box said, all models are wrong, but some are useful.

No posts

Ready for more?