Talk it through with Aurelius
LibraryAureliusThe problem
Aurelius · Work & Leadership
Knowledge + Guidance

I can follow a tutorial. Why does a real problem scare me?

You can execute. Give you the data, the notebook, the steps — you'll do it. What stops you is different: nobody handed you the map this time. In the tutorial, someone already knew the answer and built a path to it. Here, no one knows. You are the one who has to decide what the model should even be doing. Call this what it is. You are not afraid of code. You are afraid of being wrong in a way that has your name on it. That is not weakness — it is the actual job. Every person who applies these tools to real problems felt this exact fear the first time the map ran out. The fix is not more tutorials. You will not find the confidence by studying longer. You find it by choosing a small piece of the real problem, deciding what you think the model should tell you, and running it to find out if you were right.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The person already has the technical skill from the tutorial; what's missing is judgment and nerve to apply it, which coaching builds better than more instruction.
How the two dials adapt to you →
What’s really going on

The fear is not the model. It's that no one wrote down what the model should do here — that choice is yours alone. You already know how to run the steps. What you lack is not skill but a decision: what question are you actually answering? Make that choice first, then run.

🔒 What you’ll build togetherUnlock by starting
A moveWrite one sentence: what decision will change depending on what this model tells you? If you can't write it, you don't have a problem yet — you have a dataset.
A moveCut the real problem down to the smallest slice you could run today. Not the whole thing. One slice.
A moveBefore you run anything, write down what result you expect. Then run it. The gap between what you expected and what you got is where the actual learning is.
A moveName three things about the problem you don't understand. Go get an answer to one of them today — from a colleague, a search, anything faster than guessing.
A moveShow someone your rough first attempt before you polish it. Choose being seen half-finished over hiding until you feel ready. You will not feel ready first.

What changes unlock by starting

  • You'll have a working first version — rough, but built by you, not borrowed from a tutorial.
  • You'll know precisely which part of the problem you still don't understand, instead of a vague fog of doubt.
  • You'll stop waiting for someone to hand you permission or a map that doesn't exist.
  • You'll trust yourself to adjust the model as you learn, instead of needing to be right on the first try.
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.