Getting a new hire client-ready

The first few weeks of a new job are rough. Lots of names, lots of tools, and a nagging feeling that everyone else knows something you don’t.

I wanted our new hires to skip as much of that as possible.

The old way

For a long time, onboarding was mostly shadowing. Sit with someone, watch, ask questions, hope it sticks.

It works, sort of. But it depends on who you shadow and what happens that week. Two new hires could have totally different first months.

What I built instead

Two things, working together.

• A knowledge base. The answers to the questions people kept asking, written in plain words and organized so you can actually find them.
• A hands-on training sprint. Short lessons that build on each other, with real practice instead of just reading.

The goal was simple: take someone from zero to client-ready, with a clear path instead of a pile of links.

Hands-on beats reading

People don’t learn software by reading about it. They learn by clicking around, getting stuck and getting unstuck.

So every lesson ends with something to do. Not a quiz. A task that looks like real work.

The part that still matters most

Docs and lessons get people most of the way. The last mile is still a person.

I onboard and train new coaches and support staff myself, and the best moments are always side by side. Someone shares their screen, gets stuck, and we work through it together. That’s when the knowledge base stops being a document and starts being theirs.

What I’d tell anyone building onboarding

• Write down the questions new people ask. That’s your table of contents.
• Make it hands-on. Every lesson should end with doing something.
• Keep a human in it. The material sets the path. People make it stick.
• Update it every time someone gets confused. Confusion is free feedback.

I’m still tuning it. Every new hire finds a gap I didn’t see. That’s not failure. That’s the next edit.