From New Hire to Plex-Confident in 30 Days


ERP implementations don't usually fail on the software. They fail on Monday morning, when a new hire logs in for the first time, stares at the launch page, and quietly decides to keep using the spreadsheet.

I've watched this happen for years. The system goes live, the consultants leave, and the people who actually run the plant get about twenty minutes of "here's how you log in" before they're expected to be productive. Then everyone acts surprised when the new hire routes around the system by the end of week one.

It doesn't have to go that way. The fix is not a longer training class. It is a 30-day path with a clear job for each week. Week one, the new hire learns to move around. Week two, they learn their own job's screens. Week three, they learn quality and traceability. Week four, they work alone while someone watches. At the end of it, you have an operator who uses the system because it works for them, not because someone told them to.

Adoption is a navigation problem before it's anything else. So start there.

Listen to the Podcast

Week 1: Learn to Move Around First

Before a new hire touches a single transaction, teach them to navigate. That sounds basic, and it is. That is the point. A new Plex user who can log in confidently, find their launch page, read the navigation bar, search for a record, sort a display grid, and save a favorite is a user who will actually use the system. A user who can't do those things by the end of day one will route around the system by the end of week one.

Navigation is the cheapest skill in the building to teach. It takes about an hour of structured walkthrough on the things people touch every single day. Not a classroom. Not a week off the floor. An hour, at a workstation, with the new hire driving.

Here is the walkthrough, in order. First, logging in, including the Azure or Okta sign-in most companies actually use. Second, the launch page and what each section is for. Third, the navigation bar: menu, messages, history, favorites, setup, help, and the menu search with Ctrl+M. Fourth, finding records with search and the % wildcard. Fifth, reading the display grid and the action bar. Sixth, saving favorites so the tenth visit is as fast as the first.

That is the whole list. Six skills. Teach them in that order, and have the new hire do each one themselves before you move on. Watching someone click is not learning to click.

I covered these Day One skills in detail in the navigation post. The list hasn't changed, because the job hasn't changed.

By the end of week one, the test is simple. Hand the new hire a login and walk away. Can they get in on their own? Can they find their launch page, search for a record with the % wildcard, sort a grid, and save a favorite? If yes, they are ready to learn their job in the system. If no, stop and fix it now. Do not send them into week two hoping navigation will sort itself out. It won't.

Week 2: Learn Your Own Job's Screens

Week two is about the transactions the new hire actually runs. Not the whole system. Just the screens for their job, in the order they use them.

Teach these from the checklist at the point of work, not from memory. The veteran walks the job with the checklist in hand. The new hire follows the sequence on the paper, not the habits in the veteran's head. That distinction matters, because shadowing on its own transfers habits, not judgment. The new operator watches what the veteran does, not why. The checklist is what turns the veteran's sequence into something the new hire can repeat when the veteran isn't there.

So the routine is simple. The veteran does the job once while the new hire follows along on the checklist. Then the new hire does the job while the veteran watches. When reality differs from the checklist, fix the checklist. That gap between the written steps and the real job is knowledge that was living only in someone's head, and now it is written down where the next person can use it.

By the end of week two, the new hire should be able to run their job's transactions from the checklist, with the veteran nearby. They will still be slow. That is fine. Speed comes later. What matters is that the sequence is right and the record is right.

Week 3: Quality and Traceability

Week three is where most onboarding plans go quiet, and it is where they shouldn't. This is the week the new hire learns the rules that don't bend.

First, quality work happens on printed check sheets at the point of work. The check gets recorded when it happens, not from memory at the end of the shift. If the new hire needs a sign-off they can't verify, the product does not move. It gets quarantined and clearly labeled.

Second, the rule that covers everything else: never move suspect product just to make a truck on time. It is tempting, and it is always wrong. A shipment you can't trace is worse than a shipment that leaves late, because the late one is a scheduling problem and the untraceable one is a recall waiting to happen.

Third, lot and serial basics. Every container carries its lot and serial numbers, and those numbers go on the record as the work happens. Traceability cannot be recreated from memory at the end of a long shift. A missing lot number turns a labeled container into a guess, and a guess is not a record.

By the end of week three, the new hire knows the quality steps for their job, knows the quarantine rule, and knows when to stop and ask. That last one is a skill in itself. A new hire who stops and asks is not behind. They are doing it right.

Week 4: Supervised Independence and the Sign-Off

Week four is the test. The new hire works their job alone, with the trainer nearby but not hovering. The trainer checks the record, not the person. If the record is right, the work is right.

At the end of the week, the trainer signs off on a short list. Four lines, no more. The new hire can log in and navigate alone. The new hire can run their job's transactions from the checklist. The new hire knows when to stop and ask. The new hire knows the quarantine rule and follows it.

That is what ready looks like. And here is the part most plants get wrong: the new hire is ready when the trainer can walk away, not when 30 days have passed. If they are ready on day 21, sign them off on day 21. If they are not ready on day 30, keep going. The calendar does not make anyone competent. The sign-off does.

A Path, Not a Countdown

Thirty days is a path, not a countdown. The point was never the number. The point is that the new hire ramps on the system, not on one person's availability. The checklist at the point of work, the bulletin where the work happens, and one approved version in document control are what make that possible. The veteran's know-how becomes the starting point for the next operator instead of the bottleneck that holds them back.

I wrote about that handoff in The Operator Who Trains the Next Operator. The deeper point is the same here: the connection that lasts is the one written into the system.

Do one new hire this way and you will see the difference by week two. Do it for every new hire and the plant changes. The system stops being something people avoid, and the new hire stops being the person who quietly goes back to the spreadsheet.

If you want a companion for week one, my Day One course covers login and navigation in fourteen bite-size lessons. It is the course I wish every new hire watched before their first shift.

Popular posts from this blog

Ticket Triage for Plex ERP: How Small BA Teams Decide What Gets Fixed First

The Quarantine Corner: How an MRB Keeps bad parts from becoming bad shipments

Stop Typing Weights: What a Scale Connected to Plex Actually Changes