A New Hire Struggles in Week Two: Decision Tree
Why this matters
Week one is expected to be rough, everyone is nervous and new. Week two struggling is different, because the shock of "first day" has worn off and you are starting to see who this person actually is under normal conditions. Misread week two and you either panic and write off someone who just needs a specific fix, or you shrug it off as "still settling in" and watch a real problem harden into a habit by day 90. This tree sorts what week-two struggle usually means, because the four common causes need four different responses, and treating all of them the same wastes the cheapest window you have to correct course.
Start here: rule out anything outside the job itself
Before you diagnose a skill or fit problem, check for something situational that has nothing to do with their potential as a tech. A new hire dealing with a personal emergency, an unexpected home situation, or an onboarding process that itself skipped steps can look identical to a struggling hire from the outside.
- Ask directly, privately: "Is everything okay outside of work?" Most people will tell you if something is going on, if asked with genuine concern rather than suspicion.
- Check your own process. Did they actually get a proper day one, a real orientation, a mentor who showed up? A new hire struggling because onboarding itself was rushed is not a hiring problem, it is a process problem you can fix immediately. See related: New Hire Shows Up Day One, What Happens First: Decision Tree.
If either of these is the real cause, address that directly before assuming anything about the hire's fit or ability.
Step 1: Sort the struggle into a type
Once situational causes are ruled out, watch closely for a day or two and place what you are seeing into one of these buckets.
| What you observe | Likely cause | Where the fix lives |
|---|---|---|
| Slow, careful, makes few mistakes but takes twice as long | Learning curve, no red flag | Time and reps, not intervention |
| Confident but making the same mistake repeatedly | A specific skill or knowledge gap | Direct, named coaching on that one thing |
| Anxious, second-guessing everything, asking excessive questions | Confidence gap, possibly a mismatch with training pace | Slow down, more explicit reassurance |
| Sloppy, cutting corners, or dismissive of correction | Attitude or fit issue | A direct conversation now, not more training |
Step 2: If it's a normal learning curve, protect them from premature judgment
A new hire who is slow but careful and improving day over day is doing exactly what week two should look like. The risk here is not the new hire, it is an impatient supervisor or crew member deciding too early that someone is "not cutting it" because they are not yet fast.
- Compare day 10 to day 3, not day 10 to a tenured tech. The right comparison is their own trajectory, not the crew average.
- Shield them from crew impatience if you see it starting. A senior tech muttering about a slow new hire in week two can do real damage to confidence over something that is completely normal.
Step 3: If it's a specific, repeated mistake, name it directly and check for it
A confident new hire who keeps missing the same specific thing is not confused in general, they have one identifiable gap. This is the easiest bucket to fix and the easiest to miss, because the new hire's overall confidence can make you assume they have already got it.
- Say exactly what you see: "You're doing well overall, but you've skipped this specific step three times now." Vague feedback like "pay more attention" does not target the actual gap.
- Watch specifically for that one behavior on the next few jobs. A named, specific gap usually resolves within days once it has actually been said out loud, because confident new hires often did not realize they were repeating it.
Step 4: If it's anxiety and second-guessing, slow down and add explicit reassurance
Some new hires are technically capable but are visibly rattled, asking about things they were already shown, hesitating on tasks they can do. This is a confidence gap, not a competence gap, and pushing more information at them faster makes it worse, not better.
- Explicitly reassure them that questions are welcome and that hesitation is normal at this stage. Some new hires read silence from a supervisor as disapproval and spiral from there.
- Slow the pace of new material rather than pushing forward on schedule. A new hire drowning in week two who gets a week three's worth of new tasks anyway will drown further.
- Check whether the training pace itself is mismatched to how this person learns. Not everyone absorbs information at the same rate, and a standard pace that works for most new hires can genuinely be too fast for this one without it reflecting on their eventual capability.
Step 5: If it's sloppiness or a dismissive reaction to correction, have the direct conversation now
This is the bucket that needs the fastest response, because it is not a training problem, it is a fit or attitude signal, and it rarely improves on its own with more time.
- Have a direct, private conversation immediately: name specifically what you have observed, cutting a corner, brushing off a correction, and ask them to explain their side.
- Watch their reaction to the conversation itself. A new hire who is surprised, takes it seriously, and adjusts has just had a rough week two and a needed wake-up call. A new hire who is defensive, dismissive, or unbothered is showing you something important about fit this early, and it is worth taking seriously rather than hoping week three looks different on its own. See related: The New Hire Seems Like a Bad Fit: Decision Tree.
Step 6: Whatever the bucket, document it and set a specific follow-up
Regardless of which cause you land on, write down what you observed, what you did about it, and when you will check again. Week two struggles that get a private mental note but no written follow-up are the ones that quietly become week eight patterns nobody can quite trace back to when they started.
Quick recap
- Rule out something situational or a skipped step in your own onboarding process first.
- Sort the struggle: normal learning curve, a specific repeated mistake, anxiety, or sloppiness and dismissiveness.
- Learning curve: protect them from premature judgment, compare to their own trajectory.
- Repeated mistake: name it specifically, watch for it directly.
- Anxiety: slow down, add explicit reassurance, check the training pace itself.
- Sloppiness or dismissiveness: have the direct conversation now, watch how they respond to it.
- Document whatever you find and set a specific date to check again.
References
- Society for Human Resource Management (SHRM), early-tenure performance coaching guidance
- Trade-standard practice for new-hire progress evaluation
- See related: New Hire Shows Up Day One, What Happens First: Decision Tree, The New Hire Seems Like a Bad Fit: Decision Tree