The model uses 70% of available service staff hours for productive delivery. That is a capacity assumption, not a help desk burnout cutoff. Check five visible work patterns against what the technician tells you, then change the load or role that needs attention. Give each change an owner.
My test is what the change does to the board on Monday morning. If the same work still reaches the same person through the same interruptions, the manager has more to do. An invitation to a wellbeing session does not settle the staffing question.
Read the Work Without Diagnosing the Person
Use the observations below to start a private conversation about work, rather than putting a health label in the PSA.
Examine the conditions you control and agree what should change.
Compare a technician’s work with their own previous pattern and the tasks assigned. Reopened tickets might expose an unclear fix, a training gap or a change in ticket difficulty. A quiet person may simply prefer to work quietly. Ask before deciding what the pattern means.
Check Five Patterns and Assign the Response
These are proposed operational checks, not a diagnostic scale. Look for a change worth discussing and retain enough context to test your explanation. The same observation can need a different response for different technicians.
| Visible Pattern | What to Check Privately | Who Changes the Work |
|---|---|---|
| Work Repeatedly Runs Beyond the Planned Shift | Compare recorded work and the actual roster. Ask whether unresolved tickets or after-hours calls are extending the day, and check for unrecorded work without accusing the technician. | The service manager reviews coverage. The dispatcher reassigns suitable work and revises commitments; the on-call owner corrects the rotation and handoff. |
| The Queue Keeps Pulling Work Back to One Person | Check whether the technician owns difficult cases while also receiving routine interruptions or unofficial requests. Ask which decisions only they can make and why. | The technical lead transfers knowledge and authority where appropriate. The dispatcher routes new work through the agreed queue and protects necessary focus time. |
| Rework or Incomplete Handoffs Increase | Read the affected tickets with the technician. Check whether instructions were clear and whether workload, unfamiliar work or a broken process contributed. | The technical lead provides review or training. The service manager adjusts competing assignments while the cause is addressed. |
| Communication Changes Noticeably | Describe a specific interaction or withdrawal from agreed collaboration. Ask what has changed without assuming the answer concerns work or demanding personal details. | The line manager listens privately and agrees work support. If a client interaction needs repair, the service manager owns that response. |
| The Actual Role Has Expanded Beyond the Agreed Job | Compare assigned responsibilities with the role description. Ask about unofficial lead work or repeated extra coverage and whether the technician considers the arrangement sustainable. | The owner and people lead review responsibilities and pay. The service manager removes or redistributes duties that have not been properly assigned. |
Do not turn the table into surveillance. You need work evidence and a conversation, not a record of every facial expression. Keep sensitive personal information out of shared ticket notes and restrict any necessary people records to those responsible for handling them.
For a proposed opener, say: “I noticed these tickets continued after your planned shift. What kept the work with you, and what should I change?” Listen for what the technician actually identifies. Do not make them prove that they deserve help before reviewing an overloaded assignment.
Make the Capacity Plan Match the Work
The model starts with 1,660 available hours per FTE each year. Calculate annual productive hours by applying its 70% service utilization assumption, then divide by 12 for monthly capacity. The model gives 96.83 productive hours a month. That is planning capacity after the model’s availability deductions. It does not mean you should fill every remaining gap with tickets.
Check the work already included in your calculation before adding more. A technician handling an escalation remains occupied even when the ticket belongs to someone else. Unrecorded assistance can make their visible allocation look lighter than their actual work.
Assign the service manager to reconcile demand with capacity. If work exceeds what the team can deliver, the owner must choose how to address that gap. A temporary reassignment needs coverage, and a recruitment plan needs an interim answer for the work arriving now.
Keep client commitments visible while adjusting the queue. The account owner handles any required conversation about changed expectations. Do not leave the technician to explain a managerial scheduling decision to each waiting client.
Fix the Rotation and the Role Separately
If after-hours duty is the issue, review the calls actually taken and the next working period alongside the roster. Name who receives an unresolved incident at handoff. Let the manager handle coverage changes rather than relying on the same technician to find their own replacement.
Pizza does not answer the on-call phone. Record what duty will move and who will take it, with the technician involved in the discussion. Check that the receiving person has the capability and authority required for the work.
If the role has grown, review its responsibilities and compensation together. The model’s position is to run healthy margins so you can pay good people well. A pay review can address a mismatch in the job; it cannot establish that the present workload is sustainable.
I have no patience for “resilience optimization” in a staffing plan. Name the work the manager will remove or the support they will provide. Make the promised change specific enough for the technician to tell whether it happened.
Use an Owned Follow-Up Checklist
Finish the conversation with actions the manager can verify. Agree the follow-up date with the technician rather than claiming a standard recovery period. Use this checklist to keep the work moving.
- The line manager records the work concern in the technician’s own terms and confirms which action they have agreed.
- The service manager changes the relevant assignment or roster and checks that essential client coverage remains owned.
- The technical lead completes any agreed support or knowledge transfer and checks whether the technician can use it in the actual workflow.
- The owner or people lead completes an agreed role or pay review and communicates the decision directly.
- The line manager reviews whether the promised changes happened and asks the technician whether those changes helped. If they did not, the manager revisits the work design.
Keep the outcome narrower than a claim that burnout has been solved. Fewer late tickets may show that work moved; they do not prove how the person feels. Check both the operational result and the technician’s account before deciding what to do next.
mspoutpost.com/articles/help-desk-burnout-five-work-patterns-managers-can-check
Written by Megan Friesen
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.