For a service desk below 10 people, the normal pooled arrangement has a team lead from the existing technician pool handle dispatch. Service desk succession planning should develop someone who can make agreed lead decisions while another person carries the technical work they set aside. Start with a supervised acting assignment and a named reviewer.
Keep that development assignment separate from a permanent promotion. The pooled arrangement assumes no additional dispatcher and no separate lead stipend. Check the actual role and workload before deciding what cover you can promise.
Choose a Lead Decision That Needs Cover
The service manager owns the coverage problem. Identify a lead decision that currently waits for the same person, then define the boundary another person needs to practice. Keep the first assignment small enough for the reviewer to observe its reasoning.
For a hypothetical acting assignment, choose the routine reallocation of work when an engineer becomes unavailable. The candidate must inspect the outstanding commitments and propose who can take them. The existing lead retains approval until the candidate has demonstrated the agreed scope.
Paul Green emphasizes communication and resource planning when considering whether a service desk manager must come from a technical background. I'd use that distinction when choosing the assignment. The next lead needs practice making the service decision, rather than another test of who can solve the hardest ticket.
Keep major incident authority separate from routine queue cover. Nick and Jeni Clift distinguish incident leadership, communication, technical remediation, and keeping ordinary work running. Their incident-role advice is a reason to check those arrangements explicitly before assuming an acting desk lead can take them all on.
Make the Development Opportunity Visible
Explain the acting work to the team before selecting someone for it. State the prerequisites and how interested staff can discuss taking part. Keep the selection tied to a responsibility the business needs covered, with a reason the reviewer can explain.
James Bier recommends showing technicians what a possible next role involves and which agreed benchmarks or qualifications support progression. He also recognizes that some people prefer their existing help-desk role. Ask about interest instead of treating every capable technician as an unannounced management candidate.
Mark Sowden describes service-desk management as developing a continuing pipeline of people, including those who want other technical roles. That's his development view. A succession plan should make room for an honest answer about direction, rather than turn technical progression into pressure to accept leadership.
Tell the candidate what has actually been agreed: 'This is a supervised opportunity to practice these decisions. The permanent role and pay decision remain separate.' Put the same explanation in the development record so the team doesn't have to interpret a temporary title.
Give the Acting Assignment a Reviewer and a Stop Route
The current lead owns the supervision plan. Agree which decisions the candidate may make, which require approval, and how to reach the reviewer. Make the boundaries visible to the people receiving instructions during the assignment.
| Stage | Candidate Responsibility | Reviewer Responsibility |
|---|---|---|
| Observe | Explain the service decision and identify the information it needs | Demonstrate the reasoning and check what the candidate understood |
| Recommend | Propose the next action within the agreed assignment | Approve or correct the proposal before it is carried out |
| Act Within Limits | Make the decisions expressly delegated for the assignment | Remain available through the agreed route and record interventions |
| Review | Explain the result and what required help | Accept the demonstrated scope or arrange specific further practice |
These are stages to agree, not a timetable or a guarantee of readiness. Progress when the work supports the decision. If a suitable case hasn't occurred, arrange an appropriate controlled exercise or another supervised opportunity instead of pretending the calendar supplied the evidence.
For the hypothetical reallocation, the candidate checks whether the receiving engineer can do the work and has room for it. A conflict with an existing commitment goes through the agreed stop route. Record the referral as part of the work rather than treating any request for help as failure.
Backfill the Technical Work Before the Assignment
The scheduler owns the candidate's remaining workload. Count the work that must move while the candidate practices lead decisions, and name who accepts it. Use actual ticket demand and handling time to check the proposed coverage rather than assuming enthusiasm supplies capacity.
Matt Tougas says his former MSP's combined level-two triage, dispatch, and service-delivery-management role became overloaded. That is his account of a combined role. I'd use it as a prompt to inspect the responsibilities you're combining here, not as proof that your desk needs the same structure or a new tool.
A spreadsheet is very brave about other people's calendars. Have the covering engineer accept the actual assignments and check the reviewer is available too. If you can't provide that cover, reduce the acting scope or move it to a time you can support.
Use my board test: what does this change on Monday morning? The board should identify who is exercising the agreed lead decisions and who is carrying the displaced technical work. Keep the current lead's supervision visible instead of counting their time as free capacity.
Record Decisions Rather Than a General Impression
The reviewer owns the readiness record. Capture the situation and the candidate's proposed action before writing a conclusion. Keep prompts or corrections visible so another reviewer can distinguish independent judgment from a result the supervisor supplied.
| Evidence to Keep | What the Reviewer Checks |
|---|---|
| Decision and relevant work | The candidate identified the commitments affected by the choice |
| Authority and approval route | The action stayed within the agreed limits or was referred appropriately |
| Reasoning and alternatives | The explanation accounts for capacity and the service promise |
| Help and intervention | The record identifies what the reviewer supplied |
| Observed result and next practice | The conclusion follows the work, with any remaining gap described |
Compare the record with the standard the candidate was given. Avoid a vague verdict that the person lacks leadership presence. Describe the decision that still needs practice and arrange work that can demonstrate it.
Peter Bell recounts a technician who struggled as a service delivery manager and later moved into leading sales. He uses that account to distinguish a wrong role from a wrong person. Keep the same distinction available if an acting assignment reveals a different preference or fit.
Explain the Coverage Plan and the Remaining Vacancy
The owner decides whether a permanent role exists and who can approve it. Record demonstrated cover separately from that decision. Someone may be ready to cover routine lead work while the business still has no vacancy or budget for a permanent appointment.
Erick Simpson describes planning how a departing employee's role will be covered alongside how the change will be explained to the team. He raises internal development and shared coverage among the options. Use that planning question before an absence or departure, while keeping the arrangement you actually approve clear to staff.
Have the service manager check whether the written operating methods still describe the desk. Mark Sowden recommends teaching company-specific standards and revisiting them through training. A candidate shouldn't have to guess which unwritten version the reviewer expects them to follow.
Assign the Next Practice and Its Owners
Skip leadership-pipeline optimization. Name the decision, the supervision, and the work that moves. Use this checklist to make the next acting assignment concrete.
- Owner: confirm the purpose of the development assignment and keep permanent promotion and pay approvals explicit.
- Service manager: agree the decision boundaries and explain the opportunity and selection to the team.
- Current lead: supervise the assignment, remain reachable, and record help or corrections.
- Scheduler: arrange the candidate’s technical backfill and the reviewer’s available time.
- Candidate: confirm interest, explain the next decision, and use the agreed stop route.
End the assignment with a written scope the person has demonstrated and a specific next practice where needed. Keep that record current as responsibilities change. The useful result is cover you can schedule and explain, with the limits still visible.
mspoutpost.com/articles/service-desk-succession-planning-develop-lead-cover
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.
