Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can I run a model but not build one from scratch?

You know how to turn the crank. Inputs go in, the machine runs, numbers come out. This has let you believe you understand actuarial modeling. Then someone asks you to build the machine. You discover you only ever knew how to use one. This is not a skill gap you can shame yourself out of. No one builds a complete model in their head before touching a spreadsheet. The people whose models you run built them the same way. One assumption, one table, one test at a time. Slowly, with plenty of wrong turns. The overwhelm you feel is not proof you are unqualified. It is proof you are looking at the finished house and wondering how to lay every brick at once. No one lays every brick at once. Choose the first one.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
Half the struggle is not knowing how models get built piece by piece; half is the fear of starting before you can see the whole shape — both need direct address.
How the two dials adapt to you →
What’s really going on

You can run a model because someone else broke the problem into pieces first. Building one from scratch is the same work — you just do the breaking now. Stop waiting to see the whole structure before you start. Choose one assumption. Build it. Test it. That is the entire method.

🔒 What you’ll build togetherUnlock by starting
A moveWrite down the single output the model must produce — not the model, the number.
A movePick one assumption you already understand and build only that piece today.
A moveBuild a crude, wrong version of the whole model before refining any one piece.
A moveSet a timer for 25 minutes and build something before you let yourself research more.
A moveList every piece you think you need, then cross off whatever version one can live without.

What changes unlock by starting

  • A working, rough version of your model instead of a perfect plan for one.
  • A short list of the real pieces you need, instead of a vague dread of 'everything.'
  • Evidence, from your own hands, that you can build structure, not just run it.
  • Less time staring at the blank file, more time working inside it.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.