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

The algorithm builds models faster. What's still mine?

You and your team built models. Now the algorithms build models too — faster, cheaper, without sleep. You feel this as a threat to your work. It isn't, but you have to look straight at what it actually threatens. It threatens a story you told yourselves: that building the model was the skill. It wasn't. The skill was seeing where an edge lived before anyone coded it, and knowing when it had quietly died. That kind of seeing sits in your heads, not in your repositories. So ask your team a plain question, out loud: which of you can still say why an edge exists, not just that the numbers say it does? Start there. Everything useful follows from that answer.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The reframe is simple to state but hard to live, so the page leans toward coaching moves the team can practice together rather than concepts to learn.
How the two dials adapt to you →
What’s really going on

The model was never the skill. Judgment was — knowing what edge is, why it exists, when it dies. That doesn't run on a GPU. Stop mourning the tool your team used to build things. Sit down together and name what each of you actually understands that the machine only imitates.

🔒 What you’ll build togetherUnlock by starting
A moveGather your team and list every edge you've found. For each, write one plain sentence explaining why it exists — no jargon allowed.
A moveStrip the reasoning from a strategy's output and hand it to a teammate. Ask them to guess why it works. If they can't, the model's speed won't save you either.
A moveAssign one person to try to break each edge using only faster tools than yours. Watch what actually survives.
A moveStop ranking each other by whose model runs fastest. Start ranking by whose judgment catches a failure first.
A moveHold a weekly meeting where the team argues about why an edge might die — not how to automate around it.
PractiseEdge Autopsy · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team can state, in plain words, why each edge exists — not just that the backtest holds up.
  • You stop racing the algorithm on speed and start competing on discernment instead.
  • The pod builds a habit of asking why before automating how.
  • You know which teammate to trust when a model's output looks wrong.

Related problems

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.