Talk it through with Aurelius
When your new hire is still lost after 90 days
Three months in, your new hire still can't work independently — still asking basic questions, still needing hand-holding, still not contributing at the level you hired for. The team's frustrated and starting to think it was a bad hire. But the same thing happened with the last one.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
A team-onboarding problem, worked together. Mostly the craft of building an onboarding system (knowledge); a little honesty that it's the system, not the hire (guidance).
How the two dials adapt to you →What’s really going on
When a new hire is still lost after 90 days, the reflex is to blame the hire — but when it keeps happening, the problem is your onboarding, not your hiring. A team with no deliberate way to bring people up to speed leaves every new person to figure it out by osmosis, which is slow and unreliable. We fix the system that keeps producing lost new hires: what they need to know, who owns getting them there, and how you'll know it worked.
🔒 What you’ll build togetherUnlock by starting
KnowledgeWhen it's the onboarding, not the hire
KnowledgeOnboarding by osmosis doesn't work
KnowledgeWho owns getting a new hire productive
A moveName what your last two new hires struggled with — the repeat is your onboarding gap.
A moveAssign one person to own each new hire's first-90-days ramp, with a clear "independent" bar.
PractiseThe onboarding teardown · a Pod of 6 · 45 min
What changes unlock by starting
- New hires reach independence on a predictable timeline.
- The team stops blaming hires for an onboarding gap.
- Someone owns each new person's ramp.
- You can tell when onboarding worked — and fix it when it didn't.
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.