Every MSP has a version of the same onboarding story. A new tech shows up, gets a laptop and a PSA login, shadows someone for a week or two, and starts taking tickets. Some figure it out. Some quietly struggle for months. A few leave before anyone realizes the fit was wrong.
Amanda Doucette-Lachapelle has seen that story from every seat. She started at Auvik as an MSP Field and Community Engagement Manager and has spent nearly 20 years in the MSP world as an owner, ops leader, and community advocate. In her view, a new technician’s first 30 days “set the tone for whether they’ll thrive, coast, or crash,” and the difference usually comes down to whether anyone built a plan for them.
Good MSP technician onboarding means having a 30-day onboarding plan with clear milestones, a See, Show, Do training method, and honest fit checks. Together, they give both management and the employee a way to confirm readiness before clients feel the consequences. This same approach also works for internal IT teams hiring a new help desk tech.
Key takeaways:
- How you onboard technicians is how they’ll treat your clients. Sink-or-swim onboarding tests stress tolerance, but it doesn’t build the planning and accountability you want techs to bring to client work.
- See, Show, Do gives every core task a readiness check before it goes live. Start with ticket intake and documentation, new user onboarding, and escalation pathways – make sure new employees have that down and are solid.
- Fit checks run both ways in the first month. Finding a mismatch in week three is kinder and cheaper for everyone than finding it in month six.
This post draws on insights from Amanda Doucette-Lachapelle’s Frankly IT newsletter on LinkedIn, specifically issue #2, “Welcome aboard, new tech! Now swab the decks”
See Auvik in action on your network
Deploy Auvik and monitor as many sites and devices as you like in this 14-day free trial.
Throwing new techs into the fire tests their nerve, not their accountability
There’s a long-standing argument in the MSP world that the best way to find out whether someone will make it is to throw them into the fire. Amanda understands the logic, and she’s the first to say some people genuinely thrive in survival mode. Her problem is with what it teaches.
“If you don’t give them structure, they’ll default to survival mode,” she writes. Survival mode gets tickets closed, but it doesn’t build the accountability most owners are hoping for. A tech who learned the job by scrambling tends to keep scrambling: skipping documentation when things get busy, escalating late, and solving the problem in front of them without thinking about the next one.
As Amanda puts it: “We set the example of the behaviour we want by how we treat technicians. So, if you want them to plan, consider and set clients up for success, we have to do the same for them.”
Most organizations aren’t doing that yet. Gallup’s research on onboarding found that just 12% of employees strongly agree their employer onboards new people well, and only 29% of new hires come out of onboarding feeling fully prepared and supported in their new role. In an MSP, the gap between “hired” and “prepared” doesn’t stay internal. It shows up in client tickets.
Real technician onboarding has milestones and knowledge checks, not a week of shadowing
Amanda is specific about what doesn’t count as a plan: “shadow another tech for a week and figure it out.” Shadowing has its place, but on its own it passes along whatever the senior tech happens to do that week, shortcuts included, and it gives you no way to tell what the new hire actually absorbed.
A real new hire training plan gives a new tech a clear path with milestones and knowledge checks. They know what’s expected of them and when, and you can prove they’re taking in the information “before releasing them into the wild of taking care of your clients,” as Amanda puts it.
Most technical onboarding advice stops at tools and access: get the laptop imaged, grant the permissions, point them at the wiki. That matters, but it isn’t the hard part. Knowledge checks are. In a service desk, the most useful ones are practical rather than written: document this practice ticket to our standard, talk through why this issue needs to escalate and to whom, complete this checklist while a lead watches. If you can’t describe what “ready” looks like for a task, you can’t tell a new tech when they’ve reached it.
Job descriptions broken down by cadence show a new tech where they fit
The other half of the plan is a job description that actually breaks down roles and responsibilities by cadence: daily, weekly, monthly, and quarterly. Once a new hire can see that breakdown, Amanda writes, “suddenly the fog lifts.” They stop guessing, see where they fit into the company, and understand how their role contributes to its success.
Most job descriptions are written to hire someone, not to onboard them, which is part of why Gallup found only 41% of employees strongly agree their job description matches the work they actually end up doing. A cadence-based breakdown closes that gap, and it builds on the role clarity and ownership Amanda has written about for growing MSPs.
| Cadence | Example responsibilities for a Tier 1 technician |
| Daily | Work the assigned ticket queue. Document every ticket to standard. Escalate with steps tried and reasoning attached. |
| Weekly | Review aging tickets with a lead. Update any SOP or KB article touched that week. One-on-one check-in with the manager. |
| Monthly | Run scheduled user onboarding and offboarding checks. Review ticket quality with manager. Flag documentation that no longer matches reality. |
| Quarterly | Goal review with manager. Take on one new process through See, Show, Do. Contribute to a documentation review. |
A 30-day onboarding plan works best when each week has one job
Amanda doesn’t prescribe a week-by-week schedule, and every team’s will look different. Here’s one way her framework maps onto a new technician’s first month.
| Week | Focus | Milestone | Fit check |
| Week 1 | See: orientation, tool access, observe ticket intake, user onboarding, and escalations | Can explain your documentation standard and escalation criteria | Manager asks what’s been confusing so far |
| Week 2 | Show: practice tickets, onboarding checklist with a mentor, mock escalation | Practice tickets pass review | Peer touchpoint on communication style |
| Week 3 | Do, with review: live tickets with manager review, checklist completed solo with lead sign-off | Live tickets pass accuracy review | Is the new tech showing initiative, or waiting for direction? |
| Week 4 | Do, with accountability: first real escalation handled end to end, cadence review of the job description | Sign-off on all three core tasks | Two-way 30-day conversation on fit |
See, Show, Do lets both sides confirm readiness before clients are affected
Amanda’s alternative to the fire is a three-step method called See, Show, Do:
- See: The new tech observes a process being done correctly by an experienced team member.
- Show: They repeat the process while being observed, with feedback.
- Do: They handle the process independently, with accountability measures in place.
If that sounds familiar, it’s a close cousin of “see one, do one, teach one” from medical training. The step that matters most is the middle one. Show puts the new tech in the driver’s seat while someone experienced is still in the passenger seat, which is where most mistakes get caught cheaply.
The See Show Do approach is an internal methodology at Auvik and mirrors how we had been doing training, “I hear this approach in a meeting but it struck me that it works just as well for IT teams bringing on new technicians,” Amanda writes. She says that this approach “gives structure, sets expectations, and lets both sides confirm readiness before clients are impacted.” Amanda recommends three specific tasks every new tech should run through See, Show, Do in their first month:
1. Ticket intake and documentation is where good habits start or quietly don’t
- See: Watch a senior tech log and document an incoming ticket.
- Show: Walk through the same process with a “practice” ticket.
- Do: Own live tickets and get manager review for accuracy.
Ticket documentation is the first thing to slip when a new tech is under pressure, and it’s the thing every other process depends on. An undocumented fix can’t be reviewed, repeated, or escalated cleanly. Getting it right in week one is how you keep documentation your team actually trusts as the team grows.
2. A standard new user onboarding checklist teaches the process and the tooling at the same time
- See: Observe a user onboarding step by step, and get trained on tools like Auvik SaaS Management that make it easier.
- Show: Perform the process alongside a mentor.
- Do: Complete the checklist solo, signed off by a lead tech.
New user onboarding touches accounts, licenses, permissions, and devices, and a missed step tends to surface weeks later as a security gap or a frustrated end user. It’s also repeatable and checklist-driven, which makes it an ideal first “Do” task. For the full process, see Auvik’s guide to user lifecycle management.
3. Escalation pathways prove a new tech understands both the technical and the communication hand-off
- See: Listen in on how a tech escalates an issue, communicates, and documents reasoning.
- Show: Run through a mock escalation with guidance.
- Do: Escalate a real client issue properly, proving they understand both the technical and communication hand-off.
New techs tend to miss on escalation in one of two directions — escalating everything, or escalating nothing until a client is angry. Usually that isn’t a skill gap. Nobody showed them what a good hand-off looks like: the steps already tried, the reasoning behind them, and what the client has been told.
| Task | See | Show | Do |
| Ticket intake and documentation | Watch a senior tech log and document an incoming ticket | Walk through the same process with a practice ticket | Own live tickets, with manager review for accuracy |
| New user onboarding checklist | Observe a user onboarding step by step; learn the tooling | Perform the process alongside a mentor | Complete the checklist solo, signed off by a lead tech |
| Escalation pathways | Listen in on an escalation, the communication, and the documented reasoning | Run a mock escalation with guidance | Escalate a real client issue, covering the technical and communication hand-off |
Book an Auvik demo
See how Auvik simplifies network management in a live, guided demo.
Fit checks in the first month protect your culture and your new hire
“There’s also one part I feel like we don’t talk about enough: fit checks,” Amanda writes. Onboarding isn’t only about teaching someone how to do the job. It’s also about finding out whether they fit the job, and whether they can become a true member of your team.
She recommends building touchpoints with the rest of the team into the first month and asking questions like:
- Are they showing curiosity, growth, and initiative, or are they stuck waiting for direction?
- Does the way they communicate mesh with how the rest of the team operates? Will it mesh with how your clients want to be communicated with?
- Do they align with the core values and energy of your business?
Fit checks go both ways. Your new hire is evaluating you just as much as you’re evaluating them. Amanda’s advice is to give them space to share frustrations early, because small irritations left alone have a way of becoming deal-breakers, and the ones nobody voices tend to show up later as technician burnout or a resignation.
The goal isn’t to catch someone out. “There’s nothing worse than realizing six months in that the fit isn’t right,” Amanda writes. “It doesn’t make them bad or you bad.” It just means one side isn’t what the other is looking for, and the sooner everyone knows that, the better. Protecting your culture, in her words, “doesn’t happen by accident.” It has to be planned for.
| Pro Tip: Ask your new tech better questions at the 30-day mark“How’s it going?” gets you “fine.” Specific questions get you something you can act on:What’s one thing you were expected to know that nobody showed you?Where did the documentation not match what you saw someone actually do?Who has been most helpful, and who have you hesitated to ask?What’s frustrating you that you haven’t said out loud yet?The second question is worth extra attention. New techs are often the first to notice the gap between documented and lived processes, because they haven’t learned to work around it yet. Keep the manager in this conversation: Gallup found that employees whose managers are actively involved in onboarding are 3.4 times as likely to rate the experience as exceptional. |
Auvik gives new technicians the context senior techs carry in their heads
Every See, Show, Do plan runs into the same constraint. The See step depends on a senior tech’s time, and much of what a new tech needs to learn about a client lives in that senior tech’s head (how the network is laid out, which firewall is the problem child, what changed last month). That’s the bus factor of one problem, and onboarding is where it hurts most.
Auvik Network Management automatically discovers and maps client networks and keeps that documentation current as things change. For a new tech, the See step has something accurate to look at, and an escalation hand-off can reference real topology, device relationships, and configuration history instead of someone’s memory. It’s one of the reasons MSPs use automated MSP documentation to cut ramp-up time for new technicians.
Auvik AI is newer, so it’s worth being specific about what it does for a junior tech. Instead of generic answers pulled from the public internet, it grounds troubleshooting and alerting guidance in your actual network data — topology, device relationships, performance metrics, and alert history. It surfaces likely root causes as hypotheses, not verdicts, and every recommended action needs a human to review and approve it before it runs, with an audit trail of what was recommended and who signed off.
That structure lines up closely with See, Show, Do. A new tech can see the reasoning behind a recommendation, a lead still approves the action, and there’s a record the two of them can review afterward. The mentor is still doing the teaching. Auvik AI gives them something grounded in the real network to teach from.
See how Auvik can give your next new tech a better first 30 days
Before your next hire starts, pick the three tasks above and write down what See, Show, and Do look like for each in your environment. Then decide who owns the fit check conversations. If any step depends on “ask Jane, she knows that client,” that’s the gap to close first. Whether you’re an MSP bringing on your fifth tech or an internal IT team hiring your first dedicated help desk analyst, book a demo to see how Auvik Network Management and Auvik AI give new technicians accurate context from day one.
FAQs about MSP technician onboarding
Is 30 days long enough to onboard a new MSP technician?
Thirty days is long enough to confirm a new tech is ready for client work on core tasks and that the fit is right on both sides. However, it isn’t long enough for mastery. Gallup’s research suggests it typically takes new employees about a year to reach their full performance potential in a role, so treat the 30-day plan as the first milestone, not the finish line.
Should we use a 30-60-90 day onboarding plan instead?
A 30-60-90 day plan extends the same idea across three months, usually moving from learning to contributing to owning. The two work well together. Use the first 30 days for See, Show, Do on core tasks and fit checks, then use days 31 to 90 for more complex work like specific client environments, project tasks, and after-hours coverage.
What if the senior tech handling the “See” step doesn’t follow our documented process?
Then the new tech will learn the undocumented version. Before onboarding starts, have whoever runs See walk through the SOP with a lead and confirm it still matches reality. Onboarding is also one of the best moments to catch process drift, because a new tech will notice the gap if you ask them to.
How do we run See, Show, Do when we can’t pull senior techs off the queue?
Keep See and Show short and scheduled rather than ad hoc. Practice tickets and mock escalations can be built once and reused for every hire. An hour of senior time in week one usually costs less than the rework, client complaints, or failed hire that skipping it can lead to.
What does a knowledge check look like for a help desk technician?
Practical, not theoretical. Ask the new tech to document a practice ticket to your standard, explain why a specific issue should escalate and to whom, or complete a user onboarding checklist while a lead watches. If they can do the task and explain why each step exists, they’ve passed.
What access should a new technician have in the first week?
Enough to observe and practice, not enough to break something. Many teams give read-only or sandbox access during See and Show, then expand permissions as each task reaches Do with a lead’s sign-off. It keeps client environments safe and gives the new tech a visible sense of progress.
What should we do if a fit check shows it isn’t working?
Say so early and directly. As Amanda puts it, a poor fit “doesn’t make them bad or you bad.” Have a candid conversation, share what you’ve observed, and decide together whether there’s a realistic path forward. Resolving it at 30 days is kinder, and cheaper, than resolving it at six months.
How do we get honest feedback from a new hire who’s worried about looking bad?
Ask specific questions instead of “how’s it going?” For example: what were you expected to know that nobody showed you? Make it clear that frustrations are useful information, and act visibly on at least one piece of feedback so they know it was heard.
Does this onboarding approach work for internal IT teams, or only MSPs?
Both. Amanda notes See, Show, Do works just as well for IT teams bringing on new technicians. The three core tasks translate directly: internal help desks still handle ticket intake, new user onboarding, and escalations, with employees in place of clients.