Problem guide
New hires take months to learn the process
New hires take months to learn the process because the process is not written anywhere; it lives in the heads of a few experienced people and in workarounds nobody explains. The fix is making the real process visible and building it into the tools people use every day, so the right next step is shown instead of remembered.
What it usually looks like
A new billing coordinator starts on a Monday and sits beside the person who has done the job for years. She learns that some customers need a purchase order number on the invoice, some need it emailed to a second address, and one needs the hours split by building. None of it is written down. Her mentor explains each rule when it comes up. Two months in she is on her own, and an invoice for a large account bounces back because nobody mentioned that customer's portal.
Signs you have this problem
- New hires keep interrupting the same one or two veterans with questions
- Training is mostly shadowing someone, and every mentor teaches it differently
- Mistakes by new people show up weeks later, in billing or with the customer
- Written procedures exist but describe how things worked years ago
- Experienced staff say it is faster to just do it themselves
What usually causes it
- Most of the real work is handling odd cases, and the rules for those live only in memoryThe exception swamp
- Knowledge passes person to person, and details drop out at every handoffThe handoff gap
- The process includes retyping between systems, with unwritten tricks for doing it rightThe re-entry trap
What to try this week
- Write down the questions new hires askFor the next new hire, keep a running list of every question they ask and who answered it. The list shows exactly what your documentation is missing.
- Map one workflow as it really runsPick the workflow new hires struggle with most. Walk through it with the person who does it best and write every step, including the workarounds, not the version in the old manual.
- Separate the routine from the exceptionsMark which steps happen every time and which only happen in odd cases. Teach the routine path first, and keep a short list of known exceptions with who handles each.
- Name one go-to person per topicInstead of everyone asking the same veteran, assign a named contact for each area, and give them time for it.
- Check a new hire's work earlyReview a new person's first several jobs or entries within days, not weeks, so errors are caught before they reach billing or the customer.
Where do-it-yourself stops
These steps capture what people know and make training more consistent. They do not remove the hidden steps themselves, and written guides drift out of date as the work changes. A lasting fix puts the process into a tool built around your own workflow and systems, so the next step is shown on screen and the retyping tricks are gone. That is what a Workflow Spec designs.
Questions people ask
Why does it take so long to train new hires?
Because much of the process is undocumented and lives in a few people's heads, especially how to handle the cases that do not fit the normal path.
Will better documentation fix it?
It helps, but documents drift out of date. It works best when the tools themselves guide people through the steps.
How do we measure ramp-up time?
Track how long it takes a new hire to handle their work without help, and how many of their errors are caught downstream. Use your own hires as the baseline.
Is the problem our hiring?
Sometimes, but if every new hire struggles in the same places, the process is the problem, not the people.
What if our best people do not have time to train?
That is a sign the knowledge is too concentrated. Capturing it once, in writing or in a tool, frees them from answering the same questions again.