Our previous blog post outlined traditional definitions of L1, L2, and L3 and explained why they matter. You can find this, here. But what if you ignore them? If your MSP operates with blurry lines, you might think you’re “flexible” or “agile.” In reality… chaos, burnout, and ticket pile-ups are just around the corner.
1. L3s Aren’t Superheroes (Even Though They Pretend to Be)
This one is pretty obvious and very important to consider from a billable hours perspective. Pulling your senior engineer into password resets or chasing down a printer jam is like asking a brain surgeon to stitch a paper cut. It may get done, but it’s a waste of genius and morale. Meanwhile, the strategic projects that actually need their expertise, stall.
2. L1s and L2s Suddenly Feel Like Gladiators in the Technical Colosseum
This is huge from a retention perspective… Throwing your junior techs into complex network troubleshooting without proper support is a recipe for stress. Expect confusion, mistakes, and maybe a few tears falling in the break room.
3. Ticket Flow? More Like Ticket Jam
When everyone’s doing everything, nothing gets done efficiently. L1 tickets escalate incorrectly, L2s spend half their day firefighting, and L3s… well, see point #1. Again, this has a seriously negative impact on billable hours.
4. Career Growth Becomes a Mystery Box
Technicians need clarity to grow. If roles are unclear, everyone’s career path looks like a treasure map drawn by a toddler, full of detours, dead ends, and confusing symbols. Motivation dips, retention drops, and your talent starts hunting for greener pastures. The MSP world is already fraught with MSPs looking for highly skilled talent, the question is, who is training these people? Also, if people are doing work outside of the scope of their job descriptions, how will they be able to present themselves properly when searching for their next gig? This impacts the MSP too when they are searching for their next great team member.
5. Clients Notice, and Not in a Good Way
When tickets take longer, issues recur, and communication is inconsistent, clients pick up on it. They don’t care about your “flexibility.” They care that their IT doesn’t work.
The Moral of the Story:
Clear L1, L2, and L3 definitions aren’t bureaucracy—they’re sanity. MSPs that define their roles well:
-
Protect their L3s from drowning in low-level work
-
Give L1s and L2s clear boundaries and confidence
-
Keep tickets flowing efficiently
-
Make career paths obvious and motivating
-
Keep clients happy
So yes, you can ignore role definitions. You can let chaos reign. But don’t be surprised when your MSP starts looking less like a smooth-running machine and more like a sitcom where everyone’s stuck in the wrong role.