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

How do we spot who'll ramp up versus flame out?

You think the problem is your judgment. It isn't. The problem is you have no written standard for what 'ramping well' looks like, so every hire is a fresh guess, and every guess feels like judgment because you have nothing else to call it. A resume tells you what someone did elsewhere, for someone else, under conditions you don't share. An interview tells you how well they talk about work. Neither tells you how they will act under your conditions, in your first ninety days. You already knew this. You hired anyway, hoping instinct would cover the gap. It won't, and it hasn't. The fix is not a better interview question. It is deciding, before anyone starts, exactly what actions prove someone is learning and adapting — then watching for those actions instead of a feeling. Do this with your team, not alone. Four eyes catch what one pair misses, and a shared standard stops arguments from becoming guesswork later.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The team needs a short, concrete framework for defining ramp markers, but the real work is the discipline of building and using it together — so guidance leads.
How the two dials adapt to you →
What’s really going on

You cannot read a person's future in a resume or an hour of interview talk. Stop trying. Build, with your team, a written picture of what good ramping looks like at day 30, 60, and 90. Then judge every new hire against that picture — not your gut, not their promises.

🔒 What you’ll build togetherUnlock by starting
A moveWrite down, as a team, three observable actions a new hire must take by day 30 that prove they're learning — not feeling settled, but doing something specific.
A moveDefine day 60 and day 90 markers the same way, before the person's first day, not after trouble starts.
A moveSet a short weekly check where you compare the hire's actions against the list, out loud, together — not a vague 'how's it going.'
A moveName who on the team is responsible for raising concerns early, and agree they must say it the day they see it, not wait to be sure.
A moveDecide now, in writing, what you will do if the day-45 picture doesn't match — so you don't invent reasons to wait when the moment comes.
PractiseThe 30-60-90 Ledger · a Pod of 4 · 30 min

What changes unlock by starting

  • A written, shared standard for 'ramping well' that replaces gut feeling.
  • Trouble spotted by day 30, not quietly tolerated until day 90.
  • Less disagreement among you about whether someone is actually working out.
  • A team habit of judging by action taken, not promise given.
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.